Skip to content

Conversation

@gakonst
Copy link
Contributor

@gakonst gakonst commented Jan 22, 2026

Problem

Direct links to /protocol/blockspace/sub-block-specification were returning 404, even though:

  • The page works when navigated to from the sidebar
  • The URL shown in the browser matches the expected path

Root Cause

There was a misconfigured redirect in vocs.config.ts:

{
  source: '/protocol/blockspace/sub-block-specification',
  destination: '/protocol/blockspace/subblock-specification', // ← doesn't exist!
  status: 301,
}

This redirected to a non-existent path (subblock-specification without hyphen), but the actual file is sub-block-specification.mdx (with hyphen).

Fix

  • Remove the broken redirect
  • Fix the /errors/tx/SubblockNonceKey redirect to point to the correct hyphenated path

Fixes: Direct URL access for the sub-block specification page

The redirect from sub-block-specification to subblock-specification was
causing 404 errors when accessing URLs directly because the destination
path doesn't exist. The actual file uses hyphens (sub-block-specification.mdx).

This removes the broken redirect and fixes the error URL to point to the
correct hyphenated path.
@vercel
Copy link

vercel bot commented Jan 22, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
tempo-docs Ready Ready Preview, Comment Jan 22, 2026 3:14pm

Request Review

@snario snario merged commit 436293d into main Jan 22, 2026
3 checks passed
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