Skip to content

Releases: cybex-gmbh/laravel-lodor

Laravel 9

10 Feb 14:51
bbd64e4
Compare
Choose a tag to compare
Laravel 9 Pre-release
Pre-release

What's Changed

  • Add Laravel 9 support by @lupinitylabs in #11
  • Dropped support for Laravel 7
  • Dropped support for PHP 7

Full Changelog: v0.6.0...v0.7.0

v0.6.0

17 Jan 18:51
f2f0c6d
Compare
Choose a tag to compare
v0.6.0 Pre-release
Pre-release

This release adds PHP 8.0 support to laravel-lodor.

On a side node, code coverage had to be disabled due to issues with Travis CI and also phpUnit 8 does not support code coverage generation with PHP 8.0. We cannot upgrade to phpUnit 9 however for backwards compatibility.

v0.5.0

15 Sep 15:57
a66d311
Compare
Choose a tag to compare
v0.5.0 Pre-release
Pre-release

This release introduces breaking changes. Please review carefully before upgrading.

Previously, Lodor would only clean up file chunks automatically. Now, it takes care of cleaning up all files created during an upload, including the upload itself.

If auto_cleanup is set to true and no FileUploaded event listeners are registered, this will lead to immediate cleanup of all files including the final upload itself directly after the upload finishes. To prevent that in a default installation, the default setting for auto_cleanup is now false.
This behavior will only intermediately occur in the 0.5.x release and is due to the upload logic that aimed for moving around files as little as possible. The upcoming 0.6.x release will perform all uploads and merge actions on a temporary disk and then move the finished files over to a permanent upload disk, which will make the handling and cleanup more concise.

Also, the prototype of the cleanupUpload() and removeUploadFiles() methods have changed. The second parameter previously determined whether files associated with a chunked or single upload should be deleted. The new behavior is that both chunked and single uploads are deleted if found, as long as the auto_cleanup and auto_cleanup_chunks configs are true. The obsolete second parameter is now replaced by a force delete that deletes both chunked and non-chunked files regardless of the config settings. This is intended for cleanup of broken uploads.

If you manually called any of these methods, make sure you change your code accordingly.

v0.4.2

13 Aug 14:28
1a01cb4
Compare
Choose a tag to compare
v0.4.2 Pre-release
Pre-release

Minor changes to update the badges in readme.md and composer config after moving laravel-lodor from Bitbucket to GitHub.

v0.4.1

12 Aug 15:17
Compare
Choose a tag to compare
v0.4.1 Pre-release
Pre-release
  • Automatic cleanup can now be switched off by setting the config value lodor.auto_cleanup or the LODOR_AUTO_CLEANUP env setting to false.
  • Lodor will now determine if an upload is chunked or not if the upload config cache entry is missing by looking at the chunk storage disk.