phpList 3.4.1 is the first update of 3.4.0 and incorporates changes both to the REST API and the Automatic Updater. Use the Automatic Updater to get it, or see the Download page for full installation and upgrade instructions.

Changes in this release

Automatic Updater Changes

• The Automatic Updater no longer removes plugin files during the update process. Instead they are moved to a temporary location and then restored. Please note that updates from phpList 3.4.1. to 3.4.2 will be the first occasion when the new Automatic Updater is used (as each update uses the Automatic Updater of the previous release). Therefore automatic updates from phpList 3.4.0 to 3.4.1 will still require re-installation of plugin files.
• Update “maintenance mode” queries to respect the database $table_prefix, to resolve issues with installations using custom database table prefixes and the Automatic Updater.
• Information about professional community support and phplist.com hosting is now shown during the Automatic Update process.

REST API Changes

• This update replaces the API access URL with a shorter one e.g:
  • Base URL: http://example.com/lists/api/v2/
    Authentication: http://example.com/lists/api/v2/sessions
  • Please make sure to have htaccess file support enabled and Apache mod_rewrite enabled
  • The old access URLs like this have been depreciated: http://example.com/lists/base/public/api/v2/
  • For system requirements and usage information see the phpList manual: API and Integrations
• A simple example of a REST API client written in PHP is available in the RestAPIclientSimpleExample repository

Fixes

1. Fixed blank public pages error introduced on the previous update to jQuery 3.3.1, due to stored reference to the old jQuery scripts in the footer of public page templates.
   Both the footer value of individual subscribe pages and the default pagefooter value on the config table are now updated to use the correct filename. The jQuery filenames no longer include the version number in order to avoid the problem recurring in the future.
2. Make the organisation name accessible via [ORGANISATION_NAME] placeholder, usable within campaign templates and campaign content.
3. Use the correct variable for the custom forward footer when forwarding campaigns — thanks to forum user @nicomars for reporting and @Duncan for implementing the fix. See the pull request.
4. Select the “System template” template by default on the ‘Default templates suite’ page.

Other:

1. Update the Readme file on phpList3 repository to state other repositories needed for properly running a local development copy of phpList.
2. Add and update documentation on the new and updated placeholders. Documentation of all placeholders can be found in the Resources Wiki.

Community-made

This release is the work of Duncan Cameron and other Open Source community members who have submitted bug reports and valuable feedback, as well as phpList Ltd. developers. To get involved in phpList development, check out the developer resources pages.

Report any issues you find with phpList 4 core or REST API  to the corresponding repo on GitHub. Please read the contribution guide on how to contribute to these modules.

Support

Need help upgrading your phpList server to the newest version? Ask the community at discuss.phplist.org. Professional support from community experts, as well as manuals, source code, and developer resources, can be found at phplist.org. Report all bugs to the bugtracker!

Want to focus on campaigns and forget hosting headaches? Sign up at phplist.com for an account with everything included. Send from 300 free messages to 30 million messages per month — simple.