phpList 3.6.16 Upgrade - Issues

When I went through the long way of updating my installation from 3.6.15, I noticed that the entire interface now looks very different–also, there was no database updated needed–it said my 3.6.15 database was up to date, even though I downloaded the 3.6.16 files and logged in with the new version.

Another issue was that the CKEditor was available, and I could not edit html, nor could use “view source” and paste an html email into a new campaign.

What is up with this new update?

It appears that there is an issue with this package:
https://github.com/phpList/phplist3/archive/refs/tags/v3.6.16.tar.gz

I reinstalled this package and it worked fine:
https://sourceforge.net/projects/phplist/files/phplist/3.6.16/phplist-3.6.16.tgz

Please double check this so others won’t have my issue.

I don’t know what is going on with phpList, but the download page states: “phpList version 3.6.15 is the latest stable release.” The 3.6.16 release notes say “You can get the latest version of phpList directly from GitHub or SourceForge” but the 3.6.15 release notes on GitHub state “Archives downloaded from GitHub are for development only and are incomplete for production use.”

If 3.6.16 is a real release that we should consider using, it has been horribly managed. I do not trust it, and it undermines my trust in the overall project.

Is phpList really maintained anymore? Or is it time to move on?

@Crenel84 I think that there is a problem in keeping all the documentation up to date when a new release is made.

You should install only from Sourceforge, not from GitHub, or use the automatic updater or the Updater plugin. 3.6.16 is indeed a real release.

1 Like

As @Crenel84 mentioned, the only “documentation” I see when there is a new version available is the link in my ACP telling me an upgrade is available, which leads me to “You can get the latest version of phpList directly from GitHub or SourceForge.” It seems like a trivial task to remove the link and mention of GitHub there, which would save people the 2 hours I wasted trying to figure out that the GitHub files load some bizarre version I’ve never seen before.

2 Likes

I finally had time to do this today. Went to Sourceforge, and it downloaded 3.6.14.zip. Followed the exact same steps again and it downloaded 3.6.16.zip.

Confusing and troubling. At least I have it… I think? No way to check integrity that I can see. This is not conducive to trusting the file.

Consider this a vote for a different method of distribution, I guess, and a note for anyone else who gets the wrong file to keep trying until the right version is downloaded.

2 Likes