Viewing 6 replies - 1 through 6 (of 6 total)
  • Could you please post a few examples? Usually the plugin just ignores anchor text (e.g. “#whatever”), so just adding a # to a link wouldn’t make it report that link as broken.

    Thread Starter Emmanuel Simond

    (@emanwebdev)

    Hi Janis

    Could you please post a few examples?

    basically all links with a “/#whatever-with-minus-sign-in-it”

    i.e. links WITHOUT explicitly given page

    e.g. with a RELATIVE link wrongly detected as 404:
    /about-us/team-mates/#john-smith

    notice the “/#whatever”

    thnanks, and have a good day

    Unfortunately, I can’t reproduce the problem. On my test sites relative links with and without #anchors are processed correctly.

    e.g. with a RELATIVE link wrongly detected as 404:
    /about-us/team-mates/#john-smith

    Is the link URL displayed correctly? Click the “Details” link in the “Status” column and check the “Final URL” field. Does it match the actual URL of the page? If some kind of bug or plugin conflict makes BLC resolve a relative link incorrectly, that would explain why it’s flagged as 404.

    Also, can you post a few specific examples along with the displayed URLs? If you don’t want to make them public, you can email me at whiteshadow@w-shadow.com.

    Thread Starter Emmanuel Simond

    (@emanwebdev)

    Basically, # anchors to the same page, WITHOUT having full URL

    specific example:
    <a title="See more info about John Smith" href="#john-smith">John Smith</a>

    with the EMPTY anchor somewhere on the very same page:

    <a name="john-smith"></a>

    the href is a simple #whatever, without any extra dash bar

    hence the regexp clash?

    Sorry, no luck. I’ve tested multiple variations of # anchors, including pasting your example code in a post and waiting for the plugin to check the link. It still showed up as “200 OK”.

    A link without a slash is still a relative link; it’s just a relative link to the current post. The plugin will try to resolve it to a fully qualified URL to check it. That’s why I asked for “final URL” field. If the plugin somehow gets the wrong URL for the post that contains the link, all #anchor links in that post will also show up as broken.

    Thread Starter Emmanuel Simond

    (@emanwebdev)

    Hi Janis

    No worries

    Thanks for your precious time

    Have great days
    Emmanuel

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘[BUG] URLs with # : wrongly 404 detection’ is closed to new replies.