WP 5.1.1: Clicking “Trash” for a page wrongly redirects to domain root

OK, so your installation is in /a/wp/ subfolder. Will mydomain.com alone get me to your WP home page? Or do I need to do mydomain.com/a/wp/? if the domain alone will get me to you home page, unless you have redirects setup for all requests, the the WP URL in settings should be https://mydomain.com/a/wp and only the site URL should be https://mydomain.com. Maybe this is what you have, or maybe you thought what is correct is different than this. I just wanted to be sure.

The other thing strange is the response header example you provided is missing some important data. It seems that some plugin or theme code somewhere is corrupting location header paths somehow. Try installing and activating the health check plugin. Enter troubleshooting mode and see if the redirects work correctly now.

If so, restore your normal configuration by using the admin bar troubleshooting item. Restore one at a time, testing after each. When things go wonky again, the last activated module is the cause.

Hey bcworkz,

thanks for your reply!

You have to navigate directly to mydomain.com/a/wp – it is a test installation and to keep it simple, we housed it in that subfolder and both the WP and Site address in the settings are set to mydomain.com/a/wp.

I have installed the troubleshooting plugin, and the redirect after trashing a page still does not work. When I am on the page list, the link to trash a page points to https://mydomain.com/a/wp/wp-admin/post.php?post=3&action=trash&_wpnonce=1a56657c9f (for example). I can click it, the post is trashed, but then the response header contains a location: https://mydomain.com/?trashed=1&ids=94. It also contains x-redirect-by: WordPress, so it’s definitely WordPress adding it.

The same behaviour happens with the standard theme. It’s really weird, it seems to run 99% as expected but small glitches like this are still throwing people off at the moment.

Any help is appreciated – thanks already!

• This reply was modified 5 years, 12 months ago by fedus.

In that case both the WP and site URL settings should include the /a/wp/ path. The URL that is used to construct the location redirect header comes directly from the “siteurl” option, set by the Site URL setting.

Actually, before “siteurl” isused, WP tries to get the redirect path from the $_SERVER[‘HTTP_REFERER’] value sent by your browser slong with the trash page request. Only when there is no referrer does WP use “siteurl”. Verify that the Referer: header sent with the trash request is supplied and is correct.

this same issue happens on 4.9 with a live site, no sub folders. On randoms ites deleting or cloning a page redirects to the home page

EDIT: resolved by quitting safari and opening/logging in again!

• This reply was modified 5 years, 11 months ago by sguk.

Dear all,

I found the problem. When I checked the referrer that the browser sent, I realised that the webserver’s referrer policy was set to strict-origin. I could luckily afford to change it to same-origin, which solved the problem by sending the full url as referrer instead of only the origin.

Thanks!