This chapter contains all changes made in Release 7.5.11 of CoreMedia Digital Experience Platform 8.
Release 7.5.11 contains the following CoreMedia modules:
CoreMedia Blueprint
CoreMedia CMS
CoreMedia Studio
CoreMedia LiveContext for IBM WebSphere Commerce
CoreMedia Elastic Social
In addition, CoreMedia DXP 8 uses the following tooling:
Product | Key | Version |
---|---|---|
CoreMedia Application Maven Plug-in | APPPLUGIN | 2.7.9 |
CoreMedia Project Maven Extension | PROJEXT | 1.0.5 |
Table 2.40. Tooling of CoreMedia DXP 8
CoreMedia Blueprint Improvements
Fixes
LinkEmbedFilter
The LinkEmbedFilter was only suitable for certain (and not documented in detail) preconditions concerning the elements of the outer and the inner HTML and thus produced invalid HTML in many cases. It has therefore undergone a major change to make it more flexible.
The appropriate behavior of the LinkEmbedFilter depends on the HTML snippet created by the view for the bean to be embedded. Since the LinkEmbedFilter is not aware of particular templates, it cannot automatically determine whether the snippet to be embedded will be a block element or a flow element. The hasBlockLevelView method reflects this information for the Blueprint's default templates. If you change the templates of the asRichtextEmbed view, you must also adjust this method accordingly.
Image Preview Setting
A new IntProperty
maxPreviewImageWidth
is added to theResponsive Image Settings
. It defines the max width of the images, displayed in the CoreMedia Studio's preview. The default value is 400px.
CoreMedia CMS Improvements
Enhancements
In order to bundle information on content located in a site you can now retrieve a special view an the content from the SitesService: the
ContentSiteAspect
. This aspect can be queried for its master, its master's version and for example for its translation state.Together with this change fallback strategies have been implemented to deal with content items which do not fulfill some requirements like providing master and master version information. Fallback strategies are to determine the master by its path or to determine the locale not only by a document property but as fallback also from the site indicator document.
Changes
Queries in the
SitesService
related to a content item in a site have now been moved to the newly introducedContentSiteAspect
. This includes:Site getSiteFor(Content)
replaced in
ContentSiteAspect
'sSite getSite()
.String getDerivedPathForSite(Content, Site)
replaced in
ContentSiteAspect
'sString getAbsolutePathInSite(Site)
.Content getDerivedContentForSite(String)
replaced in
ContentSiteAspect
'sContent getDirectlyDerived(Site)
.boolean isLocalizable(Content)
replaced in
ContentSiteAspect
'sboolean isLocalizable()
.Set<Content> getVariants(Content)
replaced in
ContentSiteAspect
'sSet<Content> getVariants()
.Map<Locale,Content> getVariantsByLocale(Content)
replaced in
ContentSiteAspect
'sMap<Locale,Content> getVariantsByLocale()
.Locale getLocale(Content)
replaced in
ContentSiteAspect
'sLocale getLocale()
.boolean isPartOf(Site,Content)
replaced in
ContentSiteAspect
'sboolean isPartOf(Site)
.
Some queries in the
SitesService
related to sites have been removed and must be retrieved from theSite
object:Content getSiteIndicator(String)
Content getSiteRootDocument(String)
Content getSiteRootFolder(String)
Server Ex-/Import have been enhanced to rebuild the translation state and thus especially the referenced master version. A special version number "0" has been introduced which will result in derived contents displayed in CoreMedia Studio as being "not-up-to-date". Exporting content with verbose flag will output the actual translation state.
Background Information: Server Ex-/Import do not export versions. Thus, it is not possible to restore a versioned link (represented by master link and master version) if the master has a new version meanwhile. Version "0" provides a best-effort solution in this case.
CoreMedia Studio Improvements
The Library can now be docked in the same place where the Control Room shows up, thus hiding the Control Room when docked. Vice versa the Control Room can now float in its own window just like the Library. To be precise Control Room and Library now have exactly the same behavior regarding docking / floating. Additionally a second dock area is available at the right side next to the Actions Toolbar. The size and position of both components are persisted and get restored on Studio startup.
Corresponding with the Server Ex-/Import change CoreMedia Studio interprets Version "0" (and actually any destroyed version) as not up-to-date. Mind that only a global warning on outdated content can be reported as the actually changed properties cannot be determined.
CoreMedia Elastic Social Improvements
Changes
Added the property "es.profile.changes.mails.enabled" to define if mails are send when a user profile was changed during moderation in the Studio. Changed the behavior, that now no mails will be send if the profile of a blocked or ignored user is changed during moderation.
CoreMedia LiveContext for IBM WebSphere Commerce Improvements
CoreMedia Project Improvements
CoreMedia Blueprint Improvements
Deployment and Virtualization
A new listener
com.coremedia.tomcat.FailedContextShutdownServerListener
will be registered to all tomcat contexts. It is added to thecontext.xml
to glue the webapps lifecycle with the lifecycle of theserver
component in order to provide a reliable status for the OS service handle. The listener shuts down a tomcat instance if any webapps context passes the lifecycle stateFAILED
.As a result of the above listener chef will restart tomcat if a webapp fails and therefore can keep its idempotency promise.
A new listener
com.coremedia.tomcat.CleanupTmpOnStartupListener
will be registered to theserver
component. It is added in theserver.xml
of tomcat to clean up temporary files at startup time.The module
coremedia-tomcat-orb
has been renamed tocoremedia-tomcat
and additionally contains now both new listeners.
Changes for Document Type Model
The content types
CMSymbol
,CMViewtype
,CMSegment
andCMUserProfile
are nowCMLocalized
. They wereCMObject
before. As a result the following changes have been applied:The document types have the additional properties
master
,masterVersion
andlocale
The parent of
CMSymbol
,CMViewtype
,CMSegment
andCMUserProfile
was changed toabstractLocalized-blueprint-doctypes
in theblueprint-contentbeans.xml
.The contentbeans have been adapted.
The
CMSymbolForm
,CMViewtypeForm
,CMSegmentForm
andCMPersonaForm
have been extended by theMultiLanguageDocumentForm
.
Closed JIRA Issues
Key | Type | Summary | Status |
---|---|---|---|
CMS-1498 | Bug | PC search/cart link broken in automatic WCS deployment pipelines | Fixed |
CMS-1489 | Bug | No Studio i18n for placements "tab" and "main" | Fixed |
CMS-1476 | Bug | DND inside ContentSet removes content | Fixed |
CMS-1472 | Bug | DB2 Configuration is required during installation | Fixed |
CMS-1467 (35864) | Bug | Remove Redundant Empty P-Tags From Markup | Fixed |
CMS-1464 | Bug | Studio: Failed IBM WCS Rest Service login prints password to log | Fixed |
CMS-1462 | Bug | RemoteBean does not fire on Loaded Event, ValueExpressions might not re-evaluate | Fixed |
CMS-1459 | Bug | Shopping Cart View Displays Weird Data | Fixed |
CMS-1452 | Bug | Products In Aurora Lack Attributes | Fixed |
CMS-1439 | Bug | ES Dynamic List for comments not working | Fixed |
CMS-1430 | Bug | Create new picture cropping component broken | Fixed |
CMS-1420 | Bug | WCS Category Links With Umlauts Cause "Generic Error" | Fixed |
CMS-1419 | Bug | Product Links On German PC Site Lead To "Generic Error" | Fixed |
CMS-1406 | Bug | CoreMedia Content Widget Image is not transparent | Fixed |
CMS-1404 | Bug | Detail view for pending translation workflows empty | Fixed |
CMS-1394 | Bug | PC login does not support email, only login name | Fixed |
CMS-1387 | Bug | Search With Suggestions In Library in IE 9 unusable | Fixed |
CMS-1368 | Bug | P13n and Elastic Social License Warnings overlap each other | Fixed |
CMS-1365 | Bug | Change icon of placement extended tooltip | Fixed |
CMS-1358 | Bug | Wrong link for articles on a Perfect Chef Category Page | Fixed |
CMS-1311 | Bug | Layout of Reset Password page is broken | Fixed |
CMS-1301 | Bug | robots.txt is delivered as download | Fixed |
CMS-1261 | Bug | Wrong Product Image Urls | Fixed |
CMS-1226 | Bug | Closing docked library makes selected document tab inaccessible | Fixed |
CMS-1208 | Bug | getAvailabiltyInfo returns null for ProductVariant | Fixed |
CMS-1192 | Bug | No option to create an "External Page" in navigation toolbar | Fixed |
CMS-1177 | Bug | Product Detail link on German Perfect Chef site broken | Fixed |
CMS-1152 | Bug | Special keys sometimes ignored in content type combo box | Fixed |
CMS-1108 (35781 35879 36015) | Bug | Studio can not upload images with Umlauts | Fixed |
CMS-1007 | Bug | RelativeDateFilterFieldsetBase produces uncacheable Solr filter query | Fixed |
CMS-969 | Bug | ESpot does not render as part of an external page | Fixed |
CMS-622 (34427) | Bug | No stacktrace for JavaScript errors inside EventUtil.invokeLater() blocks | Fixed |
Table 2.41. 7.5.11