Closed (won't fix)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
3 Nov 2013 at 14:26 UTC
Updated:
9 Sep 2018 at 22:37 UTC
Jump to comment: Most recent
Comments
Comment #1
PA robot commentedThere are some errors reported by automated review tools, did you already check them? See http://pareview.sh/pareview/httpgitdrupalorgsandboxpignaz2125707git
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
jeroentI think this module is a great idea, but is there a difference between this module and Rabbit hole?
You should change the url to clone the project to: git clone --branch 7.x-1.x http://git.drupal.org/sandbox/pignaz/2125707.git deny_content_view
Your url is for the maintainer.
Automated review:
There is still one error. You should delete the master branch as explained here: http://drupal.org/node/1127732
Manual review:
I think you should move this code to hook_uninstall in the .install file.
Comment #3
drupaldev@assyst commentedGit path updated.
Comment #4
pignaz commentedComment #5
pignaz commentedRelated: https://drupal.org/comment/8244701#comment-8244701
Rabbit hole denys to view content which is utilized into special mode, for example carousel.
Deny Content View permits to view node page about one content type and not view node page about another content type.
For example This module would permit to view node page about Video content type and not node page about Article content type.
About manual review is not possible move code into hook_uninstall because i must delete role permission about deny_content_view created by core after installation of module.
I deleted master branch.
Bye Nicola
Comment #6
pignaz commentedComment #7
pignaz commentedComment #8
pignaz commentedComment #9
pignaz commentedComment #10
pignaz commentedComment #11
pignaz commentedComment #12
pignaz commentedin addition to PAReview: review bonus is no other way to see each approved their projects? I have corrected the errors reported, commented on three projects, but I've had no response.
Thanks for your attention
Comment #13
klausiYou need to set the status to "needs review" if you want to get a review, see https://drupal.org/node/532400
Comment #14
pignaz commentedComment #15
lord_of_freaks commentedHi
I can´t understand why this piece of code:
I don´t understand why you are deleting the permissions set by other modules, and anyway if you want/need to do it you need to loop over the $modules array (see the code below) because is possible to enable/disable more than once module at once.
Also the .install file should be removed if it´s empty and is not providing any functionality
Best regards
Comment #16
lord_of_freaks commentedComment #17
pignaz commentedI changed code and remove install file
Comment #18
klausihttps://drupal.org/project/content_access
Looks like the content access module already provides that functionality? Module duplication and fragmentation is a huge problem on drupal.org and we prefer collaboration over competition. Please use the content access module to accomplish this use case.
Comment #19
pignaz commentedThanks for info about this module
Comment #20
PA robot commentedClosing due to lack of activity. Feel free to reopen if you are still working on this application (see also the project application workflow).
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #21
pignaz commentedOk. I used content access module, but this doesn't do what I want.
I want to deny to see the full content of the node, but it is possible to see the content in a views (view module). By doing so we can drive users to see a content preview (teaser), while we force users to register them to see the full content.
This feature is not present into content access module.
So i ask you to approve this module if you think that it's a good idea.
Comment #22
pignaz commentedOk. I used content access module, but this doesn't do what I want.
I want to deny to see the full content of the node, but it is possible to see the content in a views (view module). By doing so we can drive users to see a content preview (teaser), while we force users to register them to see the full content.
This feature is not present into content access module.
So i ask you to approve this module if you think that it's a good idea.
Comment #23
pignaz commentedAny response ?
Comment #24
brockfanning commentedYour last description of the use-case made me think of this module: https://drupal.org/project/premium_content
Is it possible this one takes care of your use-case?
Comment #25
pignaz commentedOk i think that my module is a clone of premium module. Sorry
Comment #26
klausiNo problem, you can contribute to the existing module if you want to propose any improvements or bug fixes.
Feel free to open a new project application whenever you want to promote another project.
Comment #27
avpaderno