Release Version 2.49

Release date: 8 August 2024.

Distribution

Source snapshots are attached to this announcement and the git tag filesender-2.49 contains the base that these snapshots were created from.

Installation

Documentation is available at https://docs.filesender.org/filesender/v2.0/install/

Major changes since 2.48

The database update script DOES need to be run.
The templates directory HAS changed.

Short summary:

Update to the upload graph to used cached data if desired. New index for emails. Some bug fixes.

Details:

help sort by downloads by better recording the count #1891

option to precache values for upload graph #1892

Update filesender.py #1875

aggregate stats: set div to 1 by default #1883

fix ip when $ip[0] doesn't exist #1886

Update known-installs.md #1890

getClientIP() tweaks #1893

Update known-installs.md #1894

build(deps-dev): bump nokogiri from 1.16.3 to 1.16.5 in /docs #1895

Fix mime types #1896

build(deps-dev): bump rexml from 3.2.6 to 3.2.8 in /docs #1900

I think the SQ may have only been for a limited amount of time #1903

ui: option to warn user if session has expired #1905

improve argument checking for filesender.py #1906

update for verp #1907

Update known-installs.md #1912

Only run CI on non-forked repositories #1914

db: add index on TranslatableEmails.token #1918

Limit CI runs on development branches as well #1921

Add parameter to Python client so it can be used without config file #1936

update docs to include information about 3.x #1941

A cherry pick of pr 1934 back to d #1950

Fix range offset calculation #1961

build(deps-dev): bump rexml from 3.2.8 to 3.3.3 in /docs #1962

Fix S3 guests losing transfer settings #1963

Fix S3 guests losing transfer settings #1965

bump in build version number #1966

New ConfigPrivate class and bugfixes #1967

Configuration changes

New configuration directive auth_warn_session_expired and upload_graph_use_cache_table added.

Support and Feedback

Please lodge new github issues for things that might improve the next release!
See Support and Mailinglists or create a Feature requests using Github issues.