fix: content page not found when reloading a page with an authenticated user #1198
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
SGrueber
approved these changes
Jun 29, 2022
Eisie96
changed the title
SGrueber
added a commit
that referenced
this pull request
Jul 1, 2022
SGrueber
added a commit
that referenced
this pull request
Jul 1, 2022
SGrueber
added a commit
that referenced
this pull request
Jul 1, 2022
SGrueber
added a commit
that referenced
this pull request
Jul 5, 2022
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.
PR Type
[ x ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build-related changes
[ ] CI-related changes
[ ] Documentation content changes
[ ] Application / infrastructure changes
[ ] Other:
What Is the Current Behavior?
When an authenticated user reloads a content page, then the "Page Not Found" component is rendered. The reason for this is, that the needed personalization call is dispatched after the content page call, which should use the pgid.
Issue Number: Closes #
What Is the New Behavior?
The content page call is dispatched only after the personalization status is determined.
Does this PR Introduce a Breaking Change?
[ ] Yes
[ x ] No
Other Information
AB#77774