Fatal error after updated to ver 3.3.2

  • francoc30

    (@francoc30)


    2 years ago

    Hi, I updated to version 3.3.2 yesterday and discovered the following fatal error in the php error log. Please advise how to resolve this. Thanks

    20230306T163957: ccpst.com/dev1/index.php
    PHP Fatal error: Uncaught Error: Call to undefined function trailingslashit() in /serverpath/public_html/test/dev1/wp-includes/class-wp-textdomain-registry.php:103
    Stack trace:

    0 /serverpath/public_html/test/dev1/wp-includes/l10n.php(784): WP_Textdomain_Registry->set(‘default’, ‘en_CA’, ‘/serverpath…’)

    1 /serverpath/public_html/test/dev1/wp-include

    20230306T164000: ccpst.com/dev1/wp-admin/admin-ajax.php
    PHP Fatal error: Uncaught Error: Call to undefined function trailingslashit() in /serverpath/public_html/test/dev1/wp-includes/class-wp-textdomain-registry.php:103
    Stack trace:

    0 /serverpath/public_html/test/dev1/wp-includes/l10n.php(784): WP_Textdomain_Registry->set(‘default’, ‘en_CA’, ‘/serverpath…’)

    1 /serverpath/public_html/test/dev1/wp-include

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Chouby

    (@chouby)

    Hello,
    Your error doesn’t seem to be related to Polylang but only to WordPress. Indeed the error Call to undefined function trailingslashit() refers to a function which is normally defined much before all plugins are loaded. Moreover the error occurs in a WordPress file.

    Maybe something went wrong during a WordPress update. I suggest to reinstall WP properly. If you still have access to your dashboard, you can do it from Dashboard > Updates.

    Thread Starter francoc30

    (@francoc30)

    @chouby thanks for your reply. My WP 6.1.1 was updated back in Nov last year. I have not spot the error since then, until recently when I did a couples of plugin updates. Polylang was one of them. Since I saw the errors were related to language, I thought they were related to Polylang. I am puzzled.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Fatal error after updated to ver 3.3.2’ is closed to new replies.