Closed (fixed)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Reporter:
Created:
13 Jan 2014 at 06:07 UTC
Updated:
22 Mar 2014 at 11:11 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
deepakaryan1988Comment #2
deepakaryan1988Comment #3
deepakaryan1988Comment #4
deepakaryan1988Comment #5
PA robot commentedThere are some errors reported by automated review tools, did you already check them? See http://pareview.sh/pareview/httpgitdrupalorgsandboxdeepakaryan1988211307...
We are currently quite busy with all the project applications and we prefer projects with a review bonus. Please help reviewing and put yourself on the high priority list, then we will take a look at your project right away :-)
Also, you should get your friends, colleagues or other community members involved to review this application. Let them go through the review checklist and post a comment that sets this issue to "needs work" (they found some problems with the project) or "reviewed & tested by the community" (they found no major flaws).
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #6
deepakaryan1988Comment #7
deepakaryan1988Comment #8
sygnetica commentedHere is correct url to results of preview.sh review tool:
http://pareview.sh/pareview/httpgitdrupalorgsandboxdeepakaryan19882113077git-0
Comment #9
sygnetica commentedWhen i click on "site_name/?q=verify" link get the error message:
Notice: Undefined index: entity_type in total_subscription_verification_mail() (line 245 of /home/sygnetica/projects/contrib/birthday_inform.dev/sites/all/modules/total_subscription/total_subscription.module).Notice: Undefined index: 1 in total_subscription_verification_mail() (line 247 of /home/sygnetica/projects/contrib/birthday_inform.dev/sites/all/modules/total_subscription/total_subscription.module).Comment #10
adam_thomason commentedHi,
I took the liberty of installing the module locally and reviewing the code. I could not find any errors, which is brilliant. I do however have the following suggestion:
perhaps code such as:
Could be moved into a .inc file? Perhaps blocks.inc? This just helps in future for maintainability of the code, particularly for third party developers who might want to extend your module.
Other than that, great module!
Cheers,
Adam
Comment #11
deepakaryan1988@Adam - That's a great suggestion and I will incorporate the same in the imminent future.
Thanks for the appreciation, and I hope you can use this in your live project soon.
Comment #12
deepakaryan1988@ sygnetica, Thanks for the reviewing my module. I have fixed those notices now.
You can check it.
And for pareview, I have looked up into it.
For this warning:-
I couldn't do anything because I like the way I have used it. It's really looking nice and easy to pick up and understand for other developer.
Comment #13
piyuesh23 commented@deepakaryan1988 Mails not getting sent if a content is unpublished and then published back. The module is missing the entry to $messages array in hook_mail for the email key being used to send emails in that case.
Comment #14
deepakaryan1988@piyuesh23
Thanks for detecting this bug.
This issue is fixed now. I hope in future you can give me more feedback for this module.
Comment #15
deepakaryan1988Comment #16
deepakaryan1988Comment #17
deepakaryan1988Comment #18
deepakaryan1988Comment #19
deepakaryan1988Applying for bonus.
Comment #20
ajitsThank you for the contribution. Just had a look at the code, it seems to be fine with no errors.
However, the name of the ctools content type in your module could conflict with the ctools content types of other modules.
Just changing the name from "subscription.inc" to "total_subscription.inc" would be enough to get this through. Not sure if it is a blocker, hence not changing the status.
Comment #21
deepakaryan1988@AjitS, Thanks for your review.
I have changed the name from "subscription.inc" to "total_subscription.inc". I think it would be great.
:)
Comment #22
isagarjadhav commentedTested. No serious issues found. Works as expected.
Comment #23
deepakaryan1988@isagarjadhav
Thanks for testing. :)
I hope you could use it in future.
Comment #24
klausiremoved copies of automated reviews from the issue summary.
Comment #25
klausiReview of the 7.x-1.x branch:
This automated report was generated with PAReview.sh, your friendly project application review script. You can also use the online version to check your project. You have to get a review bonus to get a review from me.
manual review:
Removing review bonus tag, you can add it again if you have done another 3 reviews of other projects.
Comment #26
deepakaryan1988@klausi
Thank you for reviewing my module. I would like to add Queue API for sending mail. I need a little time, but will fix it in the weekend.
Comment #27
deepakaryan1988@klausi Sorry about the delay. I have been buzy since last weekend. This weekend, I have attended DrupalCamp Mumbai :).
I will fix these issue in forthcoming days.
But the most critical issue, I have fixed. Now I am sending mail by cron. Basically during node_update and node_insert, I am sending emails to the cron queue and whenever cron gets run, it will start clearing whatever emails are in queue. So by doing this performance wont degrade.
Thanks,
Deepak
Comment #28
deepakaryan1988Comment #29
deepakaryan1988Comment #30
deepakaryan1988Hi Klausi,
I have fixed all the points which you had mentioned.
Please look after it.
I have also implemented cron queue for sending a mail so that site performance will increase.
total_subscription_menu(): "verify" as path could easily clash with other stuff on the site, maybe prefix it with totalsubscription or similar? --Done.
"t('Subscribe to these kind of') . $contexts_values->data->type,": do not concatenate variables to translatable strings, use placeholders with t() instead. --Done.
total_subscription_mail_send(): this is vulnerable to access bypass exploits. Where do you check that the receiver even has access to the node? I don't see any node_access() calls? Please also note that such an access check might not scale depending on how many subscribers you have, so I think it would be a good idea to postpone the mail sending using the queue API and let it be processed on cron runs. Otherwise your node saves could run into timeouts. And please don't remove the security tag, we keep that for statistics and to show examples of security problems. -- For node access I have given permission so that Admin will decide that page should be accessible or not. This has been done by sending the email address to the cron queue.
I will also put functionality for reports generation about subscriber which includes location of subscriber and time of subscription.
I have also reviewed three extra projects which I have to do as you have mentioned.
And I am also adding review bonus tag.
Comment #31
deepakaryan1988Comment #32
deepakaryan1988Comment #33
klausimanual review:
Comment #34
klausiComment #35
deepakaryan1988@klausi
Thanks for pointing out these issues.
I have fixed the above issues.
Comment #36
deepakaryan1988Comment #37
klausimanual review:
But otherwise looks RTBC to me now.
Assigning to ELC as he might have time to take a final look at this.
Comment #38
deepakaryan1988Thanks Klausi..
I have fixed the above issues which you have raised.
Hope this module will gonna helps lots of users.
Comment #39
klausino objections for more than a week, so ...
Thanks for your contribution, deepakaryan1988!
I updated your account so you can promote this to a full project and also create new projects as either a sandbox or a "full" project.
Here are some recommended readings to help with excellent maintainership:
You can find lots more contributors chatting on IRC in #drupal-contribute. So, come hang out and stay involved!
Thanks, also, for your patience with the review process. Anyone is welcome to participate in the review process. Please consider reviewing other projects that are pending review. I encourage you to learn more about that process and join the group of reviewers.
Thanks to the dedicated reviewer(s) as well.