Hello everyone, hope all of you are safe and healthy!
A release Candidate for upcoming phpList 3.5.4 is now available for testing.
This release includes several fixes and usability improvements.
Changes to look for
- Clickable link at the top of the click stats page – thanks to @samtuke, see the pull request
- Added HTTP_Request2 as a fallback when curl is not available – thanks to @duncanc, see the pull request for more details.
- Updater menu entry is now shown only for superusers
- The updater handles deletion of broken symlinks
- Help added for the website field on the Settings page and updated help texts about date format and ’ tracking codes – thanks to @duncanc
- Updated default list of TLDs – thanks to @duncanc for pointing it out the problem
- Fixed incorrect statistics link in German installations, due to incorrect translation see mantis issue – please consider that fetching translations won’t fix the issue for now. It’s the update itself that uses the corrected version. Thanks to @jimbocity for reporting it.
- Fixed broken link in the Install file – thanks to Hiroyuki Sato
- Changed config value for "$database_host " from ‘localhost’ to ‘dbhost’ – enabling a default setup that works with a DB that is not on the same machine
If you have experienced issues with previous installations please install this update and see if those issues are resolved.
Download the Release Candidate here (see also ‘Upgrading’).
Upgrade from releases older than phpList 3.3.7-RC1 following the usual upgrade process
Use the Automatic Updater if you are running phpList 3.3.7 or later.
Use your phpList as normal, and report any new problems that you find.
Activating the REST API
If you haven’t checked the REST API yet, you can see the dedicated chapter in the manual to help you get started with it: API and Integrations
Report any issues you find with phpList3 to the phpList Bugtracker, selecting “3.5.4-RC1” as the Product Version.
Use the usual bug fixing process if you know how to fix it.
Please read the contribution guide on how to contribute and how to run the unit tests and style checks locally.