410 and logic issue

There is a bug based on the logic.

If someone wants to serve 410 for all broken pages, the logical sense would be to choose 410 or 451 from Fallback Behaviour. These are status and not redirects, so they must be there.

In the current state, the 410 and 451 are placed under Redirection Type without being related to redirects.

That makes people use Custom Redirection [which doesn’t make sense in that case] and use Redirection Type – 410 or 451. The problem is that it wouldn’t work.

In order for it to work, you have to write something in the Custom Url [small typo as well, should be “URL”]. That thing will force the plugin to serve 410 or 451.

I don’t think many people would understand that bug. The theme would also display 404 page, even when 410 or 451 is served, no matter of the status code. That forces people to use advanced tools in order to check if the 404 URLs are really changed to 410 or 451.

In order to fix that:

1) You need to move 410 and 451 to Fall Back behaviour so that they work without artificial line in Custom Url.

2) Create 410 and 451 templates in your themes so that the status code matches what is seeing on the screen.

https://i.imgur.com/RxT13BX.jpg

• This topic was modified 5 years, 3 months ago by Lsdihfolwefjnelifushlisjfoijhslfkojdlhfsfk.
• This topic was modified 5 years, 3 months ago by Lsdihfolwefjnelifushlisjfoijhslfkojdlhfsfk.