Critical error on many sites

  • Resolved gestionatuweb

    (@gestionatuweb)


    2 weeks, 3 days ago

    Hi, today I received several critical error alerts for sites I maintain.

    The error is blocking the WordPress admin dashboard.

    The debug log indicates:

    Detalles del error ==================
    Se ha producido un error del tipo E_ERROR en la línea 2090 del archivo /…/wp-content/plugins/gtranslate/gtranslate.php.

    Mensaje de error: Uncaught ValueError: Unknown format specifier “t” in /…/wp-content/plugins/gtranslate/gtranslate.php:2090

    Stack trace: #0 /…/wp-content/plugins/gtranslate/gtranslate.php(2090): sprintf() #1 /…/wp-includes/class-wp-hook.php(341):

    GTranslate_Notices->gt_admin_notices() #2 /…/wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters() #3 /…/wp-includes/plugin.php(522): WP_Hook->do_action() #4 /…/wp-admin/admin-header.php(313): do_action() #5 /…/wp-admin/index.php(137): require_once(‘…’) #6 {main} thrown

Viewing 6 replies - 1 through 6 (of 6 total)
  • moraleja39

    (@moraleja39)

    2 weeks, 3 days ago

    Hi, I was about to report this same issue. It seems to be caused by a malformed translation of one of the admin notices for the Spanish language.

    You can fix it yourself by opening the file wp-content/languages/plugins/gtranslate-es_ES.po and replacing the line 485:

    msgstr "Puedes disfrutar de %1$traducciones automáticas con redes neuronales%2$s con una calidad comparable a la humana actualizando tu GTranslate."

    With this one:

    msgstr "Puedes disfrutar de %1$straducciones automáticas con redes neuronales%2$s con una calidad comparable a la humana actualizando tu GTranslate."

    For the plugin author, it seems the translator miss-wrote the first sprintf param, missing the last s.

    Thread Starter gestionatuweb

    (@gestionatuweb)

    2 weeks, 3 days ago

    Thank you very much @moraleja39,

    I’ll give it a try.

    Moderator Yui

    (@fierevere)

    永子

    2 weeks, 3 days ago

    The fixed string is already queued for validation, once approved (hopefully fast) there will be 1 hour before language pack will be rebuilt, updated language pack will fix the error

    Manual fixing of .po file wouldnt help, because its not really used by gettext. Gettext is using .mo file
    You can temporary revert your plugin translation to english by removing both
    wp-content/languages/plugins/gtranslate-es_ESm.mo.
    wp-content/languages/plugins/gtranslate-es_ES.po

    they will be restored by langpack update

    • This reply was modified 2 weeks, 3 days ago by Yui.
    moraleja39

    (@moraleja39)

    2 weeks, 3 days ago

    Indeed, my solution wouldn’t work.

    I have however found another faulty translation string, also missing some ‘s’, in this translation:

    #. translators: 1: Opening bold tag, 2: Closing bold tag.
    #: gtranslate.php:2100
    msgid "You can %1$sincrease%2$s your international %1$straffic%2$s by upgrading your GTranslate."
    msgstr "Puedes %1$aumentar%2$ tu %1$stráfico internacional%2$ actualizando tu GTranslate."
    Moderator Yui

    (@fierevere)

    永子

    2 weeks, 3 days ago

    Updated language pack will be available in 1 hour.

    yoniguarrior

    (@yoniguarrior)

    2 weeks, 3 days ago

    This is a problem with the Spanish translation. Several format specifiers have been incorrectly included in two specific translation entries (‘%1$tráfico’ instead of ‘%1$stráfico’, ‘%1$traducciones’ instead of ‘%1$straducciones’, ‘aumentar%2$ tu’ instead of ‘aumentar%2$s tu’ …)

    It should already have been corrected, but the incorrect translation files:

    gtranslate-es_ES.l10n.php

    gtranslate-es_ES.mo

    gtranslate-es_ES.po

    are still in /wp-content/languages/plugins

    Simply delete them so that they are reloaded, and the problem will be solved.

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

You must be logged in to reply to this topic.