Details
-
Bug
-
Status: Closed
-
Normal
-
Resolution: Fixed
-
14.6.0
-
None
-
3
-
Flagged
-
Orion
-
Orion.Cycle8.Sprint1, Orion.Cycle8.Sprint2
Description
In a client case were a custom image set was implemented, see https://documentation.bloomreach.com/14/library/concepts/images-and-assets/create-a-custom-image-set.html,
the dynamically generated bean was sometimes extending from HippoDocument instead of from HippoGalleryImagetSet.
This happens on startup of a cluster so can be related to CMS-14658.
Logging of correct server node:
[DynamicBeanDefinitionService.generateBeanDefinition:180] Creating bean of document type myproject:myimageset from parent bean HippoGalleryImageSet. [DynamicBeanDefinitionService.generateBeanDefinition:195] Bean HippoGalleryImageSet$Myimageset$cEn7FHmm is created.
Logging of incorrect server node:
[DynamicBeanDefinitionService.generateBeanDefinition:180] Creating bean of document type myproject:myimageset from parent bean HippoDocument. [DynamicBeanDefinitionService.generateBeanDefinition:195] Bean HippoDocument$Myimageset$daimXLe4 is created.
Result: images failing to show on pages because the bean has no methods like #getThumbnail(), #getOriginal().
Workaround: implementation of a concrete class for the custom image set
Attachments
Issue Links
- relates to
-
-
- Closed
-