Copied to clipboard

Flag this post as spam?

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


  • Jay 425 posts 652 karma points
    Jun 16, 2016 @ 10:16
    Jay
    0

    Vorto + Umbraco 7.4.3 assembly: 1.0.5948.18141 Multinode treepicker compulsory validation not working

    Hi All,

    Not sure if anyone came across similar issue. I have Vorto installed as well.

    I've noticed that the umbraco property validation is working for all the properties but not with Multinode tree picker.

    So when I set my normal multinode tree picker to be compulsory, on save i got the below error at the moment. not sure why that pop's out on the right sliding panel

    enter image description here

    When i check the console it shows the below. Any idea?

    Appreciate any help on this.

    enter image description here

  • Mohammed BOUTEBEL 64 posts 103 karma points
    Jun 21, 2016 @ 15:37
    Mohammed BOUTEBEL
    0

    Can you give more details on Vorto and the Multinode Tree Picker, especially how did you use Vorto and the MTP ?

  • Jay 425 posts 652 karma points
    Jun 26, 2016 @ 09:57
    Jay
    0

    I'm using Vorto to wrap nested contents.

    The weird thing is the MNTP is just an ordinary MNTP on it's own (without being wrapped with anything). But when i make the MNTP property compulsory.

    It keeps showing the POSTSAVE api error not sure why.

    Any idea?

  • Jay 425 posts 652 karma points
    Jun 26, 2016 @ 10:04
    Jay
    0

    When i tried to load the POSTSAVE url on a browser it just says about the below

    "The page you are looking for cannot be displayed because an invalid method (HTTP verb) is being used."

    I've tried the url on other sites which is working with the compulsory MNTP field and it usually display the below instead

    ")]}', {"Message":"The requested resource does not support http method 'GET'."}"

    Just noticed that I've got the same error with normal Content picker property which is compulsory as well.

  • Jay 425 posts 652 karma points
    Jun 28, 2016 @ 20:01
    Jay
    0

    Found out what's the issue after I've created a new site on the same version and by copying bits by bits of the changes in.

    I found out that it's due to the httpErrors tag within my web.config

    I have my existingResponse="Replace" instead of "PassThrough"

    Thanks

    <httpErrors errorMode="Custom" existingResponse="Replace">
    
                <remove statusCode="404" subStatusCode="-1" />
                <error statusCode="404" path="~/404/" responseMode="ExecuteURL" />
            </httpErrors>
    
  • This forum is in read-only mode while we transition to the new forum.

    You can continue this topic on the new forum by tapping the "Continue discussion" link below.

Please Sign in or register to post replies