Download the PHP package herroffizier/yii2-upload-manager without Composer
On this page you can find all versions of the php package herroffizier/yii2-upload-manager. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package yii2-upload-manager
Yii2 Upload Manager
Yii2 Upload Manager is a small extension that organizes file uploads and takes control over upload paths and urls.
Features
- Groups uploads into folders and folder structures with any depth.
- Divides upload folders into subfolders to avoid storing many files in one folder.
- Fights against file name collisions.
- Uses transparent file name generation mechanism.
- 100% code coverage :-)
Installation
Install extension with Composer:
Add extension to your application config:
There is no need to create upload folder manually. Extension will make it automatically.
Usage
Storing files.
Extension provides few ways to store files.
Simply copy file to upload folder:
Move file to upload folder:
Save raw data as file in upload folder:
Save instance to uplaod foder:
As you may notice, all methods described above return value which is relative path to uploaded file and may be considered as unique upload id.
It can be converted to absolute file by method or to absolute url by method :
Name collisions
By deafult if you'll try to save file that already exists extension will throw an exception. Such behavior is not always suitable and you definitely don't want to solve each collision manually. So you have two different strategies which solve collisions automatically.
First strategy is to overwrite existing file silently. Such approach may be suitable for saving user avatars, for example.
Second strategy is to add incremental index to file name in case of collision. This strategy may be applied when dealing with user file uploads and original file names are important.
Now let's find out how to apply these strategies.
Strategy (throw exception, overwrite, add index) is identified by constant defined in class: , and .
Also both methods and have optional last parameter named to which one of constants may be passed. Default value for is .
To sum up, let's take a look at example. Following code will throw an exception:
Hovewer, this code will work correctly because we applied overwrite strategy:
Now contains string.
Finally, let's apply rename strategy:
This code will also complete correctly and output . As you may see, second file has an index at the end of its name.
