Sign in Register
Copied to clipboard

Flag this post as spam?

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


  • Jason Haines 7 posts 77 karma points
    Dec 21, 2017 @ 14:56
    Jason Haines
    0

    Error after upgrade

    I am aware this has been raised, but the solutions have not solved my problem.

    After an upgrade from 7.5.6 to 7.6.12 I am unable to save some items and get the following error

    An error occured

    Mapping types: Content -> String[] Umbraco.Core.Models.Content -> System.String[] Destination path: ContentItemDisplay.Urls.Urls Source value: Umbraco.Core.Models.Content Exception Details AutoMapper.AutoMapperMappingException: Mapping types: Content -> String[] Umbraco.Core.Models.Content -> System.String[] Destination path: ContentItemDisplay.Urls.Urls Source value: Umbraco.Core.Models.Content

    What is odd is that if I remove any content from the rich text editor it will save.

    Copy Link
  • Alex Skrypnyk 6163 posts 24143 karma points MVP 8x admin c-trib
    Dec 27, 2017 @ 10:38
    Alex Skrypnyk
    0

    Hi Jason

    Did you do all points from upgrading guide? Maybe you miss something?

    Thanks,

    Alex

    Copy Link
  • Jason Haines 7 posts 77 karma points
    Dec 27, 2017 @ 11:57
    Jason Haines
    0

    I believe I did. What could I have missed?

    Copy Link
  • Alex Skrypnyk 6163 posts 24143 karma points MVP 8x admin c-trib
    Dec 27, 2017 @ 11:58
    Alex Skrypnyk
    0

    Maybe overwrite some dll or merge config file

    Copy Link
  • Jason Haines 7 posts 77 karma points
    Dec 27, 2017 @ 13:03
    Jason Haines
    0

    Thanks Alex,

    I have been told it is related to AutoMapper. Does this need to be upgraded or should it be included?

    Jason

    Copy Link
  • Jason Haines 7 posts 77 karma points
    Dec 28, 2017 @ 08:58
    Jason Haines
    0

    Hi Alex,

    Another cause might be an override on save as the issue only happens when there is content in a richtext document type.

    Just need to find it. The developer has now left so we can't ask him.

    Ho hum, the search continues.

    Copy Link
  • Jason Haines 7 posts 77 karma points
    Jan 04, 2018 @ 16:49
    Jason Haines
    0

    Hi Alex,

    We (I mean Marc Goodson from Moriyama) have eventually discovered what the problem was. A previous developer had set the RequestValidationMode (in the web.config) to 4.0. Setting it back to 2.0 solved the problem.

    Thanks for your help

    Jason

    P.S. Still waiting to discover if setting it to 2.0 has broken anything else.

    Copy Link
Please Sign in or register to post replies

Write your reply to:

Draft