You can see problems like this if you access VuFind on a URL that is inconsistent with the base URL provided in web/conf/config.ini. If the current browser base URL doesn't match the AJAX URL generated by VuFind, it looks like a cross-site scripting attack and browsers will block it. Your description of users looking at a record and going back to solve the problem may work because clicking an internal, VuFind-generated URL makes things consistent again. You can find this problem if you have multiple ports/hostnames pointing at the same VuFind instance, or if you have HTTP and HTTPS access to the same site. In most cases, you can solve the problem by standardizing all access to VuFind on a single URL. Also, once VuFind 2.0 comes along, it will be a bit more tolerant of this type of situation (more use of relative rather than absolute paths), though it's still a good idea to have just one address for the system if you can get away with it - it makes troubleshooting that much simpler if you don't have to worry about different access points to the same code behaving differently.
From: Byron Smith [mailto:byron@...]
Sent: Monday, July 16, 2012 10:53 PM
To: 'VuFind List'
Subject: [VuFind-General] Item information hanging on search results list only
One of our clients is experiencing a problem on specific browsers (Firefox and Google Chrome) where the item information in a search result list is hanging with "loading" and the spinning icon. As soon as a user clicks into a title and then goes back to the search result list the holding information displays as normal. The problem comes back as soon as they close the browser down and open it back up again and do another search.
They do not experience the same issue with Internet Explorer 8 except for a security warning which displays (attached screenshot) and once the user clicks 'yes' the item information loads. Although they are able to replicate the problem in both FireFox and Google Chrome) It loads for me ok in these same browsers without any issue.
My suspicion is that it has something to do with the security around XMLHttpRequest and each browser and version handling it somewhat differently. Has anyone ever experienced anything like the issues described above? Is there any configuration in VuFind that may cause this issue?