Support » Plugin: Yoast SEO » Broken Skip Link when installing the plugin for the first time

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Support Maybellyne

    (@maybellyne)

    Hello Ilovewpcom,

    Thanks for reaching out about the broken link.

    It is possible for you to share a screenshot to provide some context? You can use any image-sharing service like https://pasteboard.co/, https://snag.gy/, https://imgur.com/, https://snipboard.io/, or even upload the screenshot to your own website. Once you upload it to an image sharing service, please share the link to the image here.

    Thread Starter Dumitru Brinzan

    (@ilovewpcom)

    I don’t think that a screenshot will help in this particular case.
    If your organization is interested in fixing this bug, then a simple test would suffice.
    Just install the plugin on a new website on localhost and you will see this error.

    Plugin Support Jeroen Rotty

    (@jeroenrotty)

    Hey @ilovewpcom,

    Got it. I could replicate it locally and will create a bug report. Thank you for letting us know.

    Plugin Support Jeroen Rotty

    (@jeroenrotty)

    I marked this thread as resolved due to a lack of activity by the original poster. The original poster is always welcome to re-open this topic.

    The bug report is created and on our backlog. Please know that you can just click on the menu links as a workaround for the skip link not being functional. Thank you once again to bring it to our attention.

    Thread Starter Dumitru Brinzan

    (@ilovewpcom)

    Hi.

    Still not fixed (even in version 19.4).

    Thread Starter Dumitru Brinzan

    (@ilovewpcom)

    2 months passed, version 19.5.1, still not fixed.

    Plugin Support Jeroen Rotty

    (@jeroenrotty)

    Hey @ilovewpcom,

    It’s is indeed still just in the backlog. Due to a large number of issues, we have to focus on issues that either are breaking the plugin or affect many users. Since this issue is neither (yet), we probably cannot fix this short term.

    We do agree that this is something that should be addressed and therefore was added to our backlog. This means that it is on our radar: we have been able to confirm the bug and therefore have the intention of fixing this. Unfortunately, due to capacity, we cannot give you an estimate on when this issue will be addressed.

    We always encourage our users to contribute to our plugin, not just by submitting issues but also by submitting patches. If you (or someone else) decide(s) to write a patch for this issue, we’ll gladly include it after some code review.

    Plugin Support Jeroen Rotty

    (@jeroenrotty)

    This thread was marked resolved due to a lack of activity, but you’re always welcome to re-open the topic. Please read this post before opening a new request.

Viewing 8 replies - 1 through 8 (of 8 total)
  • You must be logged in to reply to this topic.