Popup Confirm Survey is a small module, the only purpose of which is to popup a survey confirmation box and redirect to the survey content type. The survey content type can be set from configuration section. The popup confirmation is created as a block, so admister privileged users can easily configure the required pages as well. We have used the overlay method (eg: lightbox, highslide etc) to show the confirmation popup.
GIT Path : git clone --branch master Drupaldevassyst@git.drupal.org:sandbox/Drupaldevassyst/1328204.git popup_confirm_survey
Sandbox Project link : http://drupal.org/sandbox/Drupaldevassyst/1328204
Drupal Version : 6.x
| Comment | File | Size | Author |
|---|---|---|---|
| #12 | popup_confirm_survey-result.txt | 17.33 KB | raynimmo |
Comments
Comment #1
raynimmo commentedMaster Branch
It appears you are working in the "master" branch in git. You should really be working in a version specific branch. The most direct documentation on this is Moving from a master branch to a version branch. For additional resources please see the documentation about release naming conventions and creating a branch in git.
I checked out your code after working out the correct clone path, which is actually
git clone --branch master http://git.drupal.org/sandbox/Drupaldevassyst/1328204.git popup_confirm_survey.Code Errors
You should really run the Coder module on "minor" setting to help catch the errors within your code. The coding standards
have even more information in this area.
When I ran it through coder with settings at Severity minor, Drupal Commenting Standards, Internationalization, Drupal Security Checks, Drupal SQL Standards, Drupal Coding Standards it found a large amount of errors in your code.
Comment #2
drupaldev@assyst commentedHi,
Thanks for your comments.
Completed the changes as per your suggestion and created new version branch.
git clone --branch dev1 Drupaldevassyst@git.drupal.org:sandbox/Drupaldevassyst/1328204.git popup_confirm_survey
Best Regards,
Team Assyst
Comment #3
raynimmo commentedYou should have a read of the release naming conventions and possibly rename the branch to 6.x-1.x if it is targetted at Drupal 6.
Also, the
git cloneline you are referencing is incorrect. That is for you when you are committing files to your branches as it contains your user login credentials. For other people to clone your project they would have to enter;git clone --branch 6.x-1.x http://git.drupal.org/sandbox/Drupaldevassyst/1328204.git popup_confirm_survey.If in doubt about Git commands have a read through the Git documentation.
Comment #4
drupaldev@assyst commentedHi,
Thank you very much for your valuable comments.
We had renamed the branch as you suggested and the new git URL is given below
git clone --branch 6.x-1.x http://git.drupal.org/sandbox/Drupaldevassyst/1328204.git popup_confirm_survey
Best Regards,
Team Assyst
Comment #5
drupaldev@assyst commentedHi,
Kindly confirm, whether we need to do anything more for making this project Live.
Thanks & Best Regards,
Assyst Team
Comment #6
raynimmo commentedif your project is in need of review then you should set it status to 'needs review'
Also, just noticed that you have another module application in the issue queue. Generally only one application per user is allowed, you should either close this one or #1331840 Twitter Tweets Module.
Comment #7
drupaldev@assyst commentedComment #8
raynimmo commentedDrupal Code Sniffer has found some code style issues (please check the Drupal coding standards):
Please ensure you set it back to 'needs review' once you have addressed the issues highlighted here.
Comment #9
drupaldev@assyst commentedHi,
The changes that we had made is not getting reflected in the git branch. We had deleted the current branch and created a new one with same name. I hope now all the changes are pushed to the new branch
Git url : git clone --branch 6.x-1.x http://git.drupal.org/sandbox/Drupaldevassyst/1328204.git popup_confirm_survey
Iam really sorry for the mistake happened from our end.
Thanks and Best Regards,
Assyst Team.
Comment #10
bfr commentedReview of the 6.x-1.x branch:
This automated report was generated with PAReview.sh, your friendly project application review script. Go and review some other project applications, so we can get back to yours sooner.
Comment #11
drupaldev@assyst commentedHi,
We had made the changes as listed above. Please have a look on this.
Thanks & Best Regards,
Assyst Team
Comment #12
raynimmo commentedThe automated review scripts still have quite a lot of issues with your code. Check the attached text file and be sure to set it back to 'needs review' once you are satisfied you have addressed all of the issues highlighted.
Possibly use the online tests before setting it back for review next time.
The automated report was generated with PAReview.sh, your friendly project application review script.
Source: http://ventral.org/pareview - PAReview.sh online service
Comment #13
drupaldev@assyst commentedHi,
Updated the script as per standards. Now there is no errors or warnings showing with PAReview.sh online service.
Thanks & Best Regards,
Assyst Team.
Comment #14
raynimmo commentedYou should add a link to your project page to the main description at the top of this queue to facilitate easy access for reviewers. The only way to get to the project page is by clicking your username and then selecting it from the list of projects at the bottom of your profile. You should have a read of the Issue Summary Guidelines.
Automated Review
The automated tools are changing on a daily basis and while it may not have shown any errors previously it may now help to highlight some that it missed after its own codebase has been expanded upon and updated. I would advise you to check your own code against them on a regular basis or when you notice they have posted updated files.
There are still files other than README.txt in the master branch, make sure to remove them. See also step 5 in http://drupal.org/node/1127732
Automated Review of the 6.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.
For the current report please read http://ventral.org/pareview/httpgitdrupalorgsandboxdrupaldevassyst132820...
Manual Review
Your .info file has no 'core' value specified, for Drupal 6 you should add
core = 6.xYou have a .project file in your repo, this was possibly added by your text editor. You should removed this from your repo unless it is required by your module.
You implement a
$(document).ready()call within your JavaScript when you should be using Drupal Behaviors.Also your styles.css could do with some improved formatting with regards to spacing and attribute alphabetization.
The Libraries API module is a recommended method for adding 3rd party dependencies without directly including the code on Drupal.org.
Make sure to set your status back to 'needs review' once you have addressed the issues higlighted here. It would alsoi be advantageous if you used the online PAReview service at http://ventral.org/pareview/ before you next change the status.
Comment #15
raynimmo commentedComment #16
drupaldev@assyst commentedHi,
Thank you very much for your valuable comments.
We had changed the project files and other changes as per your suggestion. The Automated Review tool is showing still there are some other files rather than Readme.txt with the master branch. But we can't able to find any other unused files with the checkout on master branch.
There are still files other than README.txt in the master branch, make sure to remove them. See also step 5 in http://drupal.org/node/1127732
Please do some help for the above.
Thanks and Best Regards
Assyst Team
Comment #17
drupaldev@assyst commentedHi,
The issue has been resolved and now only the README.txt file is with master branch.
Thanks & Best Regards
Assyst Team
Comment #17.0
drupaldev@assyst commentedGIT Path and Drupal Version added
Comment #18
drupaldev@assyst commentedHi,
Is there any latest update for the module review?
Thanks,
Assyst Team
Comment #19
raynimmo commentedThe automated review tools are still finding a number or errors within your code. They are mainly complaining about a lack of spacing within your CSS declarations and whitespace at the end of lines within your JavaScript.
Automated Review
Git checkout of branch 6.x-1.x fail
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. Get a review bonus and we will come back to your application sooner.
See the full report at http://ventral.org/pareview/httpgitdrupalorgsandboxdrupaldevassyst132820...
I will try and find some time to do a manual review tomorrow but I am currently setting to 'needs work'.
Comment #20
drupaldev@assyst commentedHi,
Resolved the issues reported by online tool.
Can you please clarify the issue with git checkout. I had done the same from my end as Non-maintainer and works fine for me. The url is below
git clone --branch 6.x-1.x http://git.drupal.org/sandbox/Drupaldevassyst/1328204.git popup_confirm_survey
Thanks,
Assyst Team
Comment #21
drupaldev@assyst commentedComment #22
tyler.frankenstein commentedAutomated Review
http://ventral.org/pareview/httpgitdrupalorgsandboxdrupaldevassyst132820...
Came back clean.
Manual Review
I downloaded the jquery.countdown.min.js to the js folder in this module's directory. I then installed the module via drush on a fresh localhost copy of Drupal 6.24. Next, I granted permissions to access the popup confirm survey.
I then created a content type called 'Survey' with a machine name of 'survey', followed by creating two page Nodes, one for Survey path, and one for Survey access denied page. I then went to the module configuration page and set node/1 to Survey path, and node/2 to Survey access denied.
Then I added the module's block to the header region of the Garland theme. At this point the survey pops up and I am presented with a form and two radio buttons, 'yes, continue with the survey' and 'no, not this time.' No matter what radio button I choose and hit submit, the popup just keeps coming back and has basically locked user #1 out of the drupal site, this was bad.
If a user didn't know how to use drush or access the system table in the database, they would basically be locked out of their drupal site. I had to use drush to disable and uninstall the module to get the site to respond to user #1 again.
At this point the experience has not been very good. I would suggest the module configuration page be a bit more descriptive, I'm not sure if I am entering the right information. I was following the README instructions, and up until I added the module's block to the header region of Garland it was going OK. But once it locked me out (on a fresh D6 install), I decided to go no further with testing, this module may need some work, or the README needs to be more descriptive.
Next, I looked over your module and install code. It looked fine from my understanding of Drupal coding standards. Basically, there needs to be more information on the project page as well as in the README, in my opinion.
I would also suggest trying to reproduce the 'lock-out' scenario I described above and figure out why that is happening. If it is user error (i.e. myself entering wrong data into the module's config forms) you need to protect against that and inform the user and/or provide clearer directions on the configuration page.
Comment #23
klausiClosing due to lack of activity. Feel free to reopen if you are still working on this application.
Comment #23.0
klausiSandbox project link added
Comment #24
avpaderno