Big Problem error 500

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: Language Redirection, Language URL

This topic contains 28 replies, has 2 voices.

Last updated by Bigul 1 year, 1 month ago.

Assigned support staff: Bigul.

Author	Posts
August 28, 2018 at 1:30 pm #2682526
benjaminS-17	All my French page are error 500. If i create a new one it's directly in error 500. But in english it's good. Link to a page where the issue can be seen: aroma-care.fr Help me please
August 28, 2018 at 4:04 pm #2683457
Bigul Supporter Languages: English (English ) Timezone: Asia/Kolkata (GMT+05:30)	Hello, Welcome to the WPML support forum. I will do my best to help you to resolve these issues. Please let me know the following details to track the issue. a) Have you made any changes to the website? Because the French pages are showing for me as expected now. Please check the attached images. b) To help you faster, I've enabled debug information for this support ticket. Please see this link for how to get this information from your site and give it to us: http://wpml.org/faq/provide-debug-information-faster-support/ c) Please share with me the WordPress debug.log (not WPML debug information). Please check this page for instructions https://wpml.org/documentation/support/debugging-wpml/ To enable it, open your wp-config.php file and look for define(‘WP_DEBUG’, false);. Change it to: // Enable WP_DEBUG mode define( 'WP_DEBUG', true ); // Enable Debug logging to the /wp-content/debug.log file define( 'WP_DEBUG_LOG', true ); // Disable display of errors and warnings define( 'WP_DEBUG_DISPLAY', false ); @ini_set( 'display_errors', 0 ); // Use dev versions of core JS and CSS files (only needed if you are modifying these core files) define( 'SCRIPT_DEBUG', true ); In this case, the errors will be saved to a debug.log log file inside the /wp-content/ directory. Please do the steps to reproduce the bug and check you are getting any errors or warning related to WPML in the log file. If you can paste your debug.log to http://pastebin.com/index.php and provide me that link it would be great! (This is the cleanest way because sometimes the logs are long and create a complete mess of discussion). -- Thanks! Bigul 2018-08-28_2137_001.png 2018-08-28_2137.png
September 5, 2018 at 6:49 am #2705680
benjaminS-17	Hello, Thank you for your help. It seems that the problem comes from the plugin "WPML Translation Management". Every day when I come back to work the pages are no longer available, as if the url was corrupt. I am forced to disable the pluggin and then reactivate it. I will look for the different steps mentioned above, do you still need it? Thank you
September 5, 2018 at 12:09 pm #2706761
Bigul Supporter Languages: English (English ) Timezone: Asia/Kolkata (GMT+05:30)	Hello, Thank you for the feedback. Please share more details about the following for a better understanding. Every day when I come back to work the pages are no longer available as if the URL was corrupt If possible, please share with me the WordPress debug.log (not WPML debug information) for tracking the error. Please check this page for instructions https://wpml.org/documentation/support/debugging-wpml/ To enable it, open your wp-config.php file and look for define(‘WP_DEBUG’, false);. Change it to: // Enable WP_DEBUG mode define( 'WP_DEBUG', true ); // Enable Debug logging to the /wp-content/debug.log file define( 'WP_DEBUG_LOG', true ); // Disable display of errors and warnings define( 'WP_DEBUG_DISPLAY', false ); @ini_set( 'display_errors', 0 ); // Use dev versions of core JS and CSS files (only needed if you are modifying these core files) define( 'SCRIPT_DEBUG', true ); In this case, the errors will be saved to a debug.log log file inside the /wp-content/ directory. Please do the steps to reproduce the bug and check you are getting any errors or warning related to WPML in the log file. If you can paste your debug.log to http://pastebin.com/index.php and provide me that link it would be great! (This is the cleanest way because sometimes the logs are long and create a complete mess of discussion). -- Thanks! Bigul
September 5, 2018 at 12:44 pm #2707029
benjaminS-17	Hello, I have tried to change the code for DEBUG, normally it is good but i don't see debug.log in the Wp-content...
September 5, 2018 at 1:23 pm #2707264
benjaminS-17	This is the debug.log info : [05-Sep-2018 12:42:58 UTC] PHP Notice: is_404 est appelée de la mauvaise manière. Les balises de requête conditionnelle ne fonctionnent pas avant le lancement de la requête. Avant cela, elles renvoient toujours le booléen false . Veuillez lire <a href="https://codex.wordpress.org/fr:Débogage_dans_WordPress">Débogage dans WordPress</a> (en) pour plus d’informations. (Ce message a été ajouté à la version 3.1.0.) in /home/aromacarvs/v2/wp-includes/functions.php on line 4161 [05-Sep-2018 12:42:58 UTC] PHP Notice: is_home est appelée de la mauvaise manière. Les balises de requête conditionnelle ne fonctionnent pas avant le lancement de la requête. Avant cela, elles renvoient toujours le booléen false . Veuillez lire <a href="https://codex.wordpress.org/fr:Débogage_dans_WordPress">Débogage dans WordPress</a> (en) pour plus d’informations. (Ce message a été ajouté à la version 3.1.0.) in /home/aromacarvs/v2/wp-includes/functions.php on line 4161 [05-Sep-2018 12:42:58 UTC] PHP Notice: is_404 est appelée de la mauvaise manière. Les balises de requête conditionnelle ne fonctionnent pas avant le lancement de la requête. Avant cela, elles renvoient toujours le booléen false . Veuillez lire <a href="https://codex.wordpress.org/fr:Débogage_dans_WordPress">Débogage dans WordPress</a> (en) pour plus d’informations. (Ce message a été ajouté à la version 3.1.0.) in /home/aromacarvs/v2/wp-includes/functions.php on line 4161 [05-Sep-2018 12:42:58 UTC] PHP Notice: is_home est appelée de la mauvaise manière. Les balises de requête conditionnelle ne fonctionnent pas avant le lancement de la requête. Avant cela, elles renvoient toujours le booléen false . Veuillez lire <a href="https://codex.wordpress.org/fr:Débogage_dans_WordPress">Débogage dans WordPress</a> (en) pour plus d’informations. (Ce message a été ajouté à la version 3.1.0.) in /home/aromacarvs/v2/wp-includes/functions.php on line 4161 [05-Sep-2018 12:47:42 UTC] PHP Notice: is_404 est appelée de la mauvaise manière. Les balises de requête conditionnelle ne fonctionnent pas avant le lancement de la requête. Avant cela, elles renvoient toujours le booléen false . Veuillez lire <a href="https://codex.wordpress.org/fr:Débogage_dans_WordPress">Débogage dans WordPress</a> (en) pour plus d’informations. (Ce message a été ajouté à la version 3.1.0.) in /home/aromacarvs/v2/wp-includes/functions.php on line 4161 [05-Sep-2018 12:47:42 UTC] PHP Notice: is_home est appelée de la mauvaise manière. Les balises de requête conditionnelle ne fonctionnent pas avant le lancement de la requête. Avant cela, elles renvoient toujours le booléen false . Veuillez lire <a href="https://codex.wordpress.org/fr:Débogage_dans_WordPress">Débogage dans WordPress</a> (en) pour plus d’informations. (Ce message a été ajouté à la version 3.1.0.) in /home/aromacarvs/v2/wp-includes/functions.php on line 4161 [05-Sep-2018 12:47:42 UTC] PHP Notice: is_404 est appelée de la mauvaise manière. Les balises de requête conditionnelle ne fonctionnent pas avant le lancement de la requête. Avant cela, elles renvoient toujours le booléen false . Veuillez lire <a href="https://codex.wordpress.org/fr:Débogage_dans_WordPress">Débogage dans WordPress</a> (en) pour plus d’informations. (Ce message a été ajouté à la version 3.1.0.) in /home/aromacarvs/v2/wp-includes/functions.php on line 4161 [05-Sep-2018 12:47:42 UTC] PHP Notice: is_home est appelée de la mauvaise manière. Les balises de requête conditionnelle ne fonctionnent pas avant le lancement de la requête. Avant cela, elles renvoient toujours le booléen false . Veuillez lire <a href="https://codex.wordpress.org/fr:Débogage_dans_WordPress">Débogage dans WordPress</a> (en) pour plus d’informations. (Ce message a été ajouté à la version 3.1.0.) in /home/aromacarvs/v2/wp-includes/functions.php on line 4161 [05-Sep-2018 13:10:19 UTC] PHP Notice: Undefined variable: required in /home/aromacarvs/v2/wp-content/plugins/woocommerce-checkout-manager/includes/classes/field_filters.php on line 463 [05-Sep-2018 13:18:14 UTC] PHP Notice: is_404 est appelée de la mauvaise manière. Les balises de requête conditionnelle ne fonctionnent pas avant le lancement de la requête. Avant cela, elles renvoient toujours le booléen false . Veuillez lire <a href="https://codex.wordpress.org/fr:Débogage_dans_WordPress">Débogage dans WordPress</a> (en) pour plus d’informations. (Ce message a été ajouté à la version 3.1.0.) in /home/aromacarvs/v2/wp-includes/functions.php on line 4161 [05-Sep-2018 13:18:14 UTC] PHP Notice: is_404 est appelée de la mauvaise manière. Les balises de requête conditionnelle ne fonctionnent pas avant le lancement de la requête. Avant cela, elles renvoient toujours le booléen false . Veuillez lire <a href="https://codex.wordpress.org/fr:Débogage_dans_WordPress">Débogage dans WordPress</a> (en) pour plus d’informations. (Ce message a été ajouté à la version 3.1.0.) in /home/aromacarvs/v2/wp-includes/functions.php on line 4161 [05-Sep-2018 13:18:14 UTC] PHP Notice: is_home est appelée de la mauvaise manière. Les balises de requête conditionnelle ne fonctionnent pas avant le lancement de la requête. Avant cela, elles renvoient toujours le booléen false . Veuillez lire <a href="https://codex.wordpress.org/fr:Débogage_dans_WordPress">Débogage dans WordPress</a> (en) pour plus d’informations. (Ce message a été ajouté à la version 3.1.0.) in /home/aromacarvs/v2/wp-includes/functions.php on line 4161 [05-Sep-2018 13:18:14 UTC] PHP Notice: is_home est appelée de la mauvaise manière. Les balises de requête conditionnelle ne fonctionnent pas avant le lancement de la requête. Avant cela, elles renvoient toujours le booléen false . Veuillez lire <a href="https://codex.wordpress.org/fr:Débogage_dans_WordPress">Débogage dans WordPress</a> (en) pour plus d’informations. (Ce message a été ajouté à la version 3.1.0.) in /home/aromacarvs/v2/wp-includes/functions.php on line 4161 [05-Sep-2018 13:18:23 UTC] PHP Notice: is_404 est appelée de la mauvaise manière. Les balises de requête conditionnelle ne fonctionnent pas avant le lancement de la requête. Avant cela, elles renvoient toujours le booléen false . Veuillez lire <a href="https://codex.wordpress.org/fr:Débogage_dans_WordPress">Débogage dans WordPress</a> (en) pour plus d’informations. (Ce message a été ajouté à la version 3.1.0.) in /home/aromacarvs/v2/wp-includes/functions.php on line 4161 [05-Sep-2018 13:18:23 UTC] PHP Notice: is_home est appelée de la mauvaise manière. Les balises de requête conditionnelle ne fonctionnent pas avant le lancement de la requête. Avant cela, elles renvoient toujours le booléen false . Veuillez lire <a href="https://codex.wordpress.org/fr:Débogage_dans_WordPress">Débogage dans WordPress</a> (en) pour plus d’informations. (Ce message a été ajouté à la version 3.1.0.) in /home/aromacarvs/v2/wp-includes/functions.php on line 4161
September 5, 2018 at 4:31 pm #2708185
Bigul Supporter Languages: English (English ) Timezone: Asia/Kolkata (GMT+05:30)	Hello, Thank you for the updates and Debug Log information. The Debug.log is not showing any notice, warning or error related to WPML. If possible, please consider a staging site(clone copy of the live site) on the same server. So we can try to reproduce and debug it further in the same environment without affecting your live site. Just to make sure, are you able to reproduce the issue again when WPML Translation management plugin is active. -- Thanks! Bigul
September 6, 2018 at 11:36 am #2710422
benjaminS-17	Hello, I have some new line in the debug.log - https://pastebin.com/cQf9nphB
September 6, 2018 at 4:53 pm #2711760
Bigul Supporter Languages: English (English ) Timezone: Asia/Kolkata (GMT+05:30)	Hello, Thank you for the Debug log details. The Debug log is showing the following error. This may be happening becuase of some string was saved without the name. [05-Sep-2018 22:37:15 UTC] PHP Fatal error: Uncaught exception 'InvalidArgumentException' with message 'Translation name cannot be empty' in /home/aromacarvs/v2/wp-content/plugins/wpml-string-translation/classes/filters/db-cache/class-wpml-st-page-translation.php:107 Stack trace: #0 /home/aromacarvs/v2/wp-content/plugins/wpml-string-translation/classes/filters/db-cache/class-wpml-st-page-translation.php(44): WPML_ST_Page_Translation->validate_values('22699', '', 'woocommerce-che...') #1 /home/aromacarvs/v2/wp-content/plugins/wpml-string-translation/classes/filters/db-cache/persist/class-wpml-st-page-translations-persist.php(108): WPML_ST_Page_Translation->__construct('22699', '', 'woocommerce-che...', '', false, '') #2 [internal function]: WPML_ST_Page_Translations_Persist->create_translation_from_db_record(Array) #3 /home/aromacarvs/v2/wp-content/plugins/wpml-string-translation/classes/filters/db-cache/persist/class-wpml-st-page-translations-persist.php(51): array_map(Array, Array) #4 /home/aromacarvs/v2/wp-content/plugins/wpml-string-translation/clas in /home/aromacarvs/v2/wp-content/plugins/wpml-string-translation/classes/filters/db-cache/class-wpml-st-page-translation.php on line 107 Please try the following steps after a full site backup and make sure you are getting this error or not. 1) Go to WPML>>Support page 2) Click on Troubleshooting link (blue link in the middle of the page) 3) In Troubleshooting page, please click on the following options of Clean up section. Wait for confirmation of processing after each one. - Clear the cache in WPML - Remove ghost entries from the translation tables - Fix element_type collation - Set language information - Assign translation status to duplicated content - Fix terms count - Fix post type assignment - Recreate ST DB cache tables Please note, if you can paste your debug.log to http://pastebin.com/index.php and provide me that link it would be great! (This is the cleanest way because sometimes the logs are long and create a complete mess of discussion). -- Thanks! Bigul
September 10, 2018 at 10:12 am #2719589
benjaminS-17	Thank you for your reply. I have done all the recommendations but the problem is still here. The website is good during few hours but after many pages are HTTP ERROR 500.
September 10, 2018 at 4:10 pm #2720660
Bigul Supporter Languages: English (English ) Timezone: Asia/Kolkata (GMT+05:30)	Hello, Thank you for the feedback. Please fill the private details fields after a full site backup. I would like to access the admin area of your site for further checking. Please check the following links for more details about our private information sharing policies. hidden link https://wpml.org/purchase/support-policy/privacy-and-security-when-providing-debug-information-for-support/ Please allow me to make a duplicator copy of your site using Duplicator plugin(https://wordpress.org/plugins/duplicator/) for debugging the issue on my local server. -- Thanks! Bigul
September 11, 2018 at 3:54 pm #2724533
Bigul Supporter Languages: English (English ) Timezone: Asia/Kolkata (GMT+05:30)	Hello, Thank you for the login information and permission. I made a Duplicator copy of the site for further debugging. I went through a few pages in the frontend and backend. But not able to reproduce the errors exactly. So please let me know the exact steps to reproduce the issue. -- Thanks! Bigul
September 12, 2018 at 9:23 am #2726934
benjaminS-17	Hello, Thanks for your help. I do not know exactly what are the steps to reproduce the problem. I think you just need to work on the website example: Edit a page and save or a product. Then (I do not know how long exactly after) many pages "disable" Like: hidden link or hidden link or even the checkout page. Thank you
September 12, 2018 at 5:35 pm #2728483
Bigul Supporter Languages: English (English ) Timezone: Asia/Kolkata (GMT+05:30)	Hello, Thank you for the updates. I can reproduce the issue on your site. But the Duplicator copy works as expected on my local server. Please check the attached images. Therefore I have a request. Please check you are getting any error message in Server Error log(not debug.log) while having Error 500. Maybe you have to contact your hosting provider for this. -- Thanks! Bigul 2018-09-12_2259.png 2018-09-12_2238.png 2018-09-12_2237.png 2018-09-12_2233.png
September 18, 2018 at 7:49 am #2743905
benjaminS-17	Hello, I contacted my hosting provider. Apparently the problem does not come from home. Here are the logs for 14/09/2018: [Fri Sep 14 13:28:16 2018] [error] [client 157.55.39.115] [host v2.aroma-care.fr] AH10141: FastCGI: comm with server "/homez.2069/aromacarvs/v2/index.php" aborted: idle timeout (300 sec) [Fri Sep 14 13:28:16 2018] [error] [client 157.55.39.115] [host v2.aroma-care.fr] AH10149: FastCGI: incomplete headers (0 bytes) received from server "/homez.2069/aromacarvs/v2/index.php" [Fri Sep 14 13:28:16 2018] [error] [client 157.55.39.115] [host v2.aroma-care.fr] AH10157: FastCGI: An error happend on Fastcgi processing, fallback to CGI [Fri Sep 14 13:29:35 2018] [error] [client 157.55.39.115] [host v2.aroma-care.fr] Script timed out before returning headers: index.php [Fri Sep 14 13:30:57 2018] [error] [client 66.249.66.79] [host aroma-care.fr] AH10141: FastCGI: comm with server "/homez.2069/aromacarvs/v2/index.php" aborted: idle timeout (300 sec) [Fri Sep 14 13:30:57 2018] [error] [client 66.249.66.79] [host aroma-care.fr] AH10149: FastCGI: incomplete headers (0 bytes) received from server "/homez.2069/aromacarvs/v2/index.php" [Fri Sep 14 13:30:57 2018] [error] [client 66.249.66.79] [host aroma-care.fr] AH10157: FastCGI: An error happend on Fastcgi processing, fallback to CGI [Fri Sep 14 13:29:31 2018] [error] [client 66.249.66.79] [host aroma-care.fr] AH10141: FastCGI: comm with server "/homez.2069/aromacarvs/v2/index.php" aborted: idle timeout (300 sec) [Fri Sep 14 13:29:31 2018] [error] [client 66.249.66.79] [host aroma-care.fr] AH10149: FastCGI: incomplete headers (0 bytes) received from server "/homez.2069/aromacarvs/v2/index.php" [Fri Sep 14 13:29:31 2018] [error] [client 66.249.66.79] [host aroma-care.fr] AH10157: FastCGI: An error happend on Fastcgi processing, fallback to CGI [Fri Sep 14 13:31:25 2018] [error] [client 42.126.145.33] [host hidden link; AH10141: FastCGI: comm with server "/homez.2069/aromacarvs/v2/wp-login.php" aborted: idle timeout (300 sec) [Fri Sep 14 13:31:25 2018] [error] [client 42.126.145.33] [host hidden link; AH10149: FastCGI: incomplete headers (0 bytes) received from server "/homez.2069/aromacarvs/v2/wp-login.php" [Fri Sep 14 13:31:25 2018] [error] [client 42.126.145.33] [host hidden link; AH10157: FastCGI: An error happend on Fastcgi processing, fallback to CGI [Fri Sep 14 13:32:25 2018] [error] [client 42.126.145.33] [host hidden link; Script timed out before returning headers: wp-login.php It's strange that there is not for yesterday for example because I still had the problems. In addition my hosting provider tells me that the errors in the logs are "timeout" which does not correspond to a 500 error. I'm lost, I do not know what to do.

The topic ‘[Closed] Big Problem error 500’ is closed to new replies.