Version Control Issue with Experience Pages

Problem

Some users might experience version control issues on the experience manager for Experience Pages. This happens when the user creates an experience page as well as a sitemap for the document and links it to the channel. The result of it is that the page is redirected to the current version instead of the specified version.

Reason

br_version_uuid parameter is missed on the front end side request.

Environment Details

  • brXM  - 14.7.5

  • SPA-SDK - 15.4.5

  • Page Model Api - 0.9

Solution

Follow the below steps to solve the problem:

  1. Troubleshoot by enabling debug flag to see what the SDK does, and on the other side observe in the site access logs if there are differences in /resourceapi calls regarding the br_version_uuid parameter between the root versions selection and the other, working xpage version selection.
  2. If br_version_uuid parameter is missing, Then it needs to be explicitly re-added to the calls to the Page Model API (/resourceapi), in a NextJS/server-side rendering SPA.
  3. If the parameter is available and the issue still persists, contact the Bloomreach Support.

Related Resources

Please provide your feedback below. We would like to know if our help center is effective in solving your queries.

Did you find this page helpful?
How could this documentation serve you better?
On this page
    Did you find this page helpful?
    How could this documentation serve you better?

    We rely on cookies

    to optimize our communication and to enhance your customer experience. By clicking on the Accept and Close button, you agree to the collection of cookies. You can also adjust your preferences by clicking on Manage Preferences. For more information please see our Privacy policy.

    Manage cookies
    Accept & close

    Cookies preferences

    Accept & close
    Back