amanahumpa

So I got it sorted out, phew. No manual file copying needed.

Because of reasons a temp folder ran full, this got obvious when using the “cou can update WP manually” (or however that’s put in english), actually the blue button.

Solution was simple then: deleting that folder (plus extending the quota, you never know).
Domainfactory’s thorough investigation did not reveal that the quota is exceeded.

Still my fault, I know.

Thank you very much karlalevelup!

• This reply was modified 4 months ago by amanahumpa.

Domainfactory got back to me with the info that server wise everything is quite slick. Nothing in the logs, all clean. So I guess something shot down some core files. Anyway WP update is not possible, it says that an automatoc update could not be finished. And it keeps asking for FTP credentials.
Seems to be a case of manual re-installing WP. That’ll be tedious ??
And I do not even know where the bug is hiding.

Hi Karlalevelup and thanks for your support and thorough suggestions. That reassures me that I did nothing wrong. At least nothing that I could comprehend.

Rights are set and sound (even with the spontaneous help of a domainfactory engineer), permalinks are flushed, console is basically clean (wow, where do you get THAT nowadays in bigger CMSes), but nothing works anymore. I can’t upgrade WordPress or any plugin for that matter. It seems I lost every right to do anything persistent inside the CMS.

I opted to write domainfactory a very thorough ticket, seems something went wrong when pulling the thing to PHP 8.2. Although it would be premature to put the blame on them, this shouldn’t have happened. And it didn’t in my other ~20 WP projects spread over 5 webhosting companies. Since I did not touch the project for such a long time it may be a legacy thing within their processes.
We’ll see. I’ll keep you updated.

The problem is not solved now but gone anyways.
In the end I deleted the caching and SEO plugins and reinstalled WordPress. If I can reproduce the issue, I will report on it here. The frontend was bye the way not compromised.

Thank you for your efforts and help!

Thanks, man. That did it.
AT LAAAAAST!

??