<![CDATA[ time to replace FCKEditor file browser? - My Forums]]> https://forums.modx.com/thread/?thread=45659 <![CDATA[Re: time to replace FCKEditor file browser?]]> https://forums.modx.com/thread/45659/time-to-replace-fckeditor-file-browser#dis-post-264217
Jeff]]> Bravado Jul 13, 2007, 10:42 AM https://forums.modx.com/thread/45659/time-to-replace-fckeditor-file-browser#dis-post-264217 <![CDATA[Re: time to replace FCKEditor file browser?]]> https://forums.modx.com/thread/45659/time-to-replace-fckeditor-file-browser#dis-post-264216 Quote from: Bravado at Jul 13, 2007, 01:48 PM

But I don’t want to implement it with any sort of mucking around with file and folder permissions.
I agree this sounds like a good approach, but how are you going to secure those resources from the web server if you do not "muck" around with file and folder permissions in some way?]]> opengeek Jul 13, 2007, 09:48 AM https://forums.modx.com/thread/45659/time-to-replace-fckeditor-file-browser#dis-post-264216 <![CDATA[Re: time to replace FCKEditor file browser?]]> https://forums.modx.com/thread/45659/time-to-replace-fckeditor-file-browser#dis-post-264215
But I don’t want to implement it with any sort of mucking around with file and folder permissions. That’s just asking for trouble when it comes to your novice users. I figure that either a user has full access, read-only access, or no access at all to any given share. And the chances of a user needing to move files between shares are pretty much slim to none. The whole share concept is driven with the idea that users organize their files based on the task at hand.

That’s kind of how I’m envisioning it for now. smiley

Jeff]]> Bravado Jul 13, 2007, 08:48 AM https://forums.modx.com/thread/45659/time-to-replace-fckeditor-file-browser#dis-post-264215 <![CDATA[Re: time to replace FCKEditor file browser?]]> https://forums.modx.com/thread/45659/time-to-replace-fckeditor-file-browser#dis-post-264214 chucktrukk Jul 13, 2007, 02:43 AM https://forums.modx.com/thread/45659/time-to-replace-fckeditor-file-browser#dis-post-264214 <![CDATA[Re: time to replace FCKEditor file browser?]]> https://forums.modx.com/thread/45659/time-to-replace-fckeditor-file-browser#dis-post-264213
I think the thing I’m not sure about is how it would integrate into the flow of what we’re aiming to do with MODx. I really would like to see a way of having permission sets for different shares. That way you could have dedicated user folders for different web users and manager users and, if needed, allow for manager users to access specific global shares as well. Extplorer seems to be more geared as a sort of Explorer-like way of managing files and directories on a server without the need of using an FTP client...which is great if that’s the sort of thing you really need. But not so great when you need to be concerned with security and what users can and can’t do on a server.

I would still rather do it from scratch simply because I’m also thinking we need some API features to allow for writing plugins and such. wink

Jeff]]> Bravado Jul 12, 2007, 04:07 PM https://forums.modx.com/thread/45659/time-to-replace-fckeditor-file-browser#dis-post-264213 <![CDATA[Re: time to replace FCKEditor file browser?]]> https://forums.modx.com/thread/45659/time-to-replace-fckeditor-file-browser#dis-post-264212 chucktrukk Jul 12, 2007, 03:55 PM https://forums.modx.com/thread/45659/time-to-replace-fckeditor-file-browser#dis-post-264212 <![CDATA[Re: time to replace FCKEditor file browser?]]> https://forums.modx.com/thread/45659/time-to-replace-fckeditor-file-browser#dis-post-264211
We’re looking at using a combo of Mootools and Ext to do the job. Looks like someone is almost done with a great file tree widget for Ext (http://ajaxian.com/archives/ext-file-tree-widget). And since Mootools and Ext are already bundled into MODx, all we have to do is write a solid file browser using something like the new file tree widget and we’ll have it made. The great thing about this approach is that since most of the javascript libraries will be cached when the manager is loaded the total footprint will be much much lower when the file browser is called. This is pretty much the primary reason why I’m against using anything that doesn’t utilize the libraries we’ve chosen to use in MODx. Not only that but we have alot of ideas for adding user-based security and folder features. This is so much easier to do when writing from scratch. As much as I’d like to just hack an existing app and call it a day...I just haven’t found anything that fits the bill just yet. However, with the file tree widget shows a ton of promise so we’re getting very close to a solution here. smiley

Jeff

]]> Bravado Jul 12, 2007, 03:37 PM https://forums.modx.com/thread/45659/time-to-replace-fckeditor-file-browser#dis-post-264211 <![CDATA[time to replace FCKEditor file browser?]]> https://forums.modx.com/thread/45659/time-to-replace-fckeditor-file-browser#dis-post-264210 http://extplorer.sourceforge.net/
]]> mmjaeger Jul 12, 2007, 07:26 AM https://forums.modx.com/thread/45659/time-to-replace-fckeditor-file-browser#dis-post-264210