As nobody answered (perhaps I'm not in the right forum ?), I used Firebug and tried to understand what's wrong with Zimbra.
Here is the faulty JS code :
Code:
ZmNotebook.prototype.getSearchPath = function() {
var serverName = "Notebook";
var clientName = ZmMsg.notebookPersonalName;
var path = ZmOrganizer.prototype.getSearchPath.call(this);
if (path.match(new RegExp("^"+clientName+"(/)?"))) {
path = serverName + path.substring(clientName.length);
}
return path;
}; In my case the value of the property "notebookPersonalName" is (in French) "Carnet" and the path is initialized to "Carnet de user1". So regarding to the previous code the regexp match and path is changed to "Notebook 2".
I don't really understand why this RegExp is for (and I didn't try to understand), also I don't understand why there is a hard coded string (in bold)!!!
A workaround of this issue is to modify the value of the key "notebookPersonalName" in the file "/opt/zimbra/jetty-6.1.22.z6/webapps/zimbra/WEB-INF/classes/messages/ZmMsg_fr.properties" (according to the user's language, you have to modify the file ZmMsg_<XXX>.properties where <XXX> is the abrevation of a language) Et voilą !
Also I tried to find where ZmMsg.notebookPersonalName is used in the source code and I've only found one instance in the previous JS method. So it seems that there's no risk to apply the mentionned workaround.
Can a Zimbra team member:
1- may explain me what does this property for ?
2- tell me how to report this issue (or report it himself) ?
Eric