Quantcast
Channel: Developer to developer
Viewing all articles
Browse latest Browse all 9076

ContentType inheritance and default AssetFolder - ContentManagement API and ContentDefinition API

$
0
0

Hi all,

I found two problems with ContentManagement API and ContentDefinition API which I can't seem to find solution.

1. Content types inheritance - content type definition can only use supported base types and content only accepts on content type.

As an example let's say I have 30 different page types and want to use SEO properties in all of them. With code it's easy to achieve this - just inherit SEO class. With API I don't see any option to have the same logic. I can neither set my custom type through ContentDefinition API for content type definition nor set multiple contentTypes through ContentManagement API for content (it disregards multiple values).

Is there any way to achieve this purely through API?

2. Default asset folder - "For This Page" not set for created page automatically and cannot be set through API.

As an example I want to create new page with ContentArea, then create few new blocks in that ContentArea. Through CMS the blocks will be created in "For This Page" asset folder, but it seems there is no way to achieve this through API.

I tried different approaches, but without any success. Creating block or SysContentAssetFolder folder with page as parent, with Content Assets (default "For This Page" folder) as parent, "For All Sites" as parent and nothing worked. It seems that it's not possible to set ContentOwnerID for the asset folder.

Is there any way to have "For This Page" set purely through API?

 

Thanks for any help that anyone can provide with this!

 


Viewing all articles
Browse latest Browse all 9076

Trending Articles