Conflict / Error 500 when changing WPML settings

Thank you for your post.

Can you please turn on debugging under Newsletters > Configuration on the right-hand side and save the WPML settings again to see if it shows any type of PHP fatal error?

Also, where are these WPML settings exactly? Under which section? Please tell me so that we can test WPML with our Newsletter plugin here.

I look forward to your response.

Thanks for your reply.

About the details :
– WP 4.5.2
– TRIBULANT newsletter newsletters-lite.4.6.1.2 (i tried also previous version, same result. When all was fine in previous WP version)
– WPML 3.3.8 and string translation 2.3.7.

This issue happens when we turn “string translation settings” to “Auto-register strings only when logged in as an administrator”. Then we get an internal error server 500.

We tried this also on a fresh install with just WP + TRIBULANT + WPML, same issue.
HTTP ERROR 500 in the admin section. Front is still available.

Thanks

Thanks again for your reply.

Pls find here below all the details including debug info :

Thanks for your reply.

About the details :
– WP 4.5.2
– TRIBULANT newsletter newsletters-lite.4.6.1.2 (i tried also previous version, same result. When all was fine in previous WP version)
– WPML 3.3.8 and string translation 2.3.7.

This issue happens when we turn “string translation settings” to “Auto-register strings only when logged in as an administrator”. Then we get an internal error server 500.

We tried this also on a fresh install with just WP + TRIBULANT + WPML, same issue.
HTTP ERROR 500 in the admin section. Front is still available.

WordPress database error: [Column ‘context’ cannot be null]?INSERT INTO wp_icl_strings (language, context, gettext_context, domain_name_context_md5, name, value, status) VALUES (‘en’, NULL, ”, ‘0b70d1aa1f2a6e35fd62513824fd7419’, ‘5026e070dc7a4b393cf425dfff96f1ab’, ‘Upgrade to PRO’, ‘0’)

Fatal error: Uncaught exception ‘Exception’ with message ‘Count not add String with arguments: value: Upgrade to PRO allow_empty_value: language: en’ in /var/www/vhosts/DOMAIN_NAME/wp-content/plugins/wpml-string-translation/classes/filters/class-wpml-admin-string-filter.php:176 Stack trace: #0 /var/www/vhosts/DOMAIN_NAME/wp-content/plugins/wpml-string-translation/classes/filters/class-wpml-admin-string-filter.php(120): WPML_Admin_String_Filter->save_string(‘Upgrade to PRO’, false, ‘en’, NULL, ”, ‘5026e070dc7a4b3…’) #1 /var/www/vhosts/DOMAIN_NAME/wp-content/plugins/wpml-string-translation/classes/filters/class-wpml-admin-string-filter.php(32): WPML_Admin_String_Filter->register_string(NULL, ‘5026e070dc7a4b3…’, ‘Upgrade to PRO’) #2 /var/www/vhosts/DOMAIN_NAME/wp-content/plugins/wpml-string-translation/inc/functions.php(307): WPML_Admin_String_Filter->translate_by_name_and_context(‘Upgrade to PRO’, ‘5026e070dc7a4b3…’, NULL, NULL) #3 /var/www/vhosts/DOMAIN_NAME_PARTLY in /var/www/vhosts/DOMAIN_NAME/wp-content/plugins/wpml-string-translation/classes/filters/class-wpml-admin-string-filter.php on line 176

Thank you to keep us posted
Thanks

Thank you for your response.

That PHP fatal error is the reason for the 500 Internal Server Error page.

I searched the error and found many discussions on the WPML forums about the same problem. Such as this: https://wpml.org/forums/topic/php-fatal-error-class-wpml-admin-string-filter-php-on-line-176/

Can you please try what the person mentions there? “To reset the site, I clicked on the WPML > Support > Troubleshooting. At the end of the page I selected the option “I am about to reset all translation and language data.” and I clicked on the “Reset and deactivate WPML” button.”

Can you please submit a ticket to us with WordPress login details so that we can fix it for you? You can submit a ticket here: https://tribulant.com/support/

I look forward to your response.

Hi

Thanks for your research and answer.

I’m a bit afraid of resetting the site, all translation and language as we are working on this since a while. We needed weeks to get the content with translation on main site.

What do you think ?

Thanks

Thank you for your response.

No problem, I fully understand.

Can you submit a ticket to us with logins to check the fatal error for you? You can submit a ticket here: https://tribulant.com/support/