We are asking folks to help us conduct a usability test on our community infrastructure as part of our infrastructure sprint:
How to help:
If you have never reported a bug in a Backdrop CMS contrib module:
- DO NOT read the comments here until you finished the test.
- Attempt to accomplish the following scenario (without actually filing a bug report)
- Post a comment below with feedback about how easy or difficult it was to accomplish this task and any ideas you have for making it easier.
Scenario:
You found a bug with the views modules and you would like to report it.
Recent comments
Thanks for explaining @herb I was actually thinking along the same lines and have created a simple module that gives the 'view any content_type content' permission and restricts just by checking the...
Disable hidden path message on particular content type
We now have a working version of Organic Groups. https://backdropcms.org/project/og
organic groups or "group module"?
@argiepiano I was referring to the main goal of restricting access to a content type. I was thinking that if the solution is to write a custom module there's a more direct way to implement access...
Disable hidden path message on particular content type
To add to @argiepiano's point; I've been following the discussion in #5634 on possible/probable performance impacts of content access modules : https://github.com/backdrop/backdrop-issues/issues/...
Disable hidden path message on particular content type
Seems to be an awkward ways to avoid using a content access module :). I don't follow. This doesn't in any way restrict or grant access. It simply removes an info message.
Disable hidden path message on particular content type