2.2.36. Release 7.5.10

This chapter contains all changes made in Release 7.5.10 of CoreMedia Digital Experience Platform 8.

[Caution]Caution

Release 7.5.10 contains a number of software bug fixes relative to 7.5.9, relevant for production deployment. Unfortunately, it also has a number of known issues in the example content, which makes this release unsuitable for demonstration and experimentation purposes. Nevertheless, CoreMedia decided to make this release available to its customers so you can benefit from fixed bugs. Content issues will be addressed in forthcoming releases.

Release 7.5.10 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:

ProductKeyVersion
CoreMedia Application Maven Plug-inAPPPLUGIN2.7.9
CoreMedia Project Maven ExtensionPROJEXT1.0.5

Table 2.43. Tooling of CoreMedia DXP 8


CoreMedia CMS Improvements

Changes

CoreMedia Studio, Workflow Server and User Changes web applications can now persist content sets and finished Studio workflows to IBM DB2. Refer to the documentation for the necessary configuration: [CoreMedia Studio Developer Manual], [CoreMedia Operations Basics Manual] and [CoreMedia Workflow Manual].

If you use the RPM post-configuration approach for installation, make sure you add the tokens to the configuration files cm7-cms-tomcat.properties, cm7-studio-tomcat.properties and cm7-wfs-tomcat.properties below /etc/coremedia:

      configure.CONTROL_ROOM_JDBC_DRIVER=com.ibm.db2.jcc.DB2Driver
      configure.CONTROL_ROOM_JDBC_URL=<JDBC URL>
      configure.CONTROL_ROOM_JDBC_USER=<USER NAME>
      configure.CONTROL_ROOM_JDBC_PASSWORD=<PASSWORD>
    

Note that you must define these properties even if you do not use DB2 for persistence of content sets and finished workflows to make post-configuration work. You can use arbitrary values for <JDBC URL>, <USER NAME> and <PASSWORD> in that case.

CoreMedia Studio Improvements

Enhancements
  • The Studio ActionScript API now allows to compute the referrers of a Content, in a dependency tracked and automatically invalidated fashion. Consult the asdoc of com.coremedia.cap.content.Content#getReferrersWithDescriptor and its variants for further details.

CoreMedia Elastic Social Improvements

CoreMedia LiveContext for IBM WebSphere Commerce Improvements

  • IBM WCS customer segments can be used in personalization rules to assemble personalized content. Existing customer segments will be automatically read from IBM WCS and proposed for selection.

  • When using IBM WCS content on CMS pages or fragments, like e-Marketing Spots, the current user is also provided to the IBM WCS. Thus, its memberships to segments can taken into account by the IBM WCS.

    In the other direction, if a content is requested from the CMS to fill a fragment on a IBM WCS page the information needed to personalize on base of customer segments is also sent to the CoreMedia CAE.

  • Time based preview (time travel) is supported across the two systems. If a preview date is set in CoreMedia Studio the date is sent to the IBM WCS as an official IBM WCS preview token. So it will affect the data received from the IBM WCS.

  • One or more IBM WCS customer segments can be used in test personas to simulate a specific user profile when requesting a personalized page in preview. The customer segments in test personas have the same effect as memberships of a real user. They are also sent as an official IBM WCS preview token to the IBM WCS

  • CoreMedia Digital Experience Platform 8 supports IBM WCS 7 Feature Pack 7 and higher. With this release a limited support for Feature Pack 6 is also guaranteed. All functions that are needed in the e-Commerce-led scenario do work. That means functionality like login and session synchronization is not supported with FEP 6.

  • Currently there is one known restriction from that rule: all e-Commerce-led scenarios are supported for FEP 6; Segments are not read automatically from the IBM WCS. The list of known customer segments must be provided with an alternative approach (and have to be implemented in projects).

CoreMedia Project Improvements

CoreMedia Blueprint Improvements

Closed JIRA Issues

KeyTypeSummaryStatus
CMS-1796BugCommerceCacheInvalidationListener sometimes does now wake up again after errorsFixed
CMS-1390BugVerbose aware Command Line Tools do not log verbose messagesFixed
CMS-1384BugSessionSynchronizer logs the guest user out Fixed
CMS-1351BugUnresponsive Browser when opening "Autumn Dishes Article" in Studio - Many Entries in Image LinklistFixed
CMS-1344Buge-Marketing spots in Fragment cant be displayedFixed
CMS-1343BugRSS Feeds are brokenFixed
CMS-1342BugMedia on Live-CAE redirect to PerfectChefFixed
CMS-1337BugArticle Studio Preview failsFixed
CMS-1335 ( 36109 )BugWrong commerce URLs for categories and productsFixed
CMS-1328BugRepository Template Pattern not configured for site specific templatesFixed
CMS-1327BugSitemap Generation brokenFixed
CMS-1319BugLinks in dynamic fragments are rendered relativeFixed
CMS-1315BugFragmentCommerceContextInterceptor resolves wrong locale/wrong siteFixed
CMS-1225ChangeRemove "/page" prefix from Handlers and Apache rulesFixed
CMS-1107BugStudio Device Slider does not work with landscape mode of PerfectChefWon't Fix
CMS-1020FeatureAdd parameter to Themeporter to import without templatesFixed
CMS-1000BugCreating a youtube video results in 404Fixed
CMS-998BugVideo preview in Studio has empty "Default View"Fixed
CMS-989BugSecure Cross-domain AJAX requestsFixed
CMS-987BugChannelSegmentValidator: Ignores CAE-Escaping Mechanism in UrlPathFormattingHelperWon't Fix
CMS-934BugEmpty library window in Studio when docking twiceFixed
CMS-924BugControl Room & docked Library might break layout of Studio (size matters...)Fixed
CMS-892BugUnlocalized Document Type ChooserFixed
CMS-689BugLogin into perfect chef redirects to the registration activation pageFixed
CMS-687BugLibrary/CollectionView: pathInfoLabel/file-path-label is null in IE9Fixed
CMS-401BugExternal Library: New Content Dialog: Studio should open the newly created content object, even when the content object has been replaced during importFixed
CMS-399BugDescriptor_de is not deleted when using CreateFromTemplate DialogFixed
CMS-326BugThe "Activate Persona" Button is available even when the persona is already activeFixed

Table 2.44. 7.5.10