neues-aus-dem-opentext-wsm-reddot-updates.png
  • Thomas Pollinger
  • 04.10.2016
  • DE/EN

OpenText™ Web Site Management (RedDot CMS) Server und Delivery (Live) Server Updates

Hallo liebe Leser,

es gibt ein neue Updates in der OpenText™ Knowledge Base. Hier die Release Notes zu der neuen Version... ;)

Der Download erfolgt direkt über das OpenText™ Knowledge Center und für den Management (RedDot CMS) Server und Delivery (Live) Server gibt es folgende Updates:

OpenText™ Web Site Management Server Release 11.2

Fixed Issues in 11.2 Service Pack 2 Hotfix 30 (Build 11.2.2.1316)

Issue Name Issue Description
WSGMS-18507 Navigation Order lost after page ex- and import (ITSM 2643198)
WSGMS-18509 Master page settings are lost when importing a page export to a unrelated server (ITSM 2643198)
WSGMS-19030 Error message "Object Store: Set(...) could not be rendered" can be found in log files (ITSM 2686502, 2742425)
WSGMS-19203 When "editing a link element" related to an anchor in SmartEdit, it is not allowed to edit in one step both the link name and the URL (ITSM 2736036)
WSGMS-19398 Master Page settings not visible in a shared content classes folder
WSGMS-19399 New content class with master page settings not visible in a shared content class folder

OpenText™ Web Site Management Server Release 16

Fixed Issues in 16.0 Hotfix 9 (Build 16.0.0.1840)

New Features/Changes:

  • Translate RedDot for child elements and in form mode
  • New options when deleting publication folders
Issue Name Issue Description
WSGMS-9476 Translate RedDot doesn't appear if only child elements were edited (ITSM 2688745)
WSGMS-13072 Wrong sort order in the tab "tasks" when using the "grouping" functionality and submitting an item to the workflow (ITSM 1960011)
WSGMS-14336 Deleted DS folder result in an error message during live-server cleaning and not deleted files on DS server (ITSM 2558000)
WSGMS-15259 Remove the pop up 'do you really want to change language' (ITSM 1962111)
WSGMS-16372 Users still able to edit unreleased content class templates using the SmartEdit (ITSM 2392797)
WSGMS-17857 URLs assigned to anchors are listed as unlinked pages, when their parent page is deleted (ITSM 2596115)
WSGMS-18411 Standard field element(date type) field reference link overwrite the date format as well. (ITSM 2637176)
WSGMS-18507 Navigation Order lost after page ex- and import (ITSM 2643198)
WSGMS-18523 Page not available message for navigation pages due to value defined for maximum number of pages on navigation list (ITSM 2640299)
WSGMS-18884 Closing the Edit Style Sheet dialoge by pressing the Cancel button causes an error message to appear (ITSM 2661388)
WSGMS-18891 Functionality for assigning styles in CKEditor defect if there are any inactive style sheet folders
WSGMS-18908 DirectEdit of standard fields shifts to new line (ITSM 2680470)
WSGMS-19029 Management Server - Page headline should be mandatory in edit dialogs (ITSM 2687578)
WSGMS-19075 When we add plugins in place where "No Action Menu available" in Action Menu Text "No Action Menu available" should not appear (ITSM 2734234)
WSGMS-19080 Wrong order displayed for publication targets assigned to publication packages on project copy or import/export (ITSM 2734236)
WSGMS-19106 Management Server - Adding extra fields in "Plugin Settings" section every time we click Ok button (ITSM 2736286)
WSGMS-19124 Pre-assigning negative values to standard fields (numeric) broken (ITSM 2737506)
WSGMS-19145 The 'Administer Projects' Action Menu uses the same icon for 'Rename Project' and 'Show Project Information' (ITSM 2734212)
WSGMS-19177 "Create Element" button in Template Editor requires additional clicks after entering special characters (ITSM 2742489)
WSGMS-19203 When "editing a link element" related to an anchor in SmartEdit, it is not allowed to edit in one step both the link name and the URL (ITSM 2736036)
WSGMS-19251 Browse element with the element settings 'Image' does not work
WSGMS-19252 Browse element properties "ALT = Preassign automatically" is not saved
WSGMS-19265 Redlining does not work with images
WSGMS-19303 When I select an external folder, the check box for external folder is not automatically marked
WSGMS-19318 Detail window in dialog 'Find and Replace' shows disabled redling context menu
WSGMS-19338 Focus moves to iframe page when switching from SmartEdit to SmartTree (ITSM 2744397)
WSGMS-19349 Table 'HOMEPAGESETTINGS' does not exist error during import of a project (ITSM 2737757)
WSGMS-19350 HTTP error 403 in workflow option Page Released
WSGMS-19356 Non xml attribute conform meta data of assets are causing a failed database update to database version 011.034 (ITSM 2737757)
WSGMS-19378 Logfile-Viewer: use Monospace font instead of Arial in the Message text
WSGMS-19399 New content class with master page settings not visible in a shared content class folder
WSGMS-19403 Users logged out when clicking on the Edit Page RedDots of any given page (ITSM 2763069)
WSGMS-19476 Transfer to FTP/DS does not send Email and aborts after 3 minutes (ITSM 2844842)

