Closed (won't fix)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
2 Aug 2015 at 11:07 UTC
Updated:
29 Mar 2016 at 07:56 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
PA robot commentedThere are some errors reported by automated review tools, did you already check them? See http://pareview.sh/pareview/httpgitdrupalorgsandboxNixou2544164git
Fixed the git clone URL in the issue summary for non-maintainer users.
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 #2
gaja_daran commentedHi Nixou,
Manual Review
I having setup for Default 404 (not found) page(admin/config/system/site-information). By sample I have mentioned node/1.
When I browse the disable content type from your module, my default error page appear twice. The fix for this issue is put exit() after drupal_not_found();
Comment #3
sheetal.nepte commentedI have installed your module and verified for Article Content Type. Your code has bug. It displays Page not found first and below it displays the normal drupal page.
Refer the attached video.
You can add below fix.
if (variable_get('disablenodeviewfull_' . $type, 0)) {
drupal_not_found();
drupal_exit();
}
Comment #4
nixou commentedThanks a lot for your review and your advice.
I fixed errors returned by PA robot.
I added drupal_exit(); and I tested again. All seems to be ok now.
Comment #5
nixou commentedComment #6
brandonferrell commentedEverything is working for me, and the code is as clean as can be.
Automatic Review
Pareview code review: http://pareview.sh/pareview/httpgitdrupalorgsandboxnixou2544164git
Manual Review
Individual user account
Yes: Follows.
No duplication
No: This module expands Views functionality.
Master Branch
Yes: Follows
Licensing
No: Add Liscense
README.txt/README.md
Yes: Follows
Code long/complex enough for review
Yes: Follows.
Secure code
Yes: Meets the security requirements.
Comment #7
nixou commentedThanks for your review.
I have a question about licensing, it's not clar for me.
Here https://www.drupal.org/node/1587704 it is said :
So I didn't create any file for licensing.
You said :
So, I understand I have something to do but I don't know what exactly.
Is it possible to have some clarification ?
Thanks you.
Comment #8
ajalan065 commentedHi Nixou,
You are right. A project should not contain LICENSE.txt by default. It is later on added when the project gets full-project application.
Very neat and clean code.
But I have an issue.
Sending you the links to two images.
1. http://snag.gy/NDiON.jpg which shows 404 error as desired by your module. Well and fine.
However, when I promote the content to front page, the entire content is displayed. See this http://snag.gy/sv1c1.jpg
According to me, this should also return 404..
Not setting it to "Needs Work", as I am not sure whether its a bug, or you intend to show it in this way. Please comment and if required, make the changes.
Else, the module is ready for RTBC.
Comment #9
nixou commentedHi Ajalan,
Thanks a lot for your answer about licensing and for your review.
About the issue you describe : since the front page show all nodes "promoted to front page" as a list of teaser on the front page, we don't need to return a 404 here.
We want to disable only the node's view full and keep it on listings.
So, for me, it is working as intended.
Comment #10
th_tushar commentedHi Nixou,
Your module is too small to promote it to full project and provide the git access. Please visit Rules for not promoting to full project for more information.
Also there is not much functionality available in the module for promoting it to full project as its achieved/ can be achieved by implementing couple of Drupal Core Hooks.
So closing the issue now. If you still want your project to be reviewed further, you can re-open the issue and tag the issue with the "PAReview: Single project promote".
Thanks for your contribution!!
Comment #11
klausiSmall modules are perfectly fine for approval, please don't close such issues.
Comment #12
joachim commentedDuplicate module check: could you compare this with Rabbithole module please?
Comment #13
nixou commentedHi,
Thanks Klausi for reopening this post.
Joachim, I checked and you're right : Rabbithole do the same job, with many more options.
I didn't know this module.
So I close this application : use Rabbithole instead.
Comment #14
nixou commented