I've just released a version 1.2 which should fix this issue.
Looks like, for some reason, the method signature for DocType.AddPropertyType has changed between 4.5 and 4.7 (4.5 returning void, and 4.7 returning a property type). This was causing it to YSOD if compiled against one, and run in the other environment. I've managed to fix it to work in both now by using reflection to find / invoke the method at runtime.
I installed package version 1.2 and the problems are solved here too.
I wonder if the mixin document type can be an alternative for the 'site' document type like in this content tree structure:
site en-US page1 page2 ... nl-BE page1 page2 ....
I'm asking this question because a parent site document type with general site settings has some implications, especially for search engines and SEO (refer to blog article by Sebastiaan Janssen: the ultimate site structure setup)
Method not found
Hi,
I just installed the package and created a mixin: 'SEO'
Then I tried to add the mixin to a document type by selecting the document type in the "structure" tab.
But I get this error:
Method not found: 'Void umbraco.cms.businesslogic.ContentType.AddPropertyType(umbraco.cms.businesslogic.datatype.DataTypeDefinition, System.String, System.String)'.
Is this a bug?
Greetings,
Anthony
Hi,
I get the same err. I am using 4.7
Hmm could be, we build it in 4.5 and don't think the API had changed with regard to PropertyTypes. Will take a look and get back to you.
Hi Guys,
I've just released a version 1.2 which should fix this issue.
Looks like, for some reason, the method signature for DocType.AddPropertyType has changed between 4.5 and 4.7 (4.5 returning void, and 4.7 returning a property type). This was causing it to YSOD if compiled against one, and run in the other environment. I've managed to fix it to work in both now by using reflection to find / invoke the method at runtime.
Let me know how you get on.
Cheers
Matt
Hi,
It works, thank you.
Hi Matt,
I installed package version 1.2 and the problems are solved here too.
I wonder if the mixin document type can be an alternative for the 'site' document type like in this content tree structure:
site
en-US
page1
page2
...
nl-BE
page1
page2
....
I'm asking this question because a parent site document type with general site settings has some implications, especially for search engines and SEO (refer to blog article by Sebastiaan Janssen: the ultimate site structure setup)
greetings,
Anthony Candaele
Belgium
Hi,Matt Brailsford where can i download the 'version 1.2 ' .thanks
is working on a reply...