Closed (won't fix)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
28 May 2014 at 20:58 UTC
Updated:
29 Jan 2015 at 23:25 UTC
Jump to comment: Most recent
Comments
Comment #1
briward commentedComment #2
briward commentedComment #3
briward commentedComment #4
briward commentedComment #5
briward commentedComment #6
PA robot commentedThere are some errors reported by automated review tools, did you already check them? See http://pareview.sh/pareview/httpgitdrupalorgsandboxbrianjamesward1820014git
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 #7
briward commentedComment #8
briward commentedI have now fixed a whole bunch of the 'standards' issues now although for some reason there appears to be some more. They don't appear to be important issues so I don't think it matters?
see - http://pareview.sh/pareview/httpgitdrupalorgsandboxbrianjamesward1820014git
Comment #9
neetu morwani commented@brianward
Module does not follow Drupal Coding standards which is the main blocker for the module to get published.
PAReview of the module gives errors and warnings which are supposed to be resolved.
http://pareview.sh/pareview/httpgitdrupalorgsandboxbrianjamesward1820014git None of these errors should exist.
1. Module doen not work properly in terms of functionality.
2. The page admin/flush/run returns nothing but WHITE SCREEN OF DEATH. On next Reload , we get the message "Flush has cleared the system cache.".
3. Incomplete README.txt file. Complete Installation instructions required.
Install as usual is not acceptable.
Mention Download the module and place the module in sites/all/modules/ directory and then enable the module by hitting the url admin/modules.
4. Mention the link of the GIT repository on the issue link as well as the project page.
Mention
git clone --branch 7.x-2.x http://git.drupal.org/sandbox/brianjamesward/1820014.git flushbefore the sandbox project link.5. Line 175 of the module has a system setting form and there are variable in the form which should be prefixed with the name of the module in order to avoid collisions with other module and also to enhance the readability of the variables in database table 'variables'.
Line 131 has a variable
$form['hotkey_help']which should be renamed to$form['flush_hotkey_help'].6. File flush.install should implement
to delete all the variables introduced in the module.
Please resolve these errors.
Comment #10
ameymudras commentedFollowing are the issues i found
1. Rather than using the following code
You can directly use the function drupal_goto
2. drupal_set_message(t('Flush has cleared the system cache.'), 'status');
drupal_flush_all_caches();
You are displaying the message before the cache is cleared
3. Interms of the functionality the module dosent work properly
Comment #11
PA robot commentedClosing due to lack of activity. If you are still working on this application, you should fix all known problems and then set the status to "Needs review". (See also the project application workflow).
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #12
briward commentedComment #13
briward commentedIssues resolved:
Re-opening this ticket now in hope it can be approved.
Comment #14
briward commentedComment #15
marcus_johansson commentedThere are still some errors coming from the automated check:
http://pareview.sh/pareview/httpgitdrupalorgsandboxbrianjamesward1820014git
You should check if they are by design or something that you should fix.
Two things you should fix and two thoughts:
Comment #16
briward commentedThanks for your comments Marcus, I'll work on adding these 4 points as soon as possible.
Comment #17
PA robot commentedClosing due to lack of activity. If you are still working on this application, you should fix all known problems and then set the status to "Needs review". (See also the project application workflow).
I'm a robot and this is an automated message from Project Applications Scraper.