Bug

Problem:
You are experiencing a fatal PHP error with the Sitepress Multilingual CMS plugin on WPEngine, specifically an error related to 'Call to private method WPML_Language_Pair_Records::convert_to_storage_format()' in the file translation-management.class.php on line 192.
Solution:
We recommend the following steps to resolve this issue:
1. Ensure all WPML components are updated to the same version. If auto-update is not possible, manually update by following these steps:
- Deactivate all WPML add-ons.
- Deactivate WPML Multilingual CMS.
- Reactivate the core plugin first.
- Go to Plugins -> Add New -> Commercial tab and activate add-ons one at a time.
2. On WPEngine, clear the object/page cache from the WPE dashboard.
3. In WPML → Support → Troubleshooting, run the following:
- Clear the cache in WPML
- Remove ghost entries from translation tables
- Fix element_type collation
- Set language information (only if you’ve seen language-less rows)
- Synchronize local job ids with ATE jobs (if you use ATE)
If these steps do not resolve the error, it may be due to outdated information or a different issue. We highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket at WPML support forum for further assistance.

Problem:
You are trying to publish translations on pages using the advanced editor, but the translations are not publishing.
Solution:
We have confirmed that this issue does not occur in our local tests, even when the String Translation plugin is reactivated. We attempted to review this on your installation via the File Manager, but it appears that debugging is not writing to the debug.log. We recommend that you verify on your side if there have been any recent changes, such as a modified log path.

If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket at WPML support forum for further assistance.

Problème :
Vous essayez d'activer la traduction des médias pour utiliser des images différentes selon la langue, mais depuis le sous-menu WPML → Media Translation, il est indiqué "Installation requise" au lieu de voir une page de configuration des traductions des médias.
Solution :
- Désactivez temporairement tous les plugins.
- Accédez à WPML > Media Translation. L'assistant de configuration devrait alors apparaître.
- Lancez l'assistant de configuration pour terminer la configuration initiale de Media Translation.
- Réactivez les plugins après la configuration.
Une fois la configuration terminée, le plugin devrait fonctionner normalement.

Si cette solution ne résout pas votre problème ou semble dépassée, nous vous recommandons de vérifier les problèmes connus, de vérifier la version du correctif permanent et de confirmer que vous avez installé les dernières versions des thèmes et plugins. Si le problème persiste, n'hésitez pas à ouvrir un nouveau ticket de support sur notre forum d'assistance.

Problem:
The footers, which appear to be widgets, are not translatable.
Solution:
For translating the Widget Group title, follow these steps:
1. Navigate to WPML -> Settings -> Custom XML Configuration (tab).
2. If the field is empty, paste the following XML code:

<wpml-config>
  <gutenberg-blocks>
    <gutenberg-block type="core/widget-group" translate="1">
      <key name="title"></key>
      <xpath>//h2</xpath>
    </gutenberg-block>
  </gutenberg-blocks>
</wpml-config>

If the field is not empty, then paste the relevant part within the

<wpml-config></wpml-config>

tags.
3. Click the Save button.
4. Go to WPML -> Translation Management and look for the Block section.
5. Select the relevant Widget and send it for translation.

If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If further assistance is needed, please open a new support ticket at WPML support forum.

Problem:
You are experiencing issues with translated portfolio pages on your website, where photos disappear, and the arrangement shows incorrect language text. This problem started after recent edits to the portfolios.
Solution:
We recommend adding a custom XML configuration to your WPML settings to ensure that all necessary attributes are correctly translated. Here is the XML code you should add:

<wpml-config>
<shortcodes>
<shortcode>
<tag>norebro_heading</tag>
<attributes>
<attribute encoding="base64">title</attribute>
<attribute encoding="base64">subtitle</attribute>
</attributes>
</shortcode>
<shortcode>
<tag>norebro_text</tag>
</shortcode>
</shortcodes>
</wpml-config>

This configuration should help in translating the subtitle and other text elements correctly. If this solution does not resolve your issue or seems outdated, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If problems persist, please open a new support ticket at WPML support forum.

Problem:
You are unable to access your store's orders from the WooCommerce app when WPML is activated, although products are synchronizing correctly.
Solution:
1. Ensure you have a backup of your site.
2. Disable all other plugins, leaving only WPML plugins and WooCommerce active.
3. Switch to the WordPress default theme.
4. Check if the issue with order synchronization in the WooCommerce app persists.
5. If the problem continues, provide access to a staging site for further investigation.

If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. Additionally, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum at WPML support forum.