Easy ajax file uploads for Symfony 2. MIT License.
Inspired by punkave/symfony2-file-uploaderbundle (no longer maintained)
This bundle provides enhanced file upload widgets based on the BlueImp jQuery file uploader package. Both drag and drop and multiple file selection are fully supported in compatible browsers.
The uploader delivers files to a folder that you specify. If that folder already contains files, they are displayed side by side with new files, as existing files that can be removed.
The bundle can automatically scale images to sizes you specify. The provided synchronization methods make it possible to create forms in which attached files respect "save" and "cancel" operations.
Make sure that jQuery is included in your html document:
<script src="https://ajax.googleapis.com/ajax/libs/jquery/2.1.3/jquery.min.js"></script>Make sure that Underscore.js is included in your html document
<script src="//cdnjs.cloudflare.com/ajax/libs/underscore.js/1.7.0/underscore-min.js"></script>Open a command console, enter your project directory and execute the following command to download the latest stable version of this bundle:
$ composer require locaine/lcn-file-uploader-bundle "~1.1"This command requires you to have Composer installed globally, as explained in the installation chapter of the Composer documentation.
Then, enable the bundle by adding the following line in the app/AppKernel.php
file of your project:
<?php
// app/AppKernel.php
// ...
class AppKernel extends Kernel
{
public function registerBundles()
{
$bundles = array(
// ...
new Lcn\FileUploaderBundle\LcnFileUploaderBundle(),
);
// ...
}
// ...
}If you need to upload files to not yet persisted entities (during creation) then you need to deal with temporary editIds which makes things a little bit more complicated.
In this example, we assume that you want to attach one or more uploaded image files to an existing entity.
The LcnFileUploader needs a unique folder for the files attached to a given entity.
Fetching $entity and validating that the user is allowed to edit that particular entity is up to you.
<?php
namespace Lcn\FileUploaderBundle\Controller;
use Symfony\Bundle\FrameworkBundle\Controller\Controller;
use Symfony\Component\HttpFoundation\Request;
use Symfony\Component\HttpKernel\Exception\AccessDeniedHttpException;
class DemoController extends Controller
{
...
/**
* Edit Uploads for the given entity id
*
* In a real world scenario you might want to check edit permissions
*
* @param Request $request
* @param $entityId
* @return \Symfony\Component\HttpFoundation\RedirectResponse|\Symfony\Component\HttpFoundation\Response
*/
public function editAction(Request $request, $entityId)
{
$editId = intval($entityId);
if ($editId < 100000000000) {
throw new \Exception('invalid editId');
}
$fileUploader = $this->container->get('lcn.file_uploader');
$uploadFolderName = $this->getUploadFolderName($editId);
$form = $this->createFormBuilder()
->setAction($this->generateUrl('lcn_file_uploader_demo_edit', array('entityId' => $entityId)))
->setMethod('POST')
->getForm();
if ($request->getMethod() == 'POST') {
$form->submit($request);
if ($form->isValid()) {
$fileUploader->syncFilesFromTemp($uploadFolderName);
return $this->redirect($this->generateUrl('lcn_file_uploader_demo_show', array('entityId' => $entityId)));
}
} else {
$fileUploader->syncFilesToTemp($uploadFolderName);
}
return $this->render('LcnFileUploaderBundle:Demo:edit.html.twig', array(
'entityId' => $entityId,
'form' => $form->createView(),
'uploadUrl' => $this->generateUrl('lcn_file_uploader_demo_handle_file_upload', array('entityId' => $entityId)),
'uploadFolderName' => $uploadFolderName,
));
}
/**
* Store the uploaded file.
*
* In a real world scenario you might probably want to check
* if the user is allowed to store uploads for the given entity id.
*
* Delegates to LcnFileUploader which implements a REST Interface and handles file uploads as well as file deletions.
*
* This action must not return a response. The response is generated in native PHP by LcnFileUploader.
*
* @param Request $request
* @param int $userId
*/
public function handleFileUploadAction(Request $request, $entityId)
{
$entityId = intval($entityId);
if ($entityId < 100000000000) {
throw new AccessDeniedHttpException('Invalid edit id: '.$entityId);
}
$this->container->get('lcn.file_uploader')->handleFileUpload(array(
'folder' => $this->getUploadFolderName($entityId),
//'max_number_of_files' => 1, //overwrites parameter lcn_file_uploader.max_number_of_files
//'max_file_size' => null //overwrites parameter lcn_file_uploader.max file size
//'allowed_extensions' => array('zip', 'rar', 'tar', 'gz'), //overwrites parameter lcn_file_uploader.allowed_extensions
//'sizes' => array('thumbnail' => array('folder' => 'thumbnail', 'max_width' => 100, 'max_height' => 100, 'crop' => true), 'profile' => array('folder' => 'profile', 'max_width' => 400, 'max_height' => 400, 'crop' => true)), //overwrites parameter lcn_file_uploader.sizes
));
}
/**
* Get the upload folder name for the given entity id.
* This is where the uploaded files will be persisted to.
*
* @param $id
* @return string
*/
private function getUploadFolderName($id)
{
//include two characters of hash to avoid file system / operating system restrictions
//with too many files/directories within a single directory.
return 'demo/' . substr(md5($id), 0, 2) . '/' . $id;
}
...
}You can skip this step if you are using LcnIncludeAssetsBundle.
Include these stylesheets and scripts in your html document:
<link rel="stylesheet" href="{{ asset('bundles/lcnfileuploader/dist/main.css') }}">
<link rel="stylesheet" href="{{ asset('bundles/lcnfileuploader/dist/theme.css') }}">
<script src="{{ asset('bundles/lcnfileuploader/dist/main.js') }}"></script>Or you can use assetic in your twig template:
{% extends 'base.html.twig' %}
{% block stylesheets %}
{{ parent() }}
<link rel="stylesheet" href="{{ asset('bundles/lcnfileuploader/dist/main.css') }}">
<link rel="stylesheet" href="{{ asset('bundles/lcnfileuploader/dist/theme.css') }}">
{% endblock %}
{% block javascripts %}
{{ parent() }}
<script src="{{ asset('bundles/lcnfileuploader/dist/main.js') }}"></script>
{% endblock %}The exact position and order does not matter. However, for best performance you should include the link tags in your head section and the script tag right before the closing body tag.
====================
Now include the upload widget anywhere on your page:
{% include 'LcnFileUploaderBundle:Theme:lcnFileUploaderWidget.html.twig' with {
'uploadUrl': uploadUrl,
'tempUploadFolderName': tempUploadFolderName,
'formSelector': '#lcn-file-uploader-demo'
} %}Full example:
{{ form_start(form, { 'attr': { 'id': 'lcn-file-uploader-demo' } }) }}
{{ form_errors(form) }}
{% include 'LcnFileUploaderBundle:Theme:lcnFileUploaderWidget.html.twig' with {
'uploadUrl': uploadUrl,
'uploadFolderName': uploadFolderName,
'formSelector': '#lcn-file-uploader-demo'
} %}
{{ form_rest(form) }}
</form>You can easily obtain a list of the names of all files stored in a given folder:
$fileUploader = $this->container->get('lcn.file_uploader');
$filenames = $fileUploader->getFilenames('demo/' . $entity->getId()));However, there is a performance cost associated with accessing the filesystem. If you run into performance problems you might want to keep a list of attachments in a Doctrine table or some cache layer.
You can easily obtain a list of urls of all files stored in a given folder:
$fileUploader = $this->container->get('lcn.file_uploader');
$fileUrls = $fileUploader->getFileUrls('demo/' . $entity->getId());However, there is a performance cost associated with accessing the filesystem. If you run into performance problems you might want to keep a list of attachments in a Doctrine table or some cache layer.
If you are dealing with image uploads, you can pass a defined size name:
$fileUploader = $this->container->get('lcn.file_uploader');
$fileUrls = $fileUploader->getFileUrls('demo/' . $entity->getId(), 'thumbnail');The image sizes are defined as lcn_file_uploader.sizes parameter:
# Define sizes for image uploads
lcn_file_uploader.sizes:
# Depending on your further requirements, you might want to define additional image sizes.
# For advanced image resizing and optimization, you can also configura an image proxy.
# required: "thumbnail"
thumbnail:
folder: thumbnail
max_width: 200
max_height: 150
crop: true
# optional: "original" - define original image size if you want to restrict the maximum image dimensions:
original:
folder: original
max_width: 1000
max_height: 1125
crop: falseFor advanced image resizing and optimization, you can optionally configure an image proxy (e.g.imgix.net).
# Define sizes for image uploads
lcn_file_uploader.sizes:
avatar:
folder: null #do not store locally - pipe original size through defined proxy
max_width: 300
max_height: 300
proxy:
enabled: %lcn_file_uploader.image_proxy_enabled%
url: https://my-source.imgix.net~imageUrl~
parameters:
w: ~max_width~
h: ~max_height~
fit: crop
crop: faces
...imageUrl gets replaced with the url to the uploaded image source.
The parameters array is used to pass additional query string parameters.
max_width and max_height get replaced with the corresponding values defined for the given image size.
If you are using an image proxy, you can remove the folder setting if you do not want to store the resized version on your own disk at all. However, the "original" and "thumbnail" sizes still need a folder setting!
Important: You also need to explicitly enable the image proxy using the parameter lcn_file_uploader.image_proxy_enabled:
parameters:
...
lcn_file_uploader.image_proxy_enabled: true
...This is especially helpful if you only want want to leverage the proxy in prod environments.
You can specify custom file types to divert from the default ones (which are defined in Resources/config/services.yml) by either specifying them in your handleFileUploadAction method or in parameters.yml.
Per Widget in corresponding handleFileUploadAction: $this->get('lcn.file_uploader')->handleFileUpload(array( 'folder' => 'temp-lcn-file-uploader-demo/' . $editId, 'allowed_extensions' => array('zip', 'rar', 'tar') ));
Globally in parameters.yml: If you have the Symfony standard edition installed you can specify them in app/config/parameters.yml:
file_uploader.allowed_extensions:
- zip
- rar
- tar
When an entity gets deleted you should delete all of the attachments, as well.
You can do this as follows:
$this->get('lcn.file_uploader'')->removeFiles(array('folder' => 'lcn-file-uploader-demo/' . $entity->getId()));
You probably might want to do that in a doctrine lifecycle preRemove event listener.
You should make sure that the temporary files do not eat up your storage.
The following Command Removes all temporary uploads older than 120 minutes
app/console lcn:file-uploader:cleanup --min-age-in-minutes=120You might want to setup a cronjob that automatically executes that command in a given interval.
This Bundle comes with three predefined FileNamer-Services:
- Sanitize: Make file names url-friendly (Default)
- Original: Use original file names as uploaded
- Hash: generate hash based on the original filename
You can define the FileNamer in the service definition:
...
services:
lcn.file_uploader:
class: Lcn\FileUploaderBundle\Services\FileUploader
arguments:
- file_namer: '@lcn.file_uploader_file_namer_sanitize'
...app/Resources/views/Form/lcnFileUploaderWidget.html.twig:
{% extends 'LcnFileUploaderBundle:Theme:lcnFileUploaderWidget.html.twig' %}
{% block lcnFileUploaderWidget %}
{# customize as needed #}
{{ parent() }}
{% endblock %}
{% block lcnFileUploaderTemplate %}
{# customize as needed #}
{{ parent() }}
{% endblock %}
{% block lcnFileUploaderFileTemplate %}
{# customize as needed #}
{{ parent() }}
{% endblock %}in your edit.html.twig:
{% include ':Form:lcnFileUploaderWidget.html.twig' with {
'uploadUrl': uploadUrl,
'uploadFolderName': uploadFolderName,
'formSelector': '#lcn-file-uploader-demo'
} %}Most of the options can be configured by overriding the parameters defined in Resources/config/services.yml in this bundle.
This bundle accesses the file system via the glob() function. It won't work out of the box with an S3 stream wrapper.
Syncing files back and forth to follow the editId pattern might not be agreeable if your attachments are very large. In that case, don't use the editId pattern. One alternative is to create objects immediately in the database and not show them in the list view until you mark them live. This way your edit action can use the permanent id of the object as part of the folder option, and nothing has to be synced. In this scenario you should probably move the attachments list below the form to hint to the user that there is no such thing as "cancelling" those actions.