WPIntell

Source evidence

Re: Redirect in loop

Find Slow Functions & Actions & Filters & Hooks (Debug Bar) · support · 2020-10-06T10:39:00+00:00

mixedsentiment
mediumseverity
0.85relevance
5replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

6 / 35 rows with source links

17.1% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

29 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
Michael Visser resolved
Hi @ttodua , same issue as reported in https://wordpress.org/support/topic/redirect-in-loop/ . Javascript is running an endless refresh loop on all WordPress pages (front-end and WP Admin). Thanks for reporting. Can you please give us step-by-step instructions how we can replicate that? (including the list of active plugins, active theme and on which page/action you face it)? Screencast will be also appreciated to be sent (i.e. GoogleDrive/WeTransfer/etc) to email: support-at-puvox.software This reply was modified 5 years, 7 months ago by ttodua . This reply was modified 5 years, 7 months ago by ttodua . This reply was modified 5 years, 7 months ago by ttodua . I have been able to find one small bug that might be causing the redirect loop. Committed the updates, and please check the new version plugin, and let us know. Thanks ! I’ll give it a try now, thanks for looking at this with me @ttodua 🙂 Nada, endless loop persists. Check for variations of the “That’s all, stop editing!” line in wp-config.php Here’s mine on WP Engine which was causing the wp-config.php file change not to be applied and then triggering the PHP public function reload to keep looping. /* That’s all, stop editing! Happy publishing. */ I recommend you clarify to Plugin users that this Plugin will make changes to the wp-config.php file and to back it up before activating (or as part of the Plugin activation process). Thanks Michael, you have been helpful. Strange, I am thinking now what remedy should be applied to this issue. One thing is what you noted – the code that will try to detect if it has access for wp-config modification. However, can you please clarify this technical detail: A) does WP engine just blocks access to wp-config.php OR B) even if you modify, it reverts the changes back from it’s memory/cache. (the “A” case will be detectable from code and somehow easier, but “B” case will be a but more headache).

Comments

5 shown
ttodua 2020-10-06T22:55:00+00:00

Thanks for reporting. Can you please give us step-by-step instructions how we can replicate that? (including the list of active plugins, active theme and on which page/action you face it)? Screencast will be also appreciated to be sent (i.e. GoogleDrive/WeTransfer/etc) to email: support-at-puvox.software This reply was modified 5 years, 7 months ago by ttodua . This reply was modified 5 years, 7 months ago by ttodua . This reply was modified 5 years, 7 months ago by ttodua .

ttodua 2020-10-06T23:49:00+00:00

I have been able to find one small bug that might be causing the redirect loop. Committed the updates, and please check the new version plugin, and let us know. Thanks !

Michael Visser 2020-10-07T11:44:00+00:00

I’ll give it a try now, thanks for looking at this with me @ttodua 🙂

Michael Visser 2020-10-07T12:14:00+00:00

Nada, endless loop persists. Check for variations of the “That’s all, stop editing!” line in wp-config.php Here’s mine on WP Engine which was causing the wp-config.php file change not to be applied and then triggering the PHP public function reload to keep looping. /* That’s all, stop editing! Happy publishing. */ I recommend you clarify to Plugin users that this Plugin will make changes to the wp-config.php file and to back it up before activating (or as part of the Plugin activation process).

ttodua 2020-10-10T07:50:00+00:00

Thanks Michael, you have been helpful. Strange, I am thinking now what remedy should be applied to this issue. One thing is what you noted – the code that will try to detect if it has access for wp-config modification. However, can you please clarify this technical detail: A) does WP engine just blocks access to wp-config.php OR B) even if you modify, it reverts the changes back from it’s memory/cache. (the “A” case will be detectable from code and somehow easier, but “B” case will be a but more headache).