Problems with translator: Retsinformation

Hello all

Up until recently the translator for retsinformation.dk worked fine, but now it stopped working. I have not been able to resolve the issue by myself, so here are the information needed as per the translator troubleshooting guide:

The exact URL of a page that isn't working (even if none are): https://www.retsinformation.dk/eli/lta/2023/1086

The Debug ID is:
D981156497

The error message says:
Der opstod en fejl, da der blev gemt med Retsinformation. Prøver at gemme med Save as Webpage i stedet for.

Translated means:
An error occurred while saving with Retsinformation. Trying to save with Embedded Metadata instead.

I hope that I provided all sufficient information, if not let me know.
Thanks as always for being a helpful community.

//Skjolde
  • BUMP (hope this is okay after 2 months has passed).
  • (I think I have a fix for this)
  • @Skjolde4 -- this should now work again, thanks for the ping (yes, definitely OK to bump after >2 weeks.)
  • @adamsmith -- I completely missed the notification that you responded to this Thread.
    I have been occupied by other project for last 6 months, but now that Zotero has my attention again, I must regrettably report, that I experience the exact same errors as before the changes you made.

    So the issue is still not resolved.
    Let me know if you need additional information from me.

    //Skjolde
  • The above linked page works for me on Firefox -- I think there are some connector issues currently, what exactly version and browser are you on?
  • edited June 6, 2024
    @adamsmith You are correct! I don't know why, but I never thought of trying a different browser, from the one where it usually works.

    I am using Zotero version 6.0.37 and using the connector in Chrome.
  • To that end, should I make a new thread clarifying the issue seems to lie with the connector Chrome and not the Translator as this thread suggest?
  • A debug ID for a failed save posted here might be helpful, though
  • edited June 6, 2024
    It's OK — we're working on a fix. It's another MV3-related regression, which only affects Chrome.
Sign In or Register to comment.