Config setting to safely allow Members-visible folders #1329
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #1224.
This PR introduces a 'Member Visible Folders' system configuration setting:
This makes visible an otherwise-hidden feature (#1224).
As the help text says, these folders are relative to
DOCUMENTS_ROOT_PATH, even if filled in as an absolute path (/Members/Meetings/).Implementation
Jethro has a
MEMBER_FILES_DIRSconstant, but this is not exposed in the System Configuration, so is not discoverable. I don't think we can safely exposeMEMBER_FILES_DIRS, because, for reasons I don't understand, it accepts arbitrary absolute paths.So I've introduced a new constant,
MEMBER_VISIBLE_FOLDERS, which is a relative-only replacement forMEMBER_FILES_DIRSintended to be set in system configuration, notconf.php.The code is backwards-compatible, so
MEMBER_FILES_DIRSis still supported if set. The code does the right thing ifMEMBER_FILES_DIRSandMEMBER_VISIBLE_FOLDERSare both set, although that would be unusual. There is a note inconf.php.samplesuggesting people use 'Member Visible Folders' config setting.