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.

This topic contains 1 reply, has 2 voices.

Last updated by Riffaz 2 months ago.

Assigned support staff: Riffaz.

Author Posts
August 17, 2019 at 8:27 am #4409583

mikeS-32

We have detected a problem with some tables in the database. Please contact WPML support to get this fixed.
Invalid query
Array
(
[language] => en
[context] => gutenberg-18637
[gettext_context] =>
[domain_name_context_md5] => 6a9284fd4e65777b260712feb968d0fd
[name] => 1a3b8ca082ada99d5f0832b3c67df5ef
[value] => 😉
[status] => 0
[translation_priority] => optional
[allow_empty_value] =>
)

August 18, 2019 at 4:29 am #4411451

Riffaz
Supporter

Languages: English (English )

Timezone: Asia/Colombo (GMT+05:30)

Hi,

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. [gettext_context] is empty.
So please refer: https://wpml.org/errata/false-positive-error-notice-we-have-detected-a-problem-with-some-tables-in-the-database/
And, for now, try to dismiss the message and see.

2. 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.

Does it help?

Regards,
Riffaz.

The topic ‘[Closed] Invalid query’ is closed to new replies.