I want to do some updates to the MODx File Manager ("Manage Files"), it seems to me that it is causing the most problems for people. There’s one change that I want to do that I thought I’d ask before doing. Here’s the change I’m proposing:
I think the [tt]filemanager_path[/tt] configuration setting should be removed and [tt]rb_base_dir[/tt] used instead. I can see the flexibility in having this option but it comes with some quirks: since no [tt]filemanage_url[/tt] is supplied, problems can arise in some scenarios where users are unable to preview files such as images.
Since the File Manager already uses [tt]upload_images[/tt], [tt]upload_media[/tt], and [tt]upload_flash[/tt] (which are all under the Resource Browser section), it seems logical to use to the rest of the Resource Browser configuration settings.
This method has two advantages: 1) It ramifies the previewing problem in certain scenarios, 2) It utilizes existing configuration settings and removes one more aspect of confusion for users.
So here’s a question, does anyone know of any scenarios in which their [tt]filemanager_path[/tt] is going to be different than [tt]rb_base_dir[/tt]?
-
☆ A M B ☆
- 1,056 Posts
So here’s a question, does anyone know of any scenarios in which their filemanager_path is going to be different than rb_base_dir?
Nothing comes to mind just yet. Hmm...
On another note, I’m currently working on a File Manager replacement. Basically, it’s the one here:
http://www.phpletter.com/Demo/Ajax-File--Manager/
Figured this would be a fairly decent replacement till we can work up a better one.
Jeff
Jeff Whitfield
"I like my coffee hot and strong, like I like my women, hot and strong... with a spoon in them."
-
MODX Staff
- 10,725 Posts
No, I do object to this; the filemanager_path is for the file manager, the rb configurations are for the resource browser. Period.
-
MODX Staff
- 10,725 Posts
Why would you want a file_manager_url? Nothing in the file manager should be exposed by URL.
I don’t understand a scenario where it should be the same. The Resource Browser is for RTE usage, could be front-end, or back-end. The rb options may be set at the system and user level and are only related to the Resource Browser. File Manager path should be set to an actual file-system path for the administrator to have access to all files, not just those that are part of the content management activities in assets/; this is intended for site/MODx administration purposes. These could also be set by user as well, to specific locations to limit admin activity in the backend by user. Only thing missing is group-based setting overrides in between system and user, which will also be coming in 0.9.7.
In addition, in 0.9.7, the file manager will also be able to browse locations for static documents that can be managed in the MODx document tree, and these may lie outside of the webserver directories altogether for security purposes. I can see other scenarios where file access through MODx to specific directories could be warranted, with no relation to an RTE or "resource browsing" activities.
I don’t see where there should be any relation between these settings at all. If you have a scenario where they need to be synchronized, use a plugin with manager settings form save event.
