Release Notes Version 3.3.x
Version 3.3.9 (released 2019-05-06)
- Added setting to set File Request expiration.
- Added emaildrop private message option.
- Added use download Content-Type setting.
- Added setting to disable IPv6.
- Added FTPdir overwrite protection setting.
Version 3.3.8 (released 2019-05-01)
- Fixed a problem where Filedrops was sometimes not sending download receipts.
- Fixed a problem where Shares Read-Only permissions was sometimes not enforced.
- Fixed SAML authentication when the default LDAP group is set to not login.
- Fixed a problem with LDAP authorization using shortname as user id.
- Cleaned up search and ordering for Message, Attachment and Download pages.
- Updated Content-Type client side detection.
- Use full text indexing of Messages.
Version 3.3.7 (released 2019-04-23)
- Show a not found page instead of redirect for invalid Filedrops.
- System Filedrops are now case insensitive.
- FTPdrop logins are now case insensitive
- Fixed a problem where User Filedrops wasn't working unless a Filedrop max file size was configured.
- Updated message authorization log.
- Updated weekly and daily maintenance with better logging of attachment id's.
- Fixed a problem where sometimes files added before v3.3.x would sometimes show up as unavailable.
- Fixed a problem where Maps wasn't being displayed properly.
- Fixed wrong download URL for API.
- Message size and message filename is not sortable (Admin → Data → Messages)
Version 3.3.6 (released 2019-04-11)
- Fixed a problem uploading files for secondary domains.
- Fixed a CSRF problem for reverse proxies going from HTTPs to HTTP.
- Update to the latest stable version of Rails.
Version 3.3.5 (released 2019-04-09)
- Added FileLink password function
- Added Download API.
- Fixed Filedrop max size check.
- Various fixes relating to mixed case email addresses.
Version 3.3.4 (released 2019-04-03)
- Use case insensitive matching for Filedrops.
- Fixed a problem with case-sensitive emails when retrieving API keys.
- Fixed a problem using chunked uploads to attachments.
- Added CSV export to the Admin → Activity Log.
- Don't allow admins to access messages from Admin → Data → Attachments if amdin access to data has been disabled.
- Fixed a problem with custom Favicons.
- Fixed a problem in Microsoft Edge that would update the Access Permission when disabled.
Version 3.3.3 (released 2019-03-26)
- Fixed an issue using non-standard ports.
- Fixed a problem with the message expiration.
- Fixed an issue with the expiration introduced in v3.3.2.
Version 3.3.2 (released 2019-03-26)
- Fixed expiration expires after calculation.
Version 3.3.1 (released 2019-03-25)
- Fixed the authorization checkboxes when default authentication is set to not require authentication.
- Redirect on the home screen if not using the correct public hostname.
- Added port numbers to public hostname.
- Return better API error messages for disabled features.
- Load the autocomplete dropdown above the html editor header toolbar.
- Fixed viewing the inbox with mixed case email addresses.
- Fixed a problem upload 0 byte files.
- Permit content-types with comma and spaces.
- Security: Updated Ruby on Rails to fix CVE-2019-5418.
Version 3.3.0 (released 2019-03-19)
- Version 3.3.0, please see the major change list below to see what's changed since v3.2.x.
Major changes from version 3.2 to version 3.3
- Database change MySQL/MariaDB → PostgreSQL. The database change itself should be transparent but should give stability improvements and will provide other intermal improvements.
- Removal of the search engine. The search engine that's been present between LiquidFiles v2.3 and v3.2 has been removed. We've been struggling with the search index getting corrupted, the search engine causing upload failures and similar issues. Searching will now be powered by internal functions in PostgreSQL and while database searching is not as fast and as flexible as when using a dedicated search engine, we believe it's fast and flexible enough for LiquidFiles.
- Added ActionScripts — Scriptable functions to automatically execute scripts when a file has been delivered to a user, when a file has been uploaded to a share or when sending a message, and for password validation.
- Added SMS Two-Factor Authentication.
- Added Delete Expires After to leave expired attachments on the system for a period of time, defaults to 7 days.
- Added a function to limit FTP Masquerading to non-local IP addresses.
- Added Settings in Admin → Groups to Enable or Disable Admins ability to access users messages and download attachments.
- Added Settings in Admin → Groups to Enable or Disable logging when Admins download a users attachments.
- Added Email Bcc all function.
- Updated the File Request view to be able view and delete File Requests.
- Reworked the Public URL settings to make it clearer between the local hostname and the Public URL. We now force setting a Public URL for the LiquidFiles system which should remove some confusion of what the URL is set in email sent and so on. The Public URL will be set from the Email Base URL if configured, and the system hostname if the Email Base URL is not set.
- Enabled HTTP/2 — HTTP/2 is supported in all modern browsers and will give performance improvements, both over longer distances and in local environments.
- Added binary uploads — when sending files with the web interface and our clients, files are uploaded in binary format rather than html form-based uploads. This should give perfomance improvements.
- Lots of added user interface caching that will make the LiquidFiles user interface a lot faster for users and admins.
- Added support for TLS v1.3 and made TLS v1.3 & TLS v1.2 only the default network protocol requirement.
- Updated versions of Ruby on Rails and lots of internal libraries updates and changes.
Deprecations between v3.2 and v3.3
HTML4 uploads — IE9 and below
Due to underlying changes, it was no longer possible to support HTML4 uploads, which pretty much means that Internet Explorer 9 and below can no longer upload files. After installing LiquidFiles v3.2.51 and later, you will be required to use a HTML5 compliant browser, Internet Explorer 10 and later, Chrome, Firefox, Safari or others.