Please make sure to update to WPML 4.3.4 before reporting any issue

Hi, Amit here, I am the WPML Support Manager, our current ticket queue is high, update your WPML plugins and make sure you meet the minimal requirements for running WPML before reporting an issue please - many tickets are resolved doing that

Please look at our updated list of Known Issues and you can also use our support search to find helpful information and of course review our documentation before opening a ticket.

If you do need to open a ticket please make sure to provide us with all the needed information as described in this page

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Tagged: 

This topic contains 5 replies, has 2 voices.

Last updated by Andrés 1 year, 1 month ago.

Assigned support staff: Andrés.

Author Posts
October 13, 2018 at 2:44 pm #2814281

Adriano

Ciao Andrés,

every so often I get the following message in the wordpress dashboard:

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

Array
(
    [language] => it
    [context] => admin_texts_woocommerce_new_order_settings
    [gettext_context] => 
    [domain_name_context_md5] => d3218db82312465bbeae3d2ebc6a624f
    [name] => [woocommerce_new_order_settings]heading
    [value] => Nuovo ordine cliente
    [status] => 0
    [translation_priority] => optional
    [allow_empty_value] => 1
)

What should I do?

Grazie,
Adriano

October 13, 2018 at 4:15 pm #2814336

Andrés
Supporter

Languages: English (English ) Spanish (Español ) French (Français )

Timezone: Europe/Paris (GMT+01:00)

Hola Adriano,

¿Trabajando de nuevo durante los fines de semana? 🙂

Many of the times, this alert is just a false positive and you shouldn't take care of it. For being sure about it:

1. Open your wp-config.php file and look for define(‘WP_DEBUG’, false);. Change it to or just add it:

define('WP_DEBUG', true);
define( 'WP_DEBUG_LOG', true );

In this case the errors will be saved to a debug.log log file inside the /wp-content/directory and look for any PHP error related to WPML.

2. If it is not the case, just follow the errata and close the warning:
https://wpml.org/errata/duplicate-entry-for-key-uc_domain_name_context_md5/

Does it help?

Un saludo,
Andrés

October 15, 2018 at 1:24 pm #2817685

Adriano

Ciao Andrés,

you also work on Saturdays ? in addition to Saturday, sometimes I also work on Sundays.

At the moment the error is no longer displayed, so I do not know whether to worry or not. In the link that you kindly gave me George writes that it is a very serious problem and that it should have been corrected with WPML 4.0.6:
https://wpml.org/errata/duplicate-entry-for-key-uc_domain_name_context_md5/#comment-1846784
but now I have version 4.0.7 and the problem reoccurs.

Un saluto,
Adriano

October 15, 2018 at 1:59 pm #2817884

Andrés
Supporter

Languages: English (English ) Spanish (Español ) French (Français )

Timezone: Europe/Paris (GMT+01:00)

Ciao Adriano,

Yes, there late days have been pretty busy, but soon I'll take some vacations.

I'm glad to know that the message has disappeared. Now, about George's comment, you are totally right but there is a difference, that user is mentioning a duplicate of a Primary key which points to a database corruption while is not the case:
Duplicate entry ‘0’ for key ‘PRIMARY’

Does it answer your question?

Regards,
Andrés

October 19, 2018 at 2:48 pm #2832439

Adriano

Ciao Andrés,

now the problem is gone, I hope it will not be repeated in the future.

Saluti,
Adriano

October 19, 2018 at 2:54 pm #2832477

Andrés
Supporter

Languages: English (English ) Spanish (Español ) French (Français )

Timezone: Europe/Paris (GMT+01:00)

Awesome, Adriano! 🙂
Ora per godersi il weekend.
Chao!