Fatal PHP error after upgrading latest version 1.4.9

  • Resolved Rick Curran

    (@rickcurran)


    8 months, 3 weeks ago

    Hi, after upgrading to the latest 1.4.9 version of the plugin I am getting a fatal PHP error.

    I am using the plugin with the stock 2025 WordPress theme in full site editing mode. I have disabled all other plugins just to check there is no clash there but I am still getting the fatal error. The server I am running on is using PHP 8.2.

    The language switcher is added to the 2025 theme by adding a shortcode block (using the [multilanguage_switcher] shortcode) to one of the header templates so that it shows in the top header along with the main menu items. I have tried removing that shortcode but I still get the fatal error.

    Here is a stack trace that is shown in the error log (I have replaced my actual domain name with a placeholder):

    [24-Mar-2025 09:15:51 UTC] PHP Fatal error:  Uncaught ValueError: Unknown format specifier "Ñ" in /var/www/mydomainname.co.uk/httpdocs/wp-includes/formatting.php:5273
    Stack trace:
    #0 /var/www/mydomainname.co.uk/httpdocs/wp-includes/formatting.php(5273): sprintf()
    #1 /var/www/mydomainname.co.uk/httpdocs/wp-content/plugins/multilanguage/multilanguage.php(1588): wp_sprintf()
    #2 /var/www/mydomainname.co.uk/httpdocs/wp-includes/class-wp-hook.php(324): mltlngg_post_tag_labels()
    #3 /var/www/mydomainname.co.uk/httpdocs/wp-includes/plugin.php(205): WP_Hook->apply_filters()
    #4 /var/www/mydomainname.co.uk/httpdocs/wp-includes/taxonomy.php(749): apply_filters()
    #5 /var/www/mydomainname.co.uk/httpdocs/wp-includes/class-wp-taxonomy.php(486): get_taxonomy_labels()
    #6 /var/www/mydomainname.co.uk/httpdocs/wp-includes/class-wp-taxonomy.php(290): WP_Taxonomy->set_props()
    #7 /var/www/mydomainname.co.uk/httpdocs/wp-includes/taxonomy.php(532): WP_Taxonomy->__construct()
    #8 /var/www/mydomainname.co.uk/httpdocs/wp-includes/taxonomy.php(86): register_taxonomy()
    #9 /var/www/mydomainname.co.uk/httpdocs/wp-includes/class-wp-hook.php(324): create_initial_taxonomies()
    #10 /var/www/mydomainname.co.uk/httpdocs/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
    #11 /var/www/mydomainname.co.uk/httpdocs/wp-includes/plugin.php(517): WP_Hook->do_action()
    #12 /var/www/mydomainname.co.uk/httpdocs/wp-settings.php(704): do_action()
    #13 /var/www/mydomainname.co.uk/wp-config.php(81): require_once('...')
    #14 /var/www/mydomainname.co.uk/httpdocs/wp-load.php(55): require_once('...')
    #15 /var/www/mydomainname.co.uk/httpdocs/wp-admin/admin.php(34): require_once('...')
    #16 /var/www/mydomainname.co.uk/httpdocs/wp-admin/plugins.php(10): require_once('...')
    #17 {main}
      thrown in /var/www/mydomainname.co.uk/httpdocs/wp-includes/formatting.php on line 5273

    Please let me know if there is any other information that may be helpful.

    Thanks!

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support andrewsupport

    (@andrewsupport)

    8 months, 2 weeks ago

    Hi Rick,

    Most likely, the error occurs due to a phrase in the line that is subject to translation:
    Translate Post Tags only on the %sTags%s page

    If you translate it into other languages, ensure that the %sTags%s part retains the %s symbols. The issue is likely caused by the Ñ character.

    If possible, please help us fix this by answering the following questions:

    • What language is your site in when the error occurs?
    • If you switch to English, does the error disappear?
    Thread Starter Rick Curran

    (@rickcurran)

    8 months, 2 weeks ago

    Hi Andrew, thanks for your reply. I’m not sure I understand the context of your reference to “Translate Post Tags only on the %sTags%s page“, I haven’t done any specific coding to implement this plugin, the process has been to install the plugin. The error causes a fatal error on both the frontend and backend admin, so I had to connect to the site via SFTP and remove the plugin from the plugins folder to be able to get in and log in to the site. As soon as I re-activated the plugin it cause the error again.

    However, I’ve managed to do a bit more debugging which may shed a bit more light. The site is using English and Ukrainian and I think the error is occurring when the site is switched to Ukrainian.

    I was able to determine this by rolling back to version 1.4.8 of the plugin which did not have the error occurring, with that version activated the site was running without error. I could see that the language switcher was set to Ukrainian (and could also confirm this as I the Multilanguage plugin settings in the WP Admin were also in Ukrainian). With version 1.4.8 activated I switched the language back to English and then updated the plugin to version 1.4.9 again, when running in English the site works fine but when I change to Ukrainian the error occurs and the site is down again.

    So it seems to be something about the Ukrainian translation that is triggering the error, and it is something that changed in version 1.4.9 that is causing this as with 1.4.8 it works without error.

    Let me know if there is anything else you need to know.

    Thanks again for your help!

    Plugin Support andrewsupport

    (@andrewsupport)

    8 months, 2 weeks ago

    The only difference that could be affecting the site’s functionality is the commented-out lines 699-701 in the mltlngg_redirect function within the multilanguage.php file.

    Try uncommenting them so they look like this:

    php

    /* gutenberg save post / / Maybe remove because it prevents the URL from changing if there is a post type in the title */
    if ( mltlngg_is_rest_api() ) {
    return;
    }
    After making these changes, upload the file via FTP and test how version 1.4.9 works.

    These lines were originally commented out because they prevented URL translation (URL changes weren’t saved).
    While this didn’t cause issues on our site, it does on yours, so you might need to uncomment them.

    Please check and let us know the result.

    Plugin Support andrewsupport

    (@andrewsupport)

    8 months, 2 weeks ago

    The only difference that could be affecting the site’s functionality is the commented-out lines 699-701 in the mltlngg_redirect function within the multilanguage.php file.

    Try uncommenting them so they look like this:

    php

    /* gutenberg save post */

    /* Maybe remove because it prevents the URL from changing if there is a post type in the title */

    if ( mltlngg_is_rest_api() ) {

    return;

    }

    After making these changes, upload the file via FTP and test how version 1.4.9 works.

    These lines were originally commented out because they prevented URL translation (URL changes weren’t saved).
    While this didn’t cause issues on our site, it does on yours, so you might need to uncomment them.

    Please check and let us know the result.

    Thread Starter Rick Curran

    (@rickcurran)

    8 months, 2 weeks ago

    HI Andrew, thanks, I have tried making that change but I still get the fatal error when switching to Ukrainian.

    Plugin Support andrewsupport

    (@andrewsupport)

    8 months, 2 weeks ago

    Your issue is likely specific to your environment, and resolving it may require access to your files, which is not safe to share on the forum.

    To solve your problem, please contact us via our Help Center: https://support.bestwebsoft.com/

    Thread Starter Rick Curran

    (@rickcurran)

    8 months, 2 weeks ago

    Hi Andrew, I have contacted via the Help centre now.

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

The topic ‘Fatal PHP error after upgrading latest version 1.4.9’ is closed to new replies.