Copied to clipboard

Flag this post as spam?

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


  • johnsmithweb 11 posts 52 karma points
    Dec 15, 2024 @ 18:42
    johnsmithweb
    0

    The specified document had an invalid configuration

    Just updated from Umbraco 14.3.0 to Umbraco 15.1.1. I created a new blog article but when I try to publish it (using the Publish action link), I'm getting the following error shown in the UI: 'The specified document had an invalid configuration' If I look in the Umbraco log file it says:

    Document {ContentName} (id={ContentId}) has been published.","@tr":"a1d6cd3c74d9ada1e6ba78d00bcde2d9","@sp":"419d86490570425c","ContentName":"Blog","ContentId":1237,"SourceContext":"Umbraco.Cms.Core.Services.ContentService","ActionId":"10569762-3681-4728-a6c5-139c51d7c13d","ActionName":"Umbraco.Cms.Api.Management.Controllers.Document.PublishDocumentController.Publish (Umbraco.Cms.Api.Management)","RequestId":"400001bf-0001-fd00-b63f-84710c7967bb","RequestPath":"/umbraco/management/api/v1/document/6b12bccc-5a84-4a2c-99a6-e0acf332d70c/publish"

    Further investigation, using the browser developer tools, indicates that the management API requires an authentication token and this call /umbraco/management/api/v1/document/{id}/publish is failing with a 403.

    I'm logged in to the backoffice as Administrator - surely the backoffice itself already has authentication.

    On another tack, I read an article on Umbraco 14/15 authorization which said that User Groups can be granted access to the management api using the backoffice, but I have no options for API access for any of my User Groups.

    Bottom line is I can't publish anything in Umbraco 15!

    Anyone any ideas? Thanks

  • johnsmithweb 11 posts 52 karma points
    Dec 22, 2024 @ 22:04
    johnsmithweb
    100

    So I managed to figure this out myself. Most of my documents are compositions, based on a document type and two elements which contain generic properties, one for sitemap settings and the other for SEO stuff. Neither of these elements had a tab created, simply because they only contained three properties each. The document types did have a tab named 'Content'. When viewing content for my blog posts, I would usually see two tabs for the document: one named 'Generic' and one named 'Content' - the 'Generic' tab contained all six property fields from the two inherited elements. (I presume Umbraco (pre version 14/15) automatically named the tab.

    enter image description here

    However, when I looked at a blog document in the content tree, both tabs were named 'Content'.

    enter image description here

    And when I clicked on the first 'Content' tab the screen did not change - it would not display the properties inherited from the two elements. I figured Umbraco now uses the word 'Content' rather than 'Generic' when inserting a tab for inherited elements which have not expressly been given a tab and then gets confused if a document has tabs of the same name.

    My workaround was to create a new SEO element with a named tab and add the six required properties. Then change all the document types to inherit from the new SEO element and remove the other two. Of course, this meant noting down all the necessary information from all the pages on my site and then manually updating and publishing all the pages. Thankfully my site is not that big, but still, 30 pages took me about 5 hours. Thanks Umbraco!

Please Sign in or register to post replies

Write your reply to:

Draft