​OpenText™ Web Site Management Delivery Server Release 11.2

Fixed Issues in 11.2 Service Pack 2 Hotfix 10 (11.2.2.483)

New Features/Changes:

  • Added Salesforce authentication via OAuth in the Social Identity Authentication Connector.
Issue Name Issue Description
WSGDS-8857 Placeholders like rdeXslXmlSeparator are overwritten while executing the webcomponent dynament so that the values might be wrong after the execution. This has been fixed. The values are set back to their previous value after execution now. (ITSM 2686700)
WSGDS-8872 The rdb dynament did not correctly convert empty string values to null when is-null=”true” was set. This has been fixed. (ITSM 2686658)
WSGDS-8870 There was a potential ClassCastException when using CoaAttributes of contents in the OpenApi. This has been fixed. (ITSM 2683533)
WSGDS-8895 In the Application Portal Header field names are not passed correctly. This has been fixed. (ITSM-2751364)
WSGDS-8903

Added Salesforce authentication via OAuth in the Social Identity Authentication Connector. The main steps to follow for Salesforce authentication are similar to all social authentication connector providers:
1. Register a user with your provider.
2. Register your application with your provider. When registering the application, you get the Consumer Key and Consumer Secret.
3. In Delivery Server, set up a social identity authentication connector.
4. In your project, to integrate social identity authentication, create a link that calls the xsoauth weblet.

The callback URL registered in the Salesforce application must point to the xsoauth weblet and contain the Delivery Server project and the URL parameter action=confirm.

http://yourhost.com/cps/rde/xsoauth/<project>?action=confirm

See also Documentation for Web Site Management Delivery Server Connectors “Working with social identity authentication connectors” about setting up social identity authentication and using the xsoauth weblet. (ITSM 2748969)


OpenText™ Web Site Management Delivery Server Release 16

Fixed Issues in 16.0 Hotfix 1 (16.0.0.524)

New Features/Changes:

  • Added Salesforce authentication via OAuth in the Social Identity Authentication Connector.
