dinhac

Hi @dkotter,

thank you very much for the investigation (yes, updating our PHP is already on the to-do list) and for the quick fix!

I don’t have a GitHub account and therefore no username for crediting.

Thank you

Hi @wpmudevsupport13,

yes, you can close this thread.

The problem has actually been solved in the meantime, at least to the extent that the Broken Link Checker on our website now reports the broken links caused by renaming and/or moving pages to other directories.
We do not yet know why. In the meantime, there have been no updates to plugins that we would associate with this issue. We are investigating further.

We started to correct the broken links manually by replacing them. Maybe that has set something in motion.

Anyway, the Broken Link Checker is now working as expected again. Very good!

Thank you.

Hi @wpmudevsupport14,

thank you for your efforts! You can download a folder containing screencasts and screenshots concerning the issue from WeTransfer: https://we.tl/t-RJuww5AoPN (link valid until Feb 18th).

There are 3 subfolders in the download folder:

1. Broken Link Checker – Settings and Status:
   Perhaps from these you can check whether our plugin settings are adequate. It also shows the status of the plugin when having checked the whole site again after moving the pages like mentioned before: No broken links were detected.
2. Defect link with invalid html-url:
   The screenshots here show the latest finding with the wrong “html”-url which is not detected by Link Checker either.
3. Move Pages With Nested Pages + Link Profile Result Before + After Moving:
   This folder contains two screencasts showing the 404s as results of moving the pages “Hauptaktionsbuttons” and the one I specifically created for testing.
   Plus a “before” and “after” screenshot I took from the Link Profile plugin which show that there were 11 posts linking to the page “Hauptaktionsbuttons” before we moved it with the Nested Pages plugin, and afterwards only two remaining: These two are provided via shortcode in combination with the Page List plugin. All other 9 links are broken after having moved the page “Hauptaktionsbuttons”. And obviously, Link Checker does not report this.
   I also added a screenshot of the Nested Pages structure from the test scenario mentioned before.

Unfortunately, all menu items are in German, since I am not allowed to simply change the language, as this would disrupt the live operation of our site.

Please let me know if further information is needed to get to the bottom of the matter.

Thank you!

Hi @wpmudevsupport13,

thank you for testing and for your reply. We used the plugin Nested Pages (https://de.ww.wp.xz.cn/plugins/wp-nested-pages/) to change the parent of the page. And yes, I would have expected too that there would be an automatic redirect by WP core afterwards. But obviously this is not happening.

I double-checked this now by creating a new page tree with a parent and three child pages for test purposes. Then I inserted on two of these child pages a link to a third child page. After that, I moved the third page via drag & drop in the nested pages view in wp-admin backend up to the same level as the former parent page. As a result, the links on child pages 1 and 2 to former sibling 3 are broken now.

In the Nested Pages plugin settings footnote, I found the following note:

**Important: Changes to the page structure can have an impact on SEO and existing inbound links. Unintentional URL changes can be prevented by deactivating the nesting function. The sorting function within the existing page structure is retained. If changes are made to the page structure of a live site, it can be helpful to create 301 redirects from the old to the new addresses.

What I do not understand is why the Link Checker does not report these resulting broken links?

You could ask now, why don’t we simply use the option to change the page parent using WordPress Attributes? We did use that. Unfortunately, the related option to determine the sorting order of the child pages “disappeared” with the update to WP core 6.7. We have a lot of nested manual pages, that is why we use the Nested Pages plugin since then.

Thank you

@jdembowski I need help with removing the URL from my initial post.
I think there is no advantage in sharing it regarding this topic but my site suffers from raised brute force attacks since I published the URL here.

Hi Fresatomica,

thanks for your reply. I have just tested if the error would disappear by using Twenty Twenty-One theme on my website.
Unfortunately, this didn’t fix the issue — the authorization header is still missing.
So I’m afraid changing the theme is not the solution to the riddle …
Especially since I need a theme which is GDPR compliant, without Google Fonts, I guess that’s not the case with Stow since it isn’t with Sela, is it?
Because Stow is already a child theme building another child from it won’t work. Really a pity.

Regards
Dinhac