Download the PHP package alxishin/fm-elfinder-bundle without Composer

FMElfinderBundle

ElFinder integration in Symfony

Code Quality Assurance

TravisCI	Coverage	License	Version

Downloads

elFinder is an open-source file manager for web, written in JavaScript using jQuery UI. Creation is inspired by simplicity and convenience of Finder program used in Mac OS X operating system.

Recommended bundles to use with:

FMTinyMCEBundle	FOSCKEditorBundle	TrsteelCkeditorBundle	FMSummernoteBundle

Table of contents

• Installation
  • Step 1: Installation
  • Step 2: Enable the bundle
  • Step 3: Import FMElfinderBundle routing file
  • Step 4: Securing paths
• Basic configuration
  • Add configuration options to your config.yaml
  • Use multiple upload folder by instance
• CORS support
• Events listeners / subscribers
  • Events
  • Sub requests
• Elfinder Form Type
  • Configuration
  • EasyAdmin 2.x
• CKEditor integration
  • Installation
  • Configuration
• TinyMCE integration
  • Integration with TinyMCE 3
  • Integration with TinyMCE 4
• Summernote integration
• Advanced configuration
  • Custom configuration provider
  • Custom loader
  • Plugins
  • Service as volume driver
  • Flysystem configuration
• Configuration dump

Installation

Step 1: Installation

For Symfony Flex installation you need to enable community recipes:

Install

Copy elfinder assets to public folder

Step 2: Enable the bundle (Optional)

Enable the bundle in the kernel (not needed with symfony flex):

Step 3: Import FMElfinderBundle routing file

Step 4: Configure your application's security.yaml

Secure ElFinder with access_control:

Basic configuration

Add configuration options to your config.yaml

• default - instance of elfinder, can be used to define multiple configurations of ElFinder, allows simultaneous configuration for different types of WYSIWYG editors in your project
• path - define root directory for the files inside web/ directory, default is "uploads". Make sure to set proper write/read and owner permissions to this directory.
• url - url to be prefixed to image path, for displaying. Can be either absolute or relative. If absolute, you can use {homeFolder} string as placeholder which will be replaced automatically. If relative, it will be prefixed with the applications base-url. If left blank, url will be the base-url, append with the value of the 'path' parameter
• driver - can be LocalFileSystem, FTP or MySQL, Flysystem, S3 and etc, check class FM\ElfinderBundle\DependencyInjection\Configuration
• locale - locale determines, which language, ElFinder will use, to translate user interface, default is current request locale
• cors_support - allows cross domain responses handling (default false)
• editor - determines what template to render, to be compatible with WYSIWYG web editor, currently supported options are: "ckeditor" (to use with FOSCKEditorBundle or TrsteelCkeditorBundle), "fm_tinymce" for tinymce4 (to use with FMTinyMCEBundle), "form" for form type, "simple" for standalone and "custom" for custom template. How to configure CKEDitor and TinyMCE to work with this bundle, will be explained further in this document.
• editor_template - define template to render when editor is set to "custom".
• connector - root node for defining options for elfinder root directories.
• roots - define "virtual directories" that reflect directories in your project.
• path_prefix - path prefix with relative_path enabled, default is slash ('/')
• show_hidden - show files and folders that starts from . (dot)
• driver - driver type, LocalFileSystem, Dropbox, FTP
• volume_id - (optional) can be used to force a volume id when mounting volume (default auto-increments). If provided, it must be an integer bigger than 0.
• alias - directory alias
• path - directory that contains files
• upload_allow: ['image/png', 'image/jpg', 'image/jpeg']
• upload_deny: ['all']
• upload_max_size: 2M

You can see the full list of roots options here. To use them, convert camelCased option name to snake_case name.

Use multiple upload folder by instance

You can set multiple upload root folder by instance configuration.

If you have configured your instance with /uploads path, you can provide an additional folder as a home folder (e.g. for a multi-users application) when accessing to the instance URL :

/elfinder/{instance}/{homeFolder} or /efconnect/{instance}/{homeFolder}

For example, accessing to /elfinder/acmeInstance/bob URL will open up elfinder with /uploads/bob as root directory which only contains Bob's files.

Then, accessing to /elfinder/acmeInstance/alice URL will re-use your instance, but open up elfinder with /uploads/alice folder as root directory, containing only Alice's files.

To use this feature, you must provide the instance name in the URL, and of course be sure to set proper write/read permissions on home folders.

Note: this feature is only available with LocalFileSystem driver.

If I want more one home folder is possible ?

Yes you can with this configuration in your fm_elfinder.yaml

where_is_multi: {connector}: {index of the connector} multi_home_folder: true folder_separator: {one char other of /}

Example