Posted by rupertj on August 20, 2009 at 12:57pm
| Project: | Restricted content |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | needs work |
Issue Summary
This module did exactly what I was looking for - but had no ability to set default restrictions for a given content type. (The site I'm setting up needs certain content types restricted by default). The supplied patch adds the ability to select default restrictions when editing a content type. These are then set when creating a new instance of that type.
| Attachment | Size |
|---|---|
| restricted_content_with_defaults.patch | 5.58 KB |
Comments
#1
I just spotted a few issues with the previous patch (Previously set defaults didn't appear when editing a content type, and the access options were in a stupid place in the forms). This new patch replaces the first one and fixes these issues.
#2
when applying the patch i have an error:
patch < restricted_content_with_defaults_2.patch
patching file restricted_content.module
Hunk #5 FAILED at 255.
1 out of 5 hunks FAILED -- saving rejects to file restricted_content.module.rej
patching file restricted_content.install
What can i do?
#3
Thanks for the patch, Rupert.
It appears to have worked well. I had to create the new table, however since the .install file didn't cause the database table to be generated. I also got the errorof Hunk #5 failing, but looking at the patch, that hunk only adds a couple of comments so I am not worried about that.
If the .install were fixed to add an update I would recommend this be rolled into a release.
Stev3