Viewing 3 replies - 1 through 3 (of 3 total)
  • Moderator bcworkz

    (@bcworkz)

    It looks like the problem lies in a WooCommerce string. You could update to 6.0 if you don’t use Arabic or don’t use WooCommerce, not very good options. If you can identify the problem string and correct it, you could submit the correction to the WooCommerce Arabic translation team.

    You could also get a head start by correcting your own installation. Update to 6.0 while WooCommerce is deactivated. Correct the translations files according to this post. You can create a staging site from your existing site with the WP Staging plugin to avoid putting your main site at risk until you’re sure everything will work correctly on the staging site.

    If you’re not sure which strings are problematic, I suggest reporting the problem in the WooCommerce support forum. Or if you have an account with WooCommerce because you purchased extensions or themes from them, their customer support would be a better option.

    Thread Starter walid91

    (@walid91)

    Hi,
    I use woocommerce and my site is in Arabic.
    I have created a staging site with the WP Staging plugin.
    The installation of wordpress 6 went well but the script-loader.php file still contains %.
    I modified the file and removed %.
    The site is working but I don’t hide you that I am not very comfortable to know that my site can crash from one moment to another.

    Moderator bcworkz

    (@bcworkz)

    I know the feeling. It’s disturbing one small typographic error can bring down an entire site. Such is the nature of computer code. Do your best to thoroughly test all aspects of the site. Bring in others to beta test if you can. Your best is all you can do.

    FWIW, there are services that periodically check your site and notify you if it’s not operating correctly. It doesn’t help you fix the problem, but knowing there’s a problem is half the battle.

    I advise that you disable auto-updates for whichever plugin has the erroneous translation file until you’re sure the issue has been corrected upstream. You can still manually update after correcting the error. This will require that you periodically check for available updates, not a bad habit anyway.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Fatal error after wordpress 6 update’ is closed to new replies.