fix: cells backend URL not properly mapped when multibackend ON - WPB-20737 🍒 #3682
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.
This PR was automatically cherry-picked based on the following PR:
Original PR description:
Issue
Context: When multibackend is ON and we switch backend to staging (or any other environment), the cells URL always resolve to prod.
Issue: When multibackend is ON, we still use the legacy backend environment which is set to production so the cells URL is not properly mapped.
Solution: Use the new backend environment if any (when multibackend enabled) otherwise use the legacy one (multibackend disabled)
Testing
switch backend from the developer menu with multibackend enabled, make sure cells URL is correct
Checklist
[WPB-XXX].UI accessibility checklist
If your PR includes UI changes, please utilize this checklist: