-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Collection links (#91) #103
Conversation
Thank you - looks great! A couple of requests:
|
This is not directly related, but in case it's of interest: https://forums.zotero.org/discussion/78550/getting-zotero-to-work-under-ubuntu-linux |
It isn't related, but if you installed from my debs, you can file an issue there. If you installed from the tarball, they don't work out of the box. |
From that forum post, I don't understand how this would be an old url? What's the difference between the two? It wouldn't be automatically fixed, no. |
Ah yes - sorry, not very clear at all. I meant that in zotero://select/groups/5/collections/3ESW8QB9, the '5' refers to a property of my zotero client (being the 5th library perhaps). This was the case with some outdated zotero:// links as well (I think). Let me start again: For example, in one of my libraries, I have these URIs:
I was expecting zotero://select/groups/2339240/collections/3ESW8QB9 for the 2nd. This is analogous to
|
Also as in put them on the clipboard together? Or as in add a new menu option?
I think that's fixed in zOSl.xpi |
Oh I see what you mean with the URI. https://0x0.st/zOSR.xpi |
Perfect - that's fixed it! And I installed from your repo, so the zotero:// links work too! Will you be able to add https://www.zotero.org/groups/2339240/edtechhub/items/collectionKey/3ESW8QB9 - style links as well? (No rush - just checking it's on the radar) |
Doesn't zOSR already add that? |
AH YES! It does - as long as I remember to turn it on the in the preferences!! THANK YOU!!!! |
The PR has been rebased |
Shouldn't make any difference, but to make sure: https://0x0.st/zVTC.xpi |
@willsALMANJ - just a tiny friendly and most courteous prod on this PR :) |
@retorquere I think the collection links may be wrong. When I copy the URI to a collection When I actually click on the lhe link, I get I realise that this is my mistake, as I suggested the wrong link - sorry. Can you adjust the code to use the alternative link instead? |
That's pretty strange because I just request the collection URI from Zotero using |
@bjohas thanks -- I haven't forgotten. I am trying to get to this as soon as I can. |
I reviewed this and it looked good to me (thanks for incidentally improving the code as you add things to it). One thing I noticed is that I get this message in the error console when clicking on an item in the collection context menu:
referencing this line. It seems that Zotero is trying to capture the click event and handle it in JS instead of using the built-in XUL system for tying commands to menu items. The copy functions still work despite the error. I am not sure there is an easy to prevent Zotero from trying to handle the click, so we might just have to leave it the way it is. What do you think? Besides that, we just need to resolve the question about the URI format, and I can copy the strings to the other locales and merge. I haven't read the clean up PR yet, but I don't anticipate that being a problem to merge after I get a chance to read it. We should add something to the documentation for these functions as well (can be done separately from this PR). |
I've asked about It's going to be hard to get rid of the |
So it looks like it's something that's going to be fixed at their end. |
https://0x0.st/zW3g.xpi disables the "copy link" option if the user isn't synced. The cleanup PR can wait until we've settled this one. I'll rebase to master after this is merged and then re-run the linter. |
Okay, so then we are good to merge this other than the benign error. I posted a comment in-line about a way to avoid the error. I am curious what you think. |
Thank you both, that's amazing! |
This implements #91. It builds on #102 -- if so desired, I can rebase onto #102 after that has been merged.