OpenOffice.org (OOo) integration - ZoteroNotMac.oxt

boky
Hi all.

I am trying to start the ZoteroNotMac.oxt extension on OpenOffice 2.2.1 (32-bit version, running on 64-bit Gentoo Linux on AMD64).

Installing and enabling extension works flawlessly until "ZoteroRPC.py" is being enabled.

This dies with:
(com.sun.star.uno.RuntimeException) { { Message = "URP-Bridge: disposed(tid=17) No typedescription can be retrieved for type com.sun.star.bridge.XProtocolProperties", Context = (com.sun.star.uno.XInterface) @0 } }

I am drawing a complete blank here. I have no idea how to debug this message or get any other feedback from OOO. I've searched the net and the forums for something similar, but have came up with nothing.

The extension used was the one linked from this issue:
https://www.zotero.org/trac/ticket/524

Specifically:
https://www.zotero.org/svn/integration/branches/ice/ZoteroNotMac.oxt

This is the only one that seemed suitable.

Zotero version is 1.0.0b4.r5 and Firefox (2.0.0.4, 32-bit) is running at the time of enabling.
  • sybille
    Hi,
    I don't know that this will help you much, but I've been able to get the plugin to run on Gentoo 32-bit, at least to some extent. I tried with the same version of the plugin you linked, with OOo 2.2.1 (not -bin) and Firefox 2.0.0.4 (not -bin). So maybe it's specifically a 64-bit issue.

    I don't know how to debug the errors you were getting, either, but I can tell you that the plugin functioned very much like the work-in-progress it is on my system. I was able to view my Zotero references, insert citations, and generate a bibliography in a test document. However, there were no decorations on the windows opened by the plugin (so they couldn't be moved around) and the text-entry fields for search and add page numbers did not function at all.

    I could tell that, once the plugin is finished, it is going to be an amazing tool. But my experience is that it's not ready yet. Also, see the comments from Dan Stillman here concerning the status of of plugin and the potential for compatibility problems as development continues:
    http://forums.zotero.org/discussion/804/word-plugin-status-update/#Item_22

    All of which is to say that I'm not sure it would be worthwhile to try to troubleshoot the plugin on AMD64 yet. But of course that could also depend on whether anyone else can make sense of the error output. :)

    I just finished working on a book-length translation project using Zotero. For citations, I used the "Create Bibliography from Selected Item.." option, copied to the clipboard and then pasted into my subdocuments with help from the Glipper clipboard manager. To create the bibliography, I made a Zotero collection that included all the sources I cited, and then exported and pasted into a separate subdocument. This certainly was not as good as the plugin will be, of course, but it worked well enough with the footnote style of citations I used. Another possible solution would be to use Bibus to insert references after exporting the data from Zotero.

    Anyway, I hope this feedback will be useful even though it does not address your question directly.
  • jesse
    edited February 17, 2008
    I got a similar error with "URP-Bridge: ...." message. I did not record all the details or carefully compare the message with this thread.

    I had already installed zotero in "My Extensions" on WindowsXP, Athlon 64, machine, JRE 6 update 4. I had not yet used the zotero extension, but tried to uninstall from My Extensions and to reinstall in OpenOffice.org Extensions when I got this "URP-Bridge..." error. Then I unistalled zotero again, and on reinstalls (including after closing and restarting OO.o), whether to My Extensions or to OO.o Extensions, I'm repeatedly getting Extension Manager error message:

    (com.sus.star.uno.RuntimeException) { {Message = "python-loader:exceptions.ImportError:No module named os, traceback follows\X000aColudn't [SIC] import traceback module", Context = (com.sun.star.uno.XInterface) @0 } }

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