jbhovik

Hi Chriz12,

Do you have any posts or pages that work with an automatic profile, and don’t result in the error?

Also, what is the type of WordPress item that gave the error?

One last question–do you use proxies or firewalls in relation to your website?

All you’ve said has been helpful.

We just released 1.0.9, which should address the problems you’re seeing.

If by chance you’re still seeing the errors after the update, go to the Settings tab for the Lingotek plugin, then Custom Fields tab, click on the save button.

This will clear out any strings that were somehow saved to the database. Then you shouldn’t see the errors again.

Thanks for your help. These debug messages were very helpful.

Hello meiocheio,

I think we may have found a solution to the problem you’re seeing. Would you mind trying this in your code?

Change lines 10 – 12 in /lingotek-translation/admin/settings/view-custom-fields.php from:

if (!empty($_POST[‘settings’])) {
update_option(‘lingotek_custom_fields’, $_POST[‘settings’]);
}

to:

if (!empty($_POST[‘settings’])) {
if (is_array($_POST[‘settings’])) {
update_option(‘lingotek_custom_fields’, $_POST[‘settings’]);
}
}

Sorry about all the code changing. We’re just not sure how a string is being saved to the database with this error.