PHP 7.4 to 8.2 broke the backend

  • Resolved amanahumpa

    (@amanahumpa)


    4 months, 1 week ago

    To up my PHP version from 7.4 to 8.2, which was prohibited by an outdated and now unsupported theme, I installed Virtue (plus toolkit), which I used some time ago already with success but did not stick to at the time.
    First I edited some pages and the layout, all fine, theme options could be saved at any point. Then I upped the PHP ver. DB is MariaDB btw. Provider is domainfactory.
    From then on when trying to save changed options, I get constantly the error “There was an issue with this action. Try again later or reload the page” or something congruent (browser language is not english).
    Website status suddenly alerted me that plugins can not be updated without FTP credentials, which I never needed since WordPress was discovered. Only Virtue plugins are running in the latest version (3.4.9 for theme, 4.9.8 for the toolkit). Debug mode on gave me hundreds of lines saying dynamic content was deprecated, all pointing to virtue theme files.
    Rollback to PHP 7.4, 8.0 and 8.1 gave no change in the save-options-failure.
    7.4 got rid of the deprecation notice, but saving options is still not an option.
    What Did I break? Did I? How to recover from this?
    Any help would be much appreciated.

Viewing 4 replies - 1 through 4 (of 4 total)

  • Hi there!

    I’d be happy to help you with this.

    I have the following versions on my website:

    • WordPress 6.6
    • Virtue Theme 3.4.9
    • Virtue/Ascend/Pinnacle ToolKit 4.9.8?
    • PHP 8.2.20

    Whenever I change a theme setting, no issues occur – https://share.zight.com/2Nu8D68w

    On the other hand, the issue where WordPress asks for FTP credentials to update plugins is not common and it typically arises from file permission or ownership problems on your server.

    You may ask for help from your hosting provider for them to check:

    • If your wp-content folder has the correct permissions:
      • Directories should have 755 permissions.
      • Files should have 644 permissions.

    Also, try flushing your permalinks to refresh your website’s .htaccess file:

    1. Go to Settings > Permalinks.
    2. Click the “Save Changes” button right away, no need to change anything.

    Lastly, could you check the browser’s console log after trying to save your theme settings? If you see errors logged there, please send a screenshot of it here. This should give us more information of what issue is happening.

    Thread Starter amanahumpa

    (@amanahumpa)

    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.

    Thread Starter amanahumpa

    (@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.

    Thread Starter amanahumpa

    (@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.
Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.