-
[ ]
I’m using stock docker compose setup, unmodified. -
[ ]
I’m using docker compose setup, with modifications (modified.yml
files, third party plugins/themes, etc.) - if so, describe your modifications in your post. Before reporting, see if your issue can be reproduced on the unmodified setup. -
[ ]
I’m not using docker on my primary instance, but my issue can be reproduced on the aforementioned docker setup and/or official demo. -
[X]
I’m running tt-rss in host mode on a shared hosting.
I hope it’s still ok to ask for support for host mode (i.e. non-docker) installations. Before posting, to avoid wasting everyone’s time, I’ve tried to spin a fresh installation of tt-rss on the same environment on a different subdomain to make sure that everything works as intended in my environment, and indeed it does. The problem below is only related to my particular install and upgrade, it’s not a general issue with the installation environment.
Until yesterday I was running a very old version of tt-rrs on a DreamHost shared hosting (schema was v. 140, the config file still had define() rather than putenv() - that old). As I’m now forced to update the environment to php 8.1 and the old install didn’t work with it, I’ve tried to update tt-rss to the latest version. I’ve updated the git repo (git pull origin master), modified the config file to the new definitions using putenv(), and I’ve run the --update-schema script. After the upgrade surprisingly things didn’t explode, but I have an annoying issue.
I have the af_comics plugin enabled and after the upgrade the website opened up in safe mode (although I didn’t enable safe mode) and the cron job failed to update feeds, with the following error on each of them:
Declaration of Af_Feedmod::hook_prefs_tabs($args) must be compatible with Plugin::hook_prefs_tabs()
If I disable the af_comics plugin in the preferences, log out, enable safe mode on next log in, log out, log in again without safe mode everything works correctly, except of course the features of af_comics are not there anymore.
What can I do to make this error go away and keep using the plugin?
As I said, everything works correctly in a fresh install, so it’s not something quite reproducible by others as it’s tied to this particular upgrade. However, I’m happy to provide a dump of the mysql database and of the config file if it can help to reproduce the issue in a different environment.
- Tiny Tiny RSS version: schema 147; git commit id: cddbf5bf5a7e2c433275a3bec089f318d4f211af
- Platform versions: DreamHost shared hosting (8.0.28-0ubuntu0.20.04.3); PHP 8.1.9; mysql/mariadb Ver 14.14 Distrib 5.7.41 (I think)