Closed (duplicate)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
4 May 2016 at 09:13 UTC
Updated:
8 Sep 2018 at 20:59 UTC
Jump to comment: Most recent
Comments
Comment #2
shaktik@himanshupathak3 : Fix pareview errors -
Review of the 7.x-1.x branch (commit 11adfaf):
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.
Source: http://pareview.sh/ - PAReview.sh online service
Comment #3
rajab natshahHi Himanshu,
Nice work on this module.
Manual review:
1. The right link for your sandbox project is.
git clone --branch 7.x-1.x https://git.drupal.org/sandbox/himanshupathak3/2712881.git quicktabs_remember2. README file is messing. It's an important to have some info.
3. The use of "quicktabs_remembered" Table to store quicktabs remember checked option. The function _quicktabs_remember_get_quicktabs. I think the use of variable_set and variable_get will ease the work and not let us have a key filtering in PHP. As by a sample concatenation format .. like quicktabs_remember quicktab_machine_name .
4. I think we could add an option to Save the last tab in the Cookies. so that the JavaScript will read that from the cookiey then do the work as well .. I do see this options to save in database or cookies.
5. I think you could make use of hook_enable and hook_disable in the in the install file.
Rewarded module ;)
Comment #4
himanshupathak3 commentedComment #5
himanshupathak3 commentedThanks Rajab.
1. Updated wrong git clone URL.
2. Adding readme file soon.
3. I thought of using variable set and variable get first, but found quicktab does not have hook for quicktab deletion, so we can't delete variable automatically when quicktab is deleted, that's why I used foreign keys to get this job done automatically. Any idea how to achieve that ?
4. Yes, adding cookies is in future scope, I wanted this across all browsers, so added db records. Yes for the same browser, I'm going to add cookies as well, so that if cookies exists, we reduce one database call. And I'm adding one more checkbox "remember per browser" (which uses cookies at back end), for that I'll not store records in db.
5. Yes, will add hook_enable and hook_disable in install file.
Thanks again for your valuable review.
Comment #6
PA robot commentedProject 1: https://www.drupal.org/node/2593421
Project 2: https://www.drupal.org/node/2718615
As successful completion of the project application process results in the applicant being granted the 'Create Full Projects' permission, there is no need to take multiple applications through the process. Once the first application has been successfully approved, then the applicant can promote other projects without review. Because of this, posting multiple applications is not necessary, and results in additional workload for reviewers ... which in turn results in longer wait times for everyone in the queue. With this in mind, your secondary applications have been marked as 'closed(duplicate)', with only one application left open (chosen at random).
If you prefer that we proceed through this review process with a different application than the one which was left open, then feel free to close the 'open' application as a duplicate, and re-open one of the project applications which had been closed.
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #7
himanshupathak3 commentedComment #8
avpaderno