[Next.js] [XMC] Fix "Could not resolve site for name" error on XMC rendering host build #1659
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
art-alexeyenko
approved these changes
Nov 9, 2023
ambrauer
added a commit
that referenced
this pull request
Nov 9, 2023
…ndering host build (#1659) * Fix issue when prerendering 404/500 pages during build on XMC editing hosts * Bump @sitecore/components to latest (1.1.2) * CHANGELOG update
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description / Motivation
This resolves the "Could not resolve site for name" error when building on XM Cloud editing hosts.
Also (unrelated), this PR bumps the @sitecore/components package to latest (1.1.2).
Testing Details
Types of changes