Document library not loading for specific users on specific browsers

[sscbrian]

This is a bizarre one.  All of a sudden over the weekend we have users that can't open Document Libraries.  The main group of users is Mac users with Chrome.  We also have one person on 32-bit Chrome on PC with the same issue.  All of the above are able to view document libraries fine with Firefox.

The rest of us have no issue with Chrome (on PC) either 32-bit or 64-bit.  The people with the issue can walk over to someone else's computer, use that "working" user's Desktop, but login to Alfresco as themselves (the "problem" person) and the document libraries will not load.  They log out, the other user logs in, and it works fine…

No errors in the Alfresco log file that match up with it.  I had one that was close, but turned out to be something else.

Any ideas?  For now having them use Firefox is a tolerable workaround, but obviously something odd is happening and I fear that Firefox may also suddenly quit working for them.

[macbazzo]

I have the same problem, but only firefox mozilla works. IE and Chrome does not work with 32-bit and 64-bit. Do you have any suggestions to solve this problem?

[macbazzo]

I have the same problem, but only firefox mozilla works. IE and Chrome does not work with 32-bit and 64-bit. Do you have any suggestions to solve this problem?

[mfmgiafa]

The same thing happens to me too.
Does anyone have the answer to how to fix this problem?

[sscbrian]

Well, for Internet Explorer the workaround is known.  For us, Google Chrome was working fine until over the weekend, and it works for some people but not others (and we're all on the same version of Chrome).  The Internet Explorer workaround from another post:

Alfresco 5.0a has a bug in the document library renderer that's supposed to be
fixed in 5.0b and later.  Append this (and then restart tomcat) to
alfresco-5.0.a/tomcat/webapps/share/WEB-
INF/classes/alfresco/templates/org/alfresco/include/alfresco-template.ftl:

<script>if (!document.baseURI){ HTMLElement.prototype.baseURI = document.URL; }</script>‍‍‍‍‍‍

Oh, and I'm currently building our 5.0.a to 5.0.d upgrade process and it appears that, for IE at least, this bug is totally fixed in 5.0.d…  Have not tested Safari yet (which there's no known workaround for 5.0.a) or Chrome.

[mfmgiafa]

Thanks for the information. We will try to upgrade to version 5.0.d.
Regards

[sscbrian]

I've verified that Chrome works in 5.0.d as well.