Copied to clipboard

Flag this post as spam?

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


  • Paul Woodland 5 posts 45 karma points
    Nov 30, 2022 @ 13:10
    Paul Woodland
    0

    Incorrectly being picked up as JSON

    We have been having a problem with syncing some text fields, which seems to have started sometime around the upgrade to 10.1, although it's taken a while to notice as it only happens when a particular piece of content is updated so that a new uSync export file is created.

    Basically, we have some standard text fields in Umbraco, which contain data like this:

    {{VariableName}}
    

    It's part of a system we use for inserting dynamic variables into text fields, hence it looking like the Angular ones. But since 10.1, from what I can work out, it is being picked up as JSON (Umbraco's built in method for detecting JSON seems to just consider anything with curly braces around it as JSON), and altered on export, which then makes the output incorrect.

    So for example, prior to 10.1, the output file contained this:

    <pageBreadcrumbTitle>
          <Value><![CDATA[{{VariableName}}]]></Value>
    </pageBreadcrumbTitle>
    

    Now it contains this:

    <pageBreadcrumbTitle>
      <Value><![CDATA["{{VariableName}}"]]></Value>
    </pageBreadcrumbTitle>
    

    (i.e quotes have been added around it)

    So when the import happens, these quotes are added into the text field, making the synced version incorrect.

    Is there any way to force it to be treated as a standard string and not JSON to avoid this? (unless I'm wrong and it isn't JSON that's the issue)

    Thanks in advance :)

  • Kevin Jump 2195 posts 14010 karma points MVP 6x c-trib
    Nov 30, 2022 @ 14:50
    Kevin Jump
    100

    Hi Paul,

    yes, looks like we did some over eager JSON detection when we were looking to fix a JSON nesting issue much further down the tree.

    We have fixed this now :

    https://github.com/KevinJump/uSync/issues/450

    And there is a nightly build with the fix in the issue - that you can use if you need it now.

    We are in the middle of v11 release stuff this week, but we will probably release a v10 update next week to address this.

  • Paul Woodland 5 posts 45 karma points
    Nov 30, 2022 @ 14:56
    Paul Woodland
    0

    Thank you very much for dealing with it so quickly, that's great and should solve the problems!

Please Sign in or register to post replies

Write your reply to:

Draft