Bug, outputs author archive url also if author archive disabled

Hi @ov3rfly, I don’t think that this is a bug. Our spec allows for the use of ‘virtual’ URLs in IDs, to ensure that we have a logic and consistent structure.

More specifically, the ID is a distinct property from the URL/URI of a resource, so, spiders shouldn’t be (stupid enough) to assume that it’s a valid URL which they can follow.

I’d be happy to consider changing this to /person/{{person-name}}/#person for cleanliness when author archives are disabled, though!

Here we go: https://github.com/Yoast/wordpress-seo/issues/12718

Bugs are reported, investigated and fixed in GitHub so this topic was closed in favor of the open bug report.

Please leave a comment or subscribe to the GitHub report to get updates on the solution.

Closed.

The linked github ticket is “Open”, has no traffic since 15 days, no solution for this issue is available.

An issue here is not resolved by simply creating a github ticket somewhere.

Feel free to mark this issue as resolved as soon as the issue is fixed in the current released plugin version.

Hi,

As a fix is currently in progress for the issue https://github.com/Yoast/wordpress-seo/issues/12718 we will close this WordPress Forum issue.

We say this as the this forum is for troubleshooting issues. Since we found an issue and verified it, we moved the issue to the GitHub repository so it can be fixed.

As a fix is currently in progress, we ask that you please comment on the issue here https://github.com/Yoast/wordpress-seo/issues/12718 (you may need an account) so you can get updates as the issue progresses.

This is has been fixed and expected to be included in Yoast SEO v11.4. You can find further information on this here.

Feel free to mark this issue as resolved as soon as the issue is fixed in the current released plugin version.

This is the www.remarpro.com support forum, not your Github issue tracker. The problem is not yet fixed here, so this thread is not resolved.

And please stop to delete user replies in this forum, thank you.

We typically close a topic which is open for longer than 7 days with no activity. In this case, we have already fixed the issue that you’re currently experiencing and it will be included in Yoast SEO v11.4 and as such, we closed them before. However, if the issue remains after we release Yoast SEO v11.4, you can always open this topic by simply letting us know that the issue persists.

On the other hand, we don’t/can’t remove any reply from www.remarpro.com Yoast SEO support forum, only forum moderator can remove a reply. So, if you see that one of your replies has been deleted, you’ll need to take it up with the forum moderator.

Yoast 11.4 is not released yet, so the problem is not yet fixed here, so this thread is not resolved.

Please stop marking this thread as resolved until the issue is fixed in the current released plugin version.

Hi,

Please know a fix for the issue you are having is expected to be included in v11.4. We understand this may not match your expectations of forum management but we close these replies after a resolution has been identified. This help us to better manage the forum replies and keep the overview.

Know too if the issue remains after we release Yoast SEO v11.4, you can always open this topic by simply letting us know that the issue persists.

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

This is the www.remarpro.com support forum, not your Github issue tracker. The problem is not yet fixed here, so this thread is not resolved.

We released Yoast 11.4 today which included a fix for this issue, so we are marking this issue as resolved.