(MLZ) Cant save items from amazon although the book item appear in the web browser error# 22900793

All of the sudden when I try to save an item from a page by clicking on the book item, the screen on the bottom right side of the screen is blank and it doesnt save the item. Error number 22900793
  • please always provide a (sample) URL with translator errors.
  • I should clarify that the page is amazon.com, all of the others work.
  • the sample URL is http://www.amazon.com/International-Law-Force-Foundations-Public/dp/0199239150/ref=sr_1_1?ie=UTF8&qid=1321729903&sr=8-1
  • The Amazon API seems slow right now, but that page works fine for me.

    You're using an old trunk SVN checkout. We don't use SVN anymore. Switch to a Git checkout or an XPI.
  • Iam kinda of new to this, how exactly do I do this? thanks
  • If you're kind of new to this you should just install a regular Zotero version, either the stable 2.1.10 version or the most recent beta (3.0b2)
    links to both are here:
    http://www.zotero.org/download/
  • Out of curiosity, why were you using an SVN checkout in the first place?
  • Iam guessing because I installed the MLZ client, since i am a lawyer and need to incorporate treaties and abreviations. I am installing Git right now. I dont mind learning new things but I would apreciate some guidance since like I said before I am new to this. As probably everyone else was at some point as well. Anyways I d apreciate ant tips on installing git since i dont really know what iam doing
  • Sorry, we absolutely can't provide support for this (and the MLZ client doesn't have anything to do with SVN or Git anyway). If you're an end user, you should be using an XPI.
  • Damn, and I just finshed setting up git, how do I use an XPI
  • you may already have done that - by just installing from:
    http://gsl-nagoya-u.net/http/pub/zotero-multi-2.xpi

    You can still report errors like this here on the forum and usually fbennett will come by and reply, but you should clearly mark them with [MLZ] or [multilingual] in the title so that Frank Bennett will see them and Zotero "plain" devs won't bother.

    (you can edit the title of this post by editing the your first message.
  • ok thankyou, the problem has been solved, I also installed XPI, and I am unsure if I should unistall GIT since I have no idea what it is. Any suggestions? Also Ill change the title now, thank you for you help
  • For some reason again its not saving the items from amazon. Only from amazon any amazon book. Could there be something wrong in my prefences or setup
  • yeah, uninstall git - git is a software that helps people collaborate on software development - you won't need it.

    As for your amazon error - there's two possibilities - one is that the there is a problem with the Amazon translator of the MLZ version - Amazon has recently changed its API requirement and Zotero adjusted the translator - not sure if that made it into MLZ.
    The other possibility is that you're just experiencing intermittent problems because the API is sluggish as Dan suggests above. Let's see what Frank says.
  • Great timing -- I've been working on this very problem this weekend.

    Translator updates have been broken in MLZ for quite some time. What may be happening is that clients installed some time ago have not been receiving updates, and so are running with stale translator code. That will be the first thing (for me) to check, anyway.

    The new legal and multilingual styles will have some specific requirements for field assignments and data markup in Zotero. To move ahead with MLZ translator and style development without messing things up in official clients, I'm setting up a separate MLZ translator update channel, which should be running within the next few hours. Once that's in place, I'll take a look at the Amazon issue.

    More soon ...
  • The update channel seems to be in order now. Try updating the MLZ client, visiting the gear menu -> Preferences -> General, and clicking the button to update translators. Then try the Amazon reference again and see if we have better luck. The reference worked fine for me here, so it might well have been a stale translator issue.

    Fingers crossed. :)

This is an old discussion that has not been active in a long time. Before commenting here, you should strongly consider starting a new discussion instead. If you think the content of this discussion is still relevant, you can link to it from your new discussion.

Sign In or Register to comment.