Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
CVS edit link for dominikb1888
We have built module which extends the existing biblio module for synchronization with the mendeley social research network (mendeley.com). It allows drupal users to connect to the mendeley api after having registered their website at dev.mendeley.com. The module allows to sychronize local biblio nodes with a mendeley shared collection and vice-versa.The project is currently hosted on github: https://github.com/jakob-stoeck/drupal-biblio-mendeley/tree/.
A PHP library to connect the API which will need to sit in the sites/all/libraries folder can be found here: https://github.com/jakob-stoeck/mendeleyapi
Comment | File | Size | Author |
---|---|---|---|
#1 | jakob-stoeck-drupal-biblio-mendeley-v2.0-3-geb96e09.tar_.gz | 10.88 KB | dominikb1888 |
Comments
Comment #1
dominikb1888 CreditAttribution: dominikb1888 commentedAttached the module files, also located at: https://github.com/jakob-stoeck/drupal-biblio-mendeley
Comment #2
apadernoHello, and thank you for applying for a CVS account.
I am adding the review tags, and some volunteers will review the module, pointing out what needs to be changed.
Comment #3
zzolo CreditAttribution: zzolo commentedHi. Please read all the following and the links provided as this is very important information about your CVS Application:
Drupal.org has moved from CVS to Git! This is a very significant change for the Drupal community and for your application. Please read the following documentation on how this affects and benefits you and the application process:
Migrating from CVS Applications to (Git) Full Project Applications
Comment #4
dominikb1888 CreditAttribution: dominikb1888 commentedhttps://github.com/jakob-stoeck/drupal-biblio-mendeley/tree/
Comment #5
dominikb1888 CreditAttribution: dominikb1888 commentedComment #6
BerdirYou need to create a sandbox project on d.o.
Some feedback about the code...
- Use two spaces instead of tabs
- "watchdog('error', $e->getMessage());". Instead of error, use a custom string, e.g. your module name
- Since are using exceptions and stuff, you should add "php = 5.0" to your .info file.
Comment #7
BerdirAlso: You can remove the $Id$ lines, they have no effect with git.
Comment #8
lorinpda CreditAttribution: lorinpda commentedHi,
Please note! There still is no sandbox for this application. Shouldn't the status be moved to "postponed" ?
Comment #9
dominikb1888 CreditAttribution: dominikb1888 commentedHi,
I created the sandbox project now: http://drupal.org/sandbox/dominikb1888/1099202.
We'll fix the issues mentioned by Berdir asap. Thx for the review!
Dominik
Comment #10
dominikb1888 CreditAttribution: dominikb1888 commentedI've commited the suggested changes now. The initial commit to the sandbox can be found here: http://drupalcode.org/sandbox/dominikb1888/1099202.git/tree/67aa60c55805...
Comment #11
dominikb1888 CreditAttribution: dominikb1888 commentedComment #12
meba CreditAttribution: meba commentedwatchdog('biblio error', $e->getMessage());
I suggest using just 'biblio', otherwise it's ready to go IMHO.
Comment #13
mlncn CreditAttribution: mlncn commentedHi Dominik,
Before getting access, could you make sure you have hooked up your Git correctly to Drupal.org? Your commits are showing up as "unknown". I think you need to set your e-mail address in your git local to the same as one listed for your Drupal.org account: http://drupal.org/node/1022156
And can get help in IRC on freenode.net, #drupal-gitsupport
Comment #14
dominikb1888 CreditAttribution: dominikb1888 commentedHi Benjamin,
I have now set email-adress and user on my local git and committed again. The user name shows up. Is that all that's required?
Best,
Dominik
Comment #15
dominikb1888 CreditAttribution: dominikb1888 commentedComment #16
ec CreditAttribution: ec commentedHi,
Is there any news with this module? What about the mendeleyApi library which is required by this module? Does it work with the new mendeley API?
Regards,
Eric
Comment #17
dominikb1888 CreditAttribution: dominikb1888 commentedHi Eric
yes it'll work with the new mendeley api library as well - actually this is the same project. But as the PHP Libraries are not Drupal Specific they're lying outside of drupal.org.
We'll push a new version to github and here in the course of this week.
Best
Dominik
Comment #18
ec CreditAttribution: ec commentedHi Dominik,
Thanks for replying and for the good news. I will stay tuned ...
Best,
Eric
Comment #19
ec CreditAttribution: ec commentedHi Dominik,
Any update on this? May I help in any thing?
Best,
Eric
Comment #20
Anonymous (not verified) CreditAttribution: Anonymous commentedSince dominikb1888 took care of the last remaining request, I'm going to RTBC this. Sorry it took so long.
Comment #21
gregglesSuggestions:
It appears you are working in the "master" branch in git. You should really be working in a version specific branch. Please see the documentation about release naming conventions and creating a branch in git.
Please take a moment to make your README.txt follow the guidelines for in-project documentation.
Please take a moment to make your project page follow tips for a great project page.
I noticed some small code style issues. Things like
if($
instead ofif ($
. Please run the module through the latest dev of coder on "minor".This could leverage the libraries API to load the file so it will work on more systems. I believe this will fail on certain php configurations:
require_once 'sites/all/libraries/mendeleyapi/Mendeley.php';
For all of your menu callbacks I think a more appropriate permission is "administer site configuration" - the current value is "access administration pages" which implies a more passive role whereas administer site configuration means the person is likely to change things.
biblio_mendeley_delete_local_nodes seems like it might fail to complete on an overloaded server or where there are lots of nodes. It would be good to move it to batch API.
Issues which need to be fixed:
The README.md should be renamed to README.txt
Your project should not have a LICENSE.txt
You should remove the gpl from each individual file. The code will be packaged with an appropriate LICENSE.txt so this information is duplicate.
You should remove $Id:$ from http://drupalcode.org/sandbox/dominikb1888/1099202.git/blob/refs/heads/m...
The code to switch users needs to be wrapped in session_save_session. See safely impersonating a user.
Questions:
Is the biblio_mendeley_consumer_secret value truly an important secret like a password? If so I suggest that the README and default configuration is storing it inside a php file on the server. You can put it in $conf['biblio_mendeley_consumer_secret'] = 'valuehere'; in settings.php and it will be available via variable_get. Putting it into an admin form means it will be stored in plain text in the database. If you put it in your settings.php file then you can be fairly confident people will be careful with that file (since it usually includes the mysql password, for example).
I'm not sure biblio_mendeley_is_synchronizing will work the way you want it to because the static php scope is only during a page request. I think you might want to use the lock system http://api.drupal.org/api/drupal/includes--lock.inc
Comment #22
dominikb1888 CreditAttribution: dominikb1888 commented@Lin: thanks very much for picking this up again
@Greg: thanks for the extensive and valuable feedback, I actually ran coder on this, but probably in an earlier stage. I shall create a proper Branch. The permission settings should actually be fine as this is mainly an admin targeted module. We are currently creating an individual connection which will have the correct permissions. I will look into your questions more deeply and come back to you on this.
Comment #23
gregglesI'm not sure that's the case. There are two permissions which sound very similar: "access administration pages" and "administer site configuration." The first is passive, meaning they can see things. The second is active meaning that they can change things. Since the menu callbacks in this module are for changing things it seems more appropriate to use the permission that is about changing settings.
This change also has some security implications - administer site configuration is on the list of permissions that can "own" your site and therefore a "vulnerability" from injecting xss into the form is not considered to be a real vulnerability if that page requires "administer site configuration."
If you feel strongly that the page should be "access administration pages" and want to keep it that way we should do a second review to confirm whether or not any of the features on that page can be considered an attack vector.
Comment #24
sunhuaifeng CreditAttribution: sunhuaifeng commentedHi, i'm using drupal 7 but the module says "This version is not compatible with Drupal 7.x and should be replaced."
Do you have a new version?
i use the following steps
1.Activate Biblio in Drupal, finished and this is OK.
2.Activate Biblio Mendeley (this module) in Drupal, when i check the modules, it shows the message.
the Biblio Mendeley module is downloaded from https://github.com/jakob-stoeck/drupal-biblio-mendeley/tree/
any help?
Comment #25
dominikb1888 CreditAttribution: dominikb1888 commentedHi Jonathan,
very sorry, there is no drupal7 version of this module at the moment. We're currently in the process of porting the module. I will let you know on here when we're ready!
Best,
Dominik
Comment #26
sunhuaifeng CreditAttribution: sunhuaifeng commentedthanks Dominik
Comment #27
MiSc CreditAttribution: MiSc commented@dominikb1888 has been contacted to ask if the application is abandoned.
http://drupal.org/node/894256
Comment #28
ec CreditAttribution: ec commentedHi, I'm trying this module on D6 again, however I still don't succeed. Is there any tips to have it running ? Or is there something wrong with it ? Thanks. Regards.
Comment #29
MiSc CreditAttribution: MiSc commentedNo action done, so closing this one, please reopen if this is wrong.