Skip to content

Conversation

@felbin1997
Copy link
Contributor

Updated the links under "Next Steps" to link to v2 sites and not 404.

Updated the links under "Next Steps" to link to v2 sites and not 404.
## Next Steps

- Follow the [**Getting Started**](./getting-started) tutorial to add Friendly Captcha to your website in 3 steps.
- Follow the [**Getting Started**](./v2/getting-started/) tutorial to add Friendly Captcha to your website in 3 steps.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@felbin1997 I'm not getting 404 errors on the production website, are you? See the link previews in the bottom left below.

Image Image

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@greenberga For me it doesn't matter which link I open it is either not loading or directly giving me a 404...
Don't matter if I choose Chrome or Safari. There is always the v2 missing in the URL.

Bildschirmfoto 2025-12-02 um 07 44 57 Bildschirmfoto 2025-12-02 um 07 44 12 Bildschirmfoto 2025-12-02 um 07 43 37

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, I think I see the problem

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's something a bit weird about how Docusaurus handles relative links. Sometimes it works and sometimes it doesn't and I can't really explain the logic behind it. But I noticed that the relative links incorrectly reference the directory structure.

├── getting-started
│   ├── index.md
│   ├── ...
├── guides
│   ├── index.md
│   ├── ...
├── introduction
│   ├── index.md
│   └── v1-and-v2.md

Using .. to step up a directory is the correct fix, I believe.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

## Next Steps

- Follow the [**Getting Started**](./getting-started) tutorial to add Friendly Captcha to your website in 3 steps.
- Follow the [**Getting Started**](./v2/getting-started/) tutorial to add Friendly Captcha to your website in 3 steps.
Copy link
Contributor

@greenberga greenberga Dec 2, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Follow the [**Getting Started**](./v2/getting-started/) tutorial to add Friendly Captcha to your website in 3 steps.
- Follow the [**Getting Started**](../getting-started/index.md) tutorial to add Friendly Captcha to your website in 3 steps.

- Follow the [**Getting Started**](./v2/getting-started/) tutorial to add Friendly Captcha to your website in 3 steps.
- Visit the [**Friendly Captcha website**](https://friendlycaptcha.com).
- Migrating from **Google reCAPTCHA** or **hCAPTCHA**? Follow our [**migration guides**](./guides).
- Migrating from **Google reCAPTCHA** or **hCAPTCHA**? Follow our [**migration guides**](./v2/guides).
Copy link
Contributor

@greenberga greenberga Dec 2, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Migrating from **Google reCAPTCHA** or **hCAPTCHA**? Follow our [**migration guides**](./v2/guides).
- Migrating from **Google reCAPTCHA** or **hCAPTCHA**? Follow our [**migration guides**](../guides/index.md).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants