3.6.13 Release Candidate ready for testing

šŸ’» Development
,
1

Hi everyone,

A Release Candidate for the upcoming phpList 3.5.13 is now available for testing.

You can get a copy of the RC version from GitHub or SourceForge .

Changes to look for

  1. Allow a plugin to update phpList. Identify whether a plugin is able to update the phpList code, and link to that pluginsā€™s update page when a new release is available. See Pull Request #946.

  2. On Pull Request #926, we used the <wbr> element immediately after a character where we want to allow wrapping. Copying/pasting an email address includes only the characters of the email address, not the <wbr> element. Specifically:

  • changes the shortenTextDisplay() function to handle only text fields
  • adds a similar shortenEmailDisplay() function which uses the <wbr> element
  • adds a similar shortenUrlDisplay() function which uses the <wbr> element
  • replaces the uses of shortenTextDisplay() for email or URL fields by the new functions
  1. Make the results of the timer class use period as the decimal point to avoid failing calculations. See Pull Request #931.
  2. Set DEFAULT_MESSAGE to 8 days so that repeated campaigns donā€™t expire. See Pull Request #932.
  3. Allow a gap between async requests. Check out the Resources Wiki for additional documentation. See Pull Request #937.
  4. Update the Common, CKEditor, and Segment plugins. See Pull Request #951.
  5. Use the content of the body element when including a message in a template. See Pull Request #938.
  6. Pull Request #935 includes several commits that tidy-up the output of processqueue. Specifically:
  • Fix the processQueueOutput() function in several places
  • Replace $GLOBALS[ā€˜I18Nā€™]->get() by s()
  • Replace a few uses of a call to sprintf() wrapping s()
  1. Minor changes to avoid warning on PHP 8.2. See Pull Request #930.
  2. Remove unused files. See Pull Request #936.

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 4 .

Reporting issues

Report any issues you find with phpList3 RC to the phpList3 GitHub repository, selecting ā€œrelease candidateā€ in the Labelsā€™ dropdown menu.

Use the usual bug fixing process if you know how to fix it.

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 and how to run the unit tests and style checks locally.

Happy testing!

Mariana

2

Just to expand on some of these changes.

1 This release includes a new plugin, the Updater plugin. This change is to link to that plugin when displaying a message that a new release of phplist is available, instead of linking to the current automatic updater.

2 Currently, copying an email address from some statistics pages then pasting that value to search for the subscriber does not work.

If you copy an email address from the Open Statistics page, that includes a zero width space character immediately
after the @ character. That character was added to allow the browser to break the email address at that point to improve the layout on a narrow device.
This means that the email address that is visible is not the same as that used for searching after pasting into a search field.

The new change is to use the html <wbr> element instead of a zero width space. That element is specifically designed to allow the browser to break at that point, and is not included when copying/pasting the email address.

3 This change fixes a problem that occurs with php 8 and using a locale that has comma as the decimal point. The problem causes phplist to fail after sending the first email of a batch.

5 This change is to improve a change in phplist 3.6.12 that displays the subscriber counts for each list asynchronously on the Lists page. That change leads to a stream of requests that can be rejected by the web server with 403.

The new change is to add a configurable delay between sending the requests for subscriber counts.

1 Like
3

There is a special procedure for installing Release Candidates versions?

After installing the 3.6.13-RC1 all my plugins show as disabled as they canā€™t figure out the version number and the version reported in the footer of the admin page is ā€œvdevā€
If I didnā€™t follow the correct procedure, I apologize, but I couldnā€™t find particular indications in the documentation

Thank you for the support

4

@Enrico Did you download from Sourceforge? Iā€™m not sure that the download from Github works properly.

5

You are right! The github package is much smaller and has an empty plugins folder, even the user interface itā€™s not the same.

Thank you, i can continue testing.

6

A second (Release Candidate) RC for version 3.6.13 was published featuring one change.

Download RC:

Change on this RC: