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 don't already know the answer to this question:
- DO NOT read the comments here until you have finished the test.
- Attempt to accomplish the following scenario within a reasonable amount of time
- Post a comment below with feedback about and or all of the following:
- how easy or difficult it was to accomplish this task
- ideas you have for making it easier
- Did you find what you were looking for?
- What would you have liked to find?
Scenario:
You have heard a lot about Backdrop CMS, but are concerned about its maintainability and security in specific. You would like to find out if you will get at least the same level of support as with Drupal. Have past security issues been dealt with in a timely manner?
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