• Resolved westaubrey

    (@westaubrey)


    Hi,

    Since the latest update, I get an error (“There has been a critical error on your website”) whenever I try to open the WordPress Dashboard with GiveWP enabled. When I manually disable GiveWP the site functions as normal with all other plugins enabled.

    I have looked through documentation, and the bugs page, but am at a loss. Any advice on how to get this back up and running?

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter westaubrey

    (@westaubrey)

    I was able to roll it back to version 3.0.1 and the dashboard is working now, just obviously showing that my GiveWP is out of date. Let me know if you need more info.

    Plugin Support David G. Johnson

    (@haveanepiphany)

    Hi @westaubrey,

    Happy to help here. Glad you were able to roll back to 3.0.1 and get to your dashboard!

    I’m working to investigate this and see if I can replicate the error somehow. By any chance are you using the Elementor page builder? I looked at your site and don’t see evidence of it, but we are working on a known issue that involves Elementor so I just wanted to confirm.

    One thing that would be a huge help so that we can diagnose what happened on your site would be the details for the error you encountered. The “There has been a critical error on your website” message is a WordPress system-generated error message that means something has caused a PHP fatal error. Whenever you see that message, it means that a more detailed error log has been sent to the main admin email address (which you can configure at Settings > General in the main WordPress settings).

    Check that email, and then pass along any error messages you are getting, and we’ll be able to help.

    If you did not receive an email or if you don’t have access to it, your site’s PHP error logs for today should contain the details.

    (If you don’t know how to get error logs you can use the Fatal Error Notify plugin, but after activating it you’ll have to trigger the error again to see it. This would mean updating the plugin, then rolling it back again, which may not be ideal for you.) Sometimes that doesn’t work so you can ask your host where to find the PHP error logs on the server, then copy/paste the relevant error in your reply here.

    Looking forward to helping you get this resolved!

    Thread Starter westaubrey

    (@westaubrey)

    Thanks David! I installed the Fatal Error Notify plugin, but when I updated GiveWP it didn’t cause the same error. I’m not sure if you did something but thanks either way. Here are the error details that were originally emailed just in case they are helpful in some way:

    WordPress version 6.3.2
    Current theme: Divi (version 4.22.2)
    Current plugin: Matomo Analytics – Ethical Stats. Powerful Insights. (version 4.15.2)
    PHP version 7.4.33

    Error Details
    =============
    An error of type E_COMPILE_ERROR was caused in line 210 of the file /home/westaubr/public_html/mrpmchristmashamper.org/wp-content/plugins/matomo/app/vendor/php-di/php-di/src/Container.php. Error message: Declaration of DI\Container::has($name) must be compatible with Psr\Container\ContainerInterface::has(string $id): bool

    Plugin Support Matheus Martins

    (@matheusfd)

    Hi, @westaubrey.

    We released a fix for it already, and you likely installed it too. If you did not, then update GiveWP to the latest version and you should be good to go.

    Before taking any steps for troubleshooting or updating, I highly recommend taking a good backup of the site you can confidently restore from. Having a backup of your site is essential to a solid workflow, and will allow you to restore to a previous version of the site if you run into any issues. You can read more about our top recommendations for taking a backup here: https://givewp.com/backup-for-faster-troubleshooting/

    Thanks for using GiveWP! Have a great day.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘“There has been a critical error on your website”’ is closed to new replies.