サポートフォーラム アーカイブ

Problem:
Learndash courses disappeared from the frontend after updating to WordPress 5.8

Solution:
The debug log file showed the following error:

PHP Fatal error:  Uncaught InvalidArgumentException: element_id and type do not match for element_id:42 the database contains post_attachment while this function was called with post_post in xxxx/wp-content/plugins/sitepress-multilingual-cms/classes/core-abstract-classes/class-wpml-set-language.php:34

And it was fixed with the following steps:

Go to WPML > Support > Troubleshooting page, then click these options:

- Clear the Cache in WPML
- Remove ghost entries from the translation tables
- Fix element_type collation
- Fix WPML table collation
- Set language information

Problem:
I have migrated the website from our staging server to the live server and I get this error:

We have detected a problem with some tables in the database. Please contact WPML support to get this fixed.

Table 'himmelsg_wp991.wp0g_icl_strings' doesn't exist

Array
(
[language] => en
[context] => WP Endpoints
[gettext_context] =>
[domain_name_context_md5] => 8d0ee533eb6eaa9960c52ecb3fc80232
[name] => order-pay
[value] => order-pay
[status] => 0
[translation_priority] => optional
[allow_empty_value] =>
)

I followed the instructions here: https://wpml.org/errata/missing-_icl_strings-_icl_string_translations-data-tables/

But the issue is still there, the code made no difference. The error doesn't appear on the staging server.

Solution:
We could solve the icl_table issue in your website following these steps:

- First, we excluded WPML plugins and reinstalled with their latest versions
- Then, we removed the code on functions.php that you've added in order to recreate the icl tables
- We went to your database and could find the entries "wpml_string_table_ok_for_mo_import" and "wpml_notices"
- After we deleted them, the issue was fixed and the notice on your WP Dashboard disappeared

Relevant Documentation:
https://wpml.org/errata/missing-_icl_strings-_icl_string_translations-data-tables/

Problem:
I translate the page and save the translation, but when I go to a page for that language i.e. http://example.com/en/about-us/ the content of the header is still the default.

Solution:
First of all, please go to WPML → Settings → Custom XML Configuration tab and add this XML config to it:

<wpml-config>
    <admin-texts>
        <key name="indutri_theme_options">
            <key name="header_layout"/></key>
    </admin-texts>
</wpml-config>

Once you did this, please edit the header template:
https://website.com/wp-admin/post.php?post=16&action=edit&lang=en

Now, use the top admin language switcher and select Spanish:
https://website.com/wp-admin/post.php?post=22&action=edit&lang=es

Here, edit the Permalink and change fmt-header to fmt-header-es (just simply add -es at the end, so the permalink in each language can be different).

The last step is to go to WPML → String Translation and search for the header template permalink. In the test website is fmt-header. As the translation, just simply add the permalink that you just set, fmt-header-es.

This time, when checking a page in the secondary language, the translated header will be used:
https://website.com/es/

Relevant Documentation:
https://wpml.org/documentation/getting-started-guide/string-translation/finding-strings-that-dont-appear-on-the-string-translation-page/#strings-arent-selected-for-translation

Problem:
In WPML - Settings - Custom Fields Translation, many fields are linked to a plugin that no longer exists, but still many Fields are present. How to remove them?

Solution:
WPML doesn't know once you remove a plugin. All fields are still active in the DB and therefore, WPML still displays them. Please refer to the following post, which explains this perfectly for ACF Custom Fields.

Relevant Documentation:
The whole process is identical for any Custom Field added by a Theme or Plugin: https://wpml.org/forums/topic/deleted-acf-fields-not-removed-from-translation-editor/#post-5576393. The only solution is to remove the entries from your _postmeta table manually.