Copied to clipboard

Flag this post as spam?

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

  • MrFlo 159 posts 403 karma points
    Apr 25, 2016 @ 16:43

    Cannot save values when switching from textstring to vorto string

    If I switch my document properties from textstring to a custom vorto string for example I can not save the document and JS errors are popping up.

    TypeError: Cannot read property 'hasOwnProperty' of undefined


    DependencyHandler.axd?s=L3VtYnJhY28…:11 TypeError: Cannot read property 'isoCode' of undefined

    Is there a way to transform a property to a vorto one or do I need to delete it then save my document and then recreate a new one each time ?

  • Dave Woestenborghs 3504 posts 12133 karma points MVP 8x admin c-trib
    Apr 26, 2016 @ 06:13
    Dave Woestenborghs

    Hi MrFlo,

    Maybe try one of these things first seeing that you have js errors :

    1. Clear the client dependency cache. Go to /Config/ClientDependency.config and increment the version attribute. Additionally you can remove the files in /App_Data/TEMP/ClientDependency

    2. Clear your browser cache

    See if the problem still occurs.

    Additionally you can try to see if you have the error only when editing existing content. By that I mean content that was created before you switched to Vorto. And try if you have the error when creating new content.


  • MrFlo 159 posts 403 karma points
    Apr 26, 2016 @ 08:25

    Hi Dave,

    Thanks for answering. I had clear my cache and put debug false which normally don't use ClientDependency and I have done your suggestion but still the same issue. I can't save and JS, the error is coming from vorto.js line 199 TypeError: Cannot read property 'en-US' of undefined.

    I am using 7.4.3 may be this new property editor is not clearing the value when changing property or an additional test should be added in Vorto if there is no Json in the field?

  • Kalle Räisänen 3 posts 24 karma points
    May 26, 2016 @ 09:21
    Kalle Räisänen

    I had the same problem when changing a property from a textstring to a Vortoified textstring. Creating a new property for my Vortorific value and removing the old one worked for me.

    Possibly Vorto should have some logic for automagically converting non-vorto values to vorto JSON, but that might be tricky to do in any general way.

  • Simon 692 posts 1068 karma points
    Jul 12, 2016 @ 12:55

    I am getting the same error.

    Just install the package normally for Umbraco 7.2.6.

    enter image description here

    Any idea why?

  • Nils Frank 19 posts 89 karma points
    Apr 21, 2017 @ 07:18
    Nils Frank

    Im getting the same errors. Umbraco version 7.5.10.

    Did you find a fix for it?

  • MrFlo 159 posts 403 karma points
    May 08, 2017 @ 22:00


    So this is happening when you switch the property type. The previous data is not a JSON as expected by Vorto. A fix is to delete the property and recreate a new one, as Kalle mention.

Please Sign in or register to post replies

Write your reply to: