Skip to content

Fix "Page not found" flash when clicking connectors - #594

Open
Sachindu-Nethmin wants to merge 2 commits into
wso2:mainfrom
Sachindu-Nethmin:fix-connector-404-flash
Open

Fix "Page not found" flash when clicking connectors#594
Sachindu-Nethmin wants to merge 2 commits into
wso2:mainfrom
Sachindu-Nethmin:fix-connector-404-flash

Conversation

@Sachindu-Nethmin

@Sachindu-Nethmin Sachindu-Nethmin commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

Purpose

Resolves #509
Fixes the issue where an abnormal "Page not found" page flashes before loading the correct content when a connector is clicked from the Connector Catalog.

Goals

Eliminate the 404 flash and provide a smooth SPA transition when navigating to connector pages.

Approach

The issue occurred because the ConnectorCatalog component used a standard HTML <a> tag with an explicitly appended trailing slash for connector links, while Docusaurus is configured with trailingSlash: false. This mismatch caused the Docusaurus router to initially fail to match the route (resulting in a 404) before automatically normalizing the URL and redirecting to the correct page.
This was fixed by:

  1. Using the @docusaurus/Link component instead of standard <a> tags to enable seamless client-side routing.
  2. Removing the explicitly appended trailing slash from the connector links to match the trailingSlash: false configuration.

User stories

N/A

Release note

Fix "Page not found" flash when navigating to connectors in the catalog.

Documentation

N/A

Training

N/A

Certification

N/A

Marketing

N/A

Automation tests

  • Unit tests
    N/A
  • Integration tests
    N/A

Security checks

Samples

N/A

Related PRs

N/A

Migrations (if applicable)

N/A

Test environment

Tested locally on macOS using Chrome.

Learning

N/A

Summary by CodeRabbit

  • Bug Fixes
    • Improved connector catalog navigation with faster client-side page transitions.
    • Prevented incorrectly formatted links caused by trailing slashes in catalog paths.

@coderabbitai

coderabbitai Bot commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Warning

Review limit reached

@Sachindu-Nethmin, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 56 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 936d4f49-45c7-4fc9-8eb8-3efd4d95b8b2

📥 Commits

Reviewing files that changed from the base of the PR and between d0e04e6 and 5d9092e.

📒 Files selected for processing (1)
  • en/src/components/ConnectorCatalog/index.tsx
📝 Walkthrough

Walkthrough

Connector cards now use Docusaurus client-side navigation, with trailing slashes removed from constructed connector paths.

Changes

Connector navigation

Layer / File(s) Summary
Update connector card links
en/src/components/ConnectorCatalog/index.tsx
Imports Docusaurus Link, replaces the card anchor wrapper, and normalizes trailing slashes in the destination path.

Estimated code review effort: 2 (Simple) | ~5 minutes

Suggested reviewers: daneshk, anupama-pathirage, rosensilva

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly describes the user-visible fix to the connector click 404 flash.
Description check ✅ Passed The PR description follows the template and includes the issue reference, goals, approach, release note, and other required sections.
Linked Issues check ✅ Passed The change addresses #509 by using client-side Link navigation and removing trailing slashes, matching the reported 404 flash issue.
Out of Scope Changes check ✅ Passed No unrelated code changes are evident; the diff is limited to the connector catalog navigation fix.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@en/src/components/ConnectorCatalog/index.tsx`:
- Line 117: Update the Link construction in the connector catalog to use a valid
trailing-slash regex in the c.link.replace call, removing exactly one trailing
slash while preserving the existing catalogBase, key, and styling behavior.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 6831449a-9b6f-4612-abb8-964942ff4bda

📥 Commits

Reviewing files that changed from the base of the PR and between 12e5f79 and d0e04e6.

📒 Files selected for processing (1)
  • en/src/components/ConnectorCatalog/index.tsx

Comment thread en/src/components/ConnectorCatalog/index.tsx Outdated
@github-actions

Copy link
Copy Markdown

Broken links, images & orphan pages

Passing — no broken links or images found.

Links/images come from one crawl of the production build (baseUrl-aware). Orphans are docs not referenced by sidebars.ts.

Summary

  • Broken links & images — total 0 · 🆕 introduced 0 · 📄 already on main 0
  • Orphan pages — total 8 · 🆕 introduced 0 · 📄 already on main 8

Broken links & images

Introduced by this PR

No new broken link(s)/image(s) introduced by this PR. ✅

Already on main — 0 total

None.

Orphan pages

Introduced by this PR

No new orphan page(s) introduced by this PR. ✅

Already on main — 8 total

Already present on the base branch (not caused by this PR):

Show 8
  • docs/deploy-operate/observe/datadog-integration
  • docs/deploy-operate/observe/elastic-stack-elk
  • docs/deploy-operate/observe/metrics-prometheus-grafana
  • docs/deploy-operate/observe/opensearch-integration
  • docs/deploy-operate/observe/recipe-elk-stack
  • docs/deploy-operate/observe/recipe-kubernetes-production
  • docs/deploy-operate/observe/recipe-local-development
  • docs/deploy-operate/observe/recipe-opensearch-setup

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.

Abnormal "Page not found" page loading before loading the correct content once click a connector

1 participant