U4-1648 - Umbraco 6 - Publishing was cancelled by a 3rd party add-in

Created by Andreas Iseli 05 Feb 2013, 14:09:11 Updated by Allan Cutts 02 May 2013, 10:11:49

Relates to: U4-2095

Relates to: U4-1624

When publishing a content node, the following error occurs:

Publishing was cancelled by a 3rd party add-in

Note: I do not have any additional packages installed. The error only occurs with a specific constellation of inherited document types.

Steps to reproduce:

  1. Clean umbraco installation with no installed packages / no starter kits

  2. Create a new document type "Base" with no master document type and no associated template. 1a) Add a new tab "Metadata" to the document type "Base" 1b) Add one or two properties to the "Metadata" tab which are NOT mandatory

  3. Create a new document type "Start" with "Base" as master document type and create an associated template 2a) Add a new property "WebTitle" to the tab "Metadata" (inherited from "Base") and mark it as mandatory 2b) Allow it to be created at root

  4. Create a new document type "Content" with "Base" as master document type and create an associated template

  5. Switch back to the "Start" document type and allow the "Content" document type as child (structure)

  6. Go to the content tree and create a new "Home" node based on the "Start" document type and publish it

  7. Create new content node below the "Home" noded based on the "Content" document type and try to publish it => gives the error "Publishing was cancelled by a 3rd party add-in"

Reason: Because the "Content" document type inherits the "Metadata" tab from base, it also considers the create "Webtitle" property from the "Start" document type during validation even if it is not available for editing and not inherited respectively. But unfortunately it is considered for validation (but should not).

Workarounds:

  1. Either the "WebTitle" property must be moved from the "Metadata" tab to the "Generic Properties" tab, then it is no more considered for validation
  2. Or the "WebTitle" property must set to not be mandatory

Node: I've debugged the umbraco core code to find out the reason.

1 Attachments

Download UmbracoTraceLog.txt

Comments

Morten Christensen 06 Feb 2013, 11:29:03

Hi Andreas, Thanks for the thorough report! Makes it very easy to reproduce ;) The issue has been fixed for version 6.0.1 which is due out March 1st, but I have pushed a build of the recent changes so you can use the following nightly build to correct this issue: http://nightly.umbraco.org/umbraco%206.0.1/UmbracoCms.6.0.1-build.7.zip

Just overwrite the asssemblies with the ones from the bin folder in the above zip, and you should be good to go.


Andreas Iseli 06 Feb 2013, 13:12:39

Hi Morten, many thanks for the quick fix! :) I've download and tested the build. Everything works fine now.


Morten Christensen 06 Feb 2013, 13:16:49

Fantastic!


Pinal Bhatt 08 Feb 2013, 02:05:54

Me too seeing similar error. Will we have to wait for 6.0.1 release for this fix?

I think this is a showstopper. Should have hotfix to solve this.


Sebastiaan Janssen 08 Feb 2013, 08:01:45

@Pinal use the 6.0.1 build that Morten linked to.


Pinal Bhatt 08 Feb 2013, 13:55:47

Thanks Sebastiaan. Will try out that.


Jono K 11 Feb 2013, 03:10:00

I'm still having this problem - I've tried both build 7, and the more recent build 11 but it's still giving me the error?


Sebastiaan Janssen 11 Feb 2013, 08:33:56

@Jono Could you please attach your log file here (App_Data/Logs)?


Jono K 11 Feb 2013, 23:49:26

Sure Sebastiaan, here it is


Jono K 15 Feb 2013, 10:28:53

Sebastiaan - very sorry but I've realised that I was confusing my dev environment with my production environment. The updated build does fix the error for me. Apologies again.


Owen 26 Feb 2013, 10:34:41

Thanks Morten. Fixed worked for me. Although I'm still curious as to why my project has been working fine for the last week, and only started giving me this publish issue today.


Martin Lingstuyl 28 Feb 2013, 15:03:38

Hi Morten,

I had the same issue. The fix worked, but afterwards, when I tried opening any document type, I got an "Object reference not set to an instance of an object" error. I copied back my old files, and it worked again. (thankfully my unpublishable nodes were now published) Any thoughts?

Martin


Martin Lingstuyl 28 Feb 2013, 15:06:01

...after which I tried it again by copying your new files again. and now I don't get the error anymore. Weird...


Andreas Iseli 28 Feb 2013, 17:19:04

Perhaps a caching issue?


Morten Christensen 28 Feb 2013, 17:39:27

This issue was originally related to a problem with the Mandatory setting and validation of properties, so if you changed something on your doc types, maybe just made a single property type mandatory....that could have been it.


Martin Lingstuyl 28 Feb 2013, 18:04:45

Maybe, though i didnt edit the document type between copying your files the first time and trying to open a doctype.


Andreas Iseli 04 Mar 2013, 20:26:56

Hey Morten, I've just discovered a new error according to your fix. I've currently installed build33 (1.0.4805.31661) and I'm no more able to select a tab that is inherited from a parent document type when creating a new property on the child document type.

Properties I've created before this build are still associated to the tab from the parent document type, but it is not possible to assign new properties to it.


Morten Christensen 04 Mar 2013, 20:41:29

That is a known issue for some of the nightly builds. I would recommend you start fresh with the 6.0.2 release that we released today or roll back to the doc type structure (you had and known to be correct) and upgrade to 6.0.2.


Andreas Iseli 05 Mar 2013, 07:14:53

Thanks for your quick answer. I've not realized that there is already a fix for that. I'm going to upgrade today.


Brad Richardson 07 Mar 2013, 05:02:42

I am having the same issue. I believe that it has something to do with Document Types and their relationships. I had the issue occur in 6.0.0, upgraded to 6.0.2 and then decided to try a fresh install of 6.0.2. I exported the Document Types from the previous version and the error then occurred on the fresh install when trying to publish a node.

This is terribly frustrating.


Andreas Iseli 08 Mar 2013, 10:03:33

There is still a problem with the document types. Morten is already looking into it. See http://issues.umbraco.org/issue/U4-1847


Morten Christensen 08 Mar 2013, 11:12:50

Yea, the import/export of doc types is related to issue U4-1847, which im working on improving. But luckily the issue that Brad was experiencing was because of U4-1835, which was fixed a couple of days ago, so upgrading to the 6.0.3 nightly build fixed the issue for him.


Lars-Erik Aabech 10 Apr 2013, 08:42:58

I just had this issue, and it turns out it was because I had custom property names including /. Removing the / made publishing work. Adding linked bug..


Allan Cutts 02 May 2013, 10:11:49

Testing V6.04 on a localised copy of one of our many websites (with a view to upgrading all of them) and ran into this issue. The problem was being caused by 'Terabyte Image Cropper', but I discovered that in my imported docType I had some validation text to check the crop was correct (.IsValidSize:true.) - once this was removed everything worked perfectly.


Priority: Normal

Type: Bug

State: Fixed

Assignee: Morten Christensen

Difficulty: Normal

Category:

Backwards Compatible: True

Fix Submitted:

Affected versions: 6.0.0

Due in version: 6.0.1

Sprint:

Story Points:

Cycle: