Copied to clipboard

Flag this post as spam?

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

  • Paul Wright (suedeapple) 277 posts 704 karma points
    Feb 10, 2020 @ 08:57
    Paul Wright (suedeapple)

    Variant Property Type - Database Type Change?

    I ran into a problem using the Variant Property type, whereby the node would not save at all.

    I looked at the Logs, and it appeared that the JSON generated was too long to be saved to the DB.

    To "Fix" this I changed a table in the Umbraco DB

    Table : cmsDataType
    PropertyAliasType : TeaCommerce.VariantEditor
    dbtype : nText  (was previously Nvarchar)

    @TeaCommerce support, is this something that's likely to cause "bad voodoo" elsewhere in the TC Codebase? - This was the only way I could see to fix the error.

  • Matt Brailsford 4124 posts 22220 karma points MVP 9x c-trib
    Feb 10, 2020 @ 09:09
    Matt Brailsford

    Hey Paul,

    I think your fix is perfectly fine and would likely be what we would have suggested. I personally have hit this problem before in other JSON based property editors such as Nested Content or Stacked Content and have raised this a few times with HQ.

    Not sure if it has been upped in Core by default yet, but the only other option for us would be to modify the table for you in an install script, but I'd rather not be tweaking Core tables from our solution.

    I'll try and look into this again to see if there has been any changes in Core around using ntext for data type values, but in the meantime the fix you've applied is more than ok.


Please Sign in or register to post replies

Write your reply to: