Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at

  • Frank McKenna 12 posts 83 karma points
    May 24, 2023 @ 12:06
    Frank McKenna

    uSync issue - post deployment showing "parse error" in Chrome console


    I've been using uSync (uSync.BackOffice, uSync.Core, uSync.Content: to deploy changes across environments (DEV/QA/STAGE/PRODUCTION) for a few years now. However, I've recently encountered an error in the chrome console:

    Parser error in Chrome console post-deployment

    The content for the page showing the error is persisted from a uSync "content.config" file which post-deployment cannot be updated from the CMS or from further deployments - the error arises.

    This happens on STAGE - uSync appears to update the DB for other environments successfully.

    Additionally confusing is that other pages on STAGE that are updated using uSync "content.config" files do update correctly.

    I'd like to ask the community:

    • Has anyone encountered this issue before?
    • Could this error be related to the content of the "content.config" file, which contains HTML?
    • We're using SQL Server on each environment. Could this issue be caused by differences in the DB configuration of the STAGE environment, potentially causing problems with character encoding?

    Any advice on this would be appreciated. Thanks for your time.

Please Sign in or register to post replies

Write your reply to: