Less of a request and more of a discussion starter.

Before I came across this module, I wrote a very simple one to allow me to add custom permissions. I was not trying to restrict access to specific paths. I wanted to control access to Views displays. I also saw how this might become useful in Rules.

Would adding a pathless permission to use in Views, Rules, or anywhere else where custom functionality can be added without coding, be appropriate in this module?

CommentFileSizeAuthor
#3 allow_empty_paths_1.patch1.14 KBciss

Comments

andypost’s picture

andypost
he/him
Primary language Russian
commented

@crantok I think you should promote sandbox to full project.
Custom permissions is targeted for different needs

crantok’s picture

crantok commented

Thanks for the advice. I had positive opinions from others about doing the same before I noticed this module. I hope to have time to apply for full project status in August, and will do so if no-one expresses an interest in adding this feature.

ciss’s picture

ciss commented
Version: 7.x-2.0 » 6.x-2.0
Component: Miscellaneous » Code
Status: Active » Needs review
StatusFileSize
new allow_empty_paths_1.patch1.14 KB

I had the same requirement, creating pathless permissions for use in Panels.
This module already provides a solid foundation, so I created a patch containing the following:

  • Allow submission of permissions without a path
  • Minor optimizations to paths splitting code
mlncn’s picture

mlncn commented
Issue summary: View changes
Status: Needs review » Closed (won't fix)

Cool stuff but, as noted, not in scope for this firmly module where the custom permissions are firmly based on paths (now routes).

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.