error after upgrade to 4.9.1

  • Resolved Andrei Chira

    (@smlaci)


    4 years, 2 months ago

    I get this error after upgrding WooCommerce to 4.9.1:

    
Stack trace:

#0 /home/5f6a90f4c1ac190fbc567abc/public_html/wp-includes/sodium_compat/lib/sodium_compat.php(825): require_once()

#1 /home/5f6a90f4c1ac190fbc567abc/public_html/wp-includes/sodium_compat/autoload.php(51): require_once('/home/5f6a90f4c...')

#2 /home/5f6a90f4c1ac190fbc567abc/public_html/wp-includes/compat.php(333): require('/home/5f6a90f4c...')

#3 /home/5f6a90f4c1ac190fbc567abc/public_html/wp-settings.php(107): require('/home/5f6a90f4c...')

#4 /home/5f6a90f4c1ac190fbc567abc/public_html/wp-config.php(80): require_once('/home/5f6a90f4c...')

#5 /home/5f6a90f4c1ac190fbc567abc/public_html/wp-load.php(37): require_once('/home/5f6a90f4c...')

#6 /home/5f6a90f4c1ac190fbc567abc/public_html/wp-blog-header.php(13): require_once('/home/5f6a90f4c...')

#7 /home/5f6a90f4c1ac190fbc567abc/public_html/index.php(17): require('/home/5f6a90f4c...')

#8 {main}

thrown in /home/5f6a90f4c1ac190fbc567abc/public_html/wp-includes/sodium_compat/lib/constants.php on line 8
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Gabriel – a11n

    (@gabrielfuentes)

    Hi there! ??

    This kind of problem is usually caused by either a conflict with your theme or with another plugin.
    ?
    The best way to determine this is to:

    • Temporarily switch your theme to Storefront
    • Disable all plugins except for WooCommerce
    • Repeat the action that is causing the problem

    If you’re not seeing the same problem after completing the conflict test, then you know the problem was with the plugins and/or theme you deactivated. To figure out which plugin is causing the problem, reactivate your other plugins one by one, testing after each, until you find the one causing conflict. You can find a more detailed explanation on how to do a conflict test here.

    Before you start

    1. First, please make sure you have a good backup in place of your full site and database. Most hosting companies have this included in the subscription, but you could also consider using a service like?Jetpack. If something goes wrong, it’s nice to know that you can restore your site.
    2. Second, I would suggest installing a plugin called?Health Check & Troubleshooting. This is a plugin developed by the WordPress community and it allows you to disable plugins without affecting your current site visitors.
    Thread Starter Andrei Chira

    (@smlaci)

    thank you, on the live website I have restored a backup, I’ll be testing on local to identify what’s causing the issue.

    Plugin Support abwaita a11n

    (@abwaita)

    Hi @smlaci,

    We’ve not heard back from you in a while, so I’m marking this thread as resolved. Hopefully, you were able to find a solution to your problem!

    If you have further questions, please feel free to open a new topic.

    Thanks.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘error after upgrade to 4.9.1’ is closed to new replies.