Zotero Browser trouble

rboulding
I have been having trouble using zotero after it has crashed. It seems that once it has crashed when i am editing citations online i am unable to use zotero on that browser again due to the page not loading. I have currently gone through safari, firefox and chrome and all 3 have the same problem that once a page crashes and i cannot safely log out that i am unable to use that browser again.

Any help would be greatly appreciated
  • mronkko
    So you edit the items on the Zotero website, note the Zotero plugin? What do you mean by saying that a page crashes? What page exactly does not load?

    If you provide a bit more detailed description of your problem, it is easier to provide help.
  • rboulding
    Apologies for the lack of information. I use the zotero website on my iMac and originally on safari web browser. Occasionally after editing one of the fields (usually rights as it is empty) i can note which citations i will be using. When saving this occasionally the web page will become unresponsive.
    After this i can revisit zotero.org but only view a limited number of pages of my library. Getting to a certain number e.g. 300 and the next 25 will not load. On Firefox i get the script problem which i have tried to continue using the script but to no avail so far.
    I have since had this happen on multiple browsers. From reading the forums it looks likely to be with zotero syncing the library but i am not sure.
    On safari i get a blank page which is continually loading, chrome gives me a non responsive web page pop up and safari a script problem.

    Many thanks
  • dstillman
    On Firefox i get the script problem which i have tried to continue using the script but to no avail so far.
    What script problem? Provide the exact error message.
  • rboulding
    A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will complete.

    Script: https://www.zotero.org/static/library/jquery/history/history.js:614
  • fcheslack
    What is displayed in the url bar when you get that? That used to happen on older browsers in certain instances but I haven't seen it happen across browsers before.
  • beckersu
    I have the same trouble and get the same message. Never had this probleme until yesterday, since yesterday evening I get the message everytime I try to use any function online (in both, firefox and internet explorer)
    Does anyone have an idea?

    Thanx a lot!
  • dstillman
    beckersu: Answer fcheslack's question, and confirm that it's the exact same error message, with the same file and line number.
  • beckersu
    Thank you for the fast response!

    I get the following message:

    Ein Skript auf dieser Seite ist eventuell beschäftigt oder es antwortet nicht mehr. Sie können das Skript jetzt stoppen oder fortsetzen, um zu sehen, ob das Skript fertig wird.

    Skript: https://www.zotero.org/static/library/jquery/history/history.js:614

    (Translation: A script on this page may be busy or does not respond. You can stop this script now or let it run to see, if the script will finish.)

    The path of that script is the same a with reboulding.

    I get the message, whenever I click in a group library to deisplay or modify the entry. So it is not exactly the same field as with reboulding.

    Thanx again!
  • adamsmith
    What is displayed in the url bar when you get that? (one example is enough)
  • beckersu
    One example:

    https://www.zotero.org/groups/61303/items/collectionKey/AIAHKEDG
  • fcheslack
    You get the error after clicking an item to view the details?
    What browser and OS versions?
  • fcheslack
    I believe this should be fixed now (may require an uncached refresh).
  • beckersu
    Yes, it seems to be fixed, did not get the message again. Thank you very much for the fast reaction!

    Regards from Germany

    Susanne
  • fcheslack
    If you check this thread again I'd still like to know what versions of those browsers were affected. The bug that was fixed should only have happened after lengthy sessions browsing z.org (restored sessions would also be affected) but it is very strange for it to happen in separate browsers simultaneously.
Sign In or Register to comment.