Based on the context, it sounds as if you are updating a plugin and the environment is just not supporting it. If plugins are managed via composer, and you are getting this error, they may be missing due to an incomplete run of your composer install.
You should really check and update your PHP version though if this is failing. even PHP 8.0 is end of life and 8.1/8.2 are on their way out. I’d recommend getting it up to PHP 8.3 so you actually are running a supported version which should also in turn fix his error and get your plugin installed
Hi, thanks for the response. I use WordOps and the latest version of Unbuntu, but I cannot get newer versions of php to install. tried multiple ways
Not sure If I should destroy my server and start a new one from scratch.
The message can be caused by plugins or themes that use Composer to provide an autoloader for their own functions. It is rather not completely thought through by the developer if such a message appears because you can easily prevent it with an option.
You say the plugin that was to blame before is no longer there? Have you also looked in mu-plugins (the must use plugins are there)? And then be sure to check the themes, especially the active theme (the others are not executed).
Your aim should first be to find the cause of the current message. It is not necessary to change hosting or set up a new server. If you have found the cause, I would also recommend that you report the problem to their support so that they can solve it better in a future update.
I use WordOps and the latest version of Unbuntu, but I cannot get newer versions of php to install. tried multiple ways
I use WordOps on Ubuntu 24.04 LTS, and I have multiple sites running PHP 8.3 and 8.4 on the same tiny $5/m server.
Upgrading PHP on WordOps to, say, PHP 8.3 should be as simple as running the command:
wo site update example.com --php83.
Even if you don’t have PHP 8.3 “stack” installed already, this simple command will download and install PHP 8.3, and configure it for the specified site. (Of course, ensure you have up-to-date backup before you run any shell commands.)
If the above command doesn’t work for you, then your WordOps instance is broken somehow… and their community support forum would be the best place to seek help: https://community.wordops.net/
Good luck!
Thanks for the reply. I tried for a longtime to fix it but got a new server.
