This is the project dedicated to the development of the new administrative file manager for osCMax, replacing the old file manager that has been removed from the system.This project is in the pre-development stage, nothing has yet been decided. This is the time to add your input and help decide on the best solution for osCMax.
I have been looking at some stand-alone file managers, and one of my favorites so far is : AjaXplorer
It is very full featured, highly configurable and can be tied directly to the osCMax authentication/login. There would be some coding to be done to synchronize the admin users with the ajaxplorer users, but it does not look too difficult for a group of motivated osCMax coders.
There are several other possibilities, and I would welcome all of your opinions on this, as I am by no means decided on anything at this point. Lets hear your ideas.
by ridexbuilder on Thu, 11/12/2009 - 11:34am
Having not looked at this (yet), would you view this as negating the dedicated Image Manager?
Apart from a top level Admin of a site, a full featured file manager does seem to be 'risky' in any case? A lot of potential to wreck a site by mistake/ignorance. At least with sFTP access it's possible to restrict the scope for damage.
Just musing...
by michael_s on Thu, 11/12/2009 - 12:01pm
That is why I like AjaXplorer so much, it has a full permissions system that be slaved to the osCMax login, but can still limit access to the file-system and even features of the editor itself. Each user can have their own repository with their own set of permissions, so you can mirror the admin access levels you set up, removing access down to specific files.
It can be configured by a top admin, or we could modify the install to be limited by default in osCMax, requiring an admin to go in and add repositories for more than say, template folder access by default.
It is also easy to use, so anyone can figure out how to add a repository (file tree).
As for negating the dedicated image manager, not sure. It could definitely be configured as a image-manager repository that is restricted to just the images folder tree. It does have multiple-image upload capabilities without needing to refresh a page...
AjaXplorer
It is very full featured, highly configurable and can be tied directly to the osCMax authentication/login. There would be some coding to be done to synchronize the admin users with the ajaxplorer users, but it does not look too difficult for a group of motivated osCMax coders.
There are several other possibilities, and I would welcome all of your opinions on this, as I am by no means decided on anything at this point. Lets hear your ideas.
Apart from a top level Admin of a site, a full featured file manager does seem to be 'risky' in any case? A lot of potential to wreck a site by mistake/ignorance. At least with sFTP access it's possible to restrict the scope for damage.
Just musing...
It can be configured by a top admin, or we could modify the install to be limited by default in osCMax, requiring an admin to go in and add repositories for more than say, template folder access by default.
It is also easy to use, so anyone can figure out how to add a repository (file tree).
As for negating the dedicated image manager, not sure. It could definitely be configured as a image-manager repository that is restricted to just the images folder tree. It does have multiple-image upload capabilities without needing to refresh a page...
MooTool File Manager
Runs in a nice modal box ... Also has a image resizer integrated! I have not tried it out just had a play on the demo.
Regards,
Found this page with a few more examples ...
I think KFW is a plugin for FCKeditor and CKeditor ... which could be interesting.
Regards,