Details
-
Improvement
-
Status: Closed
-
Normal
-
Resolution: Won't Fix
-
None
-
None
-
None
-
None
-
Platform 211 Eng OKRs, Platform 215, Platform 216 - Finish SSO!
Description
A content block can be defined as a compound type by using ContentBlocksFieldPlugin type in the cms editor. This case isn't supported by runtime beans and should be added.
/hippo:namespaces/connect/documentation/hipposysedit:nodetype/hipposysedit:nodetype/contentblocks:
jcr:primaryType: frontend:plugin
caption: Content blocks
contentPickerType: links
cpItemsPath: connect:contentblocks
engine: ${engine}
field: contentblocks
mode: ${mode}
model.compareTo: ${model.compareTo}
plugin.class: org.onehippo.forge.contentblocks.ContentBlocksFieldPlugin
validator.id: ${validator.id}
wicket.id: ${cluster.id}.left.item
wicket.model: ${wicket.model}
/cluster.options:
jcr:primaryType: frontend:pluginconfig
last.visited.enabled: 'true'
/hippo:namespaces/connect/documentation/editor:templates/_default_/contentblocks: jcr:primaryType: hipposysedit:field hipposysedit:mandatory: false hipposysedit:multiple: true hipposysedit:ordered: true hipposysedit:path: connect:contentblocks hipposysedit:primary: false hipposysedit:type: hippo:compound
To reproduce the case;
- Run hippo-connect project.
- In DocumentationDocument.java file, change the name of method getParagraphs to any other name and update its caller references.
- When you open a page that includes content blocks would fail now (eg: https://documentation.bloomreach.com/library/about/understand-brxm.html).
Attachments
Issue Links
- relates to
-
HSTTWO-4663 ClassLoader leak with dynamic beans
-
- Closed
-