I'm running a site in which I have quite a few Content Types, some of which are intended for public access (and therefore I don't care whether SSL is in use or not), and some of which are private and require encryption. Currently securepages.module only matches based on $path globbing, which is inadequate for my needs since there are thousands of nodes which need to be protected.
I've attached a patch against the 5.x-1.6 source, which implements this feature.
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | securepages-contenttypes-217171.patch | 4.58 KB | kenturamon |
| securepages_contenttypes.patch | 1.73 KB | smokris |
Comments
Comment #1
vikinzer commentedI just did a quick test of this patch and it seems to work. It is EXACTLY what I needed. Thank you so much for posting this patch, and I sincerely hope that it is formally evaluated and folded into the active code soon. It makes the module much more useful.
Comment #2
christefano commentedI would rather have a select list but I agree with vikinzer and think this is ready for the next release.
Comment #3
gordon commentedNo I do not believe that is something to add to secure pages.
There is an api which allows you to set the secure flag on the menu item and then secure pages will make the switch a lot faster and use less resources to do this.
example:
This will secure all store node types.
Gordon.
Comment #4
christefano commentedIn that case, I'll be watching #227633 with renewed interest.
Comment #5
vivianspencer commentedThis sounds very interesting, how does it work?
I've tried adding the snippet to a new module and can't seem to make it work, any more info would be greatly appreciated
Comment #6
seanrThis does not work in Drupal 6. There's nothing in the code that even checks for such a flag as far as I can tell and I can't even get a hook_menu function like this but ported to 6 to execute at all with the right values because of Drupal's menu cache. I think this does belong as a feature native to securepages - users shouldn't be expected to write a custom module to do this.
Comment #7
kenturamon commentedRecently had cause to implement this functionality for the securepages module in Drupal 6.
Comment #8
shaisachs commentedI've implemented a slightly different flavor of this feature while working on #587000: Cached pages are not being redirected - you can find the patch at http://drupal.org/node/587000#comment-5304070.
Comment #9
astonvictor commentedI'm closing it because the issue was created a long time ago without any further steps.
if you still need it then raise a new one.
thanks