Issue Name Issue Description
WSGDS-8812 The Action “Clear Cache” and “Clear All Cache” in the attribute proxy were changed to “Invalidate Cache” as the attribute proxy cannot be cleared without flushing its data first. Invalidate cache will invalidate all entries and trigger a flush that is done asynchronously. After the flush the invalid entries will be removed. Note: The attribute proxy also contains data for users with active sessions. These data cannot be invalidated or removed from the attribute proxy. It will only be removed when all active sessions for the user are invalidated. (ITSM 2578111)
WSGDS-8794 A new system configuration entry “reddot.encode.portal.default.post.parameter” was added to configure the default post parameter encoding in the application portal if the browser does not send an encoding. In this case Delivery Server falls back to ISO-8895-1. If you need UTF-8 instead you can set the required encoding using the new system configuration entry. reddot.encode.portal.default.post.parameter=UTF8 reddot.encode.portal.allow.post.utf-8=true (ITSM 2607597)
WSGDS-8835 Under some circumstances, there was a duplicate key exception while writing entry and exit data in the reporting consolidation process. This has been fixed by normalizing the input values and logging around the issue was extended. (ITSM 2525214)
WSGDS-8831 Under some circumstances, the table rdPwDig in the rdeuser database continues to grow unexpectedly when updating users using the OpenAPI or the Delivery Server admin ui. This has been fixed. (ITSM 2552119)
WSGDS-8830 There was a problem consolidating custom attributes using the tracking recorder extensions. Under some circumstances not all configured attributes were written into the consolidated data. This has been fixed. (ITSM 2525214)
WSGDS-8826 Under some circumstances, Delivery Server can consume 100% in an active waiting loop. This has been fixed. (ITSM 2629022)
WSGDS-8814 Target Dynament cannot handle an OR condition combining attributes from a redundant database structure with non redundant structure attributes. The target dynament now gives a clear error message that all attributes are required to be in the used redundant database structure instead of failing silently. (ITSM 2596020)
WSGDS-8809 Under some circumstances, Delivery Server loaded to much data into the memory for blob contents. The amount of data loaded for blob contents into the cache was decreased and cache size calculation for blob contents was corrected. (ITSM 2591466)
WSGDS-8781 The limit for Database ids used in Delivery Server (or-Mapper) was INTEGER and has been increased to LONG. If you reach the Integer limit, there are several manual changes to be done to the involved databases based on database type. Instructions are provided by support. (ITSM 2628279)
WSGDS-8780 Target Dynament Performance has been improved if the target dynament selects large blob contents. (ITSM 2591466)
WSGDS-8776 Under some circumstances, projects with swapped files are not correctly imported. The swapping got lost during project export and import. This has been fixed.
WSGDS-8753 In hide rde mode, Delivery Server returned an http 500 error instead 404 error for a file not found. This has been fixed. (ITSM 2595183)
WSGDS-8755 When uploading multiple files under the same request parameter, the files were overwritten in the cache as the name of the request parameter was used for the filename in the cache for each file. This has been fixed.
WSGDS-8705 There was a problem parsing an custom iolet response that lead into an exception: 'org.xml.sax.SAXParseException.Content is not allowed in prolog'. This has been fixed. Attribute Dynament mode read with op xml now trims the input before parsing it as xml. Same was changed for custom iolets if these return xml as a string to be parsed by Delivery Server. (ITSM 2576963)
WSGDS-8822 A new xample project is included fixing some issues around Delivery Server features. The update comes as ready to import transport package.
WSGDS-8821 Under some circumstances the “requires valid xsrf token” option on an xml content was not working properly. This has been fixed.
WSGDS-8803 Repository dynament mode read requires to query a specific version when used with Content Server 16.
WSGDS-8802
/ WSGDS-8801
Some unused or internal methods and parameters were removed from the REST Api. Documentation of solr autocomplete method in the REST api was improved. The method is only supported with Apache Solr but not with Info Fusion.
WSGDS-8800
/ WSGDS-8793
There were some issues using the reporting widget or the REST api from Delivery Server with hide rde mode. These have been fixed.
WSGDS-8799 New system configuration entry “reddot.searchengine.task.timeout" was added to configure the timeout for search engine tasks.
WSGDS-8798 Logging configuration sample was added for Tracking recorder plugins.
WSGDS-8546 The data consolidation in the reporting module failed with an oracle exception under some circumstances. This has been fixed. (ITSM 2237927)
WSGDS-8802 Some unused response values were removed from the Delivery Server REST API for reporting.
WSGDS-8856 When publishing from Management Server to Delivery Server with keywords including xml entities and using the option resolveentities, there was an error “the attribute path contains invalid characters”. The resolve-entities option was evaluated too late after splitting the keywords. This has been fixed. (ITSM 2552119)
WSGDS-8859 MSSQL 2016 has been added to the supported databases for Delivery Server
WSGDS-8866 Upgrade tomcat to the latest version to include latest security patches and to protect against security vulnerabilities.
WSGDS-8868 Content Server Search Connector was updated to use a thinner api method for fetching data sources and their process status. (ITSM 2640549)
WSGDS-8877 The rdb dynament did not correctly convert empty string values to null when is-null=”true” was set. This has been fixed. (ITSM 2686658)
WSGDS-8879 Placeholders like rdeXslXmlSeparator are overwritten while executing the webcomponent dynament so that the values might be wrong after the execution. This has been fixed. The values are set back to their previous value after execution now. (ITSM 2686700)
WSGDS-8880 The include dynament was not correctly working with the mime type "application/json". The mime type has been added in the mimetype.txt. (ITSM 2730317)
WSGDS-8887 There was a potential ClassCastException when using CoaAttributes of contents in the OpenApi. This has been fixed. (ITSM 2683533)
WSGDS-8894 The deploy button in a Hotdeployment configuration did not refresh other class methods. This has been fixed. Be aware that contents might be cached and to see effect under some cases the affected contents must be removed from cache in addition to deploying new classes. (ITSM 2750084)
WSGDS-8899 In the Application Portal Header field names are not passed correctly. This has been fixed. (ITSM-2751364)
WSGDS-8904 There was a NumberFormatException when upgrading from 11.2 SP2 HF5 to 16.0. The upgrade installer could not properly read/detect the existing version. This has been fixed. (ITSM 2757038)
WSGDS-8903

Added Salesforce authentication via OAuth in the Social Identity Authentication Connector. The main steps to follow for Salesforce authentication are similar to all social authentication connector providers:
1. Register a user with your provider.
2. Register your application with your provider. When registering the application, you get the Consumer Key and Consumer Secret.
3. In Delivery Server, set up a social identity authentication connector.
4. In your project, to integrate social identity authentication, create a link that calls the xsoauth weblet.

The callback URL registered in the Salesforce application must point to the xsoauth weblet and contain the Delivery Server project and the URL parameter action=confirm.

http://yourhost.com/cps/rde/xsoauth/<project>?action=confirm

See also Documentation for Web Site Management Delivery Server Connectors “Working with social identity authentication connectors” about setting up social identity authentication and using the xsoauth weblet. (ITSM 2748969)

WSGDS-8874 The REST api /rest/v1/solr/select was changed to includeMode="metainfo,meta" for a better search performance.

Legende:

 Editorial
 Development
Administration

 

Social Media