This chapter contains all changes made in Release 7.5.10 of CoreMedia Digital Experience Platform 8.
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:
Product | Key | Version |
---|---|---|
CoreMedia Application Maven Plug-in | APPPLUGIN | 2.7.9 |
CoreMedia Project Maven Extension | PROJEXT | 1.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
Key | Type | Summary | Status |
---|---|---|---|
CMS-1796 | Bug | CommerceCacheInvalidationListener sometimes does now wake up again after errors | Fixed |
CMS-1390 | Bug | Verbose aware Command Line Tools do not log verbose messages | Fixed |
CMS-1384 | Bug | SessionSynchronizer logs the guest user out | Fixed |
CMS-1351 | Bug | Unresponsive Browser when opening "Autumn Dishes Article" in Studio - Many Entries in Image Linklist | Fixed |
CMS-1344 | Bug | e-Marketing spots in Fragment cant be displayed | Fixed |
CMS-1343 | Bug | RSS Feeds are broken | Fixed |
CMS-1342 | Bug | Media on Live-CAE redirect to PerfectChef | Fixed |
CMS-1337 | Bug | Article Studio Preview fails | Fixed |
CMS-1335 ( 36109 ) | Bug | Wrong commerce URLs for categories and products | Fixed |
CMS-1328 | Bug | Repository Template Pattern not configured for site specific templates | Fixed |
CMS-1327 | Bug | Sitemap Generation broken | Fixed |
CMS-1319 | Bug | Links in dynamic fragments are rendered relative | Fixed |
CMS-1315 | Bug | FragmentCommerceContextInterceptor resolves wrong locale/wrong site | Fixed |
CMS-1225 | Change | Remove "/page" prefix from Handlers and Apache rules | Fixed |
CMS-1107 | Bug | Studio Device Slider does not work with landscape mode of PerfectChef | Won't Fix |
CMS-1020 | Feature | Add parameter to Themeporter to import without templates | Fixed |
CMS-1000 | Bug | Creating a youtube video results in 404 | Fixed |
CMS-998 | Bug | Video preview in Studio has empty "Default View" | Fixed |
CMS-989 | Bug | Secure Cross-domain AJAX requests | Fixed |
CMS-987 | Bug | ChannelSegmentValidator: Ignores CAE-Escaping Mechanism in UrlPathFormattingHelper | Won't Fix |
CMS-934 | Bug | Empty library window in Studio when docking twice | Fixed |
CMS-924 | Bug | Control Room & docked Library might break layout of Studio (size matters...) | Fixed |
CMS-892 | Bug | Unlocalized Document Type Chooser | Fixed |
CMS-689 | Bug | Login into perfect chef redirects to the registration activation page | Fixed |
CMS-687 | Bug | Library/CollectionView: pathInfoLabel/file-path-label is null in IE9 | Fixed |
CMS-401 | Bug | External Library: New Content Dialog: Studio should open the newly created content object, even when the content object has been replaced during import | Fixed |
CMS-399 | Bug | Descriptor_de is not deleted when using CreateFromTemplate Dialog | Fixed |
CMS-326 | Bug | The "Activate Persona" Button is available even when the persona is already active | Fixed |
Table 2.44. 7.5.10