Skip Navigation

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.

Sun Mon Tue Wed Thu Fri Sat
- - 9:00 – 18:00 9:00 – 18:00 9:00 – 18:00 9:00 – 18:00 9:00 – 18:00
- - - - - - -

Supporter timezone: America/Lima (GMT-05:00)

This topic contains 10 replies, has 3 voices.

Last updated by Andreas W. 1 year, 11 months ago.

Assisted by: Andreas W..

Author Posts
March 27, 2023 at 12:30 pm #13338395

georgL-14

Hi,

I know there are some threads already on this issue but I did not find any real solutions. This issue has been haunting my store for a couple of weeks while in development and it appears completely randomly. I figured out the only solution to this issue is to go to Update Permalinks. This seems to be temporary though, it can appear randomly at any time. It is clearly WPML related since renaming "sitepress-multilingual-cms" plugin resolves the issue without any other action.

Please help me find a solution to this, we are now in Nexcess that is a dedicated managed Woocommerce hosting solution and it evidently does not have anything to do with server in that sense.

Error given in error.log:
'LogLevel debug' to get a backtrace.
[Mon Mar 27 12:55:33 2023] [core:error] [pid 14145:tid 140189938509568] [client 88.196.157.242:0] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace., referer hidden link

March 28, 2023 at 12:20 am #13343965

Ahmed Mohammed
Supporter

Timezone: Africa/Cairo (GMT+02:00)

Hi there,

Thank you for contacting WPML support!

The reported issue could happen when the .htacess gets overwritten with the language folder (the URL format of the languages on your website, ie, /en/, /et/ etc).

Could you please try the fix from this page: https://wpml.org/errata/htaccess-is-rewritten-with-language-folder/ and let us know if the issue is still there?

Looking forward to hearing back from you.

March 28, 2023 at 7:43 am #13346365

georgL-14

Hi,

Thank you. Currently, adding this to the functions.php causes a WordPress error on all pages that a critical error has occured with WordPress. Not server side 500 but one given by WordPress.

Should I disable WPML, then go update Permalinks and then add the code again or what do you suggest... this issue is honestly driving me crazy and I hope we can find a solution to this. I don't know where else to go for help.

March 28, 2023 at 11:43 am #13348843

georgL-14

Disregard last, I accidentally edited WordPress functions.php. The fix has been in my theme functions.php for a week or so but the 500 error re-appears randomly. Issue is not solved.

March 28, 2023 at 9:48 pm #13352909

Andreas W.
Supporter

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

Hello,

Could you please send me a screenshot from your htaccess file or at least verify, if it meets the default WordPress configuration:

# BEGIN WordPress

RewriteEngine On
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]

# END WordPress

Source: https://wordpress.org/documentation/article/htaccess/

Best regards
Andreas

March 29, 2023 at 1:10 am #13353425

georgL-14

Hi,

Here it is.

Screenshot 2023-03-29 at 04.09.02.png
March 29, 2023 at 1:36 pm #13358631

Andreas W.
Supporter

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

Hello,

I would like to offer to have a closer look and request temporary access (wp-admin and FTP) to the website to investigate the issue further.

You can find the required fields below the comment section when you log in to leave the next reply. The information you provide is private, which means only you and I can see and access it.

IMPORTANT
Please be sure to make a backup copy of the website and database before allowing us access.
If you can't see the wp-admin / FTP fields, your post and website credentials are set as PUBLIC. DO NOT publish the data unless you see the required wp-admin / FTP fields.

I may have to install a plugin called "All In One WP Migration" to make a copy of the website where I can investigate the issue further.

However, I would also be very grateful if you could provide a staging site or copy of the website from your server yourself for this purpose.

If you have any questions about creating such a staging site, you can consult your hosting provider or use a plugin like the following, just make sure the server has enough free disk space:
https://wordpress.org/plugins/wp-staging/

If you are unable to provide such a copy of the site for testing, please let me know on this ticket.

The private response form looks like this:
hidden link

Next time you reply, click "I still need assistance."

Video:
hidden link

Please note that we are obliged to request this information individually on each ticket. We may not access any access information not specifically submitted on this ticket in the private response form.

Best regards
Andreas

March 30, 2023 at 7:06 am #13363557

georgL-14

The error I currently got from error.log of staging site is:

[Thu Mar 30 07:48:17 2023] [core:error] [pid 9506:tid 139822223996672] [client 88.196.41.195:0] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.

March 30, 2023 at 7:14 am #13363571

Andreas W.
Supporter

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

Hello,

I do understand right, that the error was solved after saving the permalinks?

If this is the case then I suspect that my colleague Ahmed already provided a reason and a solution for this issue here and this is not truly caused by WPML:
https://wpml.org/forums/topic/getting-500-error-in-back-end-request-exceeded-the-limit-of-10/#post-13343965

This means, once the 500 error occurs it might be that inside the htaccess file Rewrite Base was changed to for example /en because too many active plugins are calling the function flush_rewrite_rules(true) at the same time.

If this is the case, then you need to delete the htaccess file, save the permalinks, which should create a new auto-generate htaccess file from WordPress, and finally add our snippet to a BeTheme child theme, which means you should install a child theme for this purpose which usually comes with BeTheme on purchase - after that, the issue should not occur anymore.

Please add a BeTheme Child theme to the Staging site and include the snippet from our errata, then investigate if the issue occurs again.

BeTheme Child Theme Install Guide:
hidden link

Errata with Snippet for Fix:
https://wpml.org/errata/htaccess-is-rewritten-with-language-folder/

Best regards
Andreas

March 30, 2023 at 7:39 am #13363777

georgL-14

Hi,

I appreciate your quick reply and also a very thorough explanation to the cause. I have browsed these older threads and knew about the solution but perhaps I did some steps in the wrong order and therefore did not achieve the results.

I also compared the two htaccess files, the one that was created after updating permalinks and the one that caused the issue.

The "faulty" htaccess contains this extra bit:
# Block the include-only files.
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^wp-admin/includes/ - [F,L]
RewriteRule !^wp-includes/ - [S=3]
RewriteRule ^wp-includes/[^/]+\.php$ - [F,L]
RewriteRule ^wp-includes/js/tinymce/langs/.+\.php - [F,L]
RewriteRule ^wp-includes/theme-compat/ - [F,L]
</IfModule>

And it also has differences in these rows below in the WordPress section of htaccess:

1) FAULTY version: RewriteBase /en/
CORRECT version: RewriteBase /

2) FAULTY version: RewriteRule . /en/index.php [L]
CORRECT version: RewriteRule . /index.php [L]

I have now implemented the fix also on the Live dev site and so far so good, the site is at least working. Now we ofcourse need to wait a little bit while I work today on the site and see if the issue comes back again.

I am indeed keeping my fingers crossed here.

P.S.

Do you think this issue would not occur at all when we switch the configuration from these /en/ etc suffixes to separate domain as we are intending to?

March 30, 2023 at 6:00 pm #13369771

Andreas W.
Supporter

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

Hello,

Awesome, yes this is in fact exactly this known issue.

Please keep monitoring and if the issue occurs again and the fix (snippet) might not longer help to solve it, then please let us know.

This ticket will remain open for at least 14 days but even though you can anytime open a chat or a new ticket on the forum and refer to our conversation.

https://wpml.org/forums/topic/getting-500-error-in-back-end-request-exceeded-the-limit-of-10/

Best regards
Andreas

The topic ‘[Closed] Getting 500 error in back-end – Request exceeded the limit of 10’ is closed to new replies.