I have a use case where I would like to protect whole 'sections' of a website. In this case using a wildcard would hide child pages. eg: protect pages under: `/about/*`

I have included a patch that would expand on the existing functionality to allow for <front> and * characters.

Thanks,

CommentFileSizeAuthor
wildcards.patch8.03 KBsherakama

Comments

sherakama created an issue. See original summary.

sherakama’s picture

sherakama commented
Issue summary: View changes
XerraX’s picture

XerraX commented
Version: 7.x-2.4 » 7.x-2.x-dev
Status: Needs review » Reviewed & tested by the community

works for me

scottsawyer’s picture

scottsawyer
Primary language English
Location Atlanta
commented

Weird, I could not apply patch against 7.x-2.x but I could against 7.x-2.4

scottsawyer’s picture

scottsawyer
Primary language English
Location Atlanta
commented

Apparently this patch does not include the "Edit Protected Pages" form. If I have a Protected Page using a wild card "protected/*" and I attempt to edit the page, I get the error: Please enter a correct path!

scottsawyer’s picture

scottsawyer
Primary language English
Location Atlanta
commented
Status: Reviewed & tested by the community » Needs work

Setting to needs work because the Edit screen should allow for editing paths with a wildcard.