Filebrowser Root Path Setting failure doesn't throw error

Description

If you add a path to a folder that doesn't exist, it doesn't error when saving the setting.
If you upload the file it errors.
If you make a direct, it does make the folder.

Maybe the setting should check for existance?

Also, when in a cluster, like Ortus Prod, sometimes the setting doesn't get read into the filebrowser for the custom folder, and uses the default /contentbox/content instead of the DB setting.
A reinit fixes this... but why is this setting not updating?
Maybe its a cluster / flash issue?

Gliffy Diagrams

Activity

Show:

Luis Majano June 8, 2017 at 8:55 PM

I believe this is fixed now.

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Fix versions

Priority

Sentry

Created December 16, 2016 at 12:17 AM
Updated June 8, 2017 at 10:11 PM
Resolved June 8, 2017 at 8:55 PM