fa91c6c954
closes #11574 - the current implementation of the access property has it frontend only, and wired up only in one place - this leaves it only available in a handful of places, e.g. can't use it in a post loop or get helper - the current implementation also fails logically if the html content of the post is blank This fix moves the behaviour to the API - this ensures the field is always available no matter what context you are in - it also updates the logic to use the same membersHasAccess logic as is used to gate the post, so it's always correct TODO: should reconsider the location of this code |
||
|---|---|---|
| .. | ||
| api-acceptance | ||
| frontend-acceptance | ||
| regression | ||
| unit | ||
| utils | ||
| .eslintignore | ||
| .eslintrc.json | ||
| .jshintrc | ||