Starting from the time when I was just learning the beauty of web programming, I had the task of creating a file manager for tinyMCE. But reinventing the wheel is a waste of time, so I often get by with some kind of simple implementation or third-party plugin like
this . At that time, Image Manager 1.1 was still a beta version. Unfortunately, over time, this option has ceased to suit me for several reasons and I had to implement my own solution.
Start
I want to bring to your attention a brief overview of
sjFilemanager . The purpose of its implementation was to use on the backend. Let's see what he can do and how he looks like:

- copy / cut / paste files
- delete files / folders
- creating dynamic (unique) file names
- rename files / folders
- change permissions for file / folder
- create folder
- downloading multiple files using SWFUpload
- Downloading files / folders using a zip compressor
- getting all information about a folder / file from the file system
- friendly interface
- ability to perform operations on a group of files / folders
- frontend can work with backend written in any language
- backend is implemented in PHP5 using OOP
- standard cross browser set
- no databases
One of its main advantages is that it is a full-fledged application that can be used in rich-text editors. It is easy to make a
plugin for symfony 1.4 out of it , or you can use it in the usual way (when the user needs to add a picture to the article, then he can either upload it or select it in the file system). You only need to connect the necessary scripts, create a template for the window and configure the manager itself.
What I see cons:
- not fully localized
- no preview for media files
- javascript is written without using known libraries
For example, I will give the pros and cons of other solutions, and you will have to decide what to use.
')
sjFilemanager vs Image Manager
Advantages of Image Manager:
- localization into 2 languages (English, Russian)
- multiboot
- convenient folder navigation, creating / deleting folders
- output file information (in the bottom panel)
- file name change
- summary information about selected files
- automatic insertion of links to the original image (if it is more than the maximum allowed (by default 500px))
- insert image (s) by button insert
Cons Image Manager:
- bad code, it's hard to change something
- virtually no error messages
- the generation of the preview takes a terribly long time in the folder with a large number of drawings
- filenames are unique hashes
- connection of the whole jQuery library
- tabular layout
- this is just a tinyMCE plugin
More detailed information about this plugin can be found
here .
sjFilemanager vs Ajax file manager
Pros of Ajax file Manager:
- support for multiple javascript editors
- fully implemented on AJAX
- built-in picture editor
- utf-8 support
- authorization
- easy to edit and create themes
I was very interested in this option and decided to watch the
demo . After analyzing its capabilities, I realized that this is pure PR.
What are the disadvantages:
- no full support for AJAX (click "Refresh")
- limited opportunities
- the preview is stretched and you can see the pixels
- most written in procedural style
Well, this is the end of my constructive criticism of existing solutions. Learn more about sjFilemanager
here .