Skip to content

fix(next-drupal): handle archived content responses for path translation - #865

Open
cruno91 wants to merge 1 commit into
chapter-three:mainfrom
cruno91:fix-archived-content-response
Open

fix(next-drupal): handle archived content responses for path translation#865
cruno91 wants to merge 1 commit into
chapter-three:mainfrom
cruno91:fix-archived-content-response

Conversation

@cruno91

@cruno91 cruno91 commented Jun 27, 2025

Copy link
Copy Markdown
Contributor

This pull request is for: (mark with an "x")

  • examples/*
  • modules/next
  • packages/next-drupal
  • starters/basic-starter
  • starters/graphql-starter
  • starters/pages-starter
  • Other

GitHub Issue: #864

  • I need help adding tests. (mark with an "x")
    Code changes need test coverage. If you don't know
    how to make tests, check this box to ask for help.

Describe your changes

Similar to 404 responses when translating paths, a 403 response needs to be handled.

@vercel

vercel Bot commented Jun 27, 2025

Copy link
Copy Markdown

@cruno91 is attempting to deploy a commit to the Chapter Three Team on Vercel.

A member of the Team first needs to authorize it.

BourezBastien added a commit to BourezBastien/next-drupal that referenced this pull request Aug 24, 2026
Drupal returns 403 for archived content when translating paths. Treat
403 like 404 so Next.js renders a 404 page instead of a 500 error.

Adopted from upstream PR chapter-three#865.

Fixes chapter-three#864

Co-authored-by: Chris Runo <chris.runo@gmail.com>
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.

1 participant