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.
/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:
When I click 'save', I get the following error:
Hi Chase
Some questions to help track this down:
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.
posted data:
Updating client dependency version did not seem to fix the issue (good call though)
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.
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?
Hi Nathan,
I figured it out!
There was a section in the web.config blocking requests to paths containing 'config'.
Aha! Good hunting!
Was starting to question my sanity...
is working on a reply...