Bad translation triggers a fatal error

  • Resolved Jose

    (@giuse)


    1 year, 10 months ago

    Hello,

    In the function “kbs_setup_kbs_ticket_tag_taxonomy()” you have this line of code:

    'search_items' => sprintf( esc_html__( 'Search %s Tags', 'kb-support' ), kbs_get_ticket_label_singular() ),

    When you change the language to Spanish in the backend, that line of code becomes:

    sprintf('Buscar Etiqueta…', 'Ticket')

    It triggers a fatal error because the Spanish translation of ‘Search %s Tags’ misses the %s.

    I suggest you be sure all the translations have the format specifier required by the function sprintf.

    In my case, it triggers a fatal error in the backend because of a bad translation.

    Here what I find in the debug.log file:

    [01-Jan-2023 18:09:30 UTC] PHP Fatal error: Uncaught ValueError: Missing format specifier at end of string in /Users/josemortellaro/Sites/plugins/wp-content/plugins/kb-support/includes/post-taxonomies.php:76

    And the backend shows a white screen of death. So the issue is serius.
    In my case I have solved it, this thread is just for making you aware of this issue.

    I hope it helps.

    Have a great day!

    Jose

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

  • Hi Jose,

    Thank you very much for letting us know! Apologies for the headache!

    I opened a ticket with our development team regarding this issue and we will fix it in a future update. Here you can see the progress: https://github.com/WPChill/kb-support/issues/250

    All the best,

    Beatrice.

    This topic will be marked as resolved due to inactivity and because we have an open ticket on GitHub regarding this. Please keep in mind that the ‘resolved’ status is only for this support thread, not the issue on GitHub.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Bad translation triggers a fatal error’ is closed to new replies.