Feedback on the following chapter: https://www.phplist.org/manual/books/phplist-manual/page/upgrading-a-manual-installation
The page on automatic updating is broken.
Is it possible to perform the automatic updater and database upgrade functions from the CLI?
@simba You’re right, thanks for reporting. Not sure why.
DB upgrade should be possible via CLI. See: https://resources.phplist.com/system/commandline
The Automatic Updater is not yet accessible via CLI.
@anna Can the link https://www.phplist.org/manual/ch031_upgrading.xhtml be redirected to the new page ( https://www.phplist.org/manual/books/phplist-manual/page/upgrading-a-manual-installation ) ?
At the moment users of older versions are directed to a dead link
I’ve changed the aforementioned link in the initial post. Sadly Anna is no longer with phpList.
Hi @Dragonrider thank you for the change but I was more concerned for those that read their older UPGRADE files in the old installation. I had tried to visit the old link as it was mentioned in the old files. If easy enough maybe add an http 301 at apache level on the phplist.org site
2 Likes
You could add a section mentioning other files that can be used to customize an installation, like
- admin/defaultFrontendTexts.php
- texts/language.inc
that will also be replaced using this method.
I did not find out, if those files would be left untouched using the automatic updater. I guessed not, which is why I prefer manual updates. It would be nice though, if their content would be moved to the database like other frontend options.