ข้ามการนำทาง
หน้าแรก » Errata » l10n.php - Performant Default Translated Strings Not Displaying Correctly

l10n.php - Performant Default Translated Strings Not Displaying Correctly

Resolved

Reported for: WPML String Translation 3.2.12

Resolved in: WPML String Translation 3.2.14

Topic Tags: Compatibility

Overview of the issue

You may experience issues with native translations coming from plugins that use the Performant translations feature. For example, with plugins as WooCommerce, Blocksy or MasterStudy LMS Learning Management System, you may experience that the translations already provided does not appear correctly on the frontend.

Workaround

Please, make sure of having a full site backup of your site before proceeding.

  • Open …wp-content/plugins/wpml-string-translation/classes/MO/LoadedMODictionary.php file.
  • Look for line 46.
  • Replace: 
    				$moFileName = str_replace('l10n.php', '.mo', $loaded_file);
  • With: 
    				// WPML Workaround for compsupp-7393
				$moFileName = str_replace('l10n.php', 'mo', $loaded_file);

8 การตอบกลับ ถึง “l10n.php - Performant Default Translated Strings Not Displaying Correctly”

  1. Francamente mi aspettavo qualcosa di più definitivo, ma soprattutto che non venisse chiuso il topic così di botto, senza nemmeno aspettare se funziona.

    Onestamente per come è andata l’assistenza sto pensando di chiedere il rimborso del rinnovo dell’altro mese… prima avete negato fosse un vostro problema, poi avete dato una soluzione non definitiva, che non ho ancora provato, ma avete già chiuso il ticket. Francamente per tutto il tempo ho avuto la sensazione che voleste togliervi di torno la rogna e non fare effettivamente assistenza.

    Inoltre avevo chiesto espressa conferma della cancellazione del clone del mio sito da parte vostra e non c’è stato accenno in tal senso.

    Dopo i miei impegni lavorativi proverò il codice e mi riserverò di scrivere ancora laddove non funzioni.

    ตอบกลับ

    • Hello there,
      Unfortunately, I don’t speak Italian and I may don’t have the whole idea of this situation. I used some help from Google but apologies for any omission. If you need to re-open your ticket, you can add a note there, I will ask a confirmation regarding the clone site from our side. Please, let us know if this workaround helped in your case, we will keep this erratum updated once we have a new release fixing this issue.
      Thank you for your understanding.

      ตอบกลับ

  2. Hello Andrés,

    I thank you for your message. I didn’t receive the ticket update with the reply concerning the workaround, only the ticket close notification, so I had no chance to write about the issue anymore, nor did I get info about the clone website deleting.

    I have tried the code, and it seems it works. It prioritises the translated WPML strings and overwrites the .po and .mo files in wp-content/languages and wp-content/plugin/plugin-name/languages.

    Please prioritise fixing this problem in the next release. It would greatly help if I didn’t have to modify the file in the WPML folder at every update.

    I’ll wait for the confirmation about the clone website deleting.

    Best,
    Cristina

    ตอบกลับ