Tweet
While it's been great seeing the response I got to some issues after we upgraded from 6.14 to 6.16, there are still some lingering issues I wanted to note. You folks feel free to tell me if I am full of crap, but here's what I am seeing:
1. Name changes in new mysql db: The "System Users" folder, which is a Public contacts folder which contains all the system users, has been renamed to "system-ldap". WTF?
2. The icon set in the upper left corner works fine, except that the E-Mail icon instantly brings up a "Unable to establish connection to email server" message and says the module has been disabled. It hasn't. Only recourse is to use the folder list below it to get into the INBOX.
3. I have had to tell all my users to MANUALLY delete their cache, AND their cookies. Leaving the old cookies results in the wrong SessionID in the XMLHttpRequests, which of course results in failure. Some users simply don't have a clue how to clean out those cookies and cache files. I strongly suggest that we add a cookie cleaner in the login screen (after a good login) before setting the new one.
These are made all the more difficult to troubleshoot by the fact that I can't really see the html that the browser is rendering, especially around that E-Mail icon. View Source is useless, and even Firebug isn't helping. (Browser is not sending an XMLHttpRequest when I click the icon, so I can't track that). I have spent hours and hours on this issue. I do this as a volunteer for my local church; it isn't my day job, so finding these hours to make this work for the church staff isn't easy!
1. Name changes in new mysql db: The "System Users" folder, which is a Public contacts folder which contains all the system users, has been renamed to "system-ldap". WTF?
2. The icon set in the upper left corner works fine, except that the E-Mail icon instantly brings up a "Unable to establish connection to email server" message and says the module has been disabled. It hasn't. Only recourse is to use the folder list below it to get into the INBOX.
3. I have had to tell all my users to MANUALLY delete their cache, AND their cookies. Leaving the old cookies results in the wrong SessionID in the XMLHttpRequests, which of course results in failure. Some users simply don't have a clue how to clean out those cookies and cache files. I strongly suggest that we add a cookie cleaner in the login screen (after a good login) before setting the new one.
These are made all the more difficult to troubleshoot by the fact that I can't really see the html that the browser is rendering, especially around that E-Mail icon. View Source is useless, and even Firebug isn't helping. (Browser is not sending an XMLHttpRequest when I click the icon, so I can't track that). I have spent hours and hours on this issue. I do this as a volunteer for my local church; it isn't my day job, so finding these hours to make this work for the church staff isn't easy!
). I'd be surprised though, if deleting cookies solved a real problem and not merely worked aroud a side-effect of the other issues.
Comment