openclaw - ✅(Solved) Fix [Bug]: Broken provider links on localized docs page openclaw-ai.com/de/docs/providers/index [1 pull requests, 1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#68139Fetched 2026-04-18 05:53:47
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Timeline (top)
labeled ×2commented ×1cross-referenced ×1referenced ×1

The localized docs page for providers contains broken links.

Page: https://openclaw-ai.com/de/docs/providers/index On that page, provider links are generated like this:

  • /providers/ollama

But on this site those links return 404.

Example broken link:

Error shown:

  • 404: NOT_FOUND

Error Message

Error shown:

Root Cause

The localized docs page for providers contains broken links.

Page: https://openclaw-ai.com/de/docs/providers/index On that page, provider links are generated like this:

  • /providers/ollama

But on this site those links return 404.

Example broken link:

Error shown:

  • 404: NOT_FOUND

Fix Action

Fixed

PR fix notes

PR #68250: docs: use relative links in provider index to fix localization #68139

Description (problem / solution / changelog)

Summary

  • Problem: Links on localized documentation pages (e.g., German /de/docs/providers/index) were 404ing because they pointed to the domain root (e.g., /providers/ollama) instead of the localized documentation path (e.g., /de/docs/providers/ollama).
  • Why it matters: This broke the onboarding and configuration flow for non-English users.
  • What changed: Standardized all internal links in docs/providers/index.md to be standard root-relative paths (e.g., /providers/ollama) to comply with docs/AGENTS.md.
  • Underlying Fix: Patched the i18n relocalizer (scripts/docs-i18n/localized_links.go) to correctly include the /docs segment when rewriting root-relative links for localized sites.
  • Verification: Verified that node scripts/docs-link-audit.mjs passes with 0 broken links in the English source.

Change Type (select all)

  • Bug fix
  • Feature
  • Refactor required for the fix
  • Docs
  • Security hardening
  • Chore/infra

Scope (select all touched areas)

  • Gateway / orchestration
  • Skills / tool execution
  • Auth / tokens
  • Memory / storage
  • Integrations
  • API / contracts
  • UI / DX
  • CI/CD / infra

Linked Issue/PR

  • Closes #68139
  • This PR fixes a bug or regression

Root Cause (if applicable)

  • Root cause: The i18n relocalizer was prepending the language code (e.g., /de) but omitting the /docs segment that the localized documentation site requires. This caused standard root-relative links (mandated by Mintlify/AGENTS.md) to resolve incorrectly on the localized domain.
  • Missing detection / guardrail: The relocalizer lacked a test case or configuration to ensure compatibility with the specific sub-path requirements of the localized docs host (openclaw-ai.com/<lang>/docs/...).

Regression Test Plan (if applicable)

  • Coverage level that should have caught this:
    • Unit test
    • Seam / integration test
    • End-to-end test
    • Existing coverage already sufficient
  • Target test or file: scripts/docs-i18n/localized_links_test.go
  • Scenario the test should lock in: Rewritten localized links should include the /docs segment after the language code.

User-visible / Behavior Changes

Users on localized documentation sites will now be correctly redirected to the localized version of provider pages instead of hitting a 404 at the domain root.

Diagram (if applicable)

For UI changes or non-trivial logic flows, include a small ASCII diagram reviewers can scan quickly. Otherwise write N/A.

Source: [Ollama](/providers/ollama)
Old Relocalizer: /de/providers/ollama (404)
New Relocalizer: /de/docs/providers/ollama (Works)

Security Impact (required)

  • New permissions/capabilities? (No)
  • Secrets/tokens handling changed? (No)
  • New/changed network calls? (No)
  • Command/tool execution surface changed? (No)
  • Data access scope changed? (No)

Repro + Verification

Environment

  • OS: Darwin
  • Runtime/container: Native

Steps

  1. Run node scripts/docs-link-audit.mjs to confirm English links are valid.
  2. (Manual/Pipeline) Run scripts/docs-i18n and verify rewritten links include /docs.

Expected

  • Links resolve to the localized sub-hierarchy.

Actual

  • English link audit: checked_internal_links=2848, broken_links=0.

Evidence

Attach at least one:

  • Trace/log snippets: checked_internal_links=2848, broken_links=0

Human Verification (required)

What you personally verified (not just CI), and how:

  • Verified the patch in scripts/docs-i18n/localized_links.go ensures the /docs segment is present.
  • Re-standardized docs/providers/index.md to use the /path format required by Mintlify.

Review Conversations

  • I replied to or resolved every bot review conversation I addressed in this PR.

Compatibility / Migration

  • Backward compatible? (Yes)
  • Config/env changes? (No)
  • Migration needed? (No)

Risks and Mitigations

  • Risk: If a future deployment moves docs away from the /docs sub-path, this will need to be updated.
    • Mitigation: Centralized link rewriting logic in localized_links.go makes this a single point of change.

Changed files

  • scripts/docs-i18n/localized_links.go (modified, +2/-2)
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

The localized docs page for providers contains broken links.

Page: https://openclaw-ai.com/de/docs/providers/index On that page, provider links are generated like this:

  • /providers/ollama

But on this site those links return 404.

Example broken link:

Error shown:

  • 404: NOT_FOUND

Steps to reproduce

  1. Open: https://openclaw-ai.com/de/docs/providers/index
  2. Click a provider link such as Ollama
  3. It opens: https://openclaw-ai.com/providers/ollama
  4. The page returns 404

Expected behavior

Clicking the provider link should open the provider docs page.

For example, one of these working paths:

Actual behavior

The page links to /providers/... instead of the correct docs path, so the generated links are broken.

OpenClaw version

irrelevant

Operating system

irrelevant

Install method

irrelevant

Model

irrelevant

Provider / routing chain

irrelevant

Additional provider/model setup details

This looks like a link generation / routing bug on the localized docs page, not missing provider documentation. The provider docs still exist, but the links from the index page are wrong.

Logs, screenshots, and evidence

Impact and severity

Impact

Users cannot navigate from the localized provider index page to the actual provider documentation pages.

This causes:

  • broken documentation navigation
  • confusion about whether provider docs exist at all
  • extra support burden in Discord/GitHub
  • a poor onboarding experience for users trying to configure providers like Ollama

The docs content still exists, but the broken links make it much harder to find.

Medium

Reason:

  • this is not a security issue
  • this does not cause data loss
  • but it does break an important docs flow for setup/configuration, especially for localized docs users

Who is affected

Affected users are people using the localized docs pages on openclaw-ai.com, for example:

  • https://openclaw-ai.com/de/docs/providers/index

Especially affected:

  • new users
  • non-English users
  • users trying to configure model providers and looking up provider-specific settings

Not or less affected:

  • users who already know the correct direct docs URLs
  • users browsing the current docs site docs.openclaw.ai

Additional information

No response

extent analysis

TL;DR

Update the link generation on the localized docs page to use the correct path, such as /de/docs/providers/ollama instead of /providers/ollama.

Guidance

  • Verify that the link generation logic is correctly handling the localized path prefix (/de/docs/) and append it to the provider link.
  • Check the routing configuration to ensure it can handle the correct paths for provider documentation pages.
  • Consider adding a temporary redirect from the incorrect paths (/providers/...) to the correct ones (/de/docs/providers/...) to mitigate the issue until the link generation is fixed.
  • Review the documentation build or generation process to ensure it is correctly generating links for localized pages.

Example

No code snippet is provided as the issue does not specify the technology stack or the exact code responsible for link generation.

Notes

The fix may involve updating the documentation generation tool, the website's routing configuration, or the link generation logic in the code. Without more information about the technology stack and the codebase, it's difficult to provide a more specific solution.

Recommendation

Apply a workaround by adding temporary redirects from the incorrect paths to the correct ones, as this can quickly mitigate the issue for users while the root cause is being addressed.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Clicking the provider link should open the provider docs page.

For example, one of these working paths:

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - ✅(Solved) Fix [Bug]: Broken provider links on localized docs page openclaw-ai.com/de/docs/providers/index [1 pull requests, 1 comments, 2 participants]