Skip to content

Conversation

@Sbragul26
Copy link

Description

Fixes console 404 errors caused by missing paginated blog tag pages (e.g. /blog/tag/meshery/2).

This change removes legacy single-page tag generation logic and replaces it with proper paginated page creation, ensuring that all tag pages generate valid page-data.json files.

Issue

Closes #7346

Changes

  • Removed legacy blog tag page creation logic
  • Added paginated blog tag page generation
  • Verified page-data files are generated for all tag pages

Verification

  • Ran npm run build
  • Confirmed presence of:
    • public/page-data/blog/tag/meshery/page-data.json
    • public/page-data/blog/tag/meshery/2/page-data.json
    • Additional paginated pages

@Sbragul26
Copy link
Author

@saurabhraghuvanshii

I’ve submitted a PR that fixes the 404 errors for paginated blog tag pages. This update ensures all tag pagination pages generate valid page-data.json files.

I have tested the changes by building the site (npm run build) and inspecting the generated files via the terminal. I haven’t run the site locally in a browser because the site is quite heavy, so please review and verify if any issues persist.

Thankyou.

@saurabhraghuvanshii
Copy link
Member

saurabhraghuvanshii commented Jan 21, 2026

@Sbragul26 build failing and sign your commits

@l5io
Copy link
Contributor

l5io commented Jan 21, 2026

🚀 Preview for commit 0a36c05 at: https://6971073a256bc43f52923d8c--layer5.netlify.app

- Fix paginated blog tag page generation
- Remove legacy tag logic
- Add null-safe fallbacks to prevent GraphQL build errors

Signed-off-by: Sbragul26 <sbragul26@gmail.com>
@Sbragul26 Sbragul26 force-pushed the fix/blog-tag-pagination-404 branch from 0a36c05 to 00b66d5 Compare January 21, 2026 17:57
@l5io
Copy link
Contributor

l5io commented Jan 21, 2026

🚀 Preview for commit 00b66d5 at: https://6971173521230a7fde92e569--layer5.netlify.app

@Sbragul26
Copy link
Author

Hi @saurabhraghuvanshii

I’ve squashed and signed the commits. All checks should now be passing.
Could you please review PR #7360 for issue #7346?

Thanks!

@Bhumikagarggg
Copy link

Bhumikagarggg commented Jan 26, 2026

@Sbragul26 Thank you for your contribution! Let's discuss this during the website call today at 6:30 PM IST | 7 AM CST Add it as an agenda item to the meeting minutes, if you would 🙂

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

fix console 404 error.

4 participants