Copied to clipboard

Flag this post as spam?

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


  • Chase 4 posts 94 karma points
    Nov 24, 2020 @ 17:46
    Chase
    0

    /backoffice/Plumber/Config/savenodeconfig 404 error when adding approval flow to content node

    When I try to add a content approval flow to a content node: add approval flow

    When I click 'save', I get the following error: backoffice error enter image description here

  • Nathan Woulfe 447 posts 1665 karma points MVP 5x hq c-trib
    Nov 24, 2020 @ 22:21
    Nathan Woulfe
    0

    Hi Chase

    Some questions to help track this down:

    • Is this a new install or has the issue appeared after an upgrade?
    • Which Plumber version?
    • Which Umbraco version?

    The requested URL definitely exists, so it's more likely the posted object isn't valid. Could you inspect the request to /plumber/config/savenodeconfig and let me know what the posted data looks like?

    There were changes in the 1.4.2 and 1.4.3 release in the javascript responsible for managing configuration - it's possible that your site is caching the old rather than serving the new. Try incrementing the version in ClientDependency.config to generate new backoffice bundles.

  • Chase 4 posts 94 karma points
    Nov 24, 2020 @ 22:54
    Chase
    0
    • new install
    • Plumber v1.4.3
    • Umbraco v8.6.6

    posted data:

    {
    "id": 1065,
    "permissions": [
        {
            "nodeId": 1065,
            "permission": 0,
            "groupId": 1,
            "variant": "en-US",
            "type": 1
        }
    ],
    "variant": "en-US"
    }
    

    Updating client dependency version did not seem to fix the issue (good call though)

  • Nathan Woulfe 447 posts 1665 karma points MVP 5x hq c-trib
    Nov 25, 2020 @ 05:22
    Nathan Woulfe
    0

    Ah, I think I see the issue - the posted model is wrong. type should be a property on the object, not a property on the inner permissions object.

    How that's happening, I don't know, and why it's not broken for everyone else, I don't know. I'll have a look in latest and see what's what...

    Edit: no, that model is correct. The plot thickens.

  • Nathan Woulfe 447 posts 1665 karma points MVP 5x hq c-trib
    Nov 25, 2020 @ 06:05
    Nathan Woulfe
    0

    I've just installed 1.4.3 into a fresh 8.6 site, all fine.

    Is there anything else going on in the site that might be causing issues? (silly question I guess, if you knew that we wouldn't be in this thread)

    WebApi config?

    Is this the only endpoint 404-ing?

    Restart/recycle the app pool?

  • Chase 4 posts 94 karma points
    Nov 25, 2020 @ 22:21
    Chase
    100

    Hi Nathan,

    I figured it out!

    There was a section in the web.config blocking requests to paths containing 'config'.

    <hiddenSegments>
     <add segment="config" />
    </hiddenSegments>
    
  • Nathan Woulfe 447 posts 1665 karma points MVP 5x hq c-trib
    Nov 26, 2020 @ 05:16
    Nathan Woulfe
    0

    Aha! Good hunting!

    Was starting to question my sanity...

  • 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