{
"response": [
{
"_id": {
"$oid": "635fe2a994436e1bc82579e2"
},
"hotfix_name": "CD_2011.1.0.78968",
"modified_date": {
"$date": 1329990741832
},
"problem_description": "The ambient data framework needs to be have the ability to alter the behaviour of the claimstore. This specific scenario is about supporting smarttarget profiles in which different values \r\nshould override the default values in the claimstore. This is done to simulate different visitors and their claims. In order to support this the claimstore should become more flexible in \r\nits behaviour, therefore a more generic claimstore creation mechanism should be created. This could be as simple as providing the ability for a custom 'claimstorefactory' which is then \r\nused by the default ambient framework. Anyone could implement a customer claimstorefactory which in turn can provide their custom version of the claimstore itself.\r\n",
"readme_text": "Release Notes for Hotfix TT78968\r\n================================\r\n\r\nVersion:\r\n========\r\nThis hotfix is intended for Tridion 2011 SP1 only.\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n- TT78968 Ability to override claimstore behaviour for read-only claims\r\n\r\nInstallation:\r\n=============\r\n.NET Environment:\r\n1. Ensure the application pool of your application and/or IIS Server has been stopped;\r\n2. Copy the distributed Tridion.ContentDelivery.Interop.dll and Tridion.ContentDelivery.AmbientData.dll over the existing dlls inside the Bin folder of your webApplication;\r\n3. Copy the distributed cd_ambient.jar and cd_core.jar over the existing jars inside the Bin\\lib folder of your webApplication;\r\n4. Start the application pool and/or IIS Server.\r\n\r\nJava Environment:\r\n1. Ensure the webApplication and/or your WebApplication Server has been stopped;\r\n3. Copy the distributed cd_ambient.jar and cd_core.jar over the existing jars inside the WEB-INF\\lib folder of your webApplication;\r\n3. Start the webApplication and/or your WebApplication Server.\r\n\r\nDistributed files:\r\n==================\r\nconfigurations\\cd_ambient_conf_sample.xml\r\ndotNet\\x86\\Tridion.ContentDelivery.AmbientData.dll\r\ndotNet\\x86\\Tridion.ContentDelivery.Interop.dll\r\ndotNet\\x86_64\\Tridion.ContentDelivery.AmbientData.dll\r\ndotNet\\x86_64\\Tridion.ContentDelivery.Interop.dll\r\njava\\cd_ambient.jar\r\njava\\cd_core.jar\r\nschemas\\cd_ambient_conf.xsd\r\n\r\nDependencies:\r\n=============\r\nn.a.\r\n\r\nFixed problems:\r\n===============\r\nTT78968\r\nProblem Description\r\n-------------------\r\nThe ambient data framework needs to be have the ability to alter the behaviour of the claimstore. This specific scenario is about supporting smarttarget profiles in which different values \r\nshould override the default values in the claimstore. This is done to simulate different visitors and their claims. In order to support this the claimstore should become more flexible in \r\nits behaviour, therefore a more generic claimstore creation mechanism should be created. This could be as simple as providing the ability for a custom 'claimstorefactory' which is then \r\nused by the default ambient framework. Anyone could implement a customer claimstorefactory which in turn can provide their custom version of the claimstore itself.\r\n\r\nHotfix Description\r\n-------------------\r\nAmbient Data Framework now allows implementers to define custom ClaimStoreProviders in order to offer them full control regarding behavior of the ClaimStore.\r\n\r\nClaimStoreProviders can be configured by adding a section in cd_ambient_conf.xml at Configuration/ClaimStoreProvider. Here is an example configuration (which is also the default one used on a .NET environment):\r\ncom.tridion.ambientdata.claimstore.providers.DotNetClaimStoreProvider\r\n\r\nThe string value of ClaimStoreProvider needs to point to a class in the classpath which implements the com.tridion.ambientdata.claimstore.providers.ClaimStoreProvider interface. This interface defines a single \r\nmethod which needs to return a valid not null ClaimStore to be used by Ambient Framework:\r\n\r\n/**\r\n * Creates a new instance of a ClaimStore to be used by AmbientFramework.\r\n *\r\n * @return new instance of a ClaimStore to be used by AmbientFramework.\r\n */\r\n public ClaimStore newClaimStore();\r\n\r\n\r\nDisclaimer:\r\n===========\r\nHotfixes are released at the discretion of Tridion based on technical\r\ncomplexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/\r\nconfiguration and therefore should only be installed if approved by Tridion\r\nCustomer Support. Hotfixes should be replaced as soon as possible by the\r\nsubsequent service pack where the problem is fixed.\r\n\r\n(c) 2012 SDL Tridion B.V.\r\n",
"version": "2011 SP1"
},
{
"_id": {
"$oid": "635fe2ab94436e1bc8257a22"
},
"hotfix_name": "CD_2011.1.1.85490",
"modified_date": {
"$date": 1372856177988
},
"problem_description": "The TCDLTransformer used for processing incoming Pages/ComponentPresentation was statically initialized without taking into account the cd_deployer_conf.xml.\r\n",
"readme_text": "Release Notes for Hotfix TT85490\r\n================================\r\n\r\nVersion:\r\n========\r\nThis hotfix is intended only for The New Tridion UI (based on Tridion 2011 SP1 HR1)\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n- TT85490 When executing BrokerQuery in session, returned result from all other sessions.\r\n\r\nInstallation:\r\n=============\r\nDeployer environment:\r\n---------------------\r\nJava Environment with Session Preview Staging site:\r\n1. Ensure that you have a correct installed Session Preview Staging Site installation inside your web application\r\n2. Stop your web application server or web application containing the Session Preview Staging Site\r\n3. Copy the distributed jar files inside your web application WEB-INF\\lib directory\r\n4. Start your web application server or web application\r\n\r\nJava Environment with Session Preview WebService:\r\n1. Ensure that you have a correct installed Session Preview WebService installation inside your web application\r\n2. Stop your web application server or web application containing the Session Preview WebService\r\n3. Copy the distributed jar files inside your web application WEB-INF\\lib directory\r\n4. Start your web application server or web application\r\n\r\n.NET Environment with Session Preview Staging site:\r\n1. Ensure the application pool and or IIS Server has been stopped\r\n2. Copy the distributed jar files inside the IIS application directory bin\\lib directory. In case of central tridion installation please copy the distributed jar files\r\ninto the installation directory \\lib folder.\r\n2. Copy the distributed Tridion.ContentDelivery.Preview.dll over the existing dll inside the Bin folder of your website/application;\r\n3. Start the application pool and or IIS Server\r\n\r\n.NET Environment with Preview WebService:\r\n1. Ensure the application pool and or IIS Server has been stopped\r\n2. Copy the distributed jar files inside the IIS application directory bin\\lib directory. In case of central tridion installation please copy the distributed jar files\r\ninto the installation directory \\lib folder.\r\n3. Start the application pool and or IIS Server\r\n\r\n\r\nDistributed files:\r\n==================\r\ncd_session.jar\r\n\r\nDependencies:\r\n=============\r\nTridion 2011 SP1 HR1\r\n\r\nFixed problems:\r\n===============\r\nTT85490\r\nProblem Description\r\n-------------------\r\nThe TCDLTransformer used for processing incoming Pages/ComponentPresentation was statically initialized without taking into account the cd_deployer_conf.xml.\r\n\r\nHotfix Description\r\n-------------------\r\nFixed the problem when executing BrokerQuery in session, returned result from all other sessions.\r\n\r\nDisclaimer:\r\n===========\r\nHotfixes are released at the discretion of Tridion based on technical\r\ncomplexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/\r\nconfiguration and therefore should only be installed if approved by Tridion\r\nCustomer Support. Hotfixes should be replaced as soon as possible by the\r\nsubsequent service pack where the problem is fixed.\r\n\r\n(c) 2012 SDL Tridion B.V.\r\n",
"version": "2011 SP1 HR#1"
},
{
"_id": {
"$oid": "635fe2b294436e1bc8257bdd"
},
"hotfix_name": "CM_9.0.1.26397",
"modified_date": {
"$date": 1634819417379
},
"problem_description": "GetPublishState function being called from where clause caused poor performance of COMP_GETPUBLISHITEMS stored procedure which had significant impact on the publishing time\r\n",
"readme_text": "Release Notes for Hotfix CRQ-26397\r\n\r\nVersion: \r\n This hotfix is intended for SDL Web 9.0.1 on Oracle.\r\n\r\nProblem description:\r\n GetPublishState function being called from where clause caused poor performance of COMP_GETPUBLISHITEMS stored procedure which had significant impact on the publishing time\r\n\r\nHotfix description:\r\n Embedd the GetPublishState function call. Besides that added the missing index for T_COMPONENTPRESENTATIONS table\r\n\r\nInstallation:\r\n 1. Replace &TBLSPC_SESSION_DATA placeholder within TCM_UPDATE_TABLES.sql file with the table space used at your environment for the temporary tables. Default value is \"SESSION_DATA\".\r\n 2. Stop all TCM Services, IIS Service, and the TCM COM+ Application.\r\n 3. Using SQL*Plus, connect as \"tridion_sys\" to the database instance. \r\n 4. Temporarily grant additional rights to the Tridion database user (typically TCMDBUser):\r\n\tGRANT CREATE TRIGGER TO &TCMDBUser;\r\n\tGRANT CREATE PROCEDURE TO &TCMDBUser;\r\n \tGRANT CREATE ANY TABLE TO &TCMDBUser;\r\n\tGRANT CREATE SEQUENCE TO &TCMDBUser;\r\n GRANT CREATE ANY TYPE TO &TCMDBUser;\r\n GRANT CREATE JOB TO &TCMDBUser;\r\n\tGRANT EXECUTE ON SYS.DBMS_UTILITY TO &TCMDBUser;\r\n 5. Using SQL*Plus, log in as the Tridion database user (typically TCMDBUser).\r\n 6. Execute the SQL script CM_9.0.1.26397_ORACLE.sql.\r\n 7. Check the file CM_9.0.1.26397.log for errors.\r\n 8. Revoke the additional rights from the Tridion database user\t\r\n\tREVOKE EXECUTE ON SYS.DBMS_UTILITY FROM &TCMDBUSER;\r\n\tREVOKE CREATE TRIGGER FROM &TCMDBUser;\t \r\n\tREVOKE CREATE PROCEDURE FROM &TCMDBUser;\r\n\tREVOKE CREATE ANY TABLE FROM &TCMDBUser;\r\n REVOKE CREATE ANY TYPE FROM &TCMDBUser;\r\n REVOKE CREATE JOB FROM &TCMDBUser;\r\n\tREVOKE CREATE SEQUENCE FROM &TCMDBUser;\r\n 9. Restart the IIS Service, TCM Services and TCM COM+ Application.\r\n\r\nDistributed files:\r\n CM_9.0.1.26397_ORACLE.sql\r\n EDA_ITEMS.sql\r\n TCM_UPDATE_TABLES.sql\r\n TCM_RECOMPILE_PACKAGES.sql\r\n TCM_SESSIONS.sql\r\n Readme.txt (this file)\r\n\r\nFixes included:\r\n NA\r\n \r\nDependencies:\r\n NA\r\n\r\nDisclaimer:\r\nHotfixes (as defined under the relevant RWS product release policy) are released at RWSs discretion based on technical complexity, customer business requirements and schedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration in accordance with the Software Documentation and therefore should only be installed if approved by RWS Technical Support. Hotfixes should be replaced as soon as possible by the subsequent cumulative update where the problem is fixed.\r\n\r\nCopyright 2021 All Rights Reserved by the RWS Group for and on behalf of its affiliates and subsidiaries. All company product or service names referenced herein are properties of their respective owners.",
"version": "Sites 9.0.1"
},
{
"_id": {
"$oid": "635fe2b494436e1bc8257c13"
},
"hotfix_name": "CM_9.1.0.25181",
"modified_date": {
"$date": 1627372683977
},
"problem_description": "CM slowness for non-admin and admin users.\r\n",
"readme_text": "Release Notes for Hotfix CRQ-25181\r\n\r\nVersion: \r\n This hotfix is intended for SDL Web 9.1 on Oracle.\r\n\r\nProblem description:\r\n CM slowness for non-admin and admin users.\r\n \r\nHotfix description:\r\n EDA_ITEMS_FUNCTIONS.GETPUBLISHSTATE was made inline for the stored procedures.\r\n \r\nInstallation:\r\n 1. Stop all TCM Services, IIS Service, and the TCM COM+ Application.\r\n 2. Using SQL*Plus, connect as \"tridion_sys\" to the database instance. \r\n 3. Temporarily grant additional rights to the Tridion database user (typically TCMDBUser):\r\n\tGRANT CREATE TRIGGER TO &TCMDBUser;\r\n\tGRANT CREATE PROCEDURE TO &TCMDBUser;\r\n \tGRANT CREATE ANY TABLE TO &TCMDBUser;\r\n\tGRANT CREATE SEQUENCE TO &TCMDBUser;\r\n\tGRANT EXECUTE ON SYS.DBMS_UTILITY TO &TCMDBUser;\r\n 4. Using SQL*Plus, log in as the Tridion database user (typically TCMDBUser).\r\n 5. Execute the SQL script CM_9.1.0.25181.sql.\r\n 6. Check the file CM_9.1.0.25181.log for errors.\r\n 7. Revoke the additional rights from the Tridion database user\t\r\n\tREVOKE EXECUTE ON SYS.DBMS_UTILITY FROM &TCMDBUSER;\r\n\tREVOKE CREATE TRIGGER FROM &TCMDBUser;\t \r\n\tREVOKE CREATE PROCEDURE FROM &TCMDBUser;\r\n\tREVOKE CREATE ANY TABLE FROM &TCMDBUser;\r\n\tREVOKE CREATE SEQUENCE FROM &TCMDBUser;\r\n 8. Restart the IIS Service, TCM Services and TCM COM+ Application.\r\n\r\nDistributed files:\r\n CM_9.1.0.25181.sql\r\n EDA_ITEMS.sql\r\n TCM_WORKFLOW.sql\r\n TCM_RECOMPILE_PACKAGES.sql\r\n Readme.txt (this file)\r\n\r\nFixes included:\r\n CM_9.1.0_20842\r\n CM_9.1.0_20917\r\n CM_9.1.0_22881\r\n CM_9.1.0_22130\r\n \r\nDependencies:\r\n NA\r\n\r\nDisclaimer:\r\n Hotfixes (as defined under the relevant RWS product release policy) are released at RWSs discretion based on technical complexity, customer business requirements and schedules. \r\n Hotfixes are made and tested only for the described problem on a particular environment/configuration in accordance with the Software Documentation and therefore should only be installed if approved by RWS Technical Support. \r\n Hotfixes should be replaced as soon as possible by the subsequent cumulative update where the problem is fixed.\r\n \r\nCopyright 2021 All Rights Reserved by the RWS Group for and on behalf of its affiliates and subsidiaries. All company product or service names referenced herein are properties of their respective owners.\r\n",
"version": "Sites 9.1"
},
{
"_id": {
"$oid": "635fe2b494436e1bc8257c16"
},
"hotfix_name": "CM_9.1.0.27857",
"modified_date": {
"$date": 1647530295542
},
"problem_description": "Components with special symbols in title are not saved properly when linked to publication metadata.\r\n",
"readme_text": "Release Notes for Hotfix CRQ-27857\r\n\r\nVersion: \r\n This hotfix is intended for SDL Tridion Sites 9.1 with with Oracle database.\r\n\r\nProblem description:\r\n Components with special symbols in title are not saved properly when linked to publication metadata.\r\n\t\r\nHotfix description:\r\n Double XML escaping was mistakenly introduced when migrating to the native XML functions.\r\n\t\r\nInstallation:\r\n 1. Stop all TCM Services, IIS Service, and the TCM COM+ Application.\r\n 2. Using SQL*Plus, connect as \"tridion_sys\" to the database instance. \r\n 3. Temporarily grant additional rights to the Tridion database user (typically TCMDBUser):\r\n\tGRANT CREATE TRIGGER TO &TCMDBUser;\r\n\tGRANT CREATE PROCEDURE TO &TCMDBUser;\r\n \tGRANT CREATE ANY TABLE TO &TCMDBUser;\r\n\tGRANT CREATE SEQUENCE TO &TCMDBUser;\r\n\tGRANT EXECUTE ON SYS.DBMS_UTILITY TO &TCMDBUser;\r\n 4. Using SQL*Plus, log in as the Tridion database user (typically TCMDBUser).\r\n 5. Execute the SQL script CM_9.1.0.27857_ORACLE.sql.\r\n 6. Check the file CM_9.1.0.27857.log for errors.\r\n 7. Revoke the additional rights from the Tridion database user\t\r\n\tREVOKE EXECUTE ON SYS.DBMS_UTILITY FROM &TCMDBUSER;\r\n\tREVOKE CREATE TRIGGER FROM &TCMDBUser;\t \r\n\tREVOKE CREATE PROCEDURE FROM &TCMDBUser;\r\n\tREVOKE CREATE ANY TABLE FROM &TCMDBUser;\r\n\tREVOKE CREATE SEQUENCE FROM &TCMDBUser;\r\n 8. Restart the IIS Service, TCM Services and TCM COM+ Application.\r\n\r\nDistributed files:\r\n CM_9.1.0.27857_ORACLE.sql\r\n TCM_RECOMPILE_PACKAGES.sql\r\n EDA_PUBLICATIONS.sql\r\n Readme.txt (this file)\r\n\r\nFixes included:\r\n NA\r\n\r\nDependencies:\r\n NA\r\n\r\nDisclaimer:\r\n Hotfixes (as defined under the relevant RWS product release policy) are released at RWSs discretion based on technical complexity, customer business requirements and schedules. \r\n Hotfixes are made and tested only for the described problem on a particular environment/configuration in accordance with the Software Documentation and therefore should only be installed if approved by RWS Technical Support. \r\n Hotfixes should be replaced as soon as possible by the subsequent cumulative update where the problem is fixed.\r\n \r\nCopyright 2022 All Rights Reserved by the RWS Group for and on behalf of its affiliates and subsidiaries. All company product or service names referenced herein are properties of their respective owners\r\n",
"version": "Sites 9.1"
},
{
"_id": {
"$oid": "635fe2b794436e1bc8257c57"
},
"hotfix_name": "CM_9.5.0.26624",
"modified_date": {
"$date": 1636536624914
},
"problem_description": "CM Adddons cache keeps growing \r\n",
"readme_text": "Release Notes for Hotfix CRQ-26624\r\n\r\nVersion: \r\n This hotfix is intended for SDL Web 9.5\r\n\r\nProblem description:\r\n\tCM Adddons cache keeps growing \r\n\r\nHotfix description:\r\n Stop creating new folders for processes which are started from the same location. \r\n Therefore the number of folders in the cache located at %TRIDION_HOME%\\Addons\\RepositoryCache will stop growing\r\n \r\nInstallation:\r\n 1. Stop all TCM Services, IIS and the TCM COM+ Application.\r\n 2. Remove the file Tridion.AddonService.SDK.dll located in the %WINDIR%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.AddonService.SDK\\v4.0_1.1.0.0__ddfc895746e5ee6b.\r\n 3. Copy the Tridion.AddonService.SDK.dll file from this hotfix to the %WINDIR%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.AddonService.SDK\\v4.0_1.1.0.0__ddfc895746e5ee6b.\r\n 4. Replace Tridion.AddonService.SDK.dll in the WebRoot bin folder (%TRIDION_HOME%\\web\\WebUI\\WebRoot\\bin\\Tridion.AddonService.SDK.dll).\r\n 5. Replace Tridion.AddonService.SDK.dll in the OpenAPI bin folder (%TRIDION_HOME%\\openapi\\service\\bin\\Tridion.AddonService.SDK.dll).\r\n 6. Start the IIS, TCM Services and TCM COM+ Application.\r\n\r\nDistributed files:\r\n Tridion.AddonService.SDK.dll (File Version 1.1.0.128/Assembly version 1.1.0.128)\r\n Readme.txt (this file)\r\n\r\nFixes included:\r\n None\r\n \r\nDependencies:\r\n None\r\n\r\nDisclaimer:\r\nHotfixes (as defined under the relevant RWS product release policy) are released at RWSs discretion based on technical complexity, customer business requirements and schedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration in accordance with the Software Documentation and therefore should only be installed if approved by RWS Technical Support. Hotfixes should be replaced as soon as possible by the subsequent cumulative update where the problem is fixed.\r\n\r\nCopyright 2021 All Rights Reserved by the RWS Group for and on behalf of its affiliates and subsidiaries. All company product or service names referenced herein are properties of their respective owners.",
"version": "Sites 9.5"
},
{
"_id": {
"$oid": "635fe2a994436e1bc82579dc"
},
"hotfix_name": "CD_2011.1.0.77133",
"modified_date": {
"$date": 1322139412997
},
"problem_description": "The Component link field type not exposed in keyword metadata when requesting keyword metadata in the broker API.\r\n",
"readme_text": "Release Notes for Hotfix TT77133\r\n================================\r\n\r\nVersion:\r\n========\r\nThis hotfix is intended only for Tridion 2011 SP1\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n- TT77133 Component link field type not exposed in keyword metadata\r\n\r\nInstallation:\r\n=============\r\nDeployer environment:\r\n---------------------\r\nJava Environment with HttpUpload:\r\n1. Ensure that you have a correct installed Content Delivery installation inside your web application\r\n2. Stop your web application server or web application containing the deployer httpupload\r\n3. Copy the distributed jar files inside your web application WEB-INF\\lib directory\r\n4. Start your web application server or web application\r\n\r\n.NET Environment with HttpUpload:\r\n1. Ensure the application pool and or IIS Server has been stopped\r\n2. Copy the distributed jar files inside the IIS application directory bin\\lib directory. In case of central tridion installation please copy the distributed jar files\r\ninto the installation directory \\lib folder.\r\n3. Start the application pool and or IIS Server\r\n\r\nStandalone deployer:\r\n1. Ensure the deployer service has been stopped\r\n2. Copy the distributed jar files inside your 'Tridion installation folder'\\lib directory\r\n3. Start the deployer service\r\n\r\nDistributed files:\r\n==================\r\ncd_datalayer.jar\r\n\r\nDependencies:\r\n=============\r\nn.a.\r\n\r\nFixed problems:\r\n===============\r\nTT77133\r\nProblem Description\r\n-------------------\r\nThe Component link field type not exposed in keyword metadata when requesting keyword metadata in the broker API.\r\n\r\nHotfix Description\r\n-------------------\r\nThe issues occurs due to incorrect namespace handling of the keyword metadata in taxonomies. The link information was in a different\r\nunrecognized namespace and therefore ignored. This has been resolved by properly handling the namespace containing the link information\r\nfor the keyword.\r\n\r\nDisclaimer:\r\n===========\r\nHotfixes are released at the discretion of Tridion based on technical\r\ncomplexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/\r\nconfiguration and therefore should only be installed if approved by Tridion\r\nCustomer Support. Hotfixes should be replaced as soon as possible by the\r\nsubsequent service pack where the problem is fixed.\r\n\r\n(c) 2011 SDL Tridion B.V.\r\n",
"version": "2011 SP1"
},
{
"_id": {
"$oid": "635fe2a994436e1bc82579de"
},
"hotfix_name": "CD_2011.1.0.78258",
"modified_date": {
"$date": 1329993871416
},
"problem_description": "Dynamic Meta URL mapper is not flexible and does not allow multiple url's for a single publication\r\n",
"readme_text": "Release Notes for Hotfix TT78258\r\n================================\r\n\r\nVersion:\r\n========\r\nThis hotfix is intended only for Tridion 2011 SP1\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n- TT78258 Dynamic Meta URL mapper is not flexible and does not allow multiple url's for a single publication\r\n\r\nInstallation:\r\n=============\r\nDeployer environment:\r\n---------------------\r\nWebsite on a Java Environment:\r\n1. Ensure that you have a correct installed Content Delivery installation inside your web application\r\n2. Stop your web application server or web application containing the website\r\n3. Copy the distributed jar file inside your web application WEB-INF\\lib directory\r\n4. Start your web application server or web application\r\n\r\nWebsite on a .NET Environment:\r\n1. Ensure the application pool and or IIS Server has been stopped\r\n2. Copy the distributed jar file inside the IIS application directory bin\\lib directory. In case of central tridion installation please copy the distributed jar files\r\ninto the installation directory \\lib folder.\r\n3. Start the application pool and or IIS Server\r\n\r\nDistributed files:\r\n==================\r\ncd_core.jar\r\ncd_dynamic.jar\r\ncd_dynamic_conf_sample.xml (sample dynamic configuration file)\r\ncd_dynamic_conf.xsd (cd dynamic configuration schema file. The schema file is already present in cd_core.jar.)\r\n\r\nDependencies:\r\n=============\r\nn.a.\r\n\r\nFixed problems:\r\n===============\r\nTT78258\r\nProblem Description\r\n-------------------\r\nDynamic Meta URL mapper is not flexible and does not allow multiple url's for a single publication\r\n\r\nHotfix Description\r\n-------------------\r\nDynamic Meta URL resolving mechanism is redesigned to be more robust and to allow multiple URL's for a single publication.\r\n\r\nDisclaimer:\r\n===========\r\nHotfixes are released at the discretion of Tridion based on technical\r\ncomplexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/\r\nconfiguration and therefore should only be installed if approved by Tridion\r\nCustomer Support. Hotfixes should be replaced as soon as possible by the\r\nsubsequent service pack where the problem is fixed.\r\n\r\n(c) 2011 SDL Tridion B.V.",
"version": "2011 SP1"
},
{
"_id": {
"$oid": "635fe2b794436e1bc8257c4a"
},
"hotfix_name": "CME_9.5.0.26615",
"modified_date": {
"$date": 1637307917250
},
"problem_description": "An Allowed Schema shows as an Available Schema on a Component Link in some situations\r\n",
"readme_text": "\ufeffRelease Notes for Hotfix CRQ-26615\r\n\r\nVersion:\r\nThis hotfix is intended for SDL Tridion Sites 9.5\r\n\r\nProblem description: \r\nAn Allowed Schema shows as an Available Schema on a Component Link in some situations\r\n\r\nHotfix description:\r\nThe issue was reproducible when opening the schema having itself in a list of the available schemas. \r\nIn that case being opened schemas gets the -v0 prefix in the id which broke the logic distinguishing the list of the available schemas.\r\n\r\nInstallation:\r\n\t1. Create a backup of %TRIDION_HOME%\\web\\WebUI\\Editors\\CME\\Controls/FieldDesigner/FieldTypes/MultimediaLinkField.js file\r\n\t2. Copy the MultimediaLinkField.js file from this hotfix to %TRIDION_HOME%\\web\\WebUI\\Editors\\CME\\Controls/FieldDesigner/FieldTypes\r\n\t3. Locate \\Configuration\\servicemodel\\server node in the %TRIDION_HOME%\\web\\WebUI\\WebRoot\\Configuration\\System.config file and increase the value of its 'modification' attribute to notify client browsers to update their cache.\r\n\r\n\r\nDistributed files:\r\n- Readme.txt (this file)\r\n- MultimediaLinkField.js\r\n\r\nFixes included:\r\nn/a\r\n\r\nDependencies:\r\nn/a\r\n\r\nDISCLAIMER:\r\nHotfixes (as defined under the relevant RWS product release policy) are released at RWS\u2019s discretion based on technical complexity, customer business requirements and schedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration in accordance with the Software Documentation and therefore should only be installed if approved by RWS Technical Support. Hotfixes should be replaced as soon as possible by the subsequent cumulative update where the problem is fixed.\r\n \r\nCopyright \u00a9 2021 All Rights Reserved by the RWS Group for and on behalf of its affiliates and subsidiaries. All company product or service names referenced herein are properties of their respective owners.",
"version": "Sites 9.5"
},
{
"_id": {
"$oid": "635fe2b294436e1bc8257bda"
},
"hotfix_name": "CME_9.0.1.18769",
"modified_date": {
"$date": 1639064313741
},
"problem_description": "Option \"Localize this item and open it in edit mode\" does not show up the first time from a Page\r\n",
"readme_text": "Release Notes for Hotfix CRQ-18769\r\n\r\nVersion:\r\nThis hotfix is intended for SDL Tridion Sites 9.0 CU1\r\n\r\nProblem description: \r\nOption \"Localize this item and open it in edit mode\" does not show up the first time from a Page\r\n\r\nHotfix description:\r\nThe component partially loaded by the component list didn't contain enough properties to be able to identify whether that is localizable. Extended the range of the requested properties with the applicable actions.\r\n\r\nInstallation:\r\n\t1. Create a backup of %TRIDION_HOME%\\web\\WebUI\\Editors\\CME\\Tabs\\PageDesign.js\r\n\t2. Copy the PageDesign.js file from this hotfix to %TRIDION_HOME%\\web\\WebUI\\Editors\\CME\\Tabs folder\r\n\t3. Locate \\Configuration\\servicemodel\\server node in the %TRIDION_HOME%\\web\\WebUI\\WebRoot\\Configuration\\System.config file and increase the value of its 'modification' attribute to notify client browsers to update their cache.\r\n\r\nDistributed files:\r\n- Readme.txt (this file)\r\n- PageDesign.js\r\n\r\nFixes included:\r\nn/a\r\n\r\nDependencies:\r\nn/a\r\n\r\nDisclaimer:\r\n Hotfixes (as defined under the relevant RWS product release policy) are released at RWS\u2019s discretion based on technical complexity, customer business requirements and schedules. \r\n Hotfixes are made and tested only for the described problem on a particular environment/configuration in accordance with the Software Documentation and therefore should only be installed if approved by RWS Technical Support. \r\n Hotfixes should be replaced as soon as possible by the subsequent cumulative update where the problem is fixed.\r\n \r\nCopyright \u00a9 2021 All Rights Reserved by the RWS Group for and on behalf of its affiliates and subsidiaries. All company product or service names referenced herein are properties of their respective owners.",
"version": "Sites 9.0.1"
},
{
"_id": {
"$oid": "635fe2b294436e1bc8257bdb"
},
"hotfix_name": "CME_9.0.1.25218",
"modified_date": {
"$date": 1627914181441
},
"problem_description": "Cross-site scripting vulnerability in CME\r\n",
"readme_text": "Release Notes for Hotfix CRQ-25218\r\n\r\nVersion:\r\nThis hotfix is intended for SDL Tridion Sites 9.0 Cumulative Update 1.\r\n\r\nProblem description: \r\nCross-site scripting vulnerability in CME\r\n\r\nHotfix description:\r\nAdded escaping user input\r\n\r\nInstallation:\r\n\t1. Backup files Tridion.Web.UI.Core.dll from %TRIDION_HOME%\\web\\WebUI\\WebRoot\\bin folder.\r\n\t2. Replace files Tridion.Web.UI.Core.dll in %TRIDION_HOME%\\web\\WebUI\\WebRoot\\bin folder with file from this hotfix. If any extesnions or services uses Tridion.Web.UI.Core.dll, please check and replace as well.\r\n\t3. Recycle the application pool or restart your IIS service.\r\n\r\nDistributed files:\r\n- Readme.txt (this file)\r\n- Tridion.Web.UI.Core.dll (File Version 9.0.0.992/Assembly version 9.0.0.0)\r\n\r\nDependencies:\r\nn/a\r\n\r\nIncludes:\r\nn/a\r\n\r\nDisclaimer:\r\nHotfixes (as defined under the relevant RWS product release policy) are released at RWS\u2019s discretion based on technical complexity, customer business requirements and schedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration in accordance with the Software Documentation and therefore should only be installed if approved by RWS Technical Support. Hotfixes should be replaced as soon as possible by the subsequent cumulative update where the problem is fixed.\r\n\r\nCopyright \u00a9 2021 All Rights Reserved by the RWS Group for and on behalf of its affiliates and subsidiaries. All company product or service names referenced herein are properties of their respective owners.",
"version": "Sites 9.0.1"
},
{
"_id": {
"$oid": "635fe2b794436e1bc8257c47"
},
"hotfix_name": "CME_9.5.0.24829",
"modified_date": {
"$date": 1628247518900
},
"problem_description": "Resizing in use images blurs the image.\r\n",
"readme_text": "Release Notes for Hotfix CRQ-24829\r\n\r\nVersion:\r\nThis hotfix is intended for SDL Web 9.5\r\n\r\nProblem description: \r\nResizing in use images blurs the image.\r\n\r\nHotfix description:\r\nCache was turned off for this object.\r\n\r\nInstallation:\r\n\t1. Backup file Tridion.Web.UI.Editors.Base.dll from %TRIDION_HOME%\\web\\WebUI\\WebRoot\\bin folder.\r\n\t2. Replace file Tridion.Web.UI.Editors.Base.dll in %TRIDION_HOME%\\web\\WebUI\\WebRoot\\bin folder with file from this hotfix.\r\n\t3. Recycle the application pool or restart your IIS service.\r\n\r\nDistributed files:\r\n- Readme.txt (this file)\r\n- Tridion.Web.UI.Editors.Base.dll (File Version 9.5.0.5812/Assembly version 9.5.0.0)\r\n\r\nDependencies:\r\nn/a\r\n\r\nIncludes:\r\nn/a\r\n\r\nDisclaimer:\r\nHotfixes (as defined under the relevant RWS product release policy) are released at RWS\u2019s discretion based on technical complexity, customer business requirements and schedules. \r\nHotfixes are made and tested only for the described problem on a particular environment/configuration in accordance with the Software Documentation and therefore should only be installed if approved by RWS Technical Support. \r\nHotfixes should be replaced as soon as possible by the subsequent cumulative update where the problem is fixed.\r\n\r\nCopyright \u00a9 2021 All Rights Reserved by the RWS Group for and on behalf of its affiliates and subsidiaries. All company product or service names referenced herein are properties of their respective owners.",
"version": "Sites 9.5"
},
{
"_id": {
"$oid": "635fe2a994436e1bc82579e0"
},
"hotfix_name": "CD_2011.1.0.78355",
"modified_date": {
"$date": 1329754854678
},
"problem_description": "The Linking windows service was not correctly cleaning up a logger memory resource on certain windows platforms\r\n",
"readme_text": "Release Notes for Hotfix TT78355\r\n================================\r\n\r\nVersion:\r\n========\r\nThis hotfix is intended only for Tridion 2011 SP1\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n- TT78355 Page link fails on second attempt of accessing the page\r\n\r\nInstallation:\r\n=============\r\n1. Stop the Tridion Linking windows service\r\n2. Execute the following command cd_link.exe --remove\r\n3. Copy the distributed cd_link.exe over the old version\r\n4. Execute the following command cd_link.exe --install\r\n3. Start the Tridion Linking windows service\r\n\r\nDistributed files:\r\n==================\r\ncd_link.exe\r\n\r\nDependencies:\r\n=============\r\nn.a.\r\n\r\nFixed problems:\r\n===============\r\nTT78355\r\nProblem Description\r\n-------------------\r\nThe Linking windows service was not correctly cleaning up a logger memory resource on certain windows platforms\r\n\r\nHotfix Description\r\n-------------------\r\nThe Linking windows service now keeps a correct reference to the used logger preventing unexpected restarts of \r\nthe linking service and makes sure that there are no unresolved links.\r\n\r\nDisclaimer:\r\n===========\r\nHotfixes are released at the discretion of Tridion based on technical\r\ncomplexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/\r\nconfiguration and therefore should only be installed if approved by Tridion\r\nCustomer Support. Hotfixes should be replaced as soon as possible by the\r\nsubsequent service pack where the problem is fixed.\r\n\r\n(c) 2011 SDL Tridion B.V.\r\n",
"version": "2011 SP1"
},
{
"_id": {
"$oid": "635fe2ab94436e1bc8257a20"
},
"hotfix_name": "CD_2011.1.1.84880",
"modified_date": {
"$date": 1375300213544
},
"problem_description": "Multiple fixed related to the throttling mechanism, deployment state not being reflected on publisher side, retrieval of notification file\r\nWhen performing mass publishing action to multiple FTP destination which have limited connection availability, publishing queue slows down drastically.\r\nWhen performing mass publishing action, publishing queue halts, multiple timeout problems are reported.\r\nIn a highly multi-threaded transport environment (in this case a target with 10 destinations) we get a lot of feedback from multiple destinations causing Transport Service to attempt\r\nto update the state file from different threads at the same time. Also, in case of the same type of publishing, Transport Service is overflowing deployer with requests due to and error\r\nin calculating the available capacity (from deployer side).\r\n2 Phase publish fails when difference between publish and deploy time is too big. If the Timeout setting (by default 15 minutes) in the cd_transport_conf.xml is set to be lower than the time \r\nfor the 2nd phase, the publish job will fail after the timeout setting.\r\nIssue in the calculation of the available window size in case of 2 phase committ. For each Scheduled publish with two phases a slot from the window size was locked but never released. After a \r\nnumber of such publish actions, the transport would just hang in throttled state.\r\nIssue for FTP publishing when the time between phase one and phase two of a scheduled publishing is too small. \r\nUnable to deploy page when two destinations are part of the same publication target.\r\nIn 2011 SP1 + HR1 when having two destinations(SSHFTP) present in the same publication target the following behavior happens:\r\n- when first publishing the page, the status for both destinations will be successful;\r\n- on second publish action, for one destination, the status will be success and for the second, the status will be 'Waiting for Deployment'\r\n- on a third publish action, for both destinations, the status of the publishing action will be 'Waiting for Deployment' for both destinations.\r\nThe customer is using sshftp as their publishing protocol.\r\nAfter there is no activity on a destination controller for more then 30 minutes, destination controller stops but its threads are not closed.\r\nThis leads to increase of overall number of threads per transport service process. Eventually OS will reach its maximum number of spawned threads.\r\n",
"readme_text": "Release Notes for Hotfix TT84880\r\n================================\r\n\r\nVersion:\r\n========\r\nThis cumulative hotfix and is intended only for Tridion 2011 SP1 HR1 and only for Emirates Airlines\r\nThe hotfix includes the following fixes:\r\n- TT84880 Multiple fixed related to the throttling mechanism, deployment state not being reflected on publisher side, retrieval of notification file\r\n- TT83364 Optimize the connection usage in case of FTP protocol and add option to be able to choose between 2009 and 2011 behavior in case of Rollback on Failure\r\n- TT83230 When performing mass publishing action, publishing queue halts\r\n- TT83136 java.util.ConcurrentModificationException when publising in transactional mode to a target with multiple destinations\r\n- TT80398 2 Phase publish fails when difference between publish and deploy time is too big.\r\n- TT81040 Unable to deploy page when two destinations (SSHFTP) are part of the same publication target.\r\n- TT81083 Errors relating to inability to create new threads.\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n- TT84880 Multiple fixed related to the throttling mechanism, deployment state not being reflected on publisher side, retrieval of notification file\r\n\r\nInstallation:\r\n=============\r\n1. Ensure a correct Content Magement installation with the Transport Service installed\r\n2. Stop the Tridion Content Delivery Transport Service\r\n3. Go to %TRIDION_HOME%\\lib\r\n4. Replace jars with the ones provided in this hotfix\r\n5. Start the Tridion Content Delivery Transport Service\r\n\r\nDistributed files:\r\n==================\r\ncd_core.jar (version 6.1.0.1086)\r\ncd_model.jar (version 6.1.0.1086)\r\ncd_transport.jar (version 6.1.0.1086)\r\nresources/configurations/cd_transport_conf_sample.xml\r\nresources/schemas/cd_transport_conf.xsd\r\n\r\nDependencies:\r\n=============\r\nSDL Tridion 2011 SP1 HR1\r\n\r\nFixed problems:\r\n===============\r\nTT84880\r\nProblem Description\r\n-------------------\r\nMultiple fixed related to the throttling mechanism, deployment state not being reflected on publisher side, retrieval of notification file\r\n\r\nHotfix Description\r\n-------------------\r\nMultiple fixes:\r\na. If any exception happen during the process of checking windows size, we make sure we handle this properly instead of setting it to Throttled. Added more logs. Fixed error message that used to return transaction id -1.\r\nb. Made sure we have the right connectionInformation that we might later update. Added trace logging for batch files which we track.\r\nc. Added a condition to Transport Summary calculation for TransportTransactionControl step, so if the Rollback package is detected for destination, we are not invoking a new step (Deploying step).\r\nd. Workers that are executed on a separate thread for no good reason: ZipWorker, TransactionControlWorker, ParallelTransportWorker, \r\ne. Made sure we always schedule the retrieval of the state notification file.\r\nf. Changed the stop / start routine of the transport pool monitor\r\n\r\n\r\nTT83364\r\nProblem Description\r\n-------------------\r\nWhen performing mass publishing action to multiple FTP destination which have limited connection availability, publishing queue slows down drastically.\r\n\r\nHotfix Description\r\n-------------------\r\nMultiple fixes:\r\na. Optimized the checking of the available capacity for each destination.\r\nb. Minimized the number of parallel open connections.\r\nc. Optimized the way we check for transactions in progress on the deployer side in case of FTP transport connector.\r\nd. Sloved theoretically possible thread blocking issues.\r\ne. Adding configuration of the LegacyMode for customer that want to use 2009 behavior in case of Rollback on Failure. You can now configure it in the cd_transport_conf.xml: ..\r\nf. Introduced additional logging to help diagnosing problems with the Transport service and with the FTP connection.\r\n\r\n\r\nTT83230\r\nProblem Description\r\n-------------------\r\nWhen performing mass publishing action, publishing queue halts, multiple timeout problems are reported.\r\n\r\nHotfix Description\r\n-------------------\r\nMultiple fixes:\r\na. Making sure that the transport pooling timeout is calculated starting with the moment when the transaction is sent on the deployer side.\r\nb. Adding configuration of the SendTimeout in case the sending of the transport package over the network is too slow. You can now configure it in the cd_transport_conf.xml: ..\r\nc. Introduces additional logging to help diagnosing problems with the Transport service.\r\n\r\n\r\nTT83136\r\nProblem Description\r\n-------------------\r\nIn a highly multi-threaded transport environment (in this case a target with 10 destinations) we get a lot of feedback from multiple destinations causing Transport Service to attempt\r\nto update the state file from different threads at the same time. Also, in case of the same type of publishing, Transport Service is overflowing deployer with requests due to and error\r\nin calculating the available capacity (from deployer side).\r\n\r\nHotfix Description\r\n-------------------\r\nMultiple fixes:\r\na. Fixes the issue that causes a ConcurrentModificationException exception by ensuring only a single thread at a time can modify the same state file;\r\nb. Fixes the calculation of available capacity for the Transport service window to a more optimal level;\r\nc. Introduces additional logging to help diagnosing problems with the Transport service.\r\n\r\n\r\n\r\nTT80398\r\nProblem Description\r\n-------------------\r\n2 Phase publish fails when difference between publish and deploy time is too big. If the Timeout setting (by default 15 minutes) in the cd_transport_conf.xml is set to be lower than the time \r\nfor the 2nd phase, the publish job will fail after the timeout setting.\r\nIssue in the calculation of the available window size in case of 2 phase committ. For each Scheduled publish with two phases a slot from the window size was locked but never released. After a \r\nnumber of such publish actions, the transport would just hang in throttled state.\r\nIssue for FTP publishing when the time between phase one and phase two of a scheduled publishing is too small. \r\n\r\n\r\nHotfix Description\r\n-------------------\r\nWhen we have a 2 phase committ this is what happens: before the first phase (sending of content package) transport locks a slot of the window size, after the first phase is done we release the\r\nslot and we stop polling for information (because the package is just parked on deployer side in WAIT state) until the second phase (sending of commit package) occurs, then before the second\r\nphase occurs we lock again a window size slot so we can perform the actual transport and after deployment finished (one way or another) we finally release the window size slot.\r\nMade sure that, in case the time between the 2 phases of a scheduled publishing is too small, we properly handle second phase. Note that this solves (different) problems for both HTTP(S) and FTP deployment.\r\n\r\nTT81040\r\nProblem Description\r\n-------------------\r\nUnable to deploy page when two destinations are part of the same publication target.\r\nIn 2011 SP1 + HR1 when having two destinations(SSHFTP) present in the same publication target the following behavior happens:\r\n- when first publishing the page, the status for both destinations will be successful;\r\n- on second publish action, for one destination, the status will be success and for the second, the status will be 'Waiting for Deployment'\r\n- on a third publish action, for both destinations, the status of the publishing action will be 'Waiting for Deployment' for both destinations.\r\n\r\nThe customer is using sshftp as their publishing protocol.\r\n\r\n\r\nHotfix Description\r\n-------------------\r\nWe made sure that after each access to the SSHFTP server we properly disconnect the client thus preventing thread blocking. Also made sure that we properly handle situations when the deployer has no status yet for a given transaction.\r\n\r\nTT81083\r\nProblem Description\r\n-------------------\r\nAfter there is no activity on a destination controller for more then 30 minutes, destination controller stops but its threads are not closed.\r\nThis leads to increase of overall number of threads per transport service process. Eventually OS will reach its maximum number of spawned threads.\r\n\r\n\r\nHotfix Description\r\n-------------------\r\nOnce destination controller is stoped after inactivity period, all children threads are stopped also.\r\n\r\n\r\nDisclaimer:\r\n===========\r\nHotfixes are released at the discretion of Tridion based on technical\r\ncomplexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/\r\nconfiguration and therefore should only be installed if approved by Tridion\r\nCustomer Support. Hotfixes should be replaced as soon as possible by the\r\nsubsequent service pack where the problem is fixed.\r\n\r\n(c) 2013 SDL Tridion B.V.\r\n",
"version": "2011 SP1 HR#1"
},
{
"_id": {
"$oid": "635fe2b494436e1bc8257c14"
},
"hotfix_name": "CM_9.1.0.25638",
"modified_date": {
"$date": 1630660745953
},
"problem_description": "Visio Workflow Client v.9.1 connects WCF services with TLS 1.0\r\n",
"readme_text": "\ufeffRelease Notes for Hotfix CRQ 25638\r\n\r\nVersion: \r\n This hotfix is intended for SDL Web 9.1\r\n\r\nProblem description:\r\n Visio Workflow Client v.9.1 connects WCF services with TLS 1.0\r\nHotfix description:\r\n Hardcoded version TLS 1.2 inside.\r\n \r\nInstallation:\r\n 1. Uninstall visio workflow designer.\r\n 2. Install new version from the package.\r\n\r\nDistributed files:\r\n\tVWD.msi \r\n\tReadme.txt (this file)\r\n\r\nFixes included:\r\n no\r\n\r\nDependencies:\r\n no\r\n\r\nDISCLAIMER:\r\n\r\nHotfixes (as defined under the relevant RWS product release policy) are released at RWS\u2019s discretion based on technical complexity, customer business requirements and schedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration in accordance with the Software Documentation and therefore should only be installed if approved by RWS Technical Support. Hotfixes should be replaced as soon as possible by the subsequent cumulative update where the problem is fixed.\r\n\r\nCopyright \u00a9 2021 All Rights Reserved by the RWS Group for and on behalf of its affiliates and subsidiaries. All company product or service names referenced herein are properties of their respective owners.",
"version": "Sites 9.1"
},
{
"_id": {
"$oid": "635fe2ab94436e1bc8257a1f"
},
"hotfix_name": "CD_2011.1.1.84879",
"modified_date": {
"$date": 1363975052522
},
"problem_description": "Multiple fixed related to the throttling mechanism, deployment state not being reflected on publisher side, retrieval of notification file\r\nWhen performing mass publishing action, publishing queue halts, multiple timeout problems are reported.\r\nIn a highly multi-threaded transport environment (in this case a target with 10 destinations) we get a lot of feedback from multiple destinations causing Transport Service to attempt\r\nto update the state file from different threads at the same time. Also, in case of the same type of publishing, Transport Service is overflowing deployer with requests due to and error\r\nin calculating the available capacity (from deployer side).\r\n2 Phase publish fails when difference between publish and deploy time is too big. If the Timeout setting (by default 15 minutes) in the cd_transport_conf.xml is set to be lower than the time \r\nfor the 2nd phase, the publish job will fail after the timeout setting.\r\nIssue in the calculation of the available window size in case of 2 phase committ. For each Scheduled publish with two phases a slot from the window size was locked but never released. After a \r\nnumber of such publish actions, the transport would just hang in throttled state.\r\nIssue for FTP publishing when the time between phase one and phase two of a scheduled publishing is too small. \r\nUnable to deploy page when two destinations are part of the same publication target.\r\nIn 2011 SP1 + HR1 when having two destinations(SSHFTP) present in the same publication target the following behavior happens:\r\n- when first publishing the page, the status for both destinations will be successful;\r\n- on second publish action, for one destination, the status will be success and for the second, the status will be 'Waiting for Deployment'\r\n- on a third publish action, for both destinations, the status of the publishing action will be 'Waiting for Deployment' for both destinations.\r\nThe customer is using sshftp as their publishing protocol.\r\nAfter there is no activity on a destination controller for more then 30 minutes, destination controller stops but its threads are not closed.\r\nThis leads to increase of overall number of threads per transport service process. Eventually OS will reach its maximum number of spawned threads.\r\n",
"readme_text": "Release Notes for Hotfix TT84879\r\n================================\r\n\r\nVersion:\r\n========\r\nThis cumulative hotfix and is intended only for Tridion 2011 SP1 HR1\r\nThe hotfix includes the following fixes:\r\n- TT84879 Multiple fixed related to the throttling mechanism, deployment state not being reflected on publisher side, retrieval of notification file\r\n- TT83230 When performing mass publishing action, publishing queue halts\r\n- TT83136 java.util.ConcurrentModificationException when publising in transactional mode to a target with multiple destinations\r\n- TT80398 2 Phase publish fails when difference between publish and deploy time is too big.\r\n- TT81040 Unable to deploy page when two destinations (SSHFTP) are part of the same publication target.\r\n- TT81083 Errors relating to inability to create new threads.\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n- TT84879 Multiple fixed related to the throttling mechanism, deployment state not being reflected on publisher side, retrieval of notification file\r\n\r\nInstallation:\r\n=============\r\n1. Ensure a correct Content Magement installation with the Transport Service installed\r\n2. Stop the Tridion Content Delivery Transport Service\r\n3. Go to %TRIDION_HOME%\\lib\r\n4. Replace jars with the ones provided in this hotfix\r\n5. Start the Tridion Content Delivery Transport Service\r\n\r\nDistributed files:\r\n==================\r\ncd_core.jar (version 6.1.0.1085)\r\ncd_model.jar (version 6.1.0.1085)\r\ncd_transport.jar (version 6.1.0.1085)\r\nresources/configurations/cd_transport_conf_sample.xml\r\nresources/schemas/cd_transport_conf.xsd\r\n\r\nDependencies:\r\n=============\r\nSDL Tridion 2011 SP1 HR1\r\n\r\nFixed problems:\r\n===============\r\nTT84879\r\nProblem Description\r\n-------------------\r\nMultiple fixed related to the throttling mechanism, deployment state not being reflected on publisher side, retrieval of notification file\r\n\r\nHotfix Description\r\n-------------------\r\nMultiple fixes:\r\na. Optimized the checking of the available capacity for each destination.\r\nb. Minimized the number of parallel open connections.\r\nc. Optimized the way we check for transactions in progress on the deployer side in case of FTP transport connector.\r\nd. Sloved theoretically possible thread blocking issues.\r\ne. Introduced additional logging to help diagnosing problems with the Transport service and with the FTP connection.\r\nf. If any exception happen during the process of checking windows size, we make sure we handle this properly instead of setting it to Throttled. Added more logs. Fixed error message that used to return transaction id -1.\r\ng. Made sure we have the right connectionInformation that we might later update. Added trace logging for batch files which we track.\r\nh. Added a condition to Transport Summary calculation for TransportTransactionControl step, so if the Rollback package is detected for destination, we are not invoking a new step (Deploying step).\r\ni. Workers that are executed on a separate thread for no good reason: ZipWorker, TransactionControlWorker, ParallelTransportWorker, \r\nj. Made sure we always schedule the retrieval of the state notification file.\r\nk. Changed the stop / start routine of the transport pool monitor\r\n\r\n\r\nTT83230\r\nProblem Description\r\n-------------------\r\nWhen performing mass publishing action, publishing queue halts, multiple timeout problems are reported.\r\n\r\nHotfix Description\r\n-------------------\r\nMultiple fixes:\r\na. Making sure that the transport pooling timeout is calculated starting with the moment when the transaction is sent on the deployer side.\r\nb. Adding configuration of the SendTimeout in case the sending of the transport package over the network is too slow. You can now configure it in the cd_transport_conf.xml: ..\r\nc. Introduces additional logging to help diagnosing problems with the Transport service.\r\n\r\n\r\nTT83136\r\nProblem Description\r\n-------------------\r\nIn a highly multi-threaded transport environment (in this case a target with 10 destinations) we get a lot of feedback from multiple destinations causing Transport Service to attempt\r\nto update the state file from different threads at the same time. Also, in case of the same type of publishing, Transport Service is overflowing deployer with requests due to and error\r\nin calculating the available capacity (from deployer side).\r\n\r\nHotfix Description\r\n-------------------\r\nMultiple fixes:\r\na. Fixes the issue that causes a ConcurrentModificationException exception by ensuring only a single thread at a time can modify the same state file;\r\nb. Fixes the calculation of available capacity for the Transport service window to a more optimal level;\r\nc. Introduces additional logging to help diagnosing problems with the Transport service.\r\n\r\n\r\n\r\nTT80398\r\nProblem Description\r\n-------------------\r\n2 Phase publish fails when difference between publish and deploy time is too big. If the Timeout setting (by default 15 minutes) in the cd_transport_conf.xml is set to be lower than the time \r\nfor the 2nd phase, the publish job will fail after the timeout setting.\r\nIssue in the calculation of the available window size in case of 2 phase committ. For each Scheduled publish with two phases a slot from the window size was locked but never released. After a \r\nnumber of such publish actions, the transport would just hang in throttled state.\r\nIssue for FTP publishing when the time between phase one and phase two of a scheduled publishing is too small. \r\n\r\n\r\nHotfix Description\r\n-------------------\r\nWhen we have a 2 phase committ this is what happens: before the first phase (sending of content package) transport locks a slot of the window size, after the first phase is done we release the\r\nslot and we stop polling for information (because the package is just parked on deployer side in WAIT state) until the second phase (sending of commit package) occurs, then before the second\r\nphase occurs we lock again a window size slot so we can perform the actual transport and after deployment finished (one way or another) we finally release the window size slot.\r\nMade sure that, in case the time between the 2 phases of a scheduled publishing is too small, we properly handle second phase. Note that this solves (different) problems for both HTTP(S) and FTP deployment.\r\n\r\nTT81040\r\nProblem Description\r\n-------------------\r\nUnable to deploy page when two destinations are part of the same publication target.\r\nIn 2011 SP1 + HR1 when having two destinations(SSHFTP) present in the same publication target the following behavior happens:\r\n- when first publishing the page, the status for both destinations will be successful;\r\n- on second publish action, for one destination, the status will be success and for the second, the status will be 'Waiting for Deployment'\r\n- on a third publish action, for both destinations, the status of the publishing action will be 'Waiting for Deployment' for both destinations.\r\n\r\nThe customer is using sshftp as their publishing protocol.\r\n\r\n\r\nHotfix Description\r\n-------------------\r\nWe made sure that after each access to the SSHFTP server we properly disconnect the client thus preventing thread blocking. Also made sure that we properly handle situations when the deployer has no status yet for a given transaction.\r\n\r\nTT81083\r\nProblem Description\r\n-------------------\r\nAfter there is no activity on a destination controller for more then 30 minutes, destination controller stops but its threads are not closed.\r\nThis leads to increase of overall number of threads per transport service process. Eventually OS will reach its maximum number of spawned threads.\r\n\r\n\r\nHotfix Description\r\n-------------------\r\nOnce destination controller is stoped after inactivity period, all children threads are stopped also.\r\n\r\n\r\nDisclaimer:\r\n===========\r\nHotfixes are released at the discretion of Tridion based on technical\r\ncomplexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/\r\nconfiguration and therefore should only be installed if approved by Tridion\r\nCustomer Support. Hotfixes should be replaced as soon as possible by the\r\nsubsequent service pack where the problem is fixed.\r\n\r\n(c) 2012 SDL Tridion B.V.\r\n",
"version": "2011 SP1 HR#1"
},
{
"_id": {
"$oid": "635fe2ab94436e1bc8257a21"
},
"hotfix_name": "CD_2011.1.1.85023",
"modified_date": {
"$date": 1365094887659
},
"problem_description": "Error in Precommit phase if we deploy CustomMeta to FileSystem and one of the values is empty\r\nSome of the HashMaps in the storage layer are not thread-safe.\r\nWhen storing BinaryMeta there are some queries which lock the some tables for a longer time that needed.\r\nWhen updating a BinaryMeta, if there is already a ComponentMeta published and related to it, the ComponentMeta will not have its LastPublishedDate updated.\r\nDuring the mass deployment of big packages containing same binaries, the default number of deployment retries (10) might not be enough.\r\nDuring the deployment process, the deployer serializes the state to be able to pick-up from where it's left in case of failure. Because the loggers associated to each worker\r\nwere also serialized, we would get a ConcurrentModificationException under heavy load because different loggers (associated to workers in different transactions) were cached by\r\nLogBack while the current transaction state was serialized to disk.\r\nUnder heavy load, the deployer would pick-up twice the same transport package causing an error on the second attempt.\r\n'org.hibernate.TransientObjectException' would occur in case of changing related keywords of an item meta in the same transaction.\r\nThere was an issue when publishing BinaryMeta while there's an existing ComponentMeta with the same itemId in the published storage.\r\nWhen deploying unmanaged binaries, content is mixed-up between binaries in case order in binaries.xml and instructions.xml is different.\r\nThere are some limitations for the CustomMetaValue for Oracle schemas and filesystem due to some checks in the Deployer. \r\nPublishing process stuck in Resolving state\r\n",
"readme_text": "Release Notes for Hotfix TT85023\r\n================================\r\n\r\nVersion:\r\n========\r\nThis cumulative hotfix and is intended only for Tridion 2011 SP1 HR1\r\nThe hotfix includes the following fixes:\r\n- TT85023 Error in Precommit phase if we deploy CustomMeta to FileSystem and one of the values is empty\r\n- TT84845 Hanging threads in broker\r\n- TT84807 A mass publish leads to java.sql.BatchUpdateException: ORA-00060: deadlock detected while waiting for resource\r\n- TT84804 LAST_PUBLISHED_DATE not being updated when binary (image) is published\r\n- TT84736 Configuration option for the number of retries of the deployer\r\n- TT84446 Mass publishing of items to a single deployer leads to java.util.ConcurrentModificationException: null\r\n- TT83475 Deployment fails for some items with error message: Unable to unzip, ***.zip (The system cannot find the file specified), \r\n- TT83467 'Unable to remove data entity, org.hibernate.TransientObjectException' occurs randomly when deploying content to the database\r\n- TT82946 Publish to the deployer fail with the exception \"org.hibernate.exception.ConstraintViolationException: could not insert\"\r\n- TT81270 When deploying unmanaged binaries, content is mixed-up between binaries in case order in binaries.xml and instructions.xml is different,\r\n- TT81125 Deployment fails when publishing a page that contains metadata that exceeds 3400 bytes, \r\n- TT80995 Publishing process stuck in Resolving state\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n- TT85023 Error in Precommit phase if we deploy CustomMeta to FileSystem and one of the values is empty\r\n\r\nInstallation:\r\n=============\r\nDeployer environment:\r\n---------------------\r\nJava Environment with HttpUpload:\r\n1. Ensure that you have a correct installed Content Delivery installation inside your web application\r\n2. Stop your web application server or web application containing the deployer httpupload\r\n3. Copy the distributed jar files inside your web application WEB-INF\\lib directory\r\n4. Start your web application server or web application\r\n\r\n.NET Environment with HttpUpload:\r\n1. Ensure the application pool and or IIS Server has been stopped\r\n2. Copy the distributed jar files inside the IIS application directory bin\\lib directory. In case of central tridion installation please copy the distributed jar files\r\ninto the installation directory \\lib folder.\r\n3. Start the application pool and or IIS Server\r\n\r\nStandalone deployer:\r\n1. Ensure the deployer service has been stopped\r\n2. Copy the distributed jar files inside your 'Tridion installation folder'\\lib directory\r\n3. Start the deployer service\r\n\r\nDistributed files:\r\n==================\r\ncd_datalayer.jar (6.1.0.1088)\r\ncd_deployer.jar (6.1.0.1088)\r\ncd_model.jar (6.1.0.1088)\r\ncd_core.jar (6.1.0.1088)\r\n\r\nDependencies:\r\n=============\r\nSDL Tridion 2011 SP1 HR1\r\n\r\n\r\nFixed problems:\r\n===============\r\nTT85023\r\nProblem Description\r\n-------------------\r\nError in Precommit phase if we deploy CustomMeta to FileSystem and one of the values is empty\r\n\r\nHotfix Description\r\n-------------------\r\nHandling case in which the CustomMeta existing on disk has no value.\r\n\r\n\r\nTT84845\r\nProblem Description\r\n-------------------\r\nSome of the HashMaps in the storage layer are not thread-safe.\r\n\r\nHotfix Description\r\n-------------------\r\nMade these HashMaps thread-safe.\r\n\r\n\r\nTT84807\r\nProblem Description\r\n-------------------\r\nWhen storing BinaryMeta there are some queries which lock the some tables for a longer time that needed.\r\n\r\nHotfix Description\r\n-------------------\r\nMaking some of the queries done when storing BinaryMeta more efficient, to release database locks faster.\r\n\r\n\r\nTT84804\r\nProblem Description\r\n-------------------\r\nWhen updating a BinaryMeta, if there is already a ComponentMeta published and related to it, the ComponentMeta will not have its LastPublishedDate updated.\r\n\r\nHotfix Description\r\n-------------------\r\nUpdating LastPublishedDate for existing related ComponentMeta when updating BinaryMeta. Forcing consistency check related to items.\r\n\r\n\r\nTT84736\r\nProblem Description\r\n-------------------\r\nDuring the mass deployment of big packages containing same binaries, the default number of deployment retries (10) might not be enough.\r\n\r\nHotfix Description\r\n-------------------\r\nAllowing customer to define the number of retries for each Queue/Location in a MaximumRetries attribute. Example:\r\n\r\n\r\n\r\nTT84446\r\nProblem Description\r\n-------------------\r\nDuring the deployment process, the deployer serializes the state to be able to pick-up from where it's left in case of failure. Because the loggers associated to each worker\r\nwere also serialized, we would get a ConcurrentModificationException under heavy load because different loggers (associated to workers in different transactions) were cached by\r\nLogBack while the current transaction state was serialized to disk.\r\n\r\nHotfix Description\r\n-------------------\r\nMade sure that the loggers are excluded from the serializing process and optimized the declaration of all loggers involved in the transaction state.\r\n\r\n\r\nTT83475\r\nProblem Description\r\n-------------------\r\nUnder heavy load, the deployer would pick-up twice the same transport package causing an error on the second attempt.\r\n\r\nHotfix Description\r\n-------------------\r\nMade sure the same package is not picked-up twice. \r\n\r\n\r\nTT83467\r\nProblem Description\r\n-------------------\r\n'org.hibernate.TransientObjectException' would occur in case of changing related keywords of an item meta in the same transaction.\r\n\r\nHotfix Description\r\n-------------------\r\nMaking sure that the link from RelatedKeyword back to ItemMeta is nullified before saving the item meta.\r\n\r\n\r\nTT82946\r\nProblem Description\r\n-------------------\r\nThere was an issue when publishing BinaryMeta while there's an existing ComponentMeta with the same itemId in the published storage.\r\n\r\nHotfix Description\r\n-------------------\r\nRemoving the existing ComponentMeta before re-adding it with the BinaryMeta.\r\n\r\n\r\nTT81270\r\nProblem Description\r\n-------------------\r\nWhen deploying unmanaged binaries, content is mixed-up between binaries in case order in binaries.xml and instructions.xml is different.\r\n\r\nHotfix Description\r\n-------------------\r\nLook up for unmanaged binaries by the path as all of them have the same id. \r\n\r\n\r\n\r\nTT81125\r\nProblem Description\r\n-------------------\r\nThere are some limitations for the CustomMetaValue for Oracle schemas and filesystem due to some checks in the Deployer. \r\n\r\nHotfix Description\r\n-------------------\r\nThe early checks in the Deployer are removed.\r\n\r\n\r\nTT80995 \r\nProblem Description\r\n-------------------\r\nPublishing process stuck in Resolving state\r\n\r\nHotfix Description\r\n-------------------\r\nRemoving DynamicLinks might cause database locks. To prevent that we flush the session prior and after removing DynamicLinks.\r\n\r\n\r\n\r\nDisclaimer:\r\n===========\r\nHotfixes are released at the discretion of Tridion based on technical\r\ncomplexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/\r\nconfiguration and therefore should only be installed if approved by Tridion\r\nCustomer Support. Hotfixes should be replaced as soon as possible by the\r\nsubsequent service pack where the problem is fixed.\r\n\r\n(c) 2013 SDL Tridion B.V.\r\n",
"version": "2011 SP1 HR#1"
},
{
"_id": {
"$oid": "635fe2aa94436e1bc8257a19"
},
"hotfix_name": "CD_2011.1.1.84669",
"modified_date": {
"$date": 1362764427418
},
"problem_description": "When the path of the incoming request is unknown to the Broker then Experience Manager will not work.\r\nUI 2012 blocks calls to (non-Tridion) WebServices hosted on the Staging site\r\nWhen you have a .NET website with an application then preview would try to redirect to a path that does not take into accound also the relative path of the application.\r\n",
"readme_text": "Release Notes for Hotfix TT84669\r\n================================\r\n\r\nVersion:\r\n========\r\nThis is a cumulative hotfix and is intended only for The New Tridion UI (based on Tridion 2011 SP1 HR1)\r\nThe hotfix includes the following fixes:\r\n- TT84669 XPM does not work with paths that are unknown to the Broker\r\n- TT82378 UI 2012 blocks calls to (non-Tridion) WebServices hosted on the Staging site\r\n- TT81686 Update Preview does not handle properly application root within a .NET WebSite\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n- T84669 XPM does not work with paths that are unknown to the Broker\r\n\r\nInstallation:\r\n=============\r\nDeployer environment:\r\n---------------------\r\nJava Environment with Session Preview Staging site:\r\n1. Ensure that you have a correct installed Session Preview Staging Site installation inside your web application\r\n2. Stop your web application server or web application containing the Session Preview Staging Site\r\n3. Copy the distributed jar files inside your web application WEB-INF\\lib directory\r\n4. Start your web application server or web application\r\n\r\n.NET Environment with Session Preview Staging site:\r\n1. Ensure the application pool and or IIS Server has been stopped\r\n2. Copy the distributed jar files inside the IIS application directory bin\\lib directory. In case of central tridion installation please copy the distributed jar files\r\ninto the installation directory \\lib folder.\r\n2. Copy the distributed Tridion.ContentDelivery.Preview.dll over the existing dll inside the Bin folder of your website/application;\r\n3. Start the application pool and or IIS Server\r\n\r\n\r\nDistributed files:\r\n==================\r\njava\\cd_preview_web.jar (6.1.0.360)\r\ndotNet\\x86\\Tridion.ContentDelivery.Preview.dll (version 6.1.0.360)\r\ndotNet\\x86_64\\Tridion.ContentDelivery.Preview.dll (version 6.1.0.360)\r\n\r\nDependencies:\r\n=============\r\nTridion 2011 SP1 HR1\r\n\r\nFixed problems:\r\n===============\r\nTT84669\r\nProblem Description\r\n-------------------\r\nWhen the path of the incoming request is unknown to the Broker then Experience Manager will not work.\r\n\r\nHotfix Description\r\n-------------------\r\nWe offer the client the possibility to desing their own claim processor that can dictate how the Preview Filters/Modules behave.\r\nThe claim processors can set the following claims:\r\n- taf:session:preview:request:full_url;\r\n- taf:session:preview:request:real_path;\r\n- taf:session:preview:request:root_path;\r\n- taf:session:preview:request:forwarding;\r\n- taf:session:preview:request:component_presentations;\r\n- taf:session:preview:request:component_presentation_root_path.\r\nThe Preview Filters/Modules can output the following claims:\r\n- taf:session:preview:request:session_file_relative_path;\r\n- taf:session:preview:request:session_page_full_path;\r\n- taf:session:preview:request:session_binary_full_path;\r\n- taf:session:preview:request:session_component_presentation_full_paths.\r\nMore details about how these can be used you will find in the file 'SDL Tridion Experience Manager integration.pdf'.\r\n\r\n\r\nTT82378\r\nProblem Description\r\n-------------------\r\nUI 2012 blocks calls to (non-Tridion) WebServices hosted on the Staging site\r\n\r\nHotfix Description\r\n-------------------\r\nBefore processing any request to the Preview Staging Site we now check if the path of the request is maybe on the list of excluded paths of Ambient Data Framework.\r\nIn order to define a path as being excluded by the processing done by PreviewContentModule/PageFilter/BinaryContentFilter the cd_ambient_conf.xml needs to have the excludedPaths defined:\r\n\r\n\t/Home/Get\r\n\t/Home/About\r\n\r\nIn the example above we defined that all calls made to a path that starts with '/Home/Get' or with '/Home/About' will be ignored by the session logic.\r\n\r\n\r\nTT81686\r\nProblem Description\r\n-------------------\r\nWhen you have a .NET website with an application then preview would try to redirect to a path that does not take into accound also the relative path of the application.\r\n\r\n\r\nHotfix Description\r\n-------------------\r\nWe now make sure we also take into account the application path when building the new path to reroute to.\r\n\r\nDisclaimer:\r\n===========\r\nHotfixes are released at the discretion of Tridion based on technical\r\ncomplexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/\r\nconfiguration and therefore should only be installed if approved by Tridion\r\nCustomer Support. Hotfixes should be replaced as soon as possible by the\r\nsubsequent service pack where the problem is fixed.\r\n\r\n(c) 2012 SDL Tridion B.V.\r\n",
"version": "2011 SP1 HR#1"
},
{
"_id": {
"$oid": "635fe2b894436e1bc8257c5f"
},
"hotfix_name": "ECL_9.5.0.27548",
"modified_date": {
"$date": 1642696712227
},
"problem_description": "After 9.1 ECL creates new stub even if old stub already exists if ECL URI contains underscore '_'.\r\n",
"readme_text": "Release Notes for Hotfix 27548\r\n\r\nVersion:\r\n\tThis hotfix is intended only for Tridion External Content Library 9.5 included in SDL Tridion Sites 9.5.\r\n\r\nProblem description:\r\n\tAfter 9.1 ECL creates new stub even if old stub already exists if ECL URI contains underscore '_'.\r\n\r\nHotfix description:\r\n\tChange stub search logic to prefer old stub over new stub.\r\n\r\nInstallation:\r\n\t1. Stop all Tridion Content Manager Service Host and IIS Service.\r\n\t2. Move the file Tridion.ExternalContentLibrary.DomainModel.dll located in the %WINDIR%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.ExternalContentLibrary.DomainModel\\v4.0_9.5.0.0__ddfc895746e5ee6b folder\r\n\t3. Copy the file Tridion.ExternalContentLibrary.DomainModel.dll file from this hotfix to the %WINDIR%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.ExternalContentLibrary.DomainModel\\v4.0_9.5.0.0__ddfc895746e5ee6b folder\r\n\t4. Move the file Tridion.ExternalContentLibrary.Data.dll located in the %WINDIR%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.ExternalContentLibrary.Data\\v4.0_9.5.0.0__ddfc895746e5ee6b folder\r\n\t5. Copy the file Tridion.ExternalContentLibrary.Data.dll file from this hotfix to the %WINDIR%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.ExternalContentLibrary.Data\\v4.0_9.5.0.0__ddfc895746e5ee6b folder\r\n\t6. Copy the file Tridion.ExternalContentLibrary.TcmExtension.dll from this hotfix to \"%TRIDION_CM_HOME%\\bin \" replacing the old version.\r\n\t7. Restart the IIS Service and Tridion Content Manager Service Host.\r\n\r\nDistributed files:\r\n\tTridion.ExternalContentLibrary.DomainModel.dll (File Version 9.5.0.442)\r\n\tTridion.ExternalContentLibrary.Data.dll (File Version 9.5.0.442)\r\n\tTridion.ExternalContentLibrary.TcmExtension.dll (File Version 9.5.0.442)\r\n\tReadme.txt (this file)\r\n\r\nDuplicated stubs detection script:\r\n\tFindDuplicateStubs.ps1 script located in DuplicateStubs folder can be used for detecting duplicated stubs created by this issue.\r\n\t\r\n\tThis script reports so-called duplicate ECL Stub Components.\r\n\tOutputs a table in CSV format which can be directed to a file (see example) and opened in a Spreadsheet.\r\n\r\n\tSince Tridion Sites 9.1, ECL URIs are encoded differently. In particular, underscores were not encoded before, but the are encoded since 9.1.\r\n\tAs an unfortunate side-effect, the same ECL Item can have a different Stub Component location since 9.1.\r\n\tAfter upgrading a Tridion Sites to 9.1 or later, this can result in new ECL Stubs being created even though an ECL Stub already existed for the item.\r\n\tThis results in what we call \"duplicate ECL Stub Components\".\r\n\tIn the best case, this just causes an unnecessary number of ECL Stub Components.\r\n\tIn the worst case, you seem to loose the internal metadata of the ECL Stub Component (it is not really lost, but it is no longer there on the new Stub)\r\n\tand then internal metadata is re-applied on the new Stub.\r\n\tIn this case, the new Stub contains the latest version of the metadata, but after the hotfix is applied, the old Stub will be used again.\r\n\tSo, it may be necessary to copy the metadata from the new Stub to the old Stub.\r\n\r\n\tUsage example:\r\n\t\t.\\FindDuplicateStubs.ps1 -cmsUrl https://mycms.com -publicationId tcm:0-1-1 > duplicates.csv\r\n\t\r\n\tSee detailed information by using command:\r\n\t\tGet-Help .\\FindDuplicateStubs.ps1 -full\r\n\r\nFixes included:\r\n\tCRQ-21944: ECL list performance degradation when list contains more then 1000 items.\r\n\r\nDependencies:\r\n\tN/A\r\n\r\nDisclaimer:\r\n\tHotfixes are released at the discretion of RWS based on technical complexity, customer business requirements and schedules.\r\n\tHotfixes are made and tested only for the described problem on a particular environment\\configuration and therefore should only be installed if approved by Customer Support of SDL Web Content Management Solutions Division.\r\n\tHotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright \u00a9 2015-2021 All Rights Reserved by the RWS Group for and on behalf of its affiliates and subsidiaries.\r\n",
"version": "Sites 9.5"
},
{
"_id": {
"$oid": "635fe2ac94436e1bc8257aae"
},
"hotfix_name": "CD_2013.0.0.86156",
"modified_date": {
"$date": 1378285507422
},
"problem_description": "Undo transport package contains only one binary with VariantId\r\nSome of the HashMaps in the storage layer are not thread-safe.\r\nError in Precommit phase if we deploy CustomMeta to FileSystem and one of the values is empty\r\nWrong title of embedded binary in the ITEMS table after undo\r\nWhen we store page content on a filesystem we always capture it with UTF-8 chartset during undo capturing\r\nWhen attempting to deploy content, it fails with error: Unable to persist data entity, org.hibernate.exception.ConstraintViolationException\r\n",
"readme_text": "Release Notes for Hotfix TT86156\r\n================================\r\n\r\nVersion:\r\n========\r\nThis hotfix is intended only for Tridion 2013 GA.\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n- TT84562 Undo transport package contains only one binary with VariantId\r\n- TT84847 Hanging threads in broker\r\n- TT85023 Error in Precommit phase if we deploy CustomMeta to FileSystem and one of the values is empty\r\n- TT85248 Wrong title of embedded binary in the ITEMS table after undo\r\n- TT85262 When we store page content on a filesystem we always capture it with UTF-8 chartset during undo capturing\r\n- TT86037 When attempting to deploy content, it fails with error: Unable to persist data entity, org.hibernate.exception.ConstraintViolationException\r\n\r\nInstallation:\r\n=============\r\nDeployer environment:\r\n---------------------\r\nJava Environment with HttpUpload:\r\n1. Ensure that you have a correct installed Content Delivery installation inside your web application\r\n2. Stop your web application server or web application containing the deployer httpupload\r\n3. Copy the distributed jar files inside your web application WEB-INF\\lib directory\r\n4. Start your web application server or web application\r\n\r\n.NET Environment with HttpUpload:\r\n1. Ensure the application pool and or IIS Server has been stopped\r\n2. Copy the distributed jar files inside the IIS application directory bin\\lib directory. In case of central tridion installation please copy the distributed jar files\r\ninto the installation directory \\lib folder.\r\n3. Start the application pool and or IIS Server\r\n\r\nStandalone deployer:\r\n1. Ensure the deployer service has been stopped\r\n2. Copy the distributed jar files inside your 'Tridion installation folder'\\lib directory\r\n3. Start the deployer service\r\n\r\nDistributed files:\r\n==================\r\ncd_datalayer.jar (7.0.1.17)\r\ncd_model.jar (7.0.1.17)\r\ncd_undo.jar (7.0.1.17)\r\n\r\nDependencies:\r\n=============\r\nSDL Tridion 2013 GA\r\n\r\n\r\nFixed problems:\r\n===============\r\nTT84562\r\nProblem Description\r\n-------------------\r\nUndo transport package contains only one binary with VariantId\r\n\r\nHotfix Description\r\n-------------------\r\nVariantId was not taken into account when creating the transport package, so that if there were multiple variants of the same binary, only one of them would end up in the transport package. This has been fixed, so that VariantId is now taken into account.\r\n\r\nTT84847\r\nProblem Description\r\n-------------------\r\nSome of the HashMaps in the storage layer are not thread-safe.\r\n\r\nHotfix Description\r\n-------------------\r\nMade these HashMaps thread-safe.\r\n\r\nTT85023\r\nProblem Description\r\n-------------------\r\nError in Precommit phase if we deploy CustomMeta to FileSystem and one of the values is empty\r\n\r\nHotfix Description\r\n-------------------\r\nHandling case in which the CustomMeta existing on disk has no value.\r\n\r\nTT85248\r\nProblem Description\r\n-------------------\r\nWrong title of embedded binary in the ITEMS table after undo\r\n\r\nHotfix Description\r\n-------------------\r\nClass ComponentBuilder has to take LinkInfo objects into account when building a transport package.\r\n\r\nTT85262\r\nProblem Description\r\n-------------------\r\nWhen we store page content on a filesystem we always capture it with UTF-8 chartset during undo capturing\r\n\r\nHotfix Description\r\n-------------------\r\nWhen page content is stored on the filesystem, the original character set of the content is not saved. When retrieving the content, UTF-8 is assumed. This has been changed so that the default character set of the operating system (that CD is running on) is assumed. Users who use Undo and store page content on the filesystem should be aware that when they execute Undo for a page, the system will assume that the content stored on the filesystem is in the default character set.\r\n\r\nTT86037\r\nProblem Description\r\n-------------------\r\nWhen attempting to deploy content, it fails with error: Unable to persist data entity, org.hibernate.exception.ConstraintViolationException\r\n\r\nHotfix Description\r\n-------------------\r\nMade sure we insert item if it doesnt exist otherwise update by decoupling binary meta and component meta. This is a solution if multimedia component meta exist without binary meta.\r\n\r\n\r\nDisclaimer:\r\n===========\r\nHotfixes are released at the discretion of Tridion based on technical\r\ncomplexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/\r\nconfiguration and therefore should only be installed if approved by Tridion\r\nCustomer Support. Hotfixes should be replaced as soon as possible by the\r\nsubsequent service pack where the problem is fixed.\r\n\r\n(c) 2013 SDL Tridion B.V.\r\n",
"version": "2013"
},
{
"_id": {
"$oid": "635fe2aa94436e1bc8257a09"
},
"hotfix_name": "CD_2011.1.1.81083",
"modified_date": {
"$date": 1340612537871
},
"problem_description": "2 Phase publish fails when difference between publish and deploy time is too big. If the Timeout setting (by default 15 minutes) in the cd_transport_conf.xml is set to be lower than the time \r\nfor the 2nd phase, the publish job will fail after the timeout setting.\r\nIssue in the calculation of the available window size in case of 2 phase committ. For each Scheduled publish with two phases a slot from the window size was locked but never released. After a \r\nnumber of such publish actions, the transport would just hang in throttled state.\r\nIssue for FTP publishing when the time between phase one and phase two of a scheduled publishing is too small. \r\nUnable to deploy page when two destinations are part of the same publication target.\r\nIn 2011 SP1 + HR1 when having two destinations(SSHFTP) present in the same publication target the following behavior happens:\r\n- when first publishing the page, the status for both destinations will be successful;\r\n- on second publish action, for one destination, the status will be success and for the second, the status will be 'Waiting for Deployment'\r\n- on a third publish action, for both destinations, the status of the publishing action will be 'Waiting for Deployment' for both destinations.\r\nThe customer is using sshftp as their publishing protocol.\r\nAfter there is no activity on a destination controller for more then 30 minutes, destination controller stops but its threads are not closed.\r\nThis leads to increase of overall number of threads per transport service process. Eventually OS will reach its maximum number of spawned threads.\r\n",
"readme_text": "Release Notes for Hotfix TT81083\r\n================================\r\n\r\nVersion:\r\n========\r\nThis cumulative hotfix and is intended only for Tridion 2011 SP1 HR1\r\nThe hotfix includes the following fixes:\r\n- TT80398 2 Phase publish fails when difference between publish and deploy time is too big.\r\n- TT81040 Unable to deploy page when two destinations (SSHFTP) are part of the same publication target.\r\n- TT81083 Errors relating to inability to create new threads.\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n- TT81083 Errors relating to inability to create new threads.\r\n\r\nInstallation:\r\n=============\r\n1. Ensure a correct Content Magement installation with the Transport Service installed\r\n2. Stop the Tridion Content Delivery Transport Service\r\n3. Go to %TRIDION_HOME%\\lib\r\n4. Replace cd_transport.jar with the provided hotfix versions\r\n5. Start the Tridion Content Delivery Transport Service\r\n\r\nDistributed files:\r\n==================\r\ncd_transport.jar (version 6.1.0.1052)\r\n\r\nDependencies:\r\n=============\r\nSDL Tridion 2011 SP1 HR1\r\n\r\nFixed problems:\r\n===============\r\nTT80398\r\nProblem Description\r\n-------------------\r\n2 Phase publish fails when difference between publish and deploy time is too big. If the Timeout setting (by default 15 minutes) in the cd_transport_conf.xml is set to be lower than the time \r\nfor the 2nd phase, the publish job will fail after the timeout setting.\r\nIssue in the calculation of the available window size in case of 2 phase committ. For each Scheduled publish with two phases a slot from the window size was locked but never released. After a \r\nnumber of such publish actions, the transport would just hang in throttled state.\r\nIssue for FTP publishing when the time between phase one and phase two of a scheduled publishing is too small. \r\n\r\n\r\nHotfix Description\r\n-------------------\r\nWhen we have a 2 phase committ this is what happens: before the first phase (sending of content package) transport locks a slot of the window size, after the first phase is done we release the\r\nslot and we stop polling for information (because the package is just parked on deployer side in WAIT state) until the second phase (sending of commit package) occurs, then before the second\r\nphase occurs we lock again a window size slot so we can perform the actual transport and after deployment finished (one way or another) we finally release the window size slot.\r\nMade sure that, in case the time between the 2 phases of a scheduled publishing is too small, we properly handle second phase. Note that this solves (different) problems for both HTTP(S) and FTP deployment.\r\n\r\nTT81040\r\nProblem Description\r\n-------------------\r\nUnable to deploy page when two destinations are part of the same publication target.\r\nIn 2011 SP1 + HR1 when having two destinations(SSHFTP) present in the same publication target the following behavior happens:\r\n- when first publishing the page, the status for both destinations will be successful;\r\n- on second publish action, for one destination, the status will be success and for the second, the status will be 'Waiting for Deployment'\r\n- on a third publish action, for both destinations, the status of the publishing action will be 'Waiting for Deployment' for both destinations.\r\n\r\nThe customer is using sshftp as their publishing protocol.\r\n\r\n\r\nHotfix Description\r\n-------------------\r\nWe made sure that after each access to the SSHFTP server we properly disconnect the client thus preventing thread blocking. Also made sure that we properly handle situations when the deployer has no status yet for a given transaction.\r\n\r\nTT81083\r\nProblem Description\r\n-------------------\r\nAfter there is no activity on a destination controller for more then 30 minutes, destination controller stops but its threads are not closed.\r\nThis leads to increase of overall number of threads per transport service process. Eventually OS will reach its maximum number of spawned threads.\r\n\r\n\r\nHotfix Description\r\n-------------------\r\nOnce destination controller is stoped after inactivity period, all children threads are stopped also.\r\n\r\n\r\nDisclaimer:\r\n===========\r\nHotfixes are released at the discretion of Tridion based on technical\r\ncomplexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/\r\nconfiguration and therefore should only be installed if approved by Tridion\r\nCustomer Support. Hotfixes should be replaced as soon as possible by the\r\nsubsequent service pack where the problem is fixed.\r\n\r\n(c) 2012 SDL Tridion B.V.\r\n",
"version": "2011 SP1 HR#1"
},
{
"_id": {
"$oid": "635fe2aa94436e1bc8257a16"
},
"hotfix_name": "CD_2011.1.1.83475",
"modified_date": {
"$date": 1356050079866
},
"problem_description": "Under heavy load, the deployer would pick-up twice the same transport package causing an error on the second attempt.\r\nWhen deploying unmanaged binaries, content is mixed-up between binaries in case order in binaries.xml and instructions.xml is different.\r\nThere are some limitations for the CustomMetaValue for Oracle schemas and filesystem due to some checks in the Deployer. \r\nPublishing process stuck in Resolving state\r\n",
"readme_text": "Release Notes for Hotfix TT83475\r\n================================\r\n\r\nVersion:\r\n========\r\nThis cumulative hotfix and is intended only for Tridion 2011 SP1 HR1\r\nThe hotfix includes the following fixes:\r\n- TT83475 Deployment fails for some items with error message: Unable to unzip, ***.zip (The system cannot find the file specified), \r\n- TT81270 When deploying unmanaged binaries, content is mixed-up between binaries in case order in binaries.xml and instructions.xml is different,\r\n- TT81125 Deployment fails when publishing a page that contains metadata that exceeds 3400 bytes, \r\n- TT80995 Publishing process stuck in Resolving state\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n- TT83475 Deployment fails for some items with error message: Unable to unzip, ***.zip (The system cannot find the file specified), \r\n\r\nInstallation:\r\n=============\r\nDeployer environment:\r\n---------------------\r\nJava Environment with HttpUpload:\r\n1. Ensure that you have a correct installed Content Delivery installation inside your web application\r\n2. Stop your web application server or web application containing the deployer httpupload\r\n3. Copy the distributed jar files inside your web application WEB-INF\\lib directory\r\n4. Start your web application server or web application\r\n\r\n.NET Environment with HttpUpload:\r\n1. Ensure the application pool and or IIS Server has been stopped\r\n2. Copy the distributed jar files inside the IIS application directory bin\\lib directory. In case of central tridion installation please copy the distributed jar files\r\ninto the installation directory \\lib folder.\r\n3. Start the application pool and or IIS Server\r\n\r\nStandalone deployer:\r\n1. Ensure the deployer service has been stopped\r\n2. Copy the distributed jar files inside your 'Tridion installation folder'\\lib directory\r\n3. Start the deployer service\r\n\r\nDistributed files:\r\n==================\r\ncd_deployer.jar (6.1.0.1074)\r\ncd_model.jar (6.1.0.1074)\r\n\r\nDependencies:\r\n=============\r\nSDL Tridion 2011 SP1 HR1\r\n\r\n\r\nFixed problems:\r\n===============\r\nTT83475\r\nProblem Description\r\n-------------------\r\nUnder heavy load, the deployer would pick-up twice the same transport package causing an error on the second attempt.\r\n\r\nHotfix Description\r\n-------------------\r\nMade sure the same package is not picked-up twice. \r\n\r\n\r\nTT81270\r\nProblem Description\r\n-------------------\r\nWhen deploying unmanaged binaries, content is mixed-up between binaries in case order in binaries.xml and instructions.xml is different.\r\n\r\nHotfix Description\r\n-------------------\r\nLook up for unmanaged binaries by the path as all of them have the same id. \r\n\r\n\r\n\r\nTT81125\r\nProblem Description\r\n-------------------\r\nThere are some limitations for the CustomMetaValue for Oracle schemas and filesystem due to some checks in the Deployer. \r\n\r\nHotfix Description\r\n-------------------\r\nThe early checks in the Deployer are removed.\r\n\r\n\r\nTT80995 \r\nProblem Description\r\n-------------------\r\nPublishing process stuck in Resolving state\r\n\r\nHotfix Description\r\n-------------------\r\nRemoving DynamicLinks might cause database locks. To prevent that we flush the session prior and after removing DynamicLinks.\r\n\r\n\r\n\r\nDisclaimer:\r\n===========\r\nHotfixes are released at the discretion of Tridion based on technical\r\ncomplexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/\r\nconfiguration and therefore should only be installed if approved by Tridion\r\nCustomer Support. Hotfixes should be replaced as soon as possible by the\r\nsubsequent service pack where the problem is fixed.\r\n\r\n(c) 2012 SDL Tridion B.V.\r\n",
"version": "2011 SP1 HR#1"
},
{
"_id": {
"$oid": "635fe2ac94436e1bc8257aaa"
},
"hotfix_name": "85671",
"modified_date": {
"$date": 1376992081826
},
"problem_description": "- Sometime I get wrong result of pageMeta.getComponentPresentationMetas() in the session preview context\r\n- Not able to remove Component Presentation from CWA page\r\n- Not able to change order of Component Presentations on my CWA page\r\n- Still preview the same old page even after deleting components from CWA page\r\n- Preview not sending DCP - Page link information\r\n",
"readme_text": "Release Notes for Hotfix TT85671\r\n================================\r\n\r\nVersion:\r\n========\r\nThis hotfix is intended only for Tridion 2013 GA.\r\n\r\nThe hotfix includes the following fixes:\r\n----------------------------------------\r\nTT84847 - Hanging threads in broker\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n85671 - Session preview (experience manager) functionality for dynamic web applications. \r\n\r\nInstallation of CM:\r\n===================\r\n 1. Stop all TCM Services, IIS Service, and the TCM COM+ Application.\r\n 2. Backup the file Tridion.ContentManager.Publishing.PreviewService.dll located in the %TRIDION_HOME%\\Bin folder\r\n 3. Copy the Tridion.ContentManager.Publishing.PreviewService.dll file from this hotfix to the %TRIDION_HOME%\\Bin folder\r\n 4. Restart the IIS Service, TCM Services and TCM COM+ Application.\r\n\r\nDistributed files for CM:\r\n=========================\r\n Tridion.ContentManager.Publishing.PreviewService.dll (file version 7.0.0.2304)\r\n\r\nInstallation of CD:\r\n===================\r\nWeb Application:\r\n---------------------\r\nJava Web Application environment:\r\n1. Ensure that you have a correct installed Content Delivery installation inside your web application\r\n2. Stop your web application server or web application\r\n3. Copy the distributed jar files inside your web application WEB-INF\\lib directory\r\n4. Start your web application server or web application\r\n\r\n.NET Web Application environment:\r\n1. Ensure the application pool and or IIS Server has been stopped\r\n2. Copy the distributed jar files inside the IIS application directory bin\\lib directory. In case of central tridion installation please copy the distributed jar files\r\ninto the installation directory \\lib folder.\r\n3. Start the application pool and or IIS Server\r\n\r\nDistributed files for CD:\r\n=========================\r\ncd_session.jar (7.0.1.13)\r\ncd_odata.jar (7.0.1.13)\r\ncd_datalayer.jar (7.0.1.13)\r\ncd_odata_types.jar (7.0.1.13)\r\ncd_preview_webservice.jar (7.0.1.13)\r\n\r\nDependencies:\r\n=============\r\nSDL Tridion 2013 GA\r\n\r\n\r\nFixed problems:\r\n===============\r\nTT85671\r\nProblem Description\r\n-------------------\r\n- Sometime I get wrong result of pageMeta.getComponentPresentationMetas() in the session preview context\r\n- Not able to remove Component Presentation from CWA page\r\n- Not able to change order of Component Presentations on my CWA page\r\n- Still preview the same old page even after deleting components from CWA page\r\n- Preview not sending DCP - Page link information\r\n\r\nHotfix Description\r\n-------------------\r\nImproved page link information ( page to dynamic component presentation ) from both CM and CD side to make dynamic\r\nCD web applications be able to load DCP's based on the relation to a Page. \r\n\r\nDisclaimer:\r\n===========\r\nHotfixes are released at the discretion of Tridion based on technical\r\ncomplexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/\r\nconfiguration and therefore should only be installed if approved by Tridion\r\nCustomer Support. Hotfixes should be replaced as soon as possible by the\r\nsubsequent service pack where the problem is fixed.\r\n\r\n(c) 2013 SDL Tridion B.V.\r\n",
"version": "2013"
},
{
"_id": {
"$oid": "635fe2aa94436e1bc8257a15"
},
"hotfix_name": "CD_2011.1.1.83467",
"modified_date": {
"$date": 1355999394345
},
"problem_description": "'org.hibernate.TransientObjectException' would occur in case of changing related keywords of an item meta in the same transaction.\r\nThere was an issue when publishing BinaryMeta while there's an existing ComponentMeta with the same itemId in the published storage.\r\nThere are some limitations for the CustomMetaValue for Oracle schemas and filesystem due to some checks in the Deployer. \r\nPublishing process stuck in Resolving state\r\n",
"readme_text": "Release Notes for Hotfix TT82946\r\n================================\r\n\r\nVersion:\r\n========\r\nThis is a cumulative hotfix and is intended only for Tridion 2011 SP1 HR1\r\nThe hotfix includes the following fixes:\r\n- TT83467 'Unable to remove data entity, org.hibernate.TransientObjectException' occurs randomly when deploying content to the database\r\n- TT82946 Publish to the deployer fail with the exception \"org.hibernate.exception.ConstraintViolationException: could not insert\"\r\n- TT81125 Deployment fails when publishing a page that contains metadata that exceeds 3400 bytes, \r\n- TT80995 Publishing process stuck in Resolving state\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n- TT83467 'Unable to remove data entity, org.hibernate.TransientObjectException' occurs randomly when deploying content to the database\r\n\r\nInstallation:\r\n=============\r\nDeployer environment:\r\n---------------------\r\nJava Environment with HttpUpload:\r\n1. Ensure that you have a correct installed Content Delivery installation inside your web application\r\n2. Stop your web application server or web application containing the deployer httpupload\r\n3. Copy the distributed jar files inside your web application WEB-INF\\lib directory\r\n4. Start your web application server or web application\r\n\r\n.NET Environment with HttpUpload:\r\n1. Ensure the application pool and or IIS Server has been stopped\r\n2. Copy the distributed jar files inside the IIS application directory bin\\lib directory. In case of central tridion installation please copy the distributed jar files\r\ninto the installation directory \\lib folder.\r\n3. Start the application pool and or IIS Server\r\n\r\nStandalone deployer:\r\n1. Ensure the deployer service has been stopped\r\n2. Copy the distributed jar files inside your 'Tridion installation folder'\\lib directory\r\n3. Start the deployer service\r\n\r\nDistributed files:\r\n==================\r\ncd_datalayer.jar (6.1.0.1073)\r\n\r\nDependencies:\r\n=============\r\nSDL Tridion 2011 SP1 HR1\r\n\r\n\r\nFixed problems:\r\n===============\r\nTT83467\r\nProblem Description\r\n-------------------\r\n'org.hibernate.TransientObjectException' would occur in case of changing related keywords of an item meta in the same transaction.\r\n\r\nHotfix Description\r\n-------------------\r\nMaking sure that the link from RelatedKeyword back to ItemMeta is nullified before saving the item meta.\r\n\r\n\r\nTT82946\r\nProblem Description\r\n-------------------\r\nThere was an issue when publishing BinaryMeta while there's an existing ComponentMeta with the same itemId in the published storage.\r\n\r\nHotfix Description\r\n-------------------\r\nRemoving the existing ComponentMeta before re-adding it with the BinaryMeta.\r\n\r\n\r\nTT81125\r\nProblem Description\r\n-------------------\r\nThere are some limitations for the CustomMetaValue for Oracle schemas and filesystem due to some checks in the Deployer. \r\n\r\nHotfix Description\r\n-------------------\r\nThe early checks in the Deployer are removed.\r\n\r\n\r\nTT80995 \r\nProblem Description\r\n-------------------\r\nPublishing process stuck in Resolving state\r\n\r\nHotfix Description\r\n-------------------\r\nRemoving DynamicLinks might cause database locks. To prevent that we flush the session prior and after removing DynamicLinks.\r\n\r\n\r\nDisclaimer:\r\n===========\r\nHotfixes are released at the discretion of Tridion based on technical\r\ncomplexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/\r\nconfiguration and therefore should only be installed if approved by Tridion\r\nCustomer Support. Hotfixes should be replaced as soon as possible by the\r\nsubsequent service pack where the problem is fixed.\r\n\r\n(c) 2012 SDL Tridion B.V.\r\n",
"version": "2011 SP1 HR#1"
},
{
"_id": {
"$oid": "635fe2b894436e1bc8257c5e"
},
"hotfix_name": "ECL_9.5.0.23943",
"modified_date": {
"$date": 1656947171058
},
"problem_description": "Fail to open a component with link to an external when connector cannot return the external item.\r\n",
"readme_text": "Release Notes for Hotfix 23943\r\n\r\nVersion:\r\n\tThis hotfix is intended only for Tridion External Content Library 9.5 included in SDL Tridion Sites 9.5.\r\n\r\nProblem description:\r\n\tFail to open a component with link to an external when connector cannot return the external item.\r\n\r\nHotfix description:\r\n\tCheck if external item is NULL before using its object.\r\n\r\nInstallation:\r\n\t1. Stop all Tridion Content Manager Service Host and IIS Service.\r\n\t2. Move the file Tridion.ExternalContentLibrary.DomainModel.dll located in the %WINDIR%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.ExternalContentLibrary.DomainModel\\v4.0_9.5.0.0__ddfc895746e5ee6b folder\r\n\t3. Copy the file Tridion.ExternalContentLibrary.DomainModel.dll file from this hotfix to the %WINDIR%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.ExternalContentLibrary.DomainModel\\v4.0_9.5.0.0__ddfc895746e5ee6b folder\r\n\t4. Move the file Tridion.ExternalContentLibrary.Data.dll located in the %WINDIR%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.ExternalContentLibrary.Data\\v4.0_9.5.0.0__ddfc895746e5ee6b folder\r\n\t5. Copy the file Tridion.ExternalContentLibrary.Data.dll file from this hotfix to the %WINDIR%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.ExternalContentLibrary.Data\\v4.0_9.5.0.0__ddfc895746e5ee6b folder\r\n\t6. Copy the file Tridion.ExternalContentLibrary.TcmExtension.dll from this hotfix to \"%TRIDION_CM_HOME%\\bin \" replacing the old version.\r\n\t7. Copy the file Tridion.ExternalContentLibrary.UI.DataExtenders.dll from this hotfix to \"%TRIDION_CM_HOME%\\web\\WebUI\\WebRoot\\bin\\Components\\ExternalContentLibrary\" replacing the old version.\r\n\t8. Restart the IIS Service and Tridion Content Manager Service Host.\r\n\r\nDistributed files:\r\n\tTridion.ExternalContentLibrary.DomainModel.dll (File Version 9.5.0.453)\r\n\tTridion.ExternalContentLibrary.Data.dll (File Version 9.5.0.453)\r\n\tTridion.ExternalContentLibrary.TcmExtension.dll (File Version 9.5.0.453)\r\n\tTridion.ExternalContentLibrary.UI.DataExtenders.dll (File Version 9.5.0.453)\r\n\tReadme.txt (this file)\r\n\r\nFixes included:\r\n\tCRQ-21944: ECL list performance degradation when list contains more then 1000 items.\r\n\tCRQ-27548: After 9.1 ECL creates new stub even if old stub already exists if ECL URI contains underscore '_'.\r\n\r\nDependencies:\r\n\tN/A\r\n\r\nDisclaimer:\r\n\tHotfixes are released at the discretion of RWS based on technical complexity, customer business requirements and schedules.\r\n\tHotfixes are made and tested only for the described problem on a particular environment\\configuration and therefore should only be installed if approved by Customer Support of SDL Web Content Management Solutions Division.\r\n\tHotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright \u00a9 2015-2022 All Rights Reserved by the RWS Group for and on behalf of its affiliates and subsidiaries.\r\n",
"version": "Sites 9.5"
},
{
"_id": {
"$oid": "635fe2aa94436e1bc8257a0b"
},
"hotfix_name": "CD_2011.1.1.81270",
"modified_date": {
"$date": 1343036695736
},
"problem_description": "Publishing process stuck in Resolving state\r\nThere are some limitations for the CustomMetaValue for Oracle schemas and filesystem due to some checks in the Deployer. \r\nWhen deploying unmanaged binaries, content is mixed-up between binaries in case order in binaries.xml and instructions.xml is different.\r\n",
"readme_text": "Release Notes for Hotfix TT81270\r\n================================\r\n\r\nVersion:\r\n========\r\nThis cumulative hotfix and is intended only for Tridion 2011 SP1 HR1\r\nThe hotfix includes the following fixes:\r\n- TT81270 When deploying unmanaged binaries, content is mixed-up between binaries in case order in binaries.xml and instructions.xml is different,\r\n- TT81125 Deployment fails when publishing a page that contains metadata that exceeds 3400 bytes, \r\n- TT80995 Publishing process stuck in Resolving state\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n- TT81270 When deploying unmanaged binaries, content is mixed-up between binaries in case order in binaries.xml and instructions.xml is different.\r\n\r\nInstallation:\r\n=============\r\nDeployer environment:\r\n---------------------\r\nJava Environment with HttpUpload:\r\n1. Ensure that you have a correct installed Content Delivery installation inside your web application\r\n2. Stop your web application server or web application containing the deployer httpupload\r\n3. Copy the distributed jar files inside your web application WEB-INF\\lib directory\r\n4. Start your web application server or web application\r\n\r\n.NET Environment with HttpUpload:\r\n1. Ensure the application pool and or IIS Server has been stopped\r\n2. Copy the distributed jar files inside the IIS application directory bin\\lib directory. In case of central tridion installation please copy the distributed jar files\r\ninto the installation directory \\lib folder.\r\n3. Start the application pool and or IIS Server\r\n\r\nStandalone deployer:\r\n1. Ensure the deployer service has been stopped\r\n2. Copy the distributed jar files inside your 'Tridion installation folder'\\lib directory\r\n3. Start the deployer service\r\n\r\nDistributed files:\r\n==================\r\ncd_deployer.jar\r\ncd_model.jar\r\n\r\nDependencies:\r\n=============\r\nSDL Tridion 2011 SP1 HR1\r\n\r\n\r\nFixed problems:\r\n===============\r\n\r\nTT80995 \r\nProblem Description\r\n-------------------\r\nPublishing process stuck in Resolving state\r\n\r\nHotfix Description\r\n-------------------\r\nRemoving DynamicLinks might cause database locks. To prevent that we flush the session prior and after removing DynamicLinks.\r\n\r\n\r\nTT81125\r\nProblem Description\r\n-------------------\r\nThere are some limitations for the CustomMetaValue for Oracle schemas and filesystem due to some checks in the Deployer. \r\n\r\nHotfix Description\r\n-------------------\r\nThe early checks in the Deployer are removed.\r\n\r\nTT81270\r\nProblem Description\r\n-------------------\r\nWhen deploying unmanaged binaries, content is mixed-up between binaries in case order in binaries.xml and instructions.xml is different.\r\n\r\nHotfix Description\r\n-------------------\r\nLook up for unmanaged binaries by the path as all of them has the same id. \r\n\r\n\r\nDisclaimer:\r\n===========\r\nHotfixes are released at the discretion of Tridion based on technical\r\ncomplexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/\r\nconfiguration and therefore should only be installed if approved by Tridion\r\nCustomer Support. Hotfixes should be replaced as soon as possible by the\r\nsubsequent service pack where the problem is fixed.\r\n\r\n(c) 2012 SDL Tridion B.V.\r\n",
"version": "2011 SP1 HR#1"
},
{
"_id": {
"$oid": "635fe2b894436e1bc8257c67"
},
"hotfix_name": "AccessManagement_1.1.0.29317",
"modified_date": {
"$date": 1655739442142
},
"problem_description": "Tridion Access Management caches user claims obtained from an (external) Identity Provider after authenticating the user.\r\nSo, the user claims cached in the Tridion Access Management database (UserClaims table) are updated each time the user logs in.\r\nHowever, there is a bug resulting in the old claim values not being removed, but new claim values being added each time.\r\nSo, the number of rows in the UserClaims table increases each time a user logs in.\r\nThis isn't noticeable from the outside, because Access Management deduplicates (forwarded) user claims when providing them through the OIDC userInfo endpoint.\r\nHowever, if a claim value changes in the Identity Provider, Access Management will keep providing the old claim value too.\r\n",
"readme_text": "Release Notes for Hotfix 29317\r\n\r\nVersion:\r\n\tThis hotfix is only intended for Tridion Access Management 1.1 (included in SDL Tridion Sites 9.6).\r\n\r\nProblem description:\r\n\tTridion Access Management caches user claims obtained from an (external) Identity Provider after authenticating the user.\r\n\tSo, the user claims cached in the Tridion Access Management database (UserClaims table) are updated each time the user logs in.\r\n\tHowever, there is a bug resulting in the old claim values not being removed, but new claim values being added each time.\r\n\tSo, the number of rows in the UserClaims table increases each time a user logs in.\r\n\tThis isn't noticeable from the outside, because Access Management deduplicates (forwarded) user claims when providing them through the OIDC userInfo endpoint.\r\n\tHowever, if a claim value changes in the Identity Provider, Access Management will keep providing the old claim value too.\r\n\r\nHotfix description:\r\n\tThis hotfix ensures that old user claim values are removed before adding the new ones.\r\n\tAs a result, old values should no longer be provided if a claim value changes and there should (eventually) be less \"garbage\" in the UserClaims table.\r\n\r\nInstallation:\r\n\t1. Extract the contents of the Hotfix ZIP package to a temporary location on the CM Server\r\n\t2. Stop the Tridion Access Management Service (in case Access Management is hosted in IIS: stop IIS)\r\n\t3. Locate the Tridion Access Management Service deployment on file system and make a backup of the Tridion.AccessManagement.EFCore.dll\r\n\t4. Replace Tridion.AccessManagement.EFCore.dll with the one from the hotfix ZIP.\r\n\t5. Restart the Tridion Access Management Service\r\n\t6. In case of a scaled-out deployment, this procedure should be repeated on all CM Servers.\r\n\r\nDistributed files:\r\n\tTridion.AccessManagement.EFCore.dll (File version 1.1.0.9/Assembly version 1.1.0.0)\r\n\tReadme.txt (this file)\r\n\r\nFixes included:\r\n\tNone\r\n\r\nDependencies:\r\n\tNone\r\n\r\nDisclaimer:\r\n\tHotfixes are released at the discretion of RWS based on technical complexity, customer business requirements and schedules.\r\n\tHotfixes are made and tested only for the described problem on a particular environment\\configuration and therefore should only be installed if approved by Customer Support of SDL Web Content Management Solutions Division.\r\n\tHotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright \u00a9 2022 All Rights Reserved by the RWS Group for and on behalf of its affiliates and subsidiaries.\r\n",
"version": "Sites 9.6"
},
{
"_id": {
"$oid": "635fe2aa94436e1bc8257a0a"
},
"hotfix_name": "CD_2011.1.1.81125",
"modified_date": {
"$date": 1342011397895
},
"problem_description": "Publishing process stuck in Resolving state\r\nThere are some limitations for the CustomMetaValue for Oracle schemas and filesystem due to some checks in the Deployer. \r\n",
"readme_text": "Release Notes for Hotfix TT81125\r\n================================\r\n\r\nVersion:\r\n========\r\nThis cumulative hotfix and is intended only for Tridion 2011 SP1 HR1\r\nThe hotfix includes the following fixes:\r\n- TT81125 Deployment fails when publishing a page that contains metadata that exceeds 3400 bytes, \r\n- TT80995 Publishing process stuck in Resolving state\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n- TT81125 Deployment fails when publishing a page that contains metadata that exceeds 3400 bytes\r\nInstallation:\r\n=============\r\nDeployer environment:\r\n---------------------\r\nJava Environment with HttpUpload:\r\n1. Ensure that you have a correct installed Content Delivery installation inside your web application\r\n2. Stop your web application server or web application containing the deployer httpupload\r\n3. Copy the distributed jar files inside your web application WEB-INF\\lib directory\r\n4. Start your web application server or web application\r\n\r\n.NET Environment with HttpUpload:\r\n1. Ensure the application pool and or IIS Server has been stopped\r\n2. Copy the distributed jar files inside the IIS application directory bin\\lib directory. In case of central tridion installation please copy the distributed jar files\r\ninto the installation directory \\lib folder.\r\n3. Start the application pool and or IIS Server\r\n\r\nStandalone deployer:\r\n1. Ensure the deployer service has been stopped\r\n2. Copy the distributed jar files inside your 'Tridion installation folder'\\lib directory\r\n3. Start the deployer service\r\n\r\nDistributed files:\r\n==================\r\ncd_datalayer.jar\r\n\r\nDependencies:\r\n=============\r\nSDL Tridion 2011 SP1 HR1\r\n\r\n\r\nFixed problems:\r\n===============\r\n\r\nTT80995 \r\nProblem Description\r\n-------------------\r\nPublishing process stuck in Resolving state\r\n\r\nHotfix Description\r\n-------------------\r\nRemoving DynamicLinks might cause database locks. To prevent that we flush the session prior and after removing DynamicLinks.\r\n\r\n\r\nTT81125\r\nProblem Description\r\n-------------------\r\nThere are some limitations for the CustomMetaValue for Oracle schemas and filesystem due to some checks in the Deployer. \r\n\r\nHotfix Description\r\n-------------------\r\nThe early checks in the Deployer are removed.\r\n\r\n\r\nDisclaimer:\r\n===========\r\nHotfixes are released at the discretion of Tridion based on technical\r\ncomplexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/\r\nconfiguration and therefore should only be installed if approved by Tridion\r\nCustomer Support. Hotfixes should be replaced as soon as possible by the\r\nsubsequent service pack where the problem is fixed.\r\n\r\n(c) 2012 SDL Tridion B.V.\r\n",
"version": "2011 SP1 HR#1"
},
{
"_id": {
"$oid": "635fe2aa94436e1bc8257a10"
},
"hotfix_name": "CD_2011.1.1.82585",
"modified_date": {
"$date": 1349995917075
},
"problem_description": "Query cache was being flushed everytime an ItemMeta was added to the cache.\r\nDeployer Workers stop processing when the Cache Channel Service is not responding.\r\n",
"readme_text": "Release Notes for Hotfix TT82585\r\n================================\r\n\r\nVersion:\r\n========\r\nThis cumulative hotfix and is intended only for Tridion 2011 SP1 HR1\r\nThe hotfix includes the following fixes:\r\n- TT82585 Cache invalidation issue\r\n- TT82513 2011 SP1: Deployer Workers stop processing when the Cache Channel Service is not responding.\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n- TT82585 Cache invalidation issue\r\n\r\nInstallation:\r\n=============\r\nDeployer environment:\r\n---------------------\r\nJava Environment:\r\n1. Ensure that you have a correct installed Content Delivery installation inside your web application\r\n2. Stop your web application server or web application containing the deployer httpupload\r\n3. Copy the distributed jar files inside your web application WEB-INF\\lib directory\r\n4. Start your web application server or web application\r\n\r\n.NET Environment:\r\n1. Ensure the application pool and or IIS Server has been stopped\r\n2. Copy the distributed jar files inside the IIS application directory bin\\lib directory. In case of central tridion installation please copy the distributed jar files\r\ninto the installation directory \\lib folder.\r\n3. Start the application pool and or IIS Server\r\n\r\n\r\nDistributed files:\r\n==================\r\ncd_cache.jar (version 6.1.0.1060)\r\n\r\nDependencies:\r\n=============\r\nSDL Tridion 2011 SP1 HR1\r\n\r\n\r\nFixed problems:\r\n===============\r\n\r\nTT82585 \r\nProblem Description\r\n-------------------\r\nQuery cache was being flushed everytime an ItemMeta was added to the cache.\r\n\r\nHotfix Description\r\n-------------------\r\nMade sure that the Query cache does not get flushed when a Page/Component is added to the cache.\r\n\r\n\r\nTT82513\r\nProblem Description\r\n-------------------\r\nDeployer Workers stop processing when the Cache Channel Service is not responding.\r\n\r\nHotfix Description\r\n-------------------\r\nMade sure the deployer does not get block if the cache server is unavailable\r\n\r\n\r\nDisclaimer:\r\n===========\r\nHotfixes are released at the discretion of Tridion based on technical\r\ncomplexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/\r\nconfiguration and therefore should only be installed if approved by Tridion\r\nCustomer Support. Hotfixes should be replaced as soon as possible by the\r\nsubsequent service pack where the problem is fixed.\r\n\r\n(c) 2012 SDL Tridion B.V.\r\n",
"version": "2011 SP1 HR#1"
},
{
"_id": {
"$oid": "635fe2ad94436e1bc8257acc"
},
"hotfix_name": "CD_2013.1.0.88309",
"modified_date": {
"$date": 1416329330165
},
"problem_description": "This is a hotfix for:\r\n- TT88309 Using virtual folders throws a page not found when using XPM\r\n",
"readme_text": "Release Notes for Hotfix TT88309\r\n================================\r\n\r\nVersion:\r\n========\r\nThis hotfix is intended only for Tridion 2013 SP1.\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n- TT88309 Using virtual folders throws a page not found when using XPM\r\n\r\nInstallation:\r\n=============\r\n\r\nJava Web Application:\r\n1. Ensure that you have a correct installed Content Delivery installation inside your web application\r\n2. Stop your web application server or web application containing cd_preview webservice\r\n3. Copy the distributed jar files inside your web application WEB-INF\\lib directory\r\n4. Start your web application server or web application\r\n\r\n.NET Web Application:\r\n1. Ensure the application pool and or IIS Server has been stopped\r\n2. Copy the distributed jar files inside the IIS application directory bin\\lib directory. \r\n3. Copy the distributed dll files inside the IIS application directory bin directory. Please take either the version for 32 or 64 bits depending on the platform.\r\n4. Start the application pool and or IIS Server\r\n\r\n\r\nDistributed files:\r\n==================\r\ncd_preview_web.jar\r\nx86/Tridion.ContentDelivery.Interop.dll\r\nx86/Tridion.ContentDelivery.Preview.dll\r\nx86_64/Tridion.ContentDelivery.Interop.dll\r\nx86_64/Tridion.ContentDelivery.Preview.dll\r\n\r\nDependencies:\r\n=============\r\nSDL Tridion 2013 SP1\r\n\r\n\r\nFixed problems:\r\n===============\r\nTT88309\r\nUsing virtual folders throws a page not found when using XPM\r\n-------------------\r\n\r\nHotfix Description\r\n-------------------\r\nThis fix solves the issue resolving the relative paths when using virtual folders with IIS.\r\n\r\n\r\nDisclaimer:\r\n===========\r\nHotfixes are released at the discretion of Tridion based on technical\r\ncomplexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/\r\nconfiguration and therefore should only be installed if approved by Tridion\r\nCustomer Support. Hotfixes should be replaced as soon as possible by the\r\nsubsequent service pack where the problem is fixed.\r\n\r\nCopyright 2014 SDL PLC. All Rights Reserved. All company product or service names referenced herein are properties of their respective owners.\r\n",
"version": "2013 SP1"
},
{
"_id": {
"$oid": "635fe2ad94436e1bc8257acf"
},
"hotfix_name": "CD_2013.1.0.88564",
"modified_date": {
"$date": 1422457142024
},
"problem_description": "This is a hotfix for:\r\n- TT88564 - Deploying metadata to the file system is extremely slow due to large number of 'listFiles' calls\r\n",
"readme_text": "Release Notes for TT88564\r\n================================\r\n\r\nVersion:\r\n========\r\nThis hotfix is intended only for Tridion 2013 SP1.\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n- TT88564 - Deploying metadata to the file system is extremely slow due to large number of 'listFiles' calls\r\n\r\nInstallation:\r\n=============\r\nDeployer environment:\r\n---------------------\r\nJava Environment with HttpUpload:\r\n1. Ensure that you have a correct installed Content Delivery installation inside your web application\r\n2. Stop your web application server or web application containing the deployer httpupload\r\n3. Copy the distributed jar files inside your web application WEB-INF\\lib directory\r\n4. Start your web application server or web application\r\n\r\n.NET Environment with HttpUpload:\r\n1. Ensure the application pool and or IIS Server has been stopped\r\n2. Copy the distributed jar files inside the IIS application directory bin\\lib directory. In case of central tridion installation please copy the distributed jar files\r\ninto the installation directory \\lib folder.\r\n3. Start the application pool and or IIS Server\r\n\r\nStandalone deployer:\r\n1. Ensure the deployer service has been stopped\r\n2. Copy the distributed jar files inside your 'Tridion installation folder'\\lib directory\r\n3. Start the deployer service\r\n\r\nDistributed files:\r\n==================\r\ncd_datalayer.jar\r\n\r\nDependencies:\r\n=============\r\nSDL Tridion 2013 SP1\r\n\r\n\r\nFixed problems:\r\n===============\r\nTT88564\r\nDeploying metadata to the file system is extremely slow due to large number of 'listFiles' calls\r\n-------------------\r\n\r\nHotfix Description\r\n-------------------\r\nDeployer is hanging due to large componentpresentionmeta folder - this is an optimization improvement which should speed up the deployer iteration over these files. \r\n\r\n\r\nDisclaimer:\r\n===========\r\nHotfixes are released at the discretion of Tridion based on technical\r\ncomplexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/\r\nconfiguration and therefore should only be installed if approved by Tridion\r\nCustomer Support. Hotfixes should be replaced as soon as possible by the\r\nsubsequent service pack where the problem is fixed.\r\n\r\n(c) 2015 SDL Tridion B.V.\r\n",
"version": "2013 SP1"
},
{
"_id": {
"$oid": "635fe2ad94436e1bc8257aca"
},
"hotfix_name": "CD_2013.1.0.88163",
"modified_date": {
"$date": 1410957835875
},
"problem_description": "This is a hotfix for:\r\n- TT88163 Error Message has been changed\r\n",
"readme_text": "Release Notes for Hotfix TT88163\r\n================================\r\n\r\nVersion:\r\n========\r\nThis hotfix is intended only for Tridion 2013 SP1.\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n- TT88163 Error Message has been changed\r\n\r\nInstallation:\r\n=============\r\nDeployer environment:\r\n---------------------\r\nJava Environment with HttpUpload:\r\n1. Ensure that you have a correct installed Content Delivery installation inside your web application\r\n2. Stop your web application server or web application containing the deployer httpupload\r\n3. Copy the distributed jar files inside your web application WEB-INF\\lib directory\r\n4. Start your web application server or web application\r\n\r\n.NET Environment with HttpUpload:\r\n1. Ensure the application pool and or IIS Server has been stopped\r\n2. Copy the distributed jar files inside the IIS application directory bin\\lib directory. In case of central tridion installation please copy the distributed jar files\r\ninto the installation directory \\lib folder.\r\n3. Start the application pool and or IIS Server\r\n\r\nStandalone deployer:\r\n1. Ensure the deployer service has been stopped\r\n2. Copy the distributed jar files inside your 'Tridion installation folder'\\lib directory\r\n3. Start the deployer service\r\n\r\nDistributed files:\r\n==================\r\ncd_deployer.jar\r\n\r\nDependencies:\r\n=============\r\nSDL Tridion 2013 SP1\r\n\r\n\r\nFixed problems:\r\n===============\r\nTT88163\r\nError Message has been changed\r\n-------------------\r\n\r\nHotfix Description\r\n-------------------\r\nThe error message displayed in the Publishing Process Details when a unique binary filename is used in multiple multimedia components, has been changed. \r\n\r\n\r\nDisclaimer:\r\n===========\r\nHotfixes are released at the discretion of Tridion based on technical\r\ncomplexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/\r\nconfiguration and therefore should only be installed if approved by Tridion\r\nCustomer Support. Hotfixes should be replaced as soon as possible by the\r\nsubsequent service pack where the problem is fixed.\r\n\r\n(c) 2011 SDL Tridion B.V.\r\n",
"version": "2013 SP1"
},
{
"_id": {
"$oid": "635fe2bd94436e1bc8257d12"
},
"hotfix_name": "CD_8.5.0.6337",
"modified_date": {
"$date": 1506432995901
},
"problem_description": "- Using Web 8.5 and DXA 1.7, a URL with a querystring parameter with no value like this: http://localhost:90/us/system/librarylist.aspx?dfsdf Fails with the error {\"error\":\"InternalServerError\"}\r\n",
"readme_text": "\ufeffRelease Notes for Hotfix CRQ-6337\r\n=================================\r\n\r\nVersion:\r\n============\r\nThis Hotfix is intended for version 8.5.0. Layout build number is 1016.\r\n\r\nThe hotfix includes the following fixes:\r\n============\r\n - CRQ-6337 Web 8.5/DXA 1.7: InternalServerError on a URL with a querystring parameter with no value\t\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n - CRQ-6337 Web 8.5/DXA 1.7: InternalServerError on a URL with a querystring parameter with no value\t\r\n\r\nInstallation:\r\n=============\r\nThis cumulative hotfix provides updated .NET REST API role.\r\n\r\n1. Stop your rest web application\r\n2. Backup it to safe location\r\n3. Delete DLLs present in your web-app\r\n4. Copy new DLLs from api\\rest folder of this HF to your web-app\r\n5. Start web-application\r\n\r\nDistributed roles:\r\n==================\r\nREST Api Role\r\n\r\nFixed problems:\r\n===============\r\n - CRQ-6337 Web 8.5/DXA 1.7: InternalServerError on a URL with a querystring parameter with no value\t\r\n\r\n\r\nProblem Description\r\n-------------------\r\n- Using Web 8.5 and DXA 1.7, a URL with a querystring parameter with no value like this: http://localhost:90/us/system/librarylist.aspx?dfsdf Fails with the error {\"error\":\"InternalServerError\"}\r\n\r\nHotfix Description\r\n-------------------\r\n- Fixed issue with incomplete query param\r\n\r\n\r\nDisclaimer:\r\n===========\r\n\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/configuration and therefore should only be installed\r\nif approved by Customer Support. Hotfixes should be replaced as soon as possible by the subsequent patch release where the problem is fixed.\r\n\r\nCopyright \ufffd 2016-2017 SDL Group. All Rights Reserved.\r\n\r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2aa94436e1bc8257a1a"
},
"hotfix_name": "CD_2011.1.1.84736",
"modified_date": {
"$date": 1363105447296
},
"problem_description": "During the mass deployment of big packages containing same binaries, the default number of deployment retries (10) might not be enough.\r\nDuring the deployment process, the deployer serializes the state to be able to pick-up from where it's left in case of failure. Because the loggers associated to each worker\r\nwere also serialized, we would get a ConcurrentModificationException under heavy load because different loggers (associated to workers in different transactions) were cached by\r\nLogBack while the current transaction state was serialized to disk.\r\nUnder heavy load, the deployer would pick-up twice the same transport package causing an error on the second attempt.\r\n'org.hibernate.TransientObjectException' would occur in case of changing related keywords of an item meta in the same transaction.\r\nThere was an issue when publishing BinaryMeta while there's an existing ComponentMeta with the same itemId in the published storage.\r\nWhen deploying unmanaged binaries, content is mixed-up between binaries in case order in binaries.xml and instructions.xml is different.\r\nThere are some limitations for the CustomMetaValue for Oracle schemas and filesystem due to some checks in the Deployer. \r\nPublishing process stuck in Resolving state\r\n",
"readme_text": "Release Notes for Hotfix TT84736\r\n================================\r\n\r\nVersion:\r\n========\r\nThis cumulative hotfix and is intended only for Tridion 2011 SP1 HR1\r\nThe hotfix includes the following fixes:\r\n- TT84736 Configuration option for the number of retries of the deployer\r\n- TT84446 Mass publishing of items to a single deployer leads to java.util.ConcurrentModificationException: null\r\n- TT83475 Deployment fails for some items with error message: Unable to unzip, ***.zip (The system cannot find the file specified), \r\n- TT83467 'Unable to remove data entity, org.hibernate.TransientObjectException' occurs randomly when deploying content to the database\r\n- TT82946 Publish to the deployer fail with the exception \"org.hibernate.exception.ConstraintViolationException: could not insert\"\r\n- TT81270 When deploying unmanaged binaries, content is mixed-up between binaries in case order in binaries.xml and instructions.xml is different,\r\n- TT81125 Deployment fails when publishing a page that contains metadata that exceeds 3400 bytes, \r\n- TT80995 Publishing process stuck in Resolving state\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n- TT84736 Configuration option for the number of retries of the deployer\r\n\r\nInstallation:\r\n=============\r\nDeployer environment:\r\n---------------------\r\nJava Environment with HttpUpload:\r\n1. Ensure that you have a correct installed Content Delivery installation inside your web application\r\n2. Stop your web application server or web application containing the deployer httpupload\r\n3. Copy the distributed jar files inside your web application WEB-INF\\lib directory\r\n4. Start your web application server or web application\r\n\r\n.NET Environment with HttpUpload:\r\n1. Ensure the application pool and or IIS Server has been stopped\r\n2. Copy the distributed jar files inside the IIS application directory bin\\lib directory. In case of central tridion installation please copy the distributed jar files\r\ninto the installation directory \\lib folder.\r\n3. Start the application pool and or IIS Server\r\n\r\nStandalone deployer:\r\n1. Ensure the deployer service has been stopped\r\n2. Copy the distributed jar files inside your 'Tridion installation folder'\\lib directory\r\n3. Start the deployer service\r\n\r\nDistributed files:\r\n==================\r\ncd_datalayer.jar (6.1.0.1076)\r\ncd_deployer.jar (6.1.0.1076)\r\ncd_model.jar (6.1.0.1076)\r\ncd_core.jar (6.1.0.1076)\r\n\r\nDependencies:\r\n=============\r\nSDL Tridion 2011 SP1 HR1\r\n\r\n\r\nFixed problems:\r\n===============\r\nTT84736\r\nProblem Description\r\n-------------------\r\nDuring the mass deployment of big packages containing same binaries, the default number of deployment retries (10) might not be enough.\r\n\r\nHotfix Description\r\n-------------------\r\nAllowing customer to define the number of retries for each Queue/Location in a MaximumRetries attribute. Example:\r\n\r\n\r\n\r\nTT84446\r\nProblem Description\r\n-------------------\r\nDuring the deployment process, the deployer serializes the state to be able to pick-up from where it's left in case of failure. Because the loggers associated to each worker\r\nwere also serialized, we would get a ConcurrentModificationException under heavy load because different loggers (associated to workers in different transactions) were cached by\r\nLogBack while the current transaction state was serialized to disk.\r\n\r\nHotfix Description\r\n-------------------\r\nMade sure that the loggers are excluded from the serializing process and optimized the declaration of all loggers involved in the transaction state.\r\n\r\n\r\nTT83475\r\nProblem Description\r\n-------------------\r\nUnder heavy load, the deployer would pick-up twice the same transport package causing an error on the second attempt.\r\n\r\nHotfix Description\r\n-------------------\r\nMade sure the same package is not picked-up twice. \r\n\r\n\r\nTT83467\r\nProblem Description\r\n-------------------\r\n'org.hibernate.TransientObjectException' would occur in case of changing related keywords of an item meta in the same transaction.\r\n\r\nHotfix Description\r\n-------------------\r\nMaking sure that the link from RelatedKeyword back to ItemMeta is nullified before saving the item meta.\r\n\r\n\r\nTT82946\r\nProblem Description\r\n-------------------\r\nThere was an issue when publishing BinaryMeta while there's an existing ComponentMeta with the same itemId in the published storage.\r\n\r\nHotfix Description\r\n-------------------\r\nRemoving the existing ComponentMeta before re-adding it with the BinaryMeta.\r\n\r\n\r\nTT81270\r\nProblem Description\r\n-------------------\r\nWhen deploying unmanaged binaries, content is mixed-up between binaries in case order in binaries.xml and instructions.xml is different.\r\n\r\nHotfix Description\r\n-------------------\r\nLook up for unmanaged binaries by the path as all of them have the same id. \r\n\r\n\r\n\r\nTT81125\r\nProblem Description\r\n-------------------\r\nThere are some limitations for the CustomMetaValue for Oracle schemas and filesystem due to some checks in the Deployer. \r\n\r\nHotfix Description\r\n-------------------\r\nThe early checks in the Deployer are removed.\r\n\r\n\r\nTT80995 \r\nProblem Description\r\n-------------------\r\nPublishing process stuck in Resolving state\r\n\r\nHotfix Description\r\n-------------------\r\nRemoving DynamicLinks might cause database locks. To prevent that we flush the session prior and after removing DynamicLinks.\r\n\r\n\r\n\r\nDisclaimer:\r\n===========\r\nHotfixes are released at the discretion of Tridion based on technical\r\ncomplexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/\r\nconfiguration and therefore should only be installed if approved by Tridion\r\nCustomer Support. Hotfixes should be replaced as soon as possible by the\r\nsubsequent service pack where the problem is fixed.\r\n\r\n(c) 2013 SDL Tridion B.V.\r\n",
"version": "2011 SP1 HR#1"
},
{
"_id": {
"$oid": "635fe2ac94436e1bc8257a73"
},
"hotfix_name": "CD_2011.1.2.3098",
"modified_date": {
"$date": 1493736137078
},
"problem_description": "Preview service returns The server refused this request because the request entity is in a format not supported by the requested resource for the requested method *(request - response - 612.txt).* error when CM send POST request to /ws/odata.svc/BinaryContents.\r\nlog and configuration files are attached.\r\n",
"readme_text": "Release Notes for Hotfix CRQ-3098\r\n================================\r\n\r\nVersion:\r\n========\r\nThis hotfix and is intended only for Tridion 2011 SP1 HR2\r\nThe hotfix includes the following fixes:\r\n- UDP-470 Added null charset to content type of post entity\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n- CRQ-3098: CM 8.5 - CD 6.1.2: I cannot add binary through XPM \r\n\r\nInstallation:\r\n=============\r\n1. Ensure a correct Content Management installation with the Transport Service installed\r\n2. Stop the Tridion Content Delivery Transport Service\r\n3. Go to %TRIDION_HOME%\\lib\r\n4. Replace jars with the ones provided in this hotfix\r\n5. Start the Tridion Content Delivery Transport Service\r\n\r\nDistributed files:\r\n==================\r\ncd_transport.jar\r\nhttpclient.jar\r\nhttpmime.jar\r\nhttpcore.jar\r\n\r\nDependencies:\r\n=============\r\nSDL Tridion 2011 SP1 HR2\r\n\r\nFixed problems:\r\n===============\r\nCRQ-3098\r\nProblem Description\r\n-------------------\r\nPreview service returns The server refused this request because the request entity is in a format not supported by the requested resource for the requested method *(request - response - 612.txt).* error when CM send POST request to /ws/odata.svc/BinaryContents.\r\n\r\nlog and configuration files are attached.\r\n\r\nHotfix Description\r\n-------------------\r\nAdded null charset to the http post entity since sending a charset on post request causes sax parse exception on odata parsing process.\r\n\r\nDisclaimer:\r\n===========\r\nHotfixes are released at the discretion of Tridion based on technical\r\ncomplexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/\r\nconfiguration and therefore should only be installed if approved by Tridion\r\nCustomer Support. Hotfixes should be replaced as soon as possible by the\r\nsubsequent service pack where the problem is fixed.\r\n\r\n(c) 2014 SDL Tridion B.V.\r\n",
"version": "2011 SP1 HR#2"
},
{
"_id": {
"$oid": "635fe2ae94436e1bc8257b20"
},
"hotfix_name": "CD_2013.1.1.88199",
"modified_date": {
"$date": 1421054308234
},
"problem_description": "This is a hotfix for:\r\n- TT88199 Publish fails when transaction package contains \"66560\" in the number of transaction\r\n",
"readme_text": "Release Notes for Hotfix TT88199\r\n================================\r\n\r\nVersion:\r\n========\r\nThis hotfix is intended only for Tridion 2013 SP1 HR1.\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n- TT88199 Publish fails when transaction package contains \"66560\" in the number of transaction\r\n\r\nInstallation:\r\n=============\r\n\r\nTridion CD environment:\r\n-----------------------\r\n1. Stop any Tridion CD processes.\r\n2. Replace the existing cd_model.jar in your environment with the new cd_model.jar delivered by this hotfix.\r\n3. Restart any Tridion CD processes.\r\n\r\nJava web application using Tridion CD dynamic content:\r\n------------------------------------------------------\r\n1. Replace the original Tridion 2013 SP1 cd_model.jar in the WEB-INF/lib directory of your web application with the new cd_model.jar delivered by this hotfix.\r\n\r\n\r\nDistributed files:\r\n==================\r\ncd_model.jar\r\n\r\nDependencies:\r\n=============\r\nSDL Tridion 2013 SP1 HR1\r\n\r\n\r\nFixed problems:\r\n===============\r\nTT88199\r\nPublish fails when transaction package contains \"66560\" in the number of transaction\r\n-------------------\r\n\r\nHotfix Description\r\n-------------------\r\nThe publishing process fails when the transaction package contains \"66560\" in the number of transaction as follows:\r\n\r\ntcm_0-66560-66560\r\ntcm_0-166560-66560\r\ntcm_0-266560-66560\r\ntcm_0-366560-66560\r\n\r\nThe customer has a schedule publish for an amount of 100,000 transactions,\r\nafter this, they found the packages containing *66560* where failing during the publish.\r\n\r\nDisclaimer:\r\n===========\r\nHotfixes are released at the discretion of Tridion based on technical\r\ncomplexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/\r\nconfiguration and therefore should only be installed if approved by Tridion\r\nCustomer Support. Hotfixes should be replaced as soon as possible by the\r\nsubsequent service pack where the problem is fixed.\r\n\r\nCopyright 2015 SDL PLC. All Rights Reserved. All company product or service names referenced herein are properties of their respective owners.\r\n",
"version": "2013 SP1 HR#1"
},
{
"_id": {
"$oid": "635fe2b294436e1bc8257bde"
},
"hotfix_name": "ECL_9.0.0.30907",
"modified_date": {
"$date": 1661431535153
},
"problem_description": "External Content Library fail when connector trying to log message with curly brackets.\r\n",
"readme_text": "Release Notes for Hotfix 30907\r\n\r\nVersion:\r\n\tThis hotfix is intended only for Tridion External Content Library 9.0 included in SDL Tridion Sites 9.0.\r\n\r\nProblem description:\r\n\tExternal Content Library fail when connector trying to log message with curly brackets.\r\n\r\nHotfix description:\r\n\tFix logging implementation.\r\n\r\nInstallation:\r\n\t1. Stop all Tridion Content Manager Service Host and IIS Service.\r\n\t2. Move the file Tridion.Infrastructure.dll located in the %WINDIR%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.Infrastructure\\v4.0_9.0.0.0__ddfc895746e5ee6b folder\r\n\t3. Copy the file Tridion.Infrastructure.dll file from this hotfix to the %WINDIR%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.Infrastructure\\v4.0_9.0.0.0__ddfc895746e5ee6b folder\r\n\t4. Restart the IIS Service and Tridion Content Manager Service Host.\r\n\r\nDistributed files:\r\n\tTridion.Infrastructure.dll (File Version 9.0.0.56)\r\n\tReadme.txt (this file)\r\n\r\nFixes included:\r\n\tN/A\r\n\r\nDependencies:\r\n\tN/A\r\n\r\nDisclaimer:\r\n\tHotfixes are released at the discretion of RWS based on technical complexity, customer business requirements and schedules.\r\n\tHotfixes are made and tested only for the described problem on a particular environment\\configuration and therefore should only be installed if approved by Customer Support of SDL Web Content Management Solutions Division.\r\n\tHotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright \u00a9 2015-2022 All Rights Reserved by the RWS Group for and on behalf of its affiliates and subsidiaries.\r\n",
"version": "Sites 9.0.1"
},
{
"_id": {
"$oid": "635fe2a994436e1bc82579e1"
},
"hotfix_name": "CD_2011.1.0.78523",
"modified_date": {
"$date": 1329150762255
},
"problem_description": "When deploying a complex Taxonomy containing multiparent keywords and more than a few thousand keywords with many related items the deployment\r\nexceeds the transaction timeout and can take up to an hour to complete.\r\n",
"readme_text": "Release Notes for Hotfix TT78523\r\n================================\r\n\r\nVersion:\r\n========\r\nThis hotfix is intended only for Tridion 2011 SP1\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n- TT78523 Publish a large package with many linked components in 2011 SP1 along with a large, nested taxonomy exceeds transaction timeout\r\n\r\nInstallation:\r\n=============\r\nDeployer environment:\r\n---------------------\r\nJava Environment with HttpUpload:\r\n1. Ensure that you have a correct installed Content Delivery installation inside your web application\r\n2. Stop your web application server or web application containing the deployer httpupload\r\n3. Copy the distributed jar files inside your web application WEB-INF\\lib directory\r\n4. Start your web application server or web application\r\n\r\n.NET Environment with HttpUpload:\r\n1. Ensure the application pool and or IIS Server has been stopped\r\n2. Copy the distributed jar files inside the IIS application directory bin\\lib directory. In case of central tridion installation please copy the distributed jar files\r\ninto the installation directory \\lib folder.\r\n3. Start the application pool and or IIS Server\r\n\r\nStandalone deployer:\r\n1. Ensure the deployer service has been stopped\r\n2. Copy the distributed jar files inside your 'Tridion installation folder'\\lib directory\r\n3. Start the deployer service\r\n\r\nDistributed files:\r\n==================\r\ncd_datalayer.jar\r\ncd_storage_conf.xsd\r\ncd_storage_conf_sample.xml\r\n\r\nDependencies:\r\n=============\r\nn.a.\r\n\r\nFixed problems:\r\n===============\r\nTT78523\r\nProblem Description\r\n-------------------\r\nWhen deploying a complex Taxonomy containing multiparent keywords and more than a few thousand keywords with many related items the deployment\r\nexceeds the transaction timeout and can take up to an hour to complete.\r\n\r\nHotfix Description\r\n-------------------\r\nThe cause of the issue is the related item count that is provided on API level. The related item count to a keyword is calculated during deployment\r\ntime due to the complexity of taxonomies with multi-parent keywords the query for each level of the taxonomy grows exponentially in time to execute.\r\n\r\nThe solution is to provide an option to switch of the reference counting mechanism on keywords. The following configuration option is added to the\r\nstorage configuration file under the 'Global' element:\r\n\r\n\r\nBy setting this to false the keyword reference counts are no longer calculated impacting the following api's:\r\nJava Class: com.tridion.taxonomies.Keyword and method: getReferencedContentCount\r\n.NET Class: Tridion.ContentDelivery.Taxonomies.Keyword and then property: 'ReferencedContentCount'\r\n\r\nThe impact will result in these methods returning a '0' integer return value.\r\n\r\nDisclaimer:\r\n===========\r\nHotfixes are released at the discretion of Tridion based on technical\r\ncomplexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/\r\nconfiguration and therefore should only be installed if approved by Tridion\r\nCustomer Support. Hotfixes should be replaced as soon as possible by the\r\nsubsequent service pack where the problem is fixed.\r\n\r\n(c) 2012 SDL Tridion B.V.\r\n",
"version": "2011 SP1"
},
{
"_id": {
"$oid": "635fe2ae94436e1bc8257b1f"
},
"hotfix_name": "CD_2013.1.1.6857",
"modified_date": {
"$date": 1517839480987
},
"problem_description": "Problem happens when mass publishing content both in Production and lower environments.\r\n",
"readme_text": "Release Notes for Hotfix CRQ-6857\r\n================================\r\n\r\nVersion:\r\n========\r\nThis is hotfix and is intended only for Tridion 2013 SP1 HR1\r\nThe hotfix include the following fixes:\r\n\t- CRQ-6857 (SRQ-7438) Deployer throwing errors when mass publishing\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n- CRQ-6857 (SRQ-7438) Deployer throwing errors when mass publishing\r\n\r\nProblem Description\r\n====================\r\nProblem happens when mass publishing content both in Production and lower environments.\r\n\r\nHotfix Description\r\n====================\r\nWe have enabled retry mechanism and maked it configurable.\r\n\r\n\r\nInstallation:\r\n=============\r\n\r\nTridion CD environment:\r\n-----------------------\r\n1. Stop any Tridion Content Distributor Deployer Service.\r\n2. Replace the existing cd_deployer.jar in your environment with the new cd_deployer.jar delivered by this hotfix.\r\n3. Include the UnzipRetryCount property in deployer configuration. An example can be .\r\n4. Restart any Tridion Content Distributor Deployer Service.\r\n\r\nDistributed files:\r\n==================\r\ncd_deployer.jar\r\n\r\nDependencies:\r\n=============\r\nSDL Tridion 2013 SP1 HR1\r\n\r\nDisclaimer:\r\n===========\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/configuration and therefore should only be installed\r\nif approved by Customer Support. Hotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright 2017 SDL PLC. All Rights Reserved. All company product or service names referenced herein are properties of their respective owners.",
"version": "2013 SP1 HR#1"
},
{
"_id": {
"$oid": "635fe2ae94436e1bc8257b1e"
},
"hotfix_name": "CD_2013.1.1.4593",
"modified_date": {
"$date": 1495548084707
},
"problem_description": "Problem happens when the deployer service is secured with Basic Authentication and the user is sending bigger package (>1800 KB in this case).\r\nThe package is failing with HTTP 401 error code.\r\n",
"readme_text": "Release Notes for Hotfix CRQ-4593\r\n================================\r\n\r\nVersion:\r\n========\r\nThis is hotfix and is intended only for Tridion 2013 SP1 HR1\r\nThe hotfix include the following fixes:\r\n\t- CRQ-4593 (SRQ-6774) Transport service fails deploying with SSL and authentication\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n- CRQ-4593 (SRQ-6774) Transport service fails deploying with SSL and authentication\r\n\r\nProblem Description\r\n====================\r\nProblem happens when the deployer service is secured with Basic Authentication and the user is sending bigger package (>1800 KB in this case).\r\nThe package is failing with HTTP 401 error code.\r\n\r\nHotfix Description\r\n====================\r\nWe have enabled 'expect-continue' handshake request parameter which solved this issue.\r\n\r\n\r\nInstallation:\r\n=============\r\n\r\nTridion CD environment:\r\n-----------------------\r\n1. Stop any Tridion Content Distributor Transport Service.\r\n2. Replace the existing cd_transport.jar in your environment with the new cd_transport.jar delivered by this hotfix.\r\n3. Restart any Tridion Content Distributor Transport Service.\r\n\r\nDistributed files:\r\n==================\r\ncd_transport.jar\r\n\r\nDependencies:\r\n=============\r\nSDL Tridion 2013 SP1 HR1\r\n\r\nDisclaimer:\r\n===========\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/configuration and therefore should only be installed\r\nif approved by Customer Support. Hotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright 2017 SDL PLC. All Rights Reserved. All company product or service names referenced herein are properties of their respective owners.",
"version": "2013 SP1 HR#1"
},
{
"_id": {
"$oid": "635fe2aa94436e1bc8257a17"
},
"hotfix_name": "CD_2011.1.1.83520",
"modified_date": {
"$date": 1363704186633
},
"problem_description": "Sometimes when monitoring a service using the RMIHealthMonitor the response comes a bit slower and monitoring considers the monitored service as unavailable.\r\n",
"readme_text": "Release Notes for Hotfix TT83520\r\n================================\r\n\r\nVersion:\r\n========\r\nThis hotfix is intended only for Tridion 2011 SP1 HR1\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n- TT83520 Monitor the Cache Channel Service (RmiServiceHealthMonitor) while the service is definitely running and available. But the monitoring application will show this service in a NotResponding status\r\n\r\nInstallation:\r\n=============\r\n\r\n\r\nMonitoring:\r\n---------------------\r\nJava monitoring process:\r\n1. Stop your monitoring process.\r\n2. Copy the distributed jar files inside your directory.\r\n3. Start your monitoring process.\r\n\r\nStandalone monitoring service:\r\n1. Ensure the monitoring service has been stopped\r\n2. Copy the distributed jar files inside your 'Tridion installation folder'\\lib directory\r\n3. Start the monitoring service\r\n\r\nDistributed files:\r\n==================\r\ncd_monitor.jar (6.1.0.1082)\r\n\r\nDependencies:\r\n=============\r\nSDL Tridion 2011 SP1 HR1\r\n\r\n\r\nFixed problems:\r\n===============\r\nTT83520\r\nProblem Description\r\n-------------------\r\nSometimes when monitoring a service using the RMIHealthMonitor the response comes a bit slower and monitoring considers the monitored service as unavailable.\r\n\r\nHotfix Description\r\n-------------------\r\nThe RMIHealthMonitor is waiting for 5 seconds for a message from the monitored service.\r\n\r\n\r\nDisclaimer:\r\n===========\r\nHotfixes are released at the discretion of Tridion based on technical\r\ncomplexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/\r\nconfiguration and therefore should only be installed if approved by Tridion\r\nCustomer Support. Hotfixes should be replaced as soon as possible by the\r\nsubsequent service pack where the problem is fixed.\r\n\r\n(c) 2013 SDL Tridion B.V.\r\n",
"version": "2011 SP1 HR#1"
},
{
"_id": {
"$oid": "635fe2b594436e1bc8257c33"
},
"hotfix_name": "VWD_9.1.0.25696",
"modified_date": {
"$date": 1631027026162
},
"problem_description": "An old certificate error in Visio Workflow Designer.\r\n",
"readme_text": "Release Notes for Hotfix CRQ-25696\r\n\r\nVersion:\r\nThis hotfix is intended for SDL Web 9.1\r\n\r\nProblem description: \r\nAn old certificate error in Visio Workflow Designer.\r\n\r\nHotfix description:\r\nSDL certificate was updated for 2023 year.\r\n\r\nInstallation:\r\n 1. Uninstall your existing client from the Windows Control Panel before you install the new client.\r\n 2. Double-click the shortcut InstallVWDClient. The Visio Workflow Designer client application installer starts up.\r\n 3. Follow the instructions to install Visio Workflow Designer.\r\n\r\n\r\nFollow the instructions to install Visio Workflow Designer.\r\n\r\nDistributed files:\r\n- Readme.txt (this file)\r\n- InstallVWDClient\r\n- VWD.msi\r\n\r\nDependencies:\r\nn/a\r\n\r\nIncludes:\r\nn/a\r\n\r\nDisclaimer:\r\nHotfixes (as defined under the relevant RWS product release policy) are released at RWS\u2019s discretion based on technical complexity, customer business requirements and schedules. \r\nHotfixes are made and tested only for the described problem on a particular environment/configuration in accordance with the Software Documentation and therefore should only be installed if approved by RWS Technical Support. \r\nHotfixes should be replaced as soon as possible by the subsequent cumulative update where the problem is fixed.\r\n\r\nCopyright \u00a9 2021 All Rights Reserved by the RWS Group for and on behalf of its affiliates and subsidiaries. All company product or service names referenced herein are properties of their respective owners.",
"version": "Sites 9.1"
},
{
"_id": {
"$oid": "635fe2ad94436e1bc8257ad0"
},
"hotfix_name": "CD_2013.1.0.88753",
"modified_date": {
"$date": 1432655341875
},
"problem_description": "This is a hotfix for:\r\n- TT88753- Keyword meta lack navigation link \r\n",
"readme_text": "Release Notes for TT88753\r\n================================\r\n\r\nVersion:\r\n========\r\nThis hotfix is intended only for Tridion 2013 SP1.\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n- TT88753- Keyword meta lack navigation link \r\n\r\nInstallation:\r\n=============\r\n\r\nJava Environment with Webservice installed:\r\n1. Ensure that you have a correct installed Webservice installation inside your web application\r\n2. Stop your web application server or web application containing the webservice\r\n3. Copy the distributed jar file inside your web application WEB-INF\\lib directory\r\n4. Start your web application server or web application\r\n\r\n\r\nDistributed files:\r\n==================\r\ncd_odata_types.jar\r\n\r\nDependencies:\r\n=============\r\nSDL Tridion 2013 SP1\r\n\r\n\r\nFixed problems:\r\n===============\r\nTT88752\r\nKeyword meta lack navigation link\r\n-------------------\r\n\r\nHotfix Description\r\n-------------------\r\nKeyword missed \"CustomMetas\" link. With the help of this hotfix you are able to expand CustomMetas on Keywords and vice versa. (for example Keywords?$expand=CustomMetas)\r\n\r\n\r\nDisclaimer:\r\n===========\r\nHotfixes are released at the discretion of Tridion based on technical\r\ncomplexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/\r\nconfiguration and therefore should only be installed if approved by Tridion\r\nCustomer Support. Hotfixes should be replaced as soon as possible by the\r\nsubsequent service pack where the problem is fixed.\r\n\r\n(c) 2015 SDL Tridion B.V.\r\n",
"version": "2013 SP1"
},
{
"_id": {
"$oid": "635fe2b294436e1bc8257bd7"
},
"hotfix_name": "CD_11.0.1.21656",
"modified_date": {
"$date": 1609163058659
},
"problem_description": "This is a hotfix for:\r\n- CRQ-21656 - After applying CD_11.0.0.19562, SI4T startup failure for Deployer\r\n- CRQ-21847 - Deployer Failing on Committing Deployment - com.tridion.storage.Publication cannot be cast to com.tridion.storage.ComponentMeta\r\n- CRQ-21434 - Database issue after applying Surrogate key fix 9.0 \r\nPrepequisites:\r\nCumulative Update 1 for Sites 9.0 needs to be applied before installing this hotfix.\r\n",
"readme_text": "Release Notes for Hotfixes CRQ-21656 and CRQ-21847 \r\n=================================\r\n\r\nVersion:\r\n========\r\nThis cumulative hotfix is intended only for SDL Sites 9 customers.\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n - CRQ-21656 - After applying CD_11.0.0.19562, SI4T startup failure for Deployer\r\n - CRQ-21847 - Deployer Failing on Committing Deployment - com.tridion.storage.Publication cannot be cast to com.tridion.storage.ComponentMeta\r\n - CRQ-21434 - Database issue after applying Surrogate key fix 9.0 \r\n\r\nPrepequisites:\r\n=============\r\nCumulative Update 1 for Sites 9.0 needs to be applied before installing this hotfix.\r\n\r\nInstallation:\r\n=============\r\n\r\nServices\r\n--------\r\n1. Stop relevant Service\r\n2. Backup (or move) a folder where your standalone Service is located\r\n3. Uninstall the relevant Service by opening a Powershell window in the \\bin of your service and run .\\uninstallService.ps1\r\n4. Navigate to the release\\ folder of this distribution\r\n5. Copy \\standalone folder to the location where your original service was located\r\n6. Rename copied \\standalone folder to the name of your original service's folder\r\n7. Copy all files from \\config folder of your backup (see step #2) to \\config folder of a new service\r\n8. Copy custom jars (if you have any) from backup's \\services\\folder to a same location of a new service\r\n9. Install service by opening a Powershell window in in the location \\bin of new service and run .\\installService.ps1\r\n\r\nDatabase:\r\n---------\r\n1. Copy directories to a convenient location.\r\n2. Use ps1 scripts to perform content datastore upgrade or install as needed.\r\n3. The user might face issues while upgrading the database from 11.0/11.0.1 with the checksum validation.\r\n When running the Content Data Store update script, attached in this hotfix, the following error might occur :- \r\n2020-10-30 10:30:49 Unexpected error running Liquibase: Validation Failed:\r\n 1 change sets check sum\r\n 11.0/migration/broker.sqlserver_surrogate_key.xml::7561bed3-ba35-4bab-a6cd-00f749de6733::tridiondbmanager was: 8:235172ff0da5fa847b2e644e3b28faa3 but is now: 8:6592db6510486979567a0db0faefd7b7\r\nliquibase.exception.ValidationFailedException: Validation Failed:\r\n 1 change sets check sum\r\n 11.0/migration/broker.sqlserver_surrogate_key.xml::7561bed3-ba35-4bab-a6cd-00f749de6733::tridiondbmanager was: 8:235172ff0da5fa847b2e644e3b28faa3 but is now: 8:6592db6510486979567a0db0faefd7b7\r\n at liquibase.changelog.DatabaseChangeLog.validate(DatabaseChangeLog.java:291)\r\n\r\n4. The changeset ids in the Content Data Store databases need to be cleared.\r\nThe error will be reported gives you which is the problematic changeset_id(id)\r\n::changeset_id(id)::author::previous_check_sum:new_check_sum\r\nThe first value is the changeset_id. So in this case the id will be 7561bed3-ba35-4bab-a6cd-00f749de6733\r\n5. So when running the script the dialog would be something like this:-\r\n Database name. Default value is 'Tridion_Broker':\r\n Comma-separated checksum to clear: 7561bed3-ba35-4bab-a6cd-00f749de6733\r\nWhen there are more than one id to clear then use Comma-separators to clear : 7561bed3-ba35-4bab-a6cd-00f749de6733,\r\n6. After specifying the id hit enter, the database upgrade should work as expected. \r\n\r\n\r\nDistributed roles:\r\n==================\r\napi Content Delivery API role\r\ncaching Cache Channel Service\r\ncid Contextual Image Delivery role\r\ncontent Content Service role\r\ncontext Context Service role\r\ndeployer Deployer role\r\ndiscovery Discovery service role\r\npreview Preview service role\r\nsession Session service role\r\nugc/community-service UGC Community Service role\r\nugc/moderation-service UGC Moderation Service role\r\n\r\n\r\nDisclaimer:\r\n===========\r\n\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. \r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore \r\nshould only be installed if approved by Customer Support. Hotfixes should be replaced as soon as possible by the \r\nsubsequent patch release where the problem is fixed.\r\n\r\nCopyright \u00a9 2015-2020 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.\r\n",
"version": "Sites 9.0.1"
},
{
"_id": {
"$oid": "635fe2ba94436e1bc8257ca4"
},
"hotfix_name": "CD_8.1.1.7951",
"modified_date": {
"$date": 1514377044864
},
"problem_description": "- Content (session) service broker queries takes long time, which causes abnormal CPU usage rate on DB server.\r\n",
"readme_text": "\ufeffRelease Notes for Hotfix CRQ-7951\r\n=================================\r\n\r\nVersion:\r\n========\r\nThis is cumulative hotfix and is intended only for SDL Web 8.1.1\r\n\r\nDescription:\r\n============\r\nThe hotfix include the following fixes:\r\n - CRQ-7951 Executing broker queries takes long time, which causes abnormal CPU usage rate on DB server.\r\n\r\nInstallation:\r\n=============\r\nThis cumulative hotfix provides updated standalone service roles as well as In-process API role.\r\n\r\nFor Content/Session service\r\n-----------------------\r\nOn Windows System:\r\n\r\n1. Stop the Service you are going to upgrade\r\n2. Backup (or move) a folder where your standalone Service is located\r\n3. Uninstall the Service by opening a Powershell window in the \\bin of your service and running .\\uninstallService.ps1\r\n4. Navigate to the release\\\\service folder of this distribution\r\n5. Copy \\standalone folder to the location where your original service was located\r\n6. Rename copied \\standalone folder to the name of your original service's folder\r\n7. Copy all files from \\config folder of your backup (see step #2) to \\config folder of a new service.\r\n8. Copy custom jars (if you have any) from backup's \\services\\folder to a same location of a new service\r\n9. Install service by opening a Powershell window in in the location \\bin of new service and run .\\installService.ps1\r\n\r\nOn Unix System:\r\n\r\n1. Stop the Service you are going to upgrade\r\n2. Backup (or move) a folder where your standalone Service is located\r\n3. Uninstall the Service by running the command shell script stop.sh located at /bin\r\n4. Navigate to the release\\\\service folder of this distribution\r\n5. Copy \\standalone folder to the location where your original service was located\r\n6. Rename copied \\standalone folder to the name of your original service's folder\r\n7. Copy all files from \\config folder of your backup (see step #2) to \\config folder of a new service.\r\n8. Copy custom jars (if you have any) from backup's \\services\\folder to a same location of a new service\r\n9. Install service by running the command shell script start.sh locted at /bin directory\r\n\r\nFor Legacy Api Role(in-process)\r\n---------------------------\r\n1. Stop your legacy(in-process) web application\r\n2. Backup it to safe location\r\n3. Delete jars/DLLs present in your web-app\r\n4. Copy new jars/DLLs from api\\in-process folder of this HF to your web-app\r\n5. Restore any custom jars or DLLs from your backup\r\n6. Start web-application\r\n\r\nDistributed roles:\r\n==================\r\ncontent-service\t\t\tContent service role\r\nsession-service\t\t\tSession content service role\r\napi/in-process\t\t\tLegacy in-process API server role\r\n\r\nFixed problems:\r\n===============\r\n - CRQ-7951 Executing broker queries takes long time, which causes abnormal CPU usage rate on DB server.\r\n\r\nProblem Description\r\n-------------------\r\n- Content (session) service broker queries takes long time, which causes abnormal CPU usage rate on DB server.\r\n\r\nHotfix Description\r\n-------------------\r\n- Fixed content (session) service by adding changes to the Cache implementation for the query API to prevent multiple requests to DB when there is already a query being executed.\r\n\r\nDisclaimer:\r\n===========\r\n\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/configuration and therefore should only be installed\r\nif approved by Customer Support. Hotfixes should be replaced as soon as possible by the subsequent patch release where the problem is fixed.\r\n\r\nCopyright \ufffd 2015-2017 SDL Group. All Rights Reserved.\r\n\r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.\r\n",
"version": "Web 8.1.1"
},
{
"_id": {
"$oid": "635fe2ba94436e1bc8257cc0"
},
"hotfix_name": "ECL_8.1.1.6076",
"modified_date": {
"$date": 1503925390220
},
"problem_description": "",
"readme_text": "Release Notes for Hotfix 6076\n\nVersion:\n\tThis hotfix is intended only for Tridion External Content Library 8.1.1 included in Tridion 8.1.1.\n\nProblem description:\n\tIf ECL URI is too long, thumbnail path length can exceed windows limit of 260 characters.\n\nHotfix description:\n\tFix thumbnail name generation code.\n\nInstallation:\n\t1.\tStop all Tridion Content Manager Service Host and IIS Service.\n\t2.\tMove the file Tridion.ExternalContentLibrary.DomainModel.dll located in the %WINDIR%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.ExternalContentLibrary.DomainModel\\v4.0_8.1.0.211__ddfc895746e5ee6b folder\n\t3.\tCopy the Tridion.ExternalContentLibrary.DomainModel.dll file from this hotfix to the %WINDIR%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.ExternalContentLibrary.DomainModel\\v4.0_8.1.0.211__ddfc895746e5ee6b folder\n\t4.\tMove the file Tridion.ExternalContentLibrary.IconLoader.dll located in the %WINDIR%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.ExternalContentLibrary.IconLoader\\v4.0_8.1.0.211__ddfc895746e5ee6b folder\n\t5.\tCopy the Tridion.ExternalContentLibrary.IconLoader.dll file from this hotfix to the %WINDIR%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.ExternalContentLibrary.IconLoader\\v4.0_8.1.0.211__ddfc895746e5ee6b folder\n\t6.\tMove the file Tridion.ExternalContentLibrary.UI.DataExtenders.dll located in the %Tridion%\\web\\WebUI\\WebRoot\\bin folder\n\t7.\tCopy the Tridion.ExternalContentLibrary.UI.DataExtenders.dll file from this hotfix to the %Tridion%\\web\\WebUI\\WebRoot\\bin folder\n\t8. \tMove the file Tridion.ExternalContentLibrary.UI.Http.dll located in the %Tridion%\\web\\WebUI\\WebRoot\\bin folder\n\t9. \tCopy the Tridion.ExternalContentLibrary.UI.Http.dll file from this hotfix to the %Tridion%\\web\\WebUI\\WebRoot\\bin folder\n\t10. Move the file Tridion.ExternalContentLibrary.UI.Model.dll located in the %Tridion%\\web\\WebUI\\WebRoot\\bin folder\n\t11. Copy the Tridion.ExternalContentLibrary.UI.Model.dll file from this hotfix to the %Tridion%\\web\\WebUI\\WebRoot\\bin folder \t\n\t12. Restart the IIS Service and Tridion Content Manager Service Host.\n\nDistributed files:\n\tTridion.ExternalContentLibrary.DomainModel.dll (File Version 8.1.0.245)\n\tTridion.ExternalContentLibrary.IconLoader.dll (File Version 8.1.0.245)\n\tTridion.ExternalContentLibrary.UI.DataExtenders.dll (File Version 8.1.0.245)\n\tTridion.ExternalContentLibrary.UI.Http.dll (File Version 8.1.0.245)\n\tTridion.ExternalContentLibrary.UI.Model.dll (File Version 8.1.0.245)\n\tReadme.txt (this file)\n\nFixes included:\n\tCRQ-2176: Memory leak in microsoft image manipulation library.\n\tCRQ-3664: Editors unable to use ECL items. When using Group Synchronization\n\tCRQ-5014: Error querying publish queue from GUI when MM item is shown multiple times\n\nDependencies:\n\tN/A\n\nDisclaimer:\n\tHotfixes are released at the discretion of SDL Tridion based on technical complexity, customer business requirements and schedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by SDL Tridion Customer Support. Hotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\n\nCopyright (c) 2017 SDL Group.",
"version": "Web 8.1.1"
},
{
"_id": {
"$oid": "635fe2be94436e1bc8257d26"
},
"hotfix_name": "CD_8.5.0_13733",
"modified_date": {
"$date": 1555332470378
},
"problem_description": "- Previous version of jdbc driver is not supporting socketTimeout property.\r\n- We were sending ADF headers uncompressed, which sometimes makes them too large to be handled by load balancer.\r\n",
"readme_text": "Release Notes for Hotfixes CRQ-13900 and CRQ-13733\r\n=================================\r\n\r\nVersion:\r\n========\r\nThis cumulative hotfix is intended only for SDL Web 8.5.0 customers.\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n - CRQ-13900 - Update jdbc driver to support socketTimeout property\r\n - CRQ-13733 - We're sending ADF headers uncompressed, which breaks among others XPM functionality \r\n\r\nInstallation:\r\n=============\r\nThis cumulative hotfix provides updated standalone service roles, in-process and REST api.\r\n\r\nFor all Services\r\n------------\r\n1. Stop the Service you are going to update\r\n2. Backup (or move) the folder where your standalone Service is located\r\n3. Uninstall the Service by opening a Powershell window in the \\bin folder of your service and running\r\n .\\uninstallService.ps1\r\n4. Navigate to the release\\\\service folder of this distribution\r\n5. Copy the \\standalone folder to the location where your original service was located\r\n6. Rename copied \\standalone folder to the name of your original service's folder\r\n7. Copy all files from \\config folder of your backup (see step #2) to \\config folder of a new service\r\n8. Copy custom jars (if you have any) from backup's \\services\\ folders to the same location in new service\r\n9. Install service by opening a Powershell window in in the \\bin folder of the new service and run .\\installService.ps1 \r\n\r\nFor api in-process and REST:\r\n------------\r\n1. Stop your web application\r\n2. Backup it to safe location\r\n3. Delete jars present in your web-app\r\n4. Copy new jars from api/in-process folder of this HF to your web-app\r\n5. Restore any custom jars or DLLs from your backup\r\n6. Only if you use DXA 1.7:\r\n - Replace all jackson-*-2.9.4.jar files with same of version 2.8.3\r\n - Add ehcache-2.8.3.jar next to existing ehcache-3.1.3.jar\r\n7. Start web-application\r\n\r\n\r\nDistributed roles:\r\n==================\r\napi \r\ncid\t\t\tContextual Image Delivery Service role\r\ncontent\t\tContent Service role\r\ncontext\t\tContext Service role\r\ndeployer\tDeployer Service roles\r\ndiscovery\tDiscovery Service role\r\npreview\t\tPreview Service role\r\nsession\t\tSession-enabled Content Service role\r\nugc\t\t\tUGC Service roles\r\n\r\n\r\nDependencies:\r\n=============\r\nN/A\r\n\r\nFixed problems:\r\n===============\r\n - CRQ-13900 - Update jdbc driver to support socketTimeout property\r\n - CRQ-13733 - We're sending ADF headers uncompressed, which breaks among others XPM functionality \r\n\r\nProblem Description\r\n-------------------\r\n- Previous version of jdbc driver is not supporting socketTimeout property.\r\n- We were sending ADF headers uncompressed, which sometimes makes them too large to be handled by load balancer.\r\n\r\n\r\nHotfix Description\r\n-------------------\r\n- Updated to mssql-jdbc-7.0.0\r\n- Implemented ADF header compession\r\n\r\nDisclaimer:\r\n===========\r\n\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. \r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore \r\nshould only be installed if approved by Customer Support. Hotfixes should be replaced as soon as possible by the \r\nsubsequent patch release where the problem is fixed.\r\n\r\nCopyright 2015-2019 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.\r\n",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2bb94436e1bc8257ce3"
},
"hotfix_name": "CD_8.5.0.13167",
"modified_date": {
"$date": 1549990159157
},
"problem_description": "- There were vulnerabilities identified in current Apache MQ and dom4j.\r\n- Deployer service had a memory leak\r\n",
"readme_text": "Release Notes for Hotfix CRQ-13167\r\n=================================\r\n\r\nVersion:\r\n========\r\nThis cumulative hotfix is intended only for SDL Web 8.5.0 customers.\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n - CRQ-13397 - Deployer hangs when bulk publishing due to apparent memory leak \r\n - CRQ-13166 - CVE-2016-3088, Apache MQ \r\n - CRQ-13167 - CVE-2018-1000632 - dom4j vulnerability\r\n\r\nInstallation:\r\n=============\r\nThis cumulative hotfix provides updated standalone service roles and in-process api (java).\r\n\r\nFor all Services\r\n------------\r\n1. Stop the Service you are going to update\r\n2. Backup (or move) the folder where your standalone Service is located\r\n3. Uninstall the Service by opening a Powershell window in the \\bin folder of your service and running\r\n .\\uninstallService.ps1\r\n4. Navigate to the release\\\\service folder of this distribution\r\n5. Copy the \\standalone folder to the location where your original service was located\r\n6. Rename copied \\standalone folder to the name of your original service's folder\r\n7. Copy all files from \\config folder of your backup (see step #2) to \\config folder of a new service\r\n8. Copy custom jars (if you have any) from backup's \\services\\ folders to the same location in new service\r\n9. Install service by opening a Powershell window in in the \\bin folder of the new service and run .\\installService.ps1 \r\n\r\nFor api in-process (java)\r\n------------\r\n1. Stop your legacy(in-process) web application\r\n2. Backup it to safe location\r\n3. Delete jars present in your web-app\r\n4. Copy new jars from api/in-process folder of this HF to your web-app\r\n5. Restore any custom jars or DLLs from your backup\r\n6. Start web-application\r\n\r\nDistributed roles:\r\n==================\r\napi in-process (java)\r\ncid\t\t\tContextual Image Delivery Service role\r\ncontent\t\tContent Service role\r\ncontext\t\tContext Service role\r\ndeployer\tDeployer Service roles\r\ndiscovery\tDiscovery Service role\r\npreview\t\tPreview Service role\r\nsession\t\tSession-enabled Content Service role\r\nugc\t\t\tUGC Service roles\r\n\r\n\r\nDependencies:\r\n=============\r\nN/A\r\n\r\nFixed problems:\r\n===============\r\n- CRQ-13397 - Deployer hangs when bulk publishing due to apparent memory leak \r\n- CRQ-13166 - CVE-2016-3088, Apache MQ \r\n- CRQ-13167 - CVE-2018-1000632 - dom4j vulnerability\r\n\r\nProblem Description\r\n-------------------\r\n- There were vulnerabilities identified in current Apache MQ and dom4j.\r\n- Deployer service had a memory leak\r\n\r\n\r\nHotfix Description\r\n-------------------\r\n- Updated ActiveMQ\r\n- Updated dom4j\r\n- Fixed memory leak\r\n\r\nDisclaimer:\r\n===========\r\n\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. \r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore \r\nshould only be installed if approved by Customer Support. Hotfixes should be replaced as soon as possible by the \r\nsubsequent patch release where the problem is fixed.\r\n\r\nCopyright 2015-2019 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.\r\n",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2ac94436e1bc8257a77"
},
"hotfix_name": "CD_2011.1.2.88610",
"modified_date": {
"$date": 1425980197845
},
"problem_description": "The publishing process fails when the transaction package contains \"66560\" in the number of transaction as follows:\r\ntcm_0-66560-66560\r\ntcm_0-166560-66560\r\ntcm_0-266560-66560\r\ntcm_0-366560-66560\r\nThe customer has a schedule publish for an amount of 100,000 transactions,\r\nafter this, they found the packages containing *66560* where failing during the publish.\r\nWhen attempting to deploy content, it fails with error: Unable to persist data entity, org.hibernate.exception.ConstraintViolationException\r\n",
"readme_text": "Release Notes for TT88610\r\n================================\r\n\r\nVersion:\r\n========\r\nThis cumulative hotfix and is intended only for Tridion 2011 SP1 HR2\r\nThe hotfix include the following fixes:\r\n - TT85556 When attempting to deploy content, it fails with error: Unable to persist data entity, org.hibernate.exception.ConstraintViolationException\r\n - TT88206 Publish fails when transaction package contains \"66560\" in the number of transaction\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n- TT88610 - Performance issue when undeploying content\r\n\r\nInstallation:\r\n=============\r\nDeployer environment:\r\n---------------------\r\nJava Environment with HttpUpload:\r\n1. Ensure that you have a correct installed Content Delivery installation inside your web application\r\n2. Stop your web application server or web application containing the deployer httpupload\r\n3. Copy the distributed jar files inside your web application WEB-INF\\lib directory\r\n4. Start your web application server or web application\r\n\r\n.NET Environment with HttpUpload:\r\n1. Ensure the application pool and or IIS Server has been stopped\r\n2. Copy the distributed jar files inside the IIS application directory bin\\lib directory. In case of central tridion installation please copy the distributed jar files\r\ninto the installation directory \\lib folder.\r\n3. Start the application pool and or IIS Server\r\n\r\nStandalone deployer:\r\n1. Ensure the deployer service has been stopped\r\n2. Copy the distributed jar files inside your 'Tridion installation folder'\\lib directory\r\n3. Start the deployer service\r\n\r\nDistributed files:\r\n==================\r\ncd_model.jar\r\ncd_datalayer.jar\r\n\r\nDependencies:\r\n=============\r\nSDL Tridion 2011 SP1 HR2\r\n\r\nFixed problems:\r\n===============\r\nTT88610\r\nPerformance issue when undeploying content\r\n-------------------\r\n\r\nHotfix Description\r\n-------------------\r\nThis is an optimization improvement which should speed up the content deployer when undeploying content.\r\n\r\n\r\nTT88206\r\nProblem Description\r\n-------------------\r\nThe publishing process fails when the transaction package contains \"66560\" in the number of transaction as follows:\r\n\r\ntcm_0-66560-66560\r\ntcm_0-166560-66560\r\ntcm_0-266560-66560\r\ntcm_0-366560-66560\r\n\r\nThe customer has a schedule publish for an amount of 100,000 transactions,\r\nafter this, they found the packages containing *66560* where failing during the publish.\r\n\r\nHotfix Description\r\n-------------------\r\nThe application is looking for the last occurrence of 66560 in the transaction package name.\r\n\r\n\r\nTT85556\r\nProblem Description\r\n-------------------\r\nWhen attempting to deploy content, it fails with error: Unable to persist data entity, org.hibernate.exception.ConstraintViolationException\r\n\r\nHotfix Description\r\n-------------------\r\n- Made sure we insert item if it doesn't exist otherwise update by decoupling binary meta and component meta. This is a solution if multimedia component meta exist without binary meta.\r\n\r\n\r\nDisclaimer:\r\n===========\r\nHotfixes are released at the discretion of Tridion based on technical\r\ncomplexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/\r\nconfiguration and therefore should only be installed if approved by Tridion\r\nCustomer Support. Hotfixes should be replaced as soon as possible by the\r\nsubsequent service pack where the problem is fixed.\r\n\r\n(c) 2015 SDL Tridion B.V.\r\n",
"version": "2011 SP1 HR#2"
},
{
"_id": {
"$oid": "635fe2bc94436e1bc8257cfc"
},
"hotfix_name": "CD_8.5.0.21995",
"modified_date": {
"$date": 1611930249245
},
"problem_description": "This is a hotfix for:\r\nCRQ-21995 - Deadlock in ImprovedLRUPolicy\r\nCRQ-20625 - Make logs for loading configuration cd_storage_conf.xml clean\r\nCRQ-21166 - Add softreferences to caching\r\nCRQ-21932 - DXA - Resolving Publication mapping incorrectly when having multiple websites\r\nCRQ-22068 - Cashe statistics 'overall' shows the last cache stats instead of summing them\r\nCRQ-22019 - cacheElement.getValue gives NPE\r\nCRQ-22027 - Lots of messages \"Creating Improved LRU Policy for region /com.tridion.storage.ItemMeta\" in log\r\nCRQ-22489 - Improvements to the Broker API generated query\r\nInstallation\r\nServices\r\n1. Ensure relevant Service is stopped\r\n2. Backup (or move) a folder where your standalone Service is located\r\n3. Uninstall the relevant Service by opening a Power-shell window in the \\bin of your service and run .\\uninstallService.ps1\r\n4. Navigate to the release\\ folder of this distribution\r\n5. Copy \\standalone folder to the location where your original service was located\r\n6. Rename copied \\standalone folder to the name of your original service's folder\r\n7. Copy all files from \\config folder of your backup (see step #2) to \\config folder of a new service\r\n8. Copy custom jars (if you have any) from backup's \\services\\folder to a same location of a new service\r\n9. Re-install service by opening a Powershell window in in the location \\bin of new service and run .\\installService.ps1\r\nDistributed roles\r\ncontent Content Service role\r\ndeployer Deployer role\r\ndiscovery Discovery service role\r\npreview Preview service role\r\nsession Session service role\r\nFixed problems\r\nCRQ-21995 - Deadlock in ImprovedLRUPolicy\r\nCRQ-20625 - Make logs for loading configuration cd_storage_conf.xml clean\r\nCRQ-21166 - Add softreferences to caching\r\nCRQ-21932 - DXA - Resolving Publication mapping incorrectly when having multiple websites\r\nCRQ-22068 - Cashe statistics 'overall' shows the last cache stats instead of summing them\r\nCRQ-22019 - cacheElement.getValue gives NPE\r\nCRQ-22027 - Lots of messages \"Creating Improved LRU Policy for region /com.tridion.storage.ItemMeta\" in log\r\nDisclaimer\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. \r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore \r\nshould only be installed if approved by Customer Support. Hotfixes should be replaced as soon as possible by the \r\nsubsequent patch release where the problem is fixed.\r\nCopyright \ufffd 2015-2020 SDL Group. All Rights Reserved.\r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.\r\n",
"readme_text": "\ufeffRelease Notes for Hotfix CRQ-21995\r\n==================================\r\n\r\n\r\nVersion\r\n=======\r\nThis cumulative hotfix is intended only for SDL Web 8.5 customers.\r\n\r\n\r\nDescription\r\n===========\r\nThis is a hotfix for:\r\nCRQ-21995 - Deadlock in ImprovedLRUPolicy\r\nCRQ-20625 - Make logs for loading configuration cd_storage_conf.xml clean\r\nCRQ-21166 - Add softreferences to caching\r\nCRQ-21932 - DXA - Resolving Publication mapping incorrectly when having multiple websites\r\nCRQ-22068 - Cashe statistics 'overall' shows the last cache stats instead of summing them\r\nCRQ-22019 - cacheElement.getValue gives NPE\r\nCRQ-22027 - Lots of messages \"Creating Improved LRU Policy for region /com.tridion.storage.ItemMeta\" in log\r\nCRQ-22489 - Improvements to the Broker API generated query\r\n \r\n\r\nInstallation\r\n============\r\n\r\n\r\nServices\r\n--------\r\n1. Ensure relevant Service is stopped\r\n2. Backup (or move) a folder where your standalone Service is located\r\n3. Uninstall the relevant Service by opening a Power-shell window in the \\bin of your service and run .\\uninstallService.ps1\r\n4. Navigate to the release\\ folder of this distribution\r\n5. Copy \\standalone folder to the location where your original service was located\r\n6. Rename copied \\standalone folder to the name of your original service's folder\r\n7. Copy all files from \\config folder of your backup (see step #2) to \\config folder of a new service\r\n8. Copy custom jars (if you have any) from backup's \\services\\folder to a same location of a new service\r\n9. Re-install service by opening a Powershell window in in the location \\bin of new service and run .\\installService.ps1\r\n\r\n\r\nDistributed roles\r\n=================\r\ncontent Content Service role\r\ndeployer Deployer role\r\ndiscovery Discovery service role\r\npreview Preview service role\r\nsession Session service role\r\n\r\n\r\nFixed problems\r\n==============\r\n\r\nCRQ-21995 - Deadlock in ImprovedLRUPolicy\r\nCRQ-20625 - Make logs for loading configuration cd_storage_conf.xml clean\r\nCRQ-21166 - Add softreferences to caching\r\nCRQ-21932 - DXA - Resolving Publication mapping incorrectly when having multiple websites\r\nCRQ-22068 - Cashe statistics 'overall' shows the last cache stats instead of summing them\r\nCRQ-22019 - cacheElement.getValue gives NPE\r\nCRQ-22027 - Lots of messages \"Creating Improved LRU Policy for region /com.tridion.storage.ItemMeta\" in log\r\n\r\n\r\n\r\nDisclaimer\r\n==========\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. \r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore \r\nshould only be installed if approved by Customer Support. Hotfixes should be replaced as soon as possible by the \r\nsubsequent patch release where the problem is fixed.\r\n\r\nCopyright \ufffd 2015-2020 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.\r\n",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2bd94436e1bc8257d18"
},
"hotfix_name": "CD_8.5.0.6753",
"modified_date": {
"$date": 1508429112907
},
"problem_description": "- Calls to BinaryVariantDAO.findByURL(String urlPath) are not cached.\r\n",
"readme_text": "\ufeffRelease Notes for Hotfix CRQ-6753\r\n=================================\r\n\r\nVersion:\r\nFor version 8.5.0. Layout build number 1022\r\n========\r\nThe hotfix include the following fixes: \r\n - CRQ-6753 Poor performance of GetBinaryMetaByUrl under load\r\n\r\nDescription:\r\n============\r\nWhen implementations fetch BinaryMeta without specifying a publication id, the underlying data layer did not cache the results from that call\r\nto the Broker database. Under heavy load, this can result in the queries becoming very slow.\r\n\r\nThis hotfix implements caching for this call by using the Tridion Object Cache in order to improve performance. To work, you must have\r\nthe Tridion Object Cache enabled and ensure that the typeMapping \"BinaryVariant\" has it's cache enabled.\r\n\r\n\r\nInstallation:\r\n=============\r\nThis hotfix provides updated roles for the Content Service, Session Service as well as the In Process API role.\r\n\r\nInstructions\r\n-------------------------\r\n\r\nIn-process API:\r\n--------------\r\n1. Stop your web application\r\n2. Replace existing Java API libraries with latest ones\r\n3. Restart web application\r\n\r\nMicroservices:\r\n-------------\r\n\r\nThe instructions below are common to all types of services.\r\nYou should apply the same instructions to each of these services: api, content, session.\r\n\r\n1. Stop the service you are going to update\r\n2. Backup (or move) a folder where your standalone Content Service is located\r\n3. Uninstall the SDL Web Deployer Service by opening a Powershell window in the \\bin of your service and run .\\uninstallService.ps1\r\n4. Navigate to the release\\deployer folder of this distribution\r\n5. Copy \\standalone folder to the location where your original service was located\r\n6. Rename copied \\standalone folder to the name of your original service's folder\r\n7. Copy all files from \\config folder of your backup (see step #2) to \\config folder of a new service\r\n8. Copy custom jars (if you have any) from backup's \\services\\folder to a same location of a new service\r\n9. Install service by opening a Powershell window in in the location \\bin of new service and run .\\installService.ps1\r\n\r\n\r\nDistributed roles:\r\n==================\r\napi\t\tContent Delivery API role (in-process)\r\ncontent\t\tContent Service role\r\nsession\t\tSession-enabled Content Service role\r\n\r\nFixed problems:\r\n===============\r\n - CRQ-6753 Calls to the findByUrl(String urlPath) to fetch BinaryMeta should be cached to prevent database overload.\r\n\r\n\r\nProblem Description\r\n-------------------\r\n- Calls to BinaryVariantDAO.findByURL(String urlPath) are not cached.\r\n\r\nHotfix Description\r\n-------------------\r\n- Added caching capability to the BinaryVariantDAO.findByURL(String urlPath) call.\r\n\r\n\r\nDisclaimer:\r\n===========\r\n\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/configuration and therefore should only be installed\r\nif approved by Customer Support. Hotfixes should be replaced as soon as possible by the subsequent patch release where the problem is fixed.\r\n\r\nCopyright \u00a9 2016-2017 SDL Group. All Rights Reserved.\r\n\r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.\r\n",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2bd94436e1bc8257d1b"
},
"hotfix_name": "CD_8.5.0.7949",
"modified_date": {
"$date": 1512032101849
},
"problem_description": "- Application can unintentionally query items from wrong namespace. And during joining application do not use proper indexes as namespace column is a part of PK \r\n",
"readme_text": "Release Notes for Hotfix CRQ-7949\r\n=================================\r\n\r\nVersion:\r\n========\r\nThis is hotfix and is intended only for SDL Web 8.5.0\r\n\r\nDescription:\r\n============\r\nThe hotfix include the following fixes: \r\n - CRQ-7949 Broker API queries (Criteria) are not properly constructed\r\n\r\n\r\n Installation:\r\n=============\r\nThis cumulative hotfix provides updated services: Api role, Content Service, Preview, Session, UGC community-service and UGC moderation-service. The Layout build number 1031.\r\n\r\nFor Legacy Api Role(in-process)\r\n---------------------------\r\n1. Stop your legacy(in-process) web application\r\n2. Backup it to safe location\r\n3. Delete jars/DLLs present in your web-app\r\n4. Copy new jars/DLLs from api\\in-process folder of this HF to your web-app\r\n5. Restore any custom jars or DLLs from your backup\r\n6. Start web-application\r\n\r\n\r\nAll Services\r\n-----------------------\r\n1. Stop the Service you are going to upgrade\r\n2. Backup (or move) a folder where your standalone Service is located\r\n3. Uninstall the Service by opening a Powershell window in the \\bin of your service and running .\\uninstallService.ps1\r\n4. Navigate to the release\\\\service folder of this distribution\r\n5. Copy \\standalone folder to the location where your original service was located\r\n6. Rename copied \\standalone folder to the name of your original service's folder\r\n7. Copy all files from \\config folder of your backup (see step #2) to \\config folder of a new service.\r\n8. Copy custom jars (if you have any) from backup's \\services\\folder to a same location of a new service\r\n9. Install service by opening a Powershell window in in the location \\bin of new service and run .\\installService.ps1\r\n\r\n\r\nDistributed roles:\r\n==================\r\napi/in-process Legacy Api Role\r\ncontent Content Service role\r\npreview Preview service role\r\nsession Session service role\r\nugc/community-service UGC Community Service role\r\nugc/moderation-service UGC Moderation Service role \r\n\r\n\r\nFixed problems:\r\n===============\r\n - CRQ-7949 Broker API queries (Criteria) are not properly constructed\r\n\r\nProblem Description\r\n-------------------\r\n- Application can unintentionally query items from wrong namespace. And during joining application do not use proper indexes as namespace column is a part of PK \r\n\r\nHotfix Description\r\n-------------------\r\n- Added namespace id to the query generator and all query strategies\r\n\r\n\r\nDisclaimer:\r\n===========\r\n\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed\r\nif approved by Customer Support. Hotfixes should be replaced as soon as possible by the subsequent patch release where the problem is fixed.\r\n\r\nCopyright 2015-2017 SDL Group. All Rights Reserved.\r\n\r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.\r\n",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2ad94436e1bc8257ac4"
},
"hotfix_name": "ECL_7.0.0.86444",
"modified_date": {
"$date": 1382447026343
},
"problem_description": "Performance issues on the ECL Media Manager Connector.\r\n",
"readme_text": "Release Notes for Hotfix 86444\r\n\r\nVersion:\r\nThis hotfix is intended only for Tridion External Content Library.\r\n\r\nProblem description:\r\nPerformance issues on the ECL Media Manager Connector.\r\n\r\nHotfix description:\r\nPerformance optimized\r\n\r\nInstallation:\r\n 1. Stop all Tridion Content Manager Service Host and IIS Service.\r\n 2. Move the file Tridion.ExternalContentLibrary.DomainModel.dll located in the %WINDIR%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.ExternalContentLibrary.DomainModel\\v4.0_7.0.0.114__ddfc895746e5ee6b folder\r\n 3. Copy the Tridion.ExternalContentLibrary.DomainModel.dll file from this hotfix to the %WINDIR%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.ExternalContentLibrary.DomainModel\\v4.0_7.0.0.114__ddfc895746e5ee6b folder\r\n 4. Move the file Tridion.ExternalContentLibrary.Service.dll located in the %TRIDION_HOME%\\bin folder\r\n 5. Copy the Tridion.ExternalContentLibrary.Service.dll file from this hotfix to the %TRIDION_HOME%\\bin folder\r\n 6. Move the file Tridion.ExternalContentLibrary.UI.Model.dll located in the %TRIDION_HOME%\\web\\WebUI\\WebRoot\\bin folder\r\n 7. Copy the Tridion.ExternalContentLibrary.UI.Model.dll file from this hotfix to the %TRIDION_HOME%\\web\\WebUI\\WebRoot\\bin folder\r\n 8. Move the file Tridion.ExternalContentLibrary.Service.Client.dll located in the %TRIDION_HOME%\\web\\WebUI\\WebRoot\\bin folder\r\n 9. Copy the Tridion.ExternalContentLibrary.Service.Client.dll file from this hotfix to the %TRIDION_HOME%\\web\\WebUI\\WebRoot\\bin folder\r\n 10. Restart the IIS Service and Tridion Content Manager Service Host.\r\n\r\nDistributed files:\r\n Tridion.ExternalContentLibrary.DomainModel.dll (File Version 7.0.0.133)\r\n Tridion.ExternalContentLibrary.Service.dll (File Version 7.0.0.133)\r\n Tridion.ExternalContentLibrary.UI.Model.dll (File Version 7.0.0.133)\r\n Tridion.ExternalContentLibrary.Service.Client.dll (File Version 7.0.0.133)\r\n Readme.txt (this file)\r\n\r\nFixes included:\r\n\tN/A\r\n\r\nDependencies:\r\n\tN/A\r\n\r\nDisclaimer:\r\nHotfixes are released at the discretion of SDL based on technical complexity, customer business requirements and schedules.\r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by Customer Support of SDL Web Content Management Solutions Division.\r\nHotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright 2013 SDL PLC. All Rights Reserved. All company product or service names referenced herein are properties of their respective owners.",
"version": "2013"
},
{
"_id": {
"$oid": "635fe2bd94436e1bc8257d23"
},
"hotfix_name": "CD_8.5.0.9845",
"modified_date": {
"$date": 1525714833004
},
"problem_description": "- update spring-data-commons in Web 8.5 to version 1.3.11 to address the vulnerability CVE-2018-1273\r\n",
"readme_text": "\ufeffRelease Notes for Hotfix CRQ-9845\r\n=================================\r\n\r\nVersion:\r\n========\r\nThis hotfix is intended only for SDL Web 8.5.0 customers.\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n - CRQ-9845 Update Spring Data Commons for vulnerability (CVE-2018-1273)\r\n\r\nInstallation:\r\n=============\r\nThis cumulative hotfix provides updated standalone service roles.\r\n\r\nAll Services\r\n------------\r\n1. Stop the Service you are going to update\r\n2. Backup (or move) the folder where your standalone Service is located\r\n3. Uninstall the Service by opening a Powershell window in the \\bin folder of your service and running\r\n .\\uninstallService.ps1\r\n4. Navigate to the release\\\\service folder of this distribution\r\n5. Copy the \\standalone folder to the location where your original service was located\r\n6. Rename copied \\standalone folder to the name of your original service's folder\r\n7. Copy all files from \\config folder of your backup (see step #2) to \\config folder of a new service\r\n8. Copy custom jars (if you have any) from backup's \\services\\ folders to the same location in new service\r\n9. Install service by opening a Powershell window in in the \\bin folder of the new service and run .\\installService.ps1\r\n\r\n\r\nDistributed roles:\r\n==================\r\napi API role\r\ncaching Cache Channel Service role\r\ncid Contextual Image Delivery Service role\r\ncontent Content Service role\r\ncontext Context Service role\r\ndeployer Deployer Service roles\r\ndiscovery Discovery Service role\r\nmonitoring Monitoring Service role\r\npreview Preview Service role\r\nsession Session-enabled Content Service role\r\nugc UGC Service roles\r\ntemplate Template Service for DXA 2.0\r\n\r\nDependencies:\r\n=============\r\nN/A\r\n\r\nFixed problems:\r\n===============\r\n - CRQ-9845 Update Spring Data Commons for vulnerability (CVE-2018-1273)\r\n\r\nProblem Description\r\n-------------------\r\n - update spring-data-commons in Web 8.5 to version 1.3.11 to address the vulnerability CVE-2018-1273\r\n\r\nHotfix Description\r\n-------------------\r\nThis fix updates spring-data-commons version to 1.3.11\r\n\r\nDisclaimer:\r\n===========\r\n\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules.\r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore\r\nshould only be installed if approved by Customer Support. Hotfixes should be replaced as soon as possible by the\r\nsubsequent patch release where the problem is fixed.\r\n\r\nCopyright \ufffd 2015-2017 SDL Group. All Rights Reserved.\r\n\r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.\r\n",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2bd94436e1bc8257d09"
},
"hotfix_name": "CD_8.5.0.4115",
"modified_date": {
"$date": 1493307792054
},
"problem_description": "Existing bundled Tomcat version has known vulnerabilties (see\r\nhttps://www.us-cert.gov/ncas/current-activity/2017/04/12/Apache-Software-Foundation-Releases-Security-Updates)\r\n",
"readme_text": "Release Notes for Hotfix CRQ-4115\r\n=================================\r\n\r\nVersion:\r\n========\r\nThis cumulative hotfix is intended only for SDL Web 8.5.0 customers.\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n - CRQ-4115 Update Microservices Tomcat version - Address security vulnerabilties recently announced\r\n\r\nInstallation:\r\n=============\r\nThis cumulative hotfix provides updated standalone service roles.\r\n\r\nAll Services\r\n------------\r\n1. Stop the Service you are going to update\r\n2. Backup (or move) the folder where your standalone Service is located\r\n3. Uninstall the Service by opening a Powershell window in the \\bin folder of your service and running\r\n .\\uninstallService.ps1\r\n4. Navigate to the release\\\\service folder of this distribution\r\n5. Copy the \\standalone folder to the location where your original service was located\r\n6. Rename copied \\standalone folder to the name of your original service's folder\r\n7. Copy all files from \\config folder of your backup (see step #2) to \\config folder of a new service\r\n8. Copy custom jars (if you have any) from backup's \\services\\ folders to the same location in new service\r\n9. Install service by opening a Powershell window in in the \\bin folder of the new service and run .\\installService.ps1 \r\n\r\n\r\nDistributed roles:\r\n==================\r\ncid\t\t\tContextual Image Delivery Service role\r\ncontent\t\tContent Service role\r\ncontext\t\tContext Service role\r\ndeployer\tDeployer Service roles\r\ndiscovery\tDiscovery Service role\r\nmonitoring\tMonitoring Service role\r\npreview\t\tPreview Service role\r\nsession\t\tSession-enabled Content Service role\r\nugc\t\t\tUGC Service roles\r\n\r\nDependencies:\r\n=============\r\nN/A\r\n\r\nFixed problems:\r\n===============\r\n\t- CRQ-4115 Update Microservices Tomcat version - Address security vulnerabilties recently announced\r\n\r\nProblem Description\r\n-------------------\r\nExisting bundled Tomcat version has known vulnerabilties (see\r\nhttps://www.us-cert.gov/ncas/current-activity/2017/04/12/Apache-Software-Foundation-Releases-Security-Updates)\r\n\r\nHotfix Description\r\n-------------------\r\nThis fix updates all services to use the latest Tomcat 8.5.13.\r\n\r\nDisclaimer:\r\n===========\r\n\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. \r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore \r\nshould only be installed if approved by Customer Support. Hotfixes should be replaced as soon as possible by the \r\nsubsequent patch release where the problem is fixed.\r\n\r\nCopyright 2015-2017 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.\r\n",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2bb94436e1bc8257ce7"
},
"hotfix_name": "CD_8.5.0.14838",
"modified_date": {
"$date": 1560526639232
},
"problem_description": "This is a hotfix for:\r\n- CRQ-14128 ConcurrentModificationException occurs in ADF Client\r\n- CRQ-14838 Cleanup of Broker database temporary tables\r\n",
"readme_text": "Release Notes for Hotfix CRQ-14128, CRQ-14838\r\n==================================\r\n\r\nVersion:\r\n--------\r\nThis is hotfix and is intended for SDL Web 8.5.0\r\nThe hotfix includes the following fixes: \r\n- CRQ-14128 ConcurrentModificationException occurs in ADF Client\r\n- CRQ-14838 Cleanup of Broker database temporary tables\r\n\r\n\r\nDescription:\r\n------------\r\nThis is a hotfix for:\r\n- CRQ-14128 ConcurrentModificationException occurs in ADF Client\r\n- CRQ-14838 Cleanup of Broker database temporary tables\r\n\r\n\r\nInstallation:\r\n-------------\r\nThis hotfix provides updated roles for the API and services.\r\n\r\n\r\nInstructions:\r\n-------------\r\n\r\nAPI\r\n---\r\n1. Stop your web application\r\n2. Backup it to safe location\r\n3. Delete jars/DLLs present in your web-app\r\n4. Copy new jars/DLLs from api folder of this hotfix to your web-app\r\n5. Restore any custom jars or DLLs from your backup\r\n6. Restart web-application\r\n\r\nServices\r\n--------\r\n1. Stop relevant Service\r\n2. Backup (or move) a folder where your standalone Service is located\r\n3. Uninstall the relevant Service by opening a Powershell window in the \\bin of your service and run .\\uninstallService.ps1\r\n4. Navigate to the release\\ folder of this distribution\r\n5. Copy \\standalone folder to the location where your original service was located\r\n6. Rename copied \\standalone folder to the name of your original service's folder\r\n7. Copy all files from \\config folder of your backup (see step #2) to \\config folder of a new service\r\n8. Copy custom jars (if you have any) from backup's \\services\\folder to a same location of a new service\r\n9. Install service by opening a Powershell window in in the location \\bin of new service and run .\\installService.ps1\r\n\r\n \r\nDistributed roles:\r\n------------------\r\n- api\t\tAPI\r\n- cid\t\tContextul Image Delivery\r\n- content\tContent\r\n- context\tContext\r\n- deployer\tDeployer\r\n- discovery\tDiscovery\r\n- preview\tPreview\r\n- session\tSession-enabled Content\r\n- template\tTemplate\r\n- ugc\t\tUser Generated Content\r\n\r\n\r\nFixed problems:\r\n---------------\r\n- CRQ-14128 ConcurrentModificationException occurs in ADF Client.\r\n- CRQ-14838 Cleanup of Broker database temporary tables. In scope of this scheduled task was added which should be enabled by modifying 'application.properties' file.\r\n\r\n\r\nHotfix Description\r\n-------------------\r\n- Resolved concurrency issue within ADF Client library.\r\n- Added spring framework task execution to perform cleanup on setup schedule. To enable this task execution for periodical cleanup you should visit 'application.properties' file and setup 'state.store.cleanup.cron' property value.\r\n\r\n\r\nDisclaimer:\r\n-----------\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and \r\nschedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration \r\nand therefore should only be installed if approved by Customer Support. Hotfixes should be replaced as soon as \r\npossible by the subsequent patch release where the problem is fixed.\r\n\r\nCopyright 2016-2019 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL \r\nGroup.\r\n",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2be94436e1bc8257d28"
},
"hotfix_name": "CD_8.5.0_18569",
"modified_date": {
"$date": 1585913797318
},
"problem_description": "",
"readme_text": "Release Notes for Hotfix CRQ-18569\n=================================\n\nVersion:\n========\nThis cumulative hotfix is intended only for SDL Tridion Sites 8.5 customers.\n\nDescription:\n============\nThis is a hotfix for:\n - CRQ-18569 Cache invalidation doesn't seem to work or is delayed\n\nInstallation:\n=============\nThis cumulative hotfix provides updated following roles: API, Caching, CID, Content, Context, Deployer, Discovery, Monitoring, Preview, Session and UGC services.\n\nAll Services\n------------\n1. Stop the Service you are going to update\n2. Backup (or move) the folder where your standalone Service is located\n3. Uninstall the Service by opening a Powershell window in the \\bin folder of your service and running\n .\\uninstallService.ps1\n4. Navigate to the release\\\\service folder of this distribution\n5. Copy the \\standalone folder to the location where your original service was located\n6. Rename copied \\standalone folder to the name of your original service's folder\n7. Copy all files from \\config folder of your backup (see step #2) to \\config folder of a new service\n8. Copy custom jars (if you have any) from backup's \\services\\ folders to the same location in new service\n9. Install service by opening a Powershell window in in the \\bin folder of the new service and run .\\installService.ps1 \n\n\nDistributed roles:\n==================\napi API role\ncaching Caching role\ncid\t\t\tContextual Image Delivery Service role\ncontent\t\tContent Service role\ncontext\t\tContext Service role\ndeployer\tDeployer Service roles\ndiscovery\tDiscovery Service role\nmonitoring\tMonitoring Service role\npreview\t\tPreview Service role\nsession\t\tSession-enabled Content Service role\nugc\t\t\tUGC Service roles\n\nDependencies:\n=============\nN/A\n\nFixed problems:\n===============\n\t- CRQ-18569 Cache invalidation doesn't seem to work or is delayed\n\nProblem Description\n-------------------\nCache invalidation doesn't seem to work or is delayed - multithreading issue deteriorated calculation of cache size and prevented correct cleanup of it.\n\nHotfix Description\n-------------------\nThis fix updates all services to use the fixed Caching binaries.\n\nDisclaimer:\n===========\n\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. \nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore \nshould only be installed if approved by Customer Support. Hotfixes should be replaced as soon as possible by the \nsubsequent patch release where the problem is fixed.\n\nCopyright \u00a9 2015-2020 SDL Group. All Rights Reserved.\n \nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.\n",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2ab94436e1bc8257a31"
},
"hotfix_name": "CM_2011.1.1.78606",
"modified_date": {
"$date": 1333550120002
},
"problem_description": "Switching between details and thumbnail view of the list can cause the list to disappear. This is visible sometimes in the item selection dialog.\r\n",
"readme_text": "Release Notes for Hotfix TT 78606\r\n\r\nVersion: \r\nThis hotfix is intended for SDL Tridion 2011 SP1 HR1.\r\n\r\nProblem description:\r\nSwitching between details and thumbnail view of the list can cause the list to disappear. This is visible sometimes in the item selection dialog.\r\n\r\nInstallation:\r\n1. Copy List.js to %TRIDION%\\WebUI\\Core\\Controls\\List\\\r\n\r\nDistributed files:\r\n List.js\r\n Readme.txt (this file)\r\n \r\n\r\nFixes included:\r\nn.a.\r\n\r\nDependencies:\r\nn.a.",
"version": "2011 SP1 HR#1"
},
{
"_id": {
"$oid": "635fe2b894436e1bc8257c5a"
},
"hotfix_name": "CM_9.5.0.29412",
"modified_date": {
"$date": 1655719339052
},
"problem_description": "Structure groups load slowly for non-admin users.\r\n",
"readme_text": "Release Notes for Hotfix CRQ-29412\r\n\r\nVersion: \r\n This hotfix is intended for SDL Web 9.5 on MS SQL.\r\n\r\nProblem description:\r\n\tStructure groups load slowly for non-admin users.\r\n \r\nHotfix description:\r\n\tSQL Server doesn't maintain the statistics for table variables. Use instead the temp tables within the EDA_ORG_ITEMS_GETINHERITANCEROOT stored procedure.\r\n \r\nInstallation:\r\n 1. Database actions:\r\n a. Using Query Analyzer, osql, sqlcmd or SQL Server Management Studio, log in to the SDL Tridion database using 'sa'.\r\n b. Execute the SQL file EDA_ORG_ITEMS.sql\r\n\r\nDistributed files:\r\n EDA_ORG_ITEMS.sql\r\n Readme.txt (this file)\r\n\r\nFixes included:\r\n NA\r\n \r\nDependencies:\r\n NA\r\n\r\nDisclaimer:\r\n Hotfixes (as defined under the relevant RWS product release policy) are released at RWSs discretion based on technical complexity, customer business requirements and schedules. \r\n Hotfixes are made and tested only for the described problem on a particular environment/configuration in accordance with the Software Documentation and therefore should only be installed if approved by RWS Technical Support. \r\n Hotfixes should be replaced as soon as possible by the subsequent cumulative update where the problem is fixed.\r\n \r\nCopyright 2022 All Rights Reserved by the RWS Group for and on behalf of its affiliates and subsidiaries. All company product or service names referenced herein are properties of their respective owners.\r\n",
"version": "Sites 9.5"
},
{
"_id": {
"$oid": "635fe2aa94436e1bc8257a06"
},
"hotfix_name": "CD_2011.1.1.80398",
"modified_date": {
"$date": 1336465897105
},
"problem_description": "2 Phase publish fails when difference between publish and deploy time is too big. If the Timeout setting (by default 15 minutes) in the cd_transport_conf.xml is set to be lower than the time \r\nfor the 2nd phase, the publish job will fail after the timeout setting.\r\nIssue in the calculation of the available window size in case of 2 phase committ. For each Scheduled publish with two phases a slot from the window size was locked but never released. After a \r\nnumber of such publish actions, the transport would just hang in throttled state.\r\nIssue for FTP publishing when the time between phase one and phase two of a scheduled publishing is too small. \r\n",
"readme_text": "Release Notes for Hotfix TT80398\r\n================================\r\n\r\nVersion:\r\n========\r\nThis hotfix is intended only for SDL Tridion 2011 SP1 HR1\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n- TT80398 2 Phase publish fails when difference between publish and deploy time is too big\r\n\r\nInstallation:\r\n=============\r\n1. Ensure a correct Content Magement installation with the Transport Service installed\r\n2. Stop the Tridion Content Delivery Transport Service\r\n3. Go to %TRIDION_HOME%\\lib\r\n4. Replace cd_transport.jar with the provided hotfix versions\r\n5. Start the Tridion Content Delivery Transport Service\r\n\r\n\r\nDistributed files:\r\n==================\r\ncd_transport.jar (version 6.1.0.1045)\r\n\r\nDependencies:\r\n=============\r\nSDL Tridion 2011 SP1 HR1\r\n\r\nFixed problems:\r\n===============\r\nTT80398\r\nProblem Description\r\n-------------------\r\n2 Phase publish fails when difference between publish and deploy time is too big. If the Timeout setting (by default 15 minutes) in the cd_transport_conf.xml is set to be lower than the time \r\nfor the 2nd phase, the publish job will fail after the timeout setting.\r\nIssue in the calculation of the available window size in case of 2 phase committ. For each Scheduled publish with two phases a slot from the window size was locked but never released. After a \r\nnumber of such publish actions, the transport would just hang in throttled state.\r\nIssue for FTP publishing when the time between phase one and phase two of a scheduled publishing is too small. \r\n\r\n\r\nHotfix Description\r\n-------------------\r\nWhen we have a 2 phase committ this is what happens: before the first phase (sending of content package) transport locks a slot of the window size, after the first phase is done we release the\r\nslot and we stop polling for information (because the package is just parked on deployer side in WAIT state) until the second phase (sending of commit package) occurs, then before the second\r\nphase occurs we lock again a window size slot so we can perform the actual transport and after deployment finished (one way or another) we finally release the window size slot.\r\nMade sure that, in case the time between the 2 phases of a scheduled publishing is too small, we properly handle second phase. Note that this solves (different) problems for both HTTP(S) and FTP deployment.\r\n\r\n\r\nDisclaimer:\r\n===========\r\nHotfixes are released at the discretion of Tridion based on technical\r\ncomplexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/\r\nconfiguration and therefore should only be installed if approved by Tridion\r\nCustomer Support. Hotfixes should be replaced as soon as possible by the\r\nsubsequent service pack where the problem is fixed.\r\n\r\n(c) 2012 SDL Tridion B.V.\r\n",
"version": "2011 SP1 HR#1"
},
{
"_id": {
"$oid": "635fe2aa94436e1bc8257a1c"
},
"hotfix_name": "CD_2011.1.1.84807",
"modified_date": {
"$date": 1363618103696
},
"problem_description": "When storing BinaryMeta there are some queries which lock the some tables for a longer time that needed.\r\nWhen updating a BinaryMeta, if there is already a ComponentMeta published and related to it, the ComponentMeta will not have its LastPublishedDate updated.\r\nDuring the mass deployment of big packages containing same binaries, the default number of deployment retries (10) might not be enough.\r\nDuring the deployment process, the deployer serializes the state to be able to pick-up from where it's left in case of failure. Because the loggers associated to each worker\r\nwere also serialized, we would get a ConcurrentModificationException under heavy load because different loggers (associated to workers in different transactions) were cached by\r\nLogBack while the current transaction state was serialized to disk.\r\nUnder heavy load, the deployer would pick-up twice the same transport package causing an error on the second attempt.\r\n'org.hibernate.TransientObjectException' would occur in case of changing related keywords of an item meta in the same transaction.\r\nThere was an issue when publishing BinaryMeta while there's an existing ComponentMeta with the same itemId in the published storage.\r\nWhen deploying unmanaged binaries, content is mixed-up between binaries in case order in binaries.xml and instructions.xml is different.\r\nThere are some limitations for the CustomMetaValue for Oracle schemas and filesystem due to some checks in the Deployer. \r\nPublishing process stuck in Resolving state\r\n",
"readme_text": "Release Notes for Hotfix TT84807\r\n================================\r\n\r\nVersion:\r\n========\r\nThis cumulative hotfix and is intended only for Tridion 2011 SP1 HR1\r\nThe hotfix includes the following fixes:\r\n- TT84807 A mass publish leads to java.sql.BatchUpdateException: ORA-00060: deadlock detected while waiting for resource\r\n- TT84804 LAST_PUBLISHED_DATE not being updated when binary (image) is published\r\n- TT84736 Configuration option for the number of retries of the deployer\r\n- TT84446 Mass publishing of items to a single deployer leads to java.util.ConcurrentModificationException: null\r\n- TT83475 Deployment fails for some items with error message: Unable to unzip, ***.zip (The system cannot find the file specified), \r\n- TT83467 'Unable to remove data entity, org.hibernate.TransientObjectException' occurs randomly when deploying content to the database\r\n- TT82946 Publish to the deployer fail with the exception \"org.hibernate.exception.ConstraintViolationException: could not insert\"\r\n- TT81270 When deploying unmanaged binaries, content is mixed-up between binaries in case order in binaries.xml and instructions.xml is different,\r\n- TT81125 Deployment fails when publishing a page that contains metadata that exceeds 3400 bytes, \r\n- TT80995 Publishing process stuck in Resolving state\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n- TT84807 A mass publish leads to java.sql.BatchUpdateException: ORA-00060: deadlock detected while waiting for resource\r\n\r\nInstallation:\r\n=============\r\nDeployer environment:\r\n---------------------\r\nJava Environment with HttpUpload:\r\n1. Ensure that you have a correct installed Content Delivery installation inside your web application\r\n2. Stop your web application server or web application containing the deployer httpupload\r\n3. Copy the distributed jar files inside your web application WEB-INF\\lib directory\r\n4. Start your web application server or web application\r\n\r\n.NET Environment with HttpUpload:\r\n1. Ensure the application pool and or IIS Server has been stopped\r\n2. Copy the distributed jar files inside the IIS application directory bin\\lib directory. In case of central tridion installation please copy the distributed jar files\r\ninto the installation directory \\lib folder.\r\n3. Start the application pool and or IIS Server\r\n\r\nStandalone deployer:\r\n1. Ensure the deployer service has been stopped\r\n2. Copy the distributed jar files inside your 'Tridion installation folder'\\lib directory\r\n3. Start the deployer service\r\n\r\nDistributed files:\r\n==================\r\ncd_datalayer.jar (6.1.0.1080)\r\ncd_deployer.jar (6.1.0.1080)\r\ncd_model.jar (6.1.0.1080)\r\ncd_core.jar (6.1.0.1080)\r\n\r\nDependencies:\r\n=============\r\nSDL Tridion 2011 SP1 HR1\r\n\r\n\r\nFixed problems:\r\n===============\r\nTT84807\r\nProblem Description\r\n-------------------\r\nWhen storing BinaryMeta there are some queries which lock the some tables for a longer time that needed.\r\n\r\nHotfix Description\r\n-------------------\r\nMaking some of the queries done when storing BinaryMeta more efficient, to release database locks faster.\r\n\r\nTT84804\r\nProblem Description\r\n-------------------\r\nWhen updating a BinaryMeta, if there is already a ComponentMeta published and related to it, the ComponentMeta will not have its LastPublishedDate updated.\r\n\r\nHotfix Description\r\n-------------------\r\nUpdating LastPublishedDate for existing related ComponentMeta when updating BinaryMeta. Forcing consistency check related to items.\r\n\r\n\r\nTT84736\r\nProblem Description\r\n-------------------\r\nDuring the mass deployment of big packages containing same binaries, the default number of deployment retries (10) might not be enough.\r\n\r\nHotfix Description\r\n-------------------\r\nAllowing customer to define the number of retries for each Queue/Location in a MaximumRetries attribute. Example:\r\n\r\n\r\n\r\nTT84446\r\nProblem Description\r\n-------------------\r\nDuring the deployment process, the deployer serializes the state to be able to pick-up from where it's left in case of failure. Because the loggers associated to each worker\r\nwere also serialized, we would get a ConcurrentModificationException under heavy load because different loggers (associated to workers in different transactions) were cached by\r\nLogBack while the current transaction state was serialized to disk.\r\n\r\nHotfix Description\r\n-------------------\r\nMade sure that the loggers are excluded from the serializing process and optimized the declaration of all loggers involved in the transaction state.\r\n\r\n\r\nTT83475\r\nProblem Description\r\n-------------------\r\nUnder heavy load, the deployer would pick-up twice the same transport package causing an error on the second attempt.\r\n\r\nHotfix Description\r\n-------------------\r\nMade sure the same package is not picked-up twice. \r\n\r\n\r\nTT83467\r\nProblem Description\r\n-------------------\r\n'org.hibernate.TransientObjectException' would occur in case of changing related keywords of an item meta in the same transaction.\r\n\r\nHotfix Description\r\n-------------------\r\nMaking sure that the link from RelatedKeyword back to ItemMeta is nullified before saving the item meta.\r\n\r\n\r\nTT82946\r\nProblem Description\r\n-------------------\r\nThere was an issue when publishing BinaryMeta while there's an existing ComponentMeta with the same itemId in the published storage.\r\n\r\nHotfix Description\r\n-------------------\r\nRemoving the existing ComponentMeta before re-adding it with the BinaryMeta.\r\n\r\n\r\nTT81270\r\nProblem Description\r\n-------------------\r\nWhen deploying unmanaged binaries, content is mixed-up between binaries in case order in binaries.xml and instructions.xml is different.\r\n\r\nHotfix Description\r\n-------------------\r\nLook up for unmanaged binaries by the path as all of them have the same id. \r\n\r\n\r\n\r\nTT81125\r\nProblem Description\r\n-------------------\r\nThere are some limitations for the CustomMetaValue for Oracle schemas and filesystem due to some checks in the Deployer. \r\n\r\nHotfix Description\r\n-------------------\r\nThe early checks in the Deployer are removed.\r\n\r\n\r\nTT80995 \r\nProblem Description\r\n-------------------\r\nPublishing process stuck in Resolving state\r\n\r\nHotfix Description\r\n-------------------\r\nRemoving DynamicLinks might cause database locks. To prevent that we flush the session prior and after removing DynamicLinks.\r\n\r\n\r\n\r\nDisclaimer:\r\n===========\r\nHotfixes are released at the discretion of Tridion based on technical\r\ncomplexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/\r\nconfiguration and therefore should only be installed if approved by Tridion\r\nCustomer Support. Hotfixes should be replaced as soon as possible by the\r\nsubsequent service pack where the problem is fixed.\r\n\r\n(c) 2013 SDL Tridion B.V.\r\n",
"version": "2011 SP1 HR#1"
},
{
"_id": {
"$oid": "635fe2bd94436e1bc8257d1f"
},
"hotfix_name": "CD_8.5.0.8740",
"modified_date": {
"$date": 1517242336290
},
"problem_description": "Jackson library version should be updated.\r\n",
"readme_text": "Release Notes for Hotfix CRQ-8740\r\n=================================\r\n\r\nVersion:\r\n========\r\nThis cumulative hotfix is intended only for SDL Web 8.5.0 customers.\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n - CRQ-8740 Jackson vulnerabilities - need update to 2.9.4\r\n\r\nInstallation:\r\n=============\r\nThis cumulative hotfix provides updated standalone service roles.\r\n\r\nAll Services\r\n------------\r\n1. Stop the Service you are going to update\r\n2. Backup (or move) the folder where your standalone Service is located\r\n3. Uninstall the Service by opening a Powershell window in the \\bin folder of your service and running\r\n .\\uninstallService.ps1\r\n4. Navigate to the release\\\\service folder of this distribution\r\n5. Copy the \\standalone folder to the location where your original service was located\r\n6. Rename copied \\standalone folder to the name of your original service's folder\r\n7. Copy all files from \\config folder of your backup (see step #2) to \\config folder of a new service\r\n8. Copy custom jars (if you have any) from backup's \\services\\ folders to the same location in new service\r\n9. Install service by opening a Powershell window in in the \\bin folder of the new service and run .\\installService.ps1 \r\n\r\n\r\nDistributed roles:\r\n==================\r\napi\t\tAPI role\r\ncid\t\tContextual Image Delivery Service role\r\ncontent\t\tContent Service role\r\ncontext\t\tContext Service role\r\ndeployer\tDeployer Service roles\r\ndiscovery\tDiscovery Service role\r\nmonitoring\tMonitoring Service role\r\npreview\t\tPreview Service role\r\nsession\t\tSession-enabled Content Service role\r\ntemplate\tTemplate role\r\nugc\t\tUGC Service roles\r\n\r\nDependencies:\r\n=============\r\nN/A\r\n\r\nFixed problems:\r\n===============\r\n\t- CRQ-8740 Jackson vulnerabilities - need update to 2.9.4\r\n\r\nProblem Description\r\n-------------------\r\nJackson library version should be updated.\r\n\r\nHotfix Description\r\n-------------------\r\nThis fix updates all services to use Jackson 2.9.4 release.\r\n\r\nDisclaimer:\r\n===========\r\n\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. \r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore \r\nshould only be installed if approved by Customer Support. Hotfixes should be replaced as soon as possible by the \r\nsubsequent patch release where the problem is fixed.\r\n\r\nCopyright 2015-2017 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.\r\n",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2b994436e1bc8257c8e"
},
"hotfix_name": "CD_8.1.1.2810",
"modified_date": {
"$date": 1491815893392
},
"problem_description": "- GetTaxonomyKeywords returns instance of Keyword with valid number of KeywordChildren but all of them have empty KeywordMeta.\r\n",
"readme_text": "Release Notes for Hotfix CRQ-2810\r\n=================================\r\n\r\nVersion:\r\n========\r\nThis is cumulative hotfix and is intended only for SDL Web 8\r\n\r\nDescription:\r\n============\r\nThe hotfix include the following fixes: \r\n - CRQ-2810 TaxonomyFactory.GetTaxonomyKeywords - broken backward compatible\r\n \r\nInstallation:\r\n=============\r\nThis cumulative hotfix provides updated content, preview and session services and .NET api artifacts.\r\n\r\nCD APIs\r\n-------\r\n\tREST :\r\n\t\t[.NET] - update [.NET] artifacts from release\\api\\rest\\dotNet\\bin folder.\r\n\t\t[Java] - update Java artifacts from release\\api\\rest\\java\\lib folder.\r\n \r\nAll Services\r\n-------------\r\n1. Stop the Service you are going to upgrade\r\n2. Backup (or move) a folder where your standalone Service is located\r\n3. Uninstall the Service by opening a Powershell window in the \\bin of your service and running .\\uninstallService.ps1\r\n4. Navigate to the release\\\\service folder of this distribution\r\n5. Copy \\standalone folder to the location where your original service was located\r\n6. Rename copied \\standalone folder to the name of your original service's folder\r\n7. Copy all files from \\config folder of your backup (see step #2) to \\config folder of a new service.\r\n8. Copy custom jars (if you have any) from backup's \\services\\ folder to a same location of a new service\r\n9. Install service by opening a Powershell window in in the location \\bin of new service and run .\\installService.ps1 \r\n\t\r\n\r\nDistributed roles:\r\n==================\r\napi \t\tContent Delivery API rest role\r\ncontent\t\t\t\t\tContent Service role\r\npreview\t\t\t\t\tPreview Service role\r\nsession\t\t\t\t\tSession-enabled content service role \r\n\r\nFixed problems:\r\n===============\r\n - CRQ-2810 TaxonomyFactory.GetTaxonomyKeywords - broken backward compatible\r\n \r\nProblem Description\r\n-------------------\r\n - GetTaxonomyKeywords returns instance of Keyword with valid number of KeywordChildren but all of them have empty KeywordMeta.\r\n\r\nHotfix Description\r\n-------------------\r\n- Modified service to expand Keyword Metadata.\r\n\r\nDisclaimer:\r\n===========\r\n\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by Customer Support. Hotfixes should be replaced as soon as possible by the subsequent patch release where the problem is fixed.\r\n\r\nCopyright 2016-2017 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.",
"version": "Web 8.1.1"
},
{
"_id": {
"$oid": "635fe2b194436e1bc8257ba9"
},
"hotfix_name": "CD_11.0.0_13730",
"modified_date": {
"$date": 1553789755086
},
"problem_description": "- Keyword/category title is not properly handled by application when no keyword/category medata present in publishing package.\r\n",
"readme_text": "Release Notes for Hotfix CRQ-13730\r\n=================================\r\n\r\nVersion:\r\n========\r\nThis is hotfix and is intended only for SDL Sites 9\r\n\r\nDescription:\r\n============\r\nThe hotfix include the following fixes: \r\n - CRQ-13730 GraphQL does not return titles of categories and keywords\r\n\r\n\r\n Installation:\r\n=============\r\nThis cumulative hotfix provides updated services: Content Service, Deployer, Session Enabled Content Service. The Layout build number 1043.\r\n\r\n\r\n\r\nAll Services\r\n-----------------------\r\n1. Stop the Service you are going to upgrade\r\n2. Backup (or move) a folder where your standalone Service is located\r\n3. Uninstall the Service by opening a Powershell window in the \\bin of your service and running .\\uninstallService.ps1\r\n4. Navigate to the release\\\\service folder of this distribution\r\n5. Copy \\standalone folder to the location where your original service was located\r\n6. Rename copied \\standalone folder to the name of your original service's folder\r\n7. Copy all files from \\config folder of your backup (see step #2) to \\config folder of a new service.\r\n8. Copy custom jars (if you have any) from backup's \\services\\folder to a same location of a new service\r\n9. Install service by opening a Powershell window in in the location \\bin of new service and run .\\installService.ps1\r\n\r\n\r\nDistributed roles:\r\n==================\r\n\r\ncontent Content Service role\r\ndeployer Deployer service role\r\nsession\t\t\t Session Enabled Content Service\r\n\r\n\r\nFixed problems:\r\n===============\r\n - CRQ-12682 GraphQL does not return titles of categories and keywords\r\n\r\nProblem Description\r\n-------------------\r\n- Keyword/category title is not properly handled by application when no keyword/category medata present in publishing package.\r\n\r\nHotfix Description\r\n-------------------\r\n- General metadata for keyword/category will be created by default even if no custom metadata supplied during the publishing.\r\n- Title for the keyword/category will not be picked up from the metadata to avoid unnecessary migration overhead.\r\n\r\n\r\nDisclaimer:\r\n===========\r\n\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by Customer Support. Hotfixes should be replaced as soon as possible by the subsequent patch release where the problem is fixed.\r\n\r\nCopyright 2015-2019 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.\r\n",
"version": "Sites 9.0"
},
{
"_id": {
"$oid": "635fe2bc94436e1bc8257cfa"
},
"hotfix_name": "CD_8.5.0.19012",
"modified_date": {
"$date": 1589353690754
},
"problem_description": "",
"readme_text": "Release Notes for Hotfix CRQ-18623\n=================================\n\nVersion:\n========\nThis cumulative hotfix is intended only for SDL Tridion Sites 8.5 customers.\n\nDescription:\n============\nThis is a hotfix for:\n - CRQ-19012 CD_8.5.0_18569 - Content Service - Incorrect date format\n - CRQ-19030 Running broker API call causes DB server CPU to spike and takes 4 minutes to complete\n\nInstallation:\n=============\nThis cumulative hotfix provides updated Session and Content service role.\n\n\nFor the Session / Content\n------------\n1. Stop the Service you are going to update\n2. Backup (or move) the folder where your standalone Service is located\n3. Uninstall the Service by opening a Powershell window in the \\bin folder of your service and running\n .\\uninstallService.ps1\n4. Navigate to the release\\\\service folder of this distribution\n5. Copy the \\standalone folder to the location where your original service was located\n6. Rename copied \\standalone folder to the name of your original service's folder\n7. Copy all files from \\config folder of your backup (see step #2) to \\config folder of a new service\n8. Copy custom jars (if you have any) from backup's \\services\\ folders to the same location in new service\n9. If hotfix - CD_8.5.0.18623 was not applied - please, follow instructings in CD_8.5.0.18623.zip\\README.txt\n\n\n\nDistributed roles:\n==================\nsession Session Service role\ncontent Content Service role\n\n\nDependencies:\n=============\nN/A\n\nFixed problems:\n===============\n- Exception in Content Service - Incorrect date format\n- Low performance of Content Service when filtering by taxonomies\n\nProblem Description\n-------------------\n- Unable to filter by custom meta data(date)\n- Uneficient sql\n\nHotfix Description\n-------------------\n- Fixed date transformation \n- Fixed query builer for using index\n\nDisclaimer:\n===========\n\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. \nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore \nshould only be installed if approved by Customer Support. Hotfixes should be replaced as soon as possible by the \nsubsequent patch release where the problem is fixed.\n\nCopyright 2015-2020 SDL Group. All Rights Reserved.\n \nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.\n",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2bb94436e1bc8257cdb"
},
"hotfix_name": "CD_8.5.0.11996",
"modified_date": {
"$date": 1540910694783
},
"problem_description": "This is a hotfix for:\r\n- CRQ-11996 Discovery service with a hostname including svc\r\n",
"readme_text": "Release Notes for Hotfix CRQ-11996\r\n==================================\r\n\r\nVersion:\r\n--------\r\nThis is hotfix and is intended for SDL Web 8.5.0\r\nThe hotfix includes the following fixes: \r\n- CRQ-11996 Discovery service with a hostname including svc\r\n\r\n\r\nDescription:\r\n------------\r\nThis is a hotfix for:\r\n- CRQ-11996 Discovery service with a hostname including svc\r\n\r\n\r\nInstallation:\r\n-------------\r\nThis hotfix provides updated roles for Cid, Content, Context, Deployer, Discovery, Preview, Session and UGC.\r\nThe instructions below are common to all types of services. You should apply the same instructions to each\r\nservice type that you have installed.\r\n\r\n\r\nInstructions:\r\n-------------\r\n\r\nServices\r\n--------\r\n1. Stop relevant Service\r\n2. Backup (or move) a folder where your standalone Service is located\r\n3. Uninstall the relevant Service by opening a Powershell window in the \\bin of your service and run .\\uninstallService.ps1\r\n4. Navigate to the release\\ folder of this distribution\r\n5. Copy \\standalone folder to the location where your original service was located\r\n6. Rename copied \\standalone folder to the name of your original service's folder\r\n7. Copy all files from \\config folder of your backup (see step #2) to \\config folder of a new service\r\n8. Copy custom jars (if you have any) from backup's \\services\\folder to a same location of a new service\r\n9. Install service by opening a Powershell window in in the location \\bin of new service and run .\\installService.ps1\r\n\r\n\r\nDistributed roles:\r\n------------------\r\ncid\t\tContextual Image Delivery Service\r\ncontent\t\tContent Service\r\ncontext\t\tContext Service\r\ndeployer\tDeployer Services\r\ndiscovery\tDiscovery Service\r\npreview\t\tPreview Service\r\nsession\t\tSession Service\r\nugc\t\tUser Generated Content Services\r\n\r\n\r\nFixed problems:\r\n---------------\r\n- CRQ-11996 Discovery service with a hostname including svc\r\n\r\n\r\nHotfix Description\r\n-------------------\r\n- Modified OData to support service names with .svc in them\r\n\r\n\r\nDisclaimer:\r\n-----------\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and \r\nschedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration \r\nand therefore should only be installed if approved by Customer Support. Hotfixes should be replaced as soon as \r\npossible by the subsequent patch release where the problem is fixed.\r\n\r\nCopyright 2016-2018 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL \r\nGroup.\r\n",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2b594436e1bc8257c3f"
},
"hotfix_name": "CD_11.5.0.22583",
"modified_date": {
"$date": 1611069537283
},
"problem_description": "- Cache is not get invalidated/flushed after publishing/unpublishing\r\n",
"readme_text": "Release Notes for Hotfix CRQ-22583\r\n==================================\r\n\r\n\r\nVersion\r\n=======\r\nThis cumulative hotfix is intended only for SDL Sites 9.5 customers.\r\n\r\n\r\nDescription\r\n===========\r\nThis is a hotfix for:\r\n - CRQ-22583 - Updated content is not rendered on sites after hotfix 11.1.110-RELEASE\r\n\r\n\r\nInstallation\r\n============\r\nThis hotfix involves a change to one of the JARs, that is used in multiple services.\r\n\r\n\r\nServices\r\n--------\r\n1. Ensure relevant Service is stopped\r\n2. Backup (or move) a folder where your standalone Service is located\r\n3. Uninstall the relevant Service by opening a Power-shell window in the \\bin of your service and run .\\uninstallService.ps1\r\n4. Navigate to the release\\ folder of this distribution\r\n5. Copy \\standalone folder to the location where your original service was located\r\n6. Rename copied \\standalone folder to the name of your original service's folder\r\n7. Copy all files from \\config folder of your backup (see step #2) to \\config folder of a new service\r\n8. Copy custom jars (if you have any) from backup's \\services\\folder to the same location of a new service\r\n9. Re-install service by opening a Powershell window in the location \\bin of new service and run .\\installService.ps1\r\n\r\nAdd-ons\r\n-------\r\nIt is recommended that customers using our default add-ons use the versions provided in this hotfix (contained within the /add-ons folders). \r\n\r\nDistributed roles\r\n=================\r\ncache \t\t\t Cache Channel Service\r\ncontent Content Service role\r\ndeployer Deployer role\r\npreview Preview service role\r\nsession Session service role\r\n\r\nFixed problems\r\n==============\r\n\r\nProblem Description\r\n-------------------\r\n - Cache is not get invalidated/flushed after publishing/unpublishing\r\n\r\nHotfix Description\r\n-------------------\r\n- Aligned the way how region names were created on deployer and content services\r\n\r\n\r\nDisclaimer\r\n==========\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. \r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore \r\nshould only be installed if approved by Customer Support. Hotfixes should be replaced as soon as possible by the \r\nsubsequent patch release where the problem is fixed.\r\n\r\nCopyright \ufffd 2015-2020 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.\r\n",
"version": "Sites 9.5"
},
{
"_id": {
"$oid": "635fe2c094436e1bc8257d85"
},
"hotfix_name": "ECL_8.5.0.15630",
"modified_date": {
"$date": 1564578670723
},
"problem_description": "",
"readme_text": "Release Notes for Hotfix 15630\n\nVersion:\n\tThis hotfix is intended only for Tridion External Content Library 8.5 included in Tridion 8.5.\n\nProblem description:\n\tError notification when trying to view Checked-out Items.\n\nHotfix description:\n\tFix data extenders so UI does not fail when errors in providers occure.\n\nInstallation:\n\t1. Stop all Tridion Content Manager Service Host and IIS Service.\n\t2. Move the file Tridion.ExternalContentLibrary.UI.DataExtenders.dll located in the %Tridion%\\web\\WebUI\\WebRoot\\bin folder\n\t3. Copy the Tridion.ExternalContentLibrary.UI.DataExtenders.dll file from this hotfix to the %Tridion%\\web\\WebUI\\WebRoot\\bin folder\n\t4. Move the file Tridion.ExternalContentLibrary.UI.Http.dll located in the %Tridion%\\web\\WebUI\\WebRoot\\bin folder\n\t5. Copy the Tridion.ExternalContentLibrary.UI.Http.dll file from this hotfix to the %Tridion%\\web\\WebUI\\WebRoot\\bin folder\n\t6. Move the file Tridion.ExternalContentLibrary.UI.Model.dll located in the %Tridion%\\web\\WebUI\\WebRoot\\bin folder\n\t7. Copy the Tridion.ExternalContentLibrary.UI.Model.dll file from this hotfix to the %Tridion%\\web\\WebUI\\WebRoot\\bin folder\n\t8. Restart the IIS Service and Tridion Content Manager Service Host.\n\nDistributed files:\n Tridion.ExternalContentLibrary.UI.DataExtenders.dll (File Version 8.5.0.130)\n Tridion.ExternalContentLibrary.UI.Http.dll (File Version 8.5.0.130)\n Tridion.ExternalContentLibrary.UI.Model.dll (File Version 8.5.0.130)\n Readme.txt (this file)\n\nFixes included:\n\t12949:\tEditors unable to use ECL items. When using Group Synchronization.\n\nDependencies:\n\tN/A\n\nDisclaimer:\n\tHotfixes are released at the discretion of SDL Tridion based on technical complexity, customer business requirements and schedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by SDL Tridion Customer Support. Hotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\n\nCopyright (c) 2019 SDL Group.",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2b294436e1bc8257bd8"
},
"hotfix_name": "CD_11.0.1.22583",
"modified_date": {
"$date": 1611068957481
},
"problem_description": "- Cache is not get invalidated/flushed after publishing/unpublishing\r\n",
"readme_text": "Release Notes for Hotfix CRQ-22583\r\n==================================\r\n\r\n\r\nVersion\r\n=======\r\nThis cumulative hotfix is intended only for SDL Tridion Sites 9 customers.\r\n\r\n\r\nDescription\r\n===========\r\nThis is a hotfix for:\r\n - CRQ-22583 - Updated content is not rendered on sites after hotfix 11.1.110-RELEASE\r\n - CRQ-21973 - PageLink cache and ComponentLink cache are keeping non-read-only objects so they might be spoiled in cache\r\n\r\n\r\nInstallation\r\n============\r\nThis hotfix involves a change to one of the JARs, that is used in multiple services.\r\n\r\n\r\nServices\r\n--------\r\n1. Ensure relevant Service is stopped\r\n2. Backup (or move) a folder where your standalone Service is located\r\n3. Uninstall the relevant Service by opening a Power-shell window in the \\bin of your service and run .\\uninstallService.ps1\r\n4. Navigate to the release\\ folder of this distribution\r\n5. Copy \\standalone folder to the location where your original service was located\r\n6. Rename copied \\standalone folder to the name of your original service's folder\r\n7. Copy all files from \\config folder of your backup (see step #2) to \\config folder of a new service\r\n8. Copy custom jars (if you have any) from backup's \\services\\folder to the same location of a new service\r\n9. Re-install service by opening a Powershell window in the location \\bin of new service and run .\\installService.ps1\r\n\r\n\r\nDistributed roles\r\n=================\r\ncache Cache channel service role\r\ncontent Content Service role\r\ndeployer Deployer role\r\npreview Preview service role\r\nsession Session service role\r\n\r\nFixed problems\r\n==============\r\n\r\nProblem Description\r\n-------------------\r\n - Cache is not get invalidated/flushed after publishing/unpublishing\r\n\r\nHotfix Description\r\n-------------------\r\n- Aligned the way how cache region names were created on deployer and content services\r\n\r\n\r\nDisclaimer\r\n==========\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. \r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore \r\nshould only be installed if approved by Customer Support. Hotfixes should be replaced as soon as possible by the \r\nsubsequent patch release where the problem is fixed.\r\n\r\nCopyright \ufffd 2015-2020 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.\r\n",
"version": "Sites 9.0.1"
},
{
"_id": {
"$oid": "635fe2ac94436e1bc8257aab"
},
"hotfix_name": "CD_2013.0.0.84847",
"modified_date": {
"$date": 1363859944072
},
"problem_description": "Some of the HashMaps in the storage layer are not thread-safe.\r\n",
"readme_text": "Release Notes for Hotfix TT84847\r\n================================\r\n\r\nVersion:\r\n========\r\nThis hotfix is intended only for Tridion 2013 GA.\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n- TT84847 Hanging threads in broker\r\n\r\nInstallation:\r\n=============\r\nDeployer environment:\r\n---------------------\r\nJava Environment with HttpUpload:\r\n1. Ensure that you have a correct installed Content Delivery installation inside your web application\r\n2. Stop your web application server or web application containing the deployer httpupload\r\n3. Copy the distributed jar files inside your web application WEB-INF\\lib directory\r\n4. Start your web application server or web application\r\n\r\n.NET Environment with HttpUpload:\r\n1. Ensure the application pool and or IIS Server has been stopped\r\n2. Copy the distributed jar files inside the IIS application directory bin\\lib directory. In case of central tridion installation please copy the distributed jar files\r\ninto the installation directory \\lib folder.\r\n3. Start the application pool and or IIS Server\r\n\r\nStandalone deployer:\r\n1. Ensure the deployer service has been stopped\r\n2. Copy the distributed jar files inside your 'Tridion installation folder'\\lib directory\r\n3. Start the deployer service\r\n\r\nDistributed files:\r\n==================\r\ncd_datalayer.jar (7.0.0.1)\r\n\r\nDependencies:\r\n=============\r\nSDL Tridion 2013 GA\r\n\r\n\r\nFixed problems:\r\n===============\r\nTT84847\r\nProblem Description\r\n-------------------\r\nSome of the HashMaps in the storage layer are not thread-safe.\r\n\r\nHotfix Description\r\n-------------------\r\nMade these HashMaps thread-safe.\r\n\r\n\r\nDisclaimer:\r\n===========\r\nHotfixes are released at the discretion of Tridion based on technical\r\ncomplexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/\r\nconfiguration and therefore should only be installed if approved by Tridion\r\nCustomer Support. Hotfixes should be replaced as soon as possible by the\r\nsubsequent service pack where the problem is fixed.\r\n\r\n(c) 2011 SDL Tridion B.V.\r\n",
"version": "2013"
},
{
"_id": {
"$oid": "635fe2ba94436e1bc8257cbe"
},
"hotfix_name": "ECL_8.1.1.3664",
"modified_date": {
"$date": 1484751549028
},
"problem_description": "Editors unable to use ECL items. When using Group Synchronization\r\n",
"readme_text": "Release Notes for Hotfix 3664\r\n\r\nVersion:\r\nThis hotfix is intended only for Tridion External Content Library 8.1.1 included in Tridion 8.1.1.\r\n\r\nProblem description:\r\nEditors unable to use ECL items. When using Group Synchronization\r\n\r\nHotfix description:\r\nUse Tridion.Security.ClaimsPrincipal istead of System.Security.Claims.ClaimsPrincipal.\r\n\r\nInstallation:\r\n 1. Stop all Tridion Content Manager Service Host and IIS Service.\r\n 2. Move the file Tridion.ExternalContentLibrary.UI.DataExtenders.dll located in the %Tridion%\\web\\WebUI\\WebRoot\\bin folder\r\n 3. Copy the Tridion.ExternalContentLibrary.UI.DataExtenders.dll file from this hotfix to the %Tridion%\\web\\WebUI\\WebRoot\\bin folder\r\n 4. Move the file Tridion.ExternalContentLibrary.UI.Http.dll located in the %Tridion%\\web\\WebUI\\WebRoot\\bin folder\r\n 5. Copy the Tridion.ExternalContentLibrary.UI.Http.dll file from this hotfix to the %Tridion%\\web\\WebUI\\WebRoot\\bin folder\r\n 6. Move the file Tridion.ExternalContentLibrary.UI.Model.dll located in the %Tridion%\\web\\WebUI\\WebRoot\\bin folder\r\n 7. Copy the Tridion.ExternalContentLibrary.UI.Model.dll file from this hotfix to the %Tridion%\\web\\WebUI\\WebRoot\\bin folder\r\n 8. Restart the IIS Service and Tridion Content Manager Service Host.\r\n\r\nDistributed files:\r\n Tridion.ExternalContentLibrary.UI.DataExtenders.dll (File Version 8.1.0.240)\r\n Tridion.ExternalContentLibrary.UI.Http.dll (File Version 8.1.0.240)\r\n Tridion.ExternalContentLibrary.UI.Model.dll (File Version 8.1.0.240)\r\n Readme.txt (this file)\r\n\r\nFixes included:\r\n\tN/A\r\n\r\nDependencies:\r\n\tN/A\r\n\r\nDisclaimer:\r\n\tHotfixes are released at the discretion of SDL Tridion based on technical complexity, customer business requirements and schedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by SDL Tridion Customer Support. Hotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright (c) 2017 SDL Group.",
"version": "Web 8.1.1"
},
{
"_id": {
"$oid": "635fe2c094436e1bc8257d83"
},
"hotfix_name": "ECL_8.5.0.12949",
"modified_date": {
"$date": 1545993443373
},
"problem_description": "Editors unable to use ECL items. When using Group Synchronization.\r\n",
"readme_text": "Release Notes for Hotfix 12949\r\n\r\nVersion:\r\n\tThis hotfix is intended only for Tridion External Content Library 8.5 included in Tridion 8.5.\r\n\r\nProblem description:\r\n\tEditors unable to use ECL items. When using Group Synchronization.\r\n\r\nHotfix description:\r\n\tUse Tridion.Security.ClaimsPrincipal istead of System.Security.Claims.ClaimsPrincipal.\r\n\r\nInstallation:\r\n\t1. Stop all Tridion Content Manager Service Host and IIS Service.\r\n\t2. Move the file Tridion.ExternalContentLibrary.UI.DataExtenders.dll located in the %Tridion%\\web\\WebUI\\WebRoot\\bin folder\r\n\t3. Copy the Tridion.ExternalContentLibrary.UI.DataExtenders.dll file from this hotfix to the %Tridion%\\web\\WebUI\\WebRoot\\bin folder\r\n\t4. Move the file Tridion.ExternalContentLibrary.UI.Http.dll located in the %Tridion%\\web\\WebUI\\WebRoot\\bin folder\r\n\t5. Copy the Tridion.ExternalContentLibrary.UI.Http.dll file from this hotfix to the %Tridion%\\web\\WebUI\\WebRoot\\bin folder\r\n\t6. Move the file Tridion.ExternalContentLibrary.UI.Model.dll located in the %Tridion%\\web\\WebUI\\WebRoot\\bin folder\r\n\t7. Copy the Tridion.ExternalContentLibrary.UI.Model.dll file from this hotfix to the %Tridion%\\web\\WebUI\\WebRoot\\bin folder\r\n\t8. Restart the IIS Service and Tridion Content Manager Service Host.\r\n\r\nDistributed files:\r\n Tridion.ExternalContentLibrary.UI.DataExtenders.dll (File Version 8.5.0.124)\r\n Tridion.ExternalContentLibrary.UI.Http.dll (File Version 8.5.0.124)\r\n Tridion.ExternalContentLibrary.UI.Model.dll (File Version 8.5.0.124)\r\n Readme.txt (this file)\r\n\r\nFixes included:\r\n\tN/A\r\n\r\nDependencies:\r\n\tN/A\r\n\r\nDisclaimer:\r\n\tHotfixes are released at the discretion of SDL Tridion based on technical complexity, customer business requirements and schedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by SDL Tridion Customer Support. Hotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright (c) 2018 SDL Group.",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2bb94436e1bc8257ce1"
},
"hotfix_name": "CD_8.5.0.12584",
"modified_date": {
"$date": 1546592950218
},
"problem_description": "- Resolved Publication Mapping through our API does not return all fields\r\n",
"readme_text": "Release Notes for Hotfix CRQ-12584\r\n=================================\r\n\r\nVersion:\r\n========\r\nThis is hotfix and is intended only for SDL Web 8.5.0\r\n\r\nDescription:\r\n============\r\nThe hotfix include the following fixes: \r\n - CRQ-12584 path not being returned for child website when using CD API\r\n\r\n\r\n Installation:\r\n=============\r\nThis cumulative hotfix provides updated services: Api role, Content Service, Preview and Session. The Layout build number 1061.\r\n\r\n\r\nAll Services\r\n-----------------------\r\n1. Stop the Service you are going to upgrade\r\n2. Backup (or move) a folder where your standalone Service is located\r\n3. Uninstall the Service by opening a Powershell window in the \\bin of your service and running .\\uninstallService.ps1\r\n4. Navigate to the release\\\\service folder of this distribution\r\n5. Copy \\standalone folder to the location where your original service was located\r\n6. Rename copied \\standalone folder to the name of your original service's folder\r\n7. Copy all files from \\config folder of your backup (see step #2) to \\config folder of a new service.\r\n8. Copy custom jars (if you have any) from backup's \\services\\folder to a same location of a new service\r\n9. Install service by opening a Powershell window in in the location \\bin of new service and run .\\installService.ps1\r\n\r\n\r\nDistributed roles:\r\n==================\r\ncontent Content Service role\r\npreview Preview service role\r\nsession Session service role\r\n\r\n\r\nFixed problems:\r\n===============\r\n - CRQ-12584 path not being returned for child website when using CD API\r\n\r\nProblem Description\r\n-------------------\r\n- Resolved Publication Mapping through our API does not return all fields\r\n\r\nHotfix Description\r\n-------------------\r\n- Setting additional fields into Publication Mapping which contain information based on incomming URL and database publication path\r\n\r\n\r\nDisclaimer:\r\n===========\r\n\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed\r\nif approved by Customer Support. Hotfixes should be replaced as soon as possible by the subsequent patch release where the problem is fixed.\r\n\r\nCopyright 2015-2017 SDL Group. All Rights Reserved.\r\n\r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.\r\n",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2bb94436e1bc8257cde"
},
"hotfix_name": "CD_8.5.0.12106",
"modified_date": {
"$date": 1541800751057
},
"problem_description": "This is a hotfix for:\r\n- CRQ-12106 Deployer 8.5 Standalone Service Vulnerability - HTTP Security Header Not Detected\r\n",
"readme_text": "Release Notes for Hotfix CRQ-12106\r\n==================================\r\n\r\nVersion:\r\n--------\r\nThis is hotfix and is intended for SDL Web 8.5.0\r\nThe hotfix includes the following fixes: \r\n- CRQ-12106 Deployer 8.5 Standalone Service Vulnerability - HTTP Security Header Not Detected\r\n\r\n\r\nDescription:\r\n------------\r\nThis is a hotfix for:\r\n- CRQ-12106 Deployer 8.5 Standalone Service Vulnerability - HTTP Security Header Not Detected\r\n\r\n\r\nInstallation:\r\n-------------\r\nThis hotfix provides updated roles for the Deployer services. You should apply the same instructions to each\r\ntype of deployer service that you have installed.\r\n\r\n\r\nInstructions:\r\n-------------\r\n\r\nServices\r\n--------\r\n1. Stop relevant Service\r\n2. Backup (or move) a folder where your standalone Service is located\r\n3. Uninstall the relevant Service by opening a Powershell window in the \\bin of your service and run .\\uninstallService.ps1\r\n4. Navigate to the release\\ folder of this distribution\r\n5. Copy \\standalone folder to the location where your original service was located\r\n6. Rename copied \\standalone folder to the name of your original service's folder\r\n7. Copy all files from \\config folder of your backup (see step #2) to \\config folder of a new service\r\n8. Copy custom jars (if you have any) from backup's \\services\\folder to a same location of a new service\r\n9. Install service by opening a Powershell window in in the location \\bin of new service and run .\\installService.ps1\r\n\r\nConfiguring security options\r\n----------------------------\r\nThe security headers are configurable by modifying the following system properites (which can be set in a location application.properties). By default both are set to true:\r\n\r\ndeployer.xssprotection.enabled = true\r\ndeployer.frameoptions.enabled = true\r\n\r\n\r\nDistributed roles:\r\n------------------\r\ndeployer\tDeployer Services\r\n\r\n\r\nFixed problems:\r\n---------------\r\n- CRQ-12106 Deployer 8.5 Standalone Service Vulnerability - HTTP Security Header Not Detected\r\n\r\n\r\nHotfix Description\r\n-------------------\r\n- Added HTTP Secuirty Headers\r\n\r\n\r\nDisclaimer:\r\n-----------\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and \r\nschedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration \r\nand therefore should only be installed if approved by Customer Support. Hotfixes should be replaced as soon as \r\npossible by the subsequent patch release where the problem is fixed.\r\n\r\nCopyright 2016-2018 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL \r\nGroup.\r\n",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2b994436e1bc8257c82"
},
"hotfix_name": "CD_8.1.1.2049",
"modified_date": {
"$date": 1465320785590
},
"problem_description": "Component Presentation web control requires Page Uri to be mandatory\r\n",
"readme_text": "Release Notes for Hotfix CRQ-2049\r\n=================================\r\n\r\nVersion:\r\n========\r\nThis is cumulative hotfix and is intended only for SDL Web 8.1.1\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n - CRQ-2049 Component Presentation web control requires Page Uri to be mandatory\r\n\r\nInstallation:\r\n=============\r\nThis cumulative hotfix provides updated .NET api artifacts for CD, Contextual Image Delivery, Context Client, Session and UGC.\r\n\r\nCD API's\r\n--------\r\n\tREST:\r\n\t\t1. [.NET] - update [.NET] artifacts from release\\api\\rest\\dotNet\\bin folder.\r\n\r\nCID Proxy\r\n---------\r\n\t\t1. [.NET] - update [.NET] artifacts from release\\cid\\proxy\\dotnet\\bin\r\n\r\nContext Client API\r\n------------------\r\n\t\t1. [.NET] - update [.NET] artifacts from release\\context\\api\\dotNet\\bin\r\n\t\t\r\nSession Extension\r\n-----------------\r\n\t\t1. [.NET] - update [.NET] artifacts from release\\session\\extension-web\\rest\\dotNet\\bin\r\n\r\nUGC Extension\r\n\t\t1. [.NET] - update [.NET] artifacts from release\\ugc\\extension-web\\rest\\dotNet\\bin\r\n\r\n\r\nDistributed roles:\r\n==================\r\napi Content Delivery API role\r\ncid\t\t\t\t\t\t Contextual Image Delivery Proxy role\r\ncontext\t\t\t\t\t Context Client role\r\nsession/extension-web\t Session Extension role\r\nugc/extension-web\t\t UGC Extension role\r\n\r\nDependencies:\r\n=============\r\n\r\n\r\nFixed problems:\r\n===============\r\n\t- CRQ-2049 Component Presentation web control requires Page Uri to be mandatory\r\n\r\nProblem Description\r\n-------------------\r\nComponent Presentation web control requires Page Uri to be mandatory\r\n\r\nHotfix Description\r\n-------------------\r\nModified [.NET] control for Component Presentation to support tcm:0-0-0\r\n\r\nDisclaimer:\r\n===========\r\n\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/configuration and therefore should only be installed\r\nif approved by Customer Support. Hotfixes should be replaced as soon as possible by the subsequent patch release where the problem is fixed.\r\n\r\nCopyright 2015-2016 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.\r\n",
"version": "Web 8.1.1"
},
{
"_id": {
"$oid": "635fe2b094436e1bc8257b71"
},
"hotfix_name": "ECL_2013.1.1.5014",
"modified_date": {
"$date": 1496740528565
},
"problem_description": "",
"readme_text": "Release Notes for Hotfix 5014\n\nVersion:\nThis hotfix is intended only for Tridion External Content Library 7.1 included in Tridion 2013 SP1 HR1.\n\nProblem description:\n\tError querying publish queue from GUI when MM item is shown multiple times\n\nHotfix description:\n\tFix item grouping for parallel load. \n\nInstallation:\n\t1. Stop all Tridion Content Manager Service Host and IIS Service.\n\t2. Move the file Tridion.ExternalContentLibrary.DomainModel.dll located in the %WINDIR%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.ExternalContentLibrary.DomainModel\\v4.0_7.1.0.103__ddfc895746e5ee6b folder\n\t3. Copy the Tridion.ExternalContentLibrary.DomainModel.dll file from this hotfix to the %WINDIR%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.ExternalContentLibrary.DomainModel\\v4.0_7.1.0.103__ddfc895746e5ee6b folder\n\t4. Move the file Tridion.ExternalContentLibrary.IconLoader.dll located in the %WINDIR%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.ExternalContentLibrary.IconLoader\\v4.0_7.1.0.103__ddfc895746e5ee6b folder\n\t5. Copy the Tridion.ExternalContentLibrary.IconLoader.dll file from this hotfix to the %WINDIR%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.ExternalContentLibrary.IconLoader\\v4.0_7.1.0.103__ddfc895746e5ee6b folder\n\t6. Restart the IIS Service and Tridion Content Manager Service Host.\n\nDistributed files:\n Tridion.ExternalContentLibrary.DomainModel.dll (File Version 7.1.0.126)\n Tridion.ExternalContentLibrary.IconLoader.dll (File Version 7.1.0.126)\n Readme.txt (this file)\n\nFixes included:\n\tCRQ-2176: Memory leak in microsoft image manipulation library.\n\nDependencies:\n\tN/A\n\nDisclaimer:\n\tHotfixes are released at the discretion of SDL Tridion based on technical complexity, customer business requirements and schedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by SDL Tridion Customer Support. Hotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\n\nCopyright (c) 2016 SDL Group.",
"version": "2013 SP1 HR#1"
},
{
"_id": {
"$oid": "635fe2b994436e1bc8257c86"
},
"hotfix_name": "CD_8.1.1.2276",
"modified_date": {
"$date": 1468352040754
},
"problem_description": "BinaryVariant is missing the 'StructureGroupId' property in the metadata generated by the Content Service.\r\n",
"readme_text": "Release Notes for Hotfix CRQ-2276\r\n=================================\r\n\r\nVersion:\r\n========\r\nThis is hotfix and is intended only for SDL Web 8.1.1\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n - CRQ-2276 BinaryVariant is missing the 'StructureGroupId' property in the metadata generated by the Content Service\r\n \r\nInstallation:\r\n=============\r\nThis hotfix provides updated services.\r\n\r\nFollowing services are updated - Content Service, Preview and Session.\r\n\r\nAll Services\r\n-----------------------\r\n1. Stop the Service you are going to upgrade\r\n2. Backup (or move) a folder where your standalone Service is located\r\n3. Uninstall the Service by opening a Powershell window in the \\bin of your service and running .\\uninstallService.ps1\r\n4. Navigate to the release\\\\service folder of this distribution\r\n5. Copy \\standalone folder to the location where your original service was located\r\n6. Rename copied \\standalone folder to the name of your original service's folder\r\n7. Copy all files from \\config folder of your backup (see step #2) to \\config folder of a new service.\r\n8. Copy custom jars (if you have any) from backup's \\services\\folder to a same location of a new service\r\n9. Install service by opening a Powershell window in in the location \\bin of new service and run .\\installService.ps1\r\n\r\nDistributed roles:\r\n==================\r\ncontent Content Service role\r\npreview Preview service role\r\nsession\t\t\t\t\t Session service role\r\n\r\nDependencies:\r\n=============\r\n\r\n\r\nFixed problems:\r\n===============\r\n - CRQ-2276 BinaryVariant is missing the 'StructureGroupId' property in the metadata generated by the Content Service\r\n\r\nProblem Description\r\n-------------------\r\nBinaryVariant is missing the 'StructureGroupId' property in the metadata generated by the Content Service.\r\n\r\nHotfix Description\r\n-------------------\r\nAdded additional 'StructureGroupId' property to generated metadata.\r\n\r\nDisclaimer:\r\n===========\r\n\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/configuration and therefore should only be installed\r\nif approved by Customer Support. Hotfixes should be replaced as soon as possible by the subsequent patch release where the problem is fixed.\r\n\r\nCopyright 2015-2016 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.\r\n",
"version": "Web 8.1.1"
},
{
"_id": {
"$oid": "635fe2b994436e1bc8257c81"
},
"hotfix_name": "CD_8.1.1.1957",
"modified_date": {
"$date": 1470146194567
},
"problem_description": "Unable to store item inside current transaction: Can't read file error when publishing on Web 8.1.1.\r\n",
"readme_text": "Release Notes for Hotfix CRQ-1957\r\n=================================\r\n\r\nVersion:\r\n========\r\nThis is cumulative hotfix and is intended only for SDL Web 8.1.1\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n - CRQ-1957 Unable to store item inside current transaction: Can't read file error when publishing on Web 8.1.1\r\n\r\n \r\nInstallation:\r\n=============\r\nThis cumulative hotfix provides updated api artifacts and services.\r\n\r\nCD API's\r\n--------\r\n\tIn-Process:\r\n\t\t1. [.NET] - update [.NET] artifacts from release\\api\\in-process\\dotNet\\bin folder.\r\n\t\t2. Java - update artifacts from release\\api\\in-process\\java\\lib folder.\r\n\r\n\tREST:\r\n\t\t1. [.NET] - update [.NET] artifacts from release\\api\\rest\\dotNet\\bin folder.\r\n\t\t2. Java - update artifacts from release\\api\\rest\\java\\lib folder.\r\n\r\n\r\nFollowing services are updated - Content Service, Discovery Service, Deployer, Preview, Session, UGC community-service and UGC moderation-service.\r\n\r\nAll Services\r\n-----------------------\r\n1. Stop the Service you are going to upgrade\r\n2. Backup (or move) a folder where your standalone Service is located\r\n3. Uninstall the Service by opening a Powershell window in the \\bin of your service and running .\\uninstallService.ps1\r\n4. Navigate to the release\\\\service folder of this distribution\r\n5. Copy \\standalone folder to the location where your original service was located\r\n6. Rename copied \\standalone folder to the name of your original service's folder\r\n7. Copy all files from \\config folder of your backup (see step #2) to \\config folder of a new service.\r\n8. Copy custom jars (if you have any) from backup's \\services\\folder to a same location of a new service\r\n9. Install service by opening a Powershell window in in the location \\bin of new service and run .\\installService.ps1\r\n\r\nDistributed roles:\r\n==================\r\napi Content Delivery API role\r\ncontent Content Service role\r\ndeployer Deployer role\r\ndiscovery Discovery service role\r\npreview Preview service role\r\nsession\t\t\t\t\t Session service role\r\nugc/community-service UGC Community Service role\r\nugc/moderation-service UGC Moderation Service role\r\n\r\nDependencies:\r\n=============\r\n\r\n\r\nFixed problems:\r\n===============\r\n - CRQ-1957 Unable to store item inside current transaction: Can't read file error when publishing on Web 8.1.1\r\n\r\n\r\nProblem Description\r\n-------------------\r\nUnable to store item inside current transaction: Can't read file error when publishing on Web 8.1.1.\r\n\r\n\r\nHotfix Description\r\n-------------------\r\nCorrected exception handling when using new Java NIO files package.\r\n\r\n\r\nDisclaimer:\r\n===========\r\n\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. \r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore \r\nshould only be installed if approved by Customer Support. Hotfixes should be replaced as soon as possible by the subsequent patch release where the problem is fixed.\r\n\r\nCopyright 2015-2016 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.\r\n",
"version": "Web 8.1.1"
},
{
"_id": {
"$oid": "635fe2bd94436e1bc8257d0b"
},
"hotfix_name": "CD_8.5.0.5099",
"modified_date": {
"$date": 1499761882384
},
"problem_description": "Failed to publish larg number of packages with increased number of workers (40 workers).\r\n",
"readme_text": "Release Notes for Hotfix CRQ-5099\r\n=================================\r\n \r\nVersion:\r\n========\r\nThis is cumulative hotfix and is intended only for SDL Web 8.5.0\r\n \r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n - CRQ-5099 Web 8.5 - Publication failure due to Deadlocks on Database [Oracle 12c]\r\n\r\n \r\nInstallation:\r\n=============\r\nThis cumulative hotfix provides updated services.\r\n \r\n \r\nFollowing services are updated - Deployer.\r\n \r\nAll Services\r\n-----------------------\r\n1. Stop the Service you are going to upgrade\r\n2. Backup (or move) a folder where your standalone Service is located\r\n3. Uninstall the Service by opening a Powershell window in the \\bin of your service and running .\\uninstallService.ps1\r\n4. Navigate to the release\\\\service folder of this distribution\r\n5. Copy \\standalone folder to the location where your original service was located\r\n6. Rename copied \\standalone folder to the name of your original service's folder\r\n7. Copy all files from \\config folder of your backup (see step #2) to \\config folder of a new service.\r\n8. Copy custom jars (if you have any) from backup's \\services\\folder to a same location of a new service\r\n9. Install service by opening a Powershell window in in the location \\bin of new service and run .\\installService.ps1\r\n \r\nDistributed roles:\r\n==================\r\ndeployer Deployer role\r\n \r\nDependencies:\r\n=============\r\n \r\nFixed problems:\r\n===============\r\n - CRQ-5099 Web 8.5 - Publication failure due to Deadlocks on Database [Oracle 12c]\r\n \r\nProblem Description\r\n-------------------\r\nFailed to publish larg number of packages with increased number of workers (40 workers).\r\n \r\nHotfix Description\r\n-------------------\r\nAkka threadpool configuration was not in corelation with number of workers defined in deployer-conf.xml\r\n \r\nDisclaimer:\r\n===========\r\n \r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/configuration and therefore should only be installed\r\nif approved by Customer Support. Hotfixes should be replaced as soon as possible by the subsequent patch release where the problem is fixed.\r\n \r\nCopyright 2015-2017 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2bd94436e1bc8257d1a"
},
"hotfix_name": "CD_8.5.0.7905",
"modified_date": {
"$date": 1509962954451
},
"problem_description": "- Content (session) service is not capable of flushing page meta cache when do undeploy.\r\n",
"readme_text": "Release Notes for Hotfix CRQ-7905\r\n=================================\r\n\r\nVersion:\r\n========\r\nThis is cumulative hotfix and is intended only for SDL Web 8.5.0\r\n\r\nDescription:\r\n============\r\nThe hotfix include the following fixes:\r\n - CRQ-7905 Page meta still in cache after page is unpublished\r\n\r\nInstallation:\r\n=============\r\nThis cumulative hotfix provides updated standalone service roles.\r\n\r\nContent service\r\n-----------------------\r\n1. Stop the Service you are going to upgrade\r\n2. Backup (or move) a folder where your standalone Service is located\r\n3. Uninstall the Service by opening a Powershell window in the \\bin of your service and running .\\uninstallService.ps1\r\n4. Navigate to the release\\\\service folder of this distribution\r\n5. Copy \\standalone folder to the location where your original service was located\r\n6. Rename copied \\standalone folder to the name of your original service's folder\r\n7. Copy all files from \\config folder of your backup (see step #2) to \\config folder of a new service.\r\n8. Copy custom jars (if you have any) from backup's \\services\\folder to a same location of a new service\r\n9. Install service by opening a Powershell window in in the location \\bin of new service and run .\\installService.ps1\r\n\r\nDistributed roles:\r\n==================\r\ncontent-service\t\t\tContent service role\r\nsession-service\t\t\tSession content service role\r\n\r\nFixed problems:\r\n===============\r\n - CRQ-7905 Page meta still in cache after page is unpublished\r\n\r\nProblem Description\r\n-------------------\r\n- Content (session) service is not capable of flushing page meta cache when do undeploy.\r\n\r\nHotfix Description\r\n-------------------\r\n- Fixed content (session) service by adding cache dependency so the entry is properly flushed after undeploy.\r\n\r\nDisclaimer:\r\n===========\r\n\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/configuration and therefore should only be installed\r\nif approved by Customer Support. Hotfixes should be replaced as soon as possible by the subsequent patch release where the problem is fixed.\r\n\r\nCopyright \ufffd 2015-2017 SDL Group. All Rights Reserved.\r\n\r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.\r\n",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2bb94436e1bc8257ced"
},
"hotfix_name": "CD_8.5.0.16811",
"modified_date": {
"$date": 1572353354644
},
"problem_description": "This is a hotfix for:\r\n- CRQ-16811 - Mass publishing performance issues\r\n",
"readme_text": "Release Notes for Hotfix CRQ-16811\r\n=================================\r\n\r\nVersion:\r\n========\r\nThis cumulative hotfix is intended only for SDL Web 8.5.0 customers.\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n\t- CRQ-16811 - Mass publishing performance issues\r\n\t\r\nInstallation:\r\n=============\r\nThis cumulative hotfix provides updated standalone service, in-process and rest api roles (java)\r\n\r\nFor all Services\r\n------------\r\n1. Stop/uninstall the Service you are going to update\r\n2. Backup (or move) the folder where your standalone Service is located\r\n3. Uninstall the Service by opening a Powershell window in the \\bin folder of your service and running\r\n .\\uninstallService.ps1\r\n4. Navigate to the release\\\\service folder of this distribution\r\n5. Copy the \\standalone folder to the location where your original service was located\r\n6. Rename copied \\standalone folder to the name of your original service's folder\r\n7. Copy all files from \\config folder of your backup (see step #2) to \\config folder of a new service\r\n8. Copy custom jars (if you have any) from backup's \\services\\ folders to the same location in new service\r\n9. Install service by opening a Powershell window in in the \\bin folder of the new service and run .\\installService.ps1 \r\n\r\n\r\n\r\n\r\n\r\nDistributed roles:\r\n==================\r\n\r\ndeployer\tDeployer Service roles\r\n\r\n\r\n\r\nDependencies:\r\n=============\r\nN/A\r\n\r\nFixed problems:\r\n===============\r\n- CRQ-16811 - Mass publishing performance issues\r\n\r\n\r\nHotfix Description\r\n===========\r\n-got rid of n+1 requests on file remove\r\n-got rid of opening multiple transactions for 1 action\r\n-got rid of redundant 'exists' requests\r\n-remove file from binary storage outside transaction(for committing earlier)\r\n\r\n\r\n\r\nDisclaimer:\r\n===========\r\n\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. \r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore \r\nshould only be installed if approved by Customer Support. Hotfixes should be replaced as soon as possible by the \r\nsubsequent patch release where the problem is fixed.\r\n\r\nCopyright 2015-2019 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2bd94436e1bc8257d0c"
},
"hotfix_name": "CD_8.5.0.5198",
"modified_date": {
"$date": 1498667006978
},
"problem_description": "- Content (session) service is not capable of retrieving binaries stored on filesystem.\r\n",
"readme_text": "Release Notes for Hotfix CRQ-3966\r\n=================================\r\n\r\nVersion:\r\n========\r\nThis is cumulative hotfix and is intended only for SDL Web 8.5.0\r\n\r\nDescription:\r\n============\r\nThe hotfix include the following fixes: \r\n - CRQ-5198 Content Service unable to retrieve binaries from filesystem\r\n \r\nInstallation:\r\n=============\r\nThis cumulative hotfix provides updated standalone service roles.\r\n\r\nContent service\r\n-----------------------\r\n1. Stop the Service you are going to upgrade\r\n2. Backup (or move) a folder where your standalone Service is located\r\n3. Uninstall the Service by opening a Powershell window in the \\bin of your service and running .\\uninstallService.ps1\r\n4. Navigate to the release\\\\service folder of this distribution\r\n5. Copy \\standalone folder to the location where your original service was located\r\n6. Rename copied \\standalone folder to the name of your original service's folder\r\n7. Copy all files from \\config folder of your backup (see step #2) to \\config folder of a new service.\r\n8. Copy custom jars (if you have any) from backup's \\services\\folder to a same location of a new service\r\n9. Install service by opening a Powershell window in in the location \\bin of new service and run .\\installService.ps1\r\n\r\nDistributed roles:\r\n==================\r\ncontent-service\t\t\tContent service role\r\nsession-service\t\t\tSession content service role\r\n\r\nFixed problems:\r\n===============\r\n - CRQ-5198 Content Service unable to retrieve binaries from filesystem\r\n \r\nProblem Description\r\n-------------------\r\n- Content (session) service is not capable of retrieving binaries stored on filesystem.\r\n\r\nHotfix Description\r\n-------------------\r\n- Fixed content (session) service binary resolver to support retrieving binaries from filesystem.\r\n\r\nDisclaimer:\r\n===========\r\n\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/configuration and therefore should only be installed\r\nif approved by Customer Support. Hotfixes should be replaced as soon as possible by the subsequent patch release where the problem is fixed.\r\n\r\nCopyright 2015-2017 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2b194436e1bc8257b9e"
},
"hotfix_name": "CD_11.0.0.16811",
"modified_date": {
"$date": 1572439179674
},
"problem_description": "This is a hotfix for:\r\n- CRQ-16811 - Mass publishing performance issues\r\n",
"readme_text": "Release Notes for Hotfix CRQ-16811\r\n=================================\r\n\r\nVersion:\r\n========\r\nThis cumulative hotfix is intended only for SDL Sites 9 customers.\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n\t- CRQ-16811 - Mass publishing performance issues\r\n\t\r\nInstallation:\r\n=============\r\nThis cumulative hotfix provides updated standalone service, in-process and rest api roles (java)\r\n\r\nFor all Services\r\n------------\r\n1. Stop/uninstall the Service you are going to update\r\n2. Backup (or move) the folder where your standalone Service is located\r\n3. Uninstall the Service by opening a Powershell window in the \\bin folder of your service and running\r\n .\\uninstallService.ps1\r\n4. Navigate to the release\\\\service folder of this distribution\r\n5. Copy the \\standalone folder to the location where your original service was located\r\n6. Rename copied \\standalone folder to the name of your original service's folder\r\n7. Copy all files from \\config folder of your backup (see step #2) to \\config folder of a new service\r\n8. Copy custom jars (if you have any) from backup's \\services\\ folders to the same location in new service\r\n9. Install service by opening a Powershell window in in the \\bin folder of the new service and run .\\installService.ps1 \r\n\r\n\r\n\r\n\r\n\r\nDistributed roles:\r\n==================\r\n\r\ndeployer\tDeployer Service roles\r\n\r\n\r\n\r\nDependencies:\r\n=============\r\nN/A\r\n\r\nFixed problems:\r\n===============\r\n- CRQ-16811 - Mass publishing performance issues\r\n\r\n\r\nHotfix Description\r\n===========\r\n-got rid of n+1 requests on file remove\r\n-got rid of opening multiple transactions for 1 action\r\n-got rid of redundant 'exists' requests\r\n-remove file from binary storage outside transaction(for committing earlier)\r\n\r\n\r\n\r\nDisclaimer:\r\n===========\r\n\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. \r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore \r\nshould only be installed if approved by Customer Support. Hotfixes should be replaced as soon as possible by the \r\nsubsequent patch release where the problem is fixed.\r\n\r\nCopyright 2015-2019 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.",
"version": "Sites 9.0"
},
{
"_id": {
"$oid": "635fe2bc94436e1bc8257cef"
},
"hotfix_name": "CD_8.5.0.17389",
"modified_date": {
"$date": 1578324942247
},
"problem_description": "This is a hotfix for:\r\n- CRQ-17389 -Deployer performance fixes\r\n",
"readme_text": "Release Notes for Hotfix CRQ-17389\r\n==================================\r\n\r\nVersion:\r\n========\r\nThis cumulative hotfix is intended only for SDL Web 8.5.0 customers.\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n- CRQ-17389 -Deployer performance fixes\r\n\r\n\t\r\nInstallation:\r\n=============\r\nThis cumulative hotfix provides updated deployer standalone service roles \r\n\r\nFor all versions of the deployer roles\r\n------------\r\n1. Stop/uninstall the Service you are going to update\r\n2. Backup (or move) the folder where your standalone Service is located\r\n3. Uninstall the Service by opening a Powershell window in the \\bin folder of your service and running\r\n .\\uninstallService.ps1\r\n4. Navigate to the release\\\\service folder of this distribution\r\n5. Copy the \\standalone folder to the location where your original service was located\r\n6. Rename copied \\standalone folder to the name of your original service's folder\r\n7. Copy all files from \\config folder of your backup (see step #2) to \\config folder of a new service\r\n8. Copy custom jars (if you have any) from backup's \\services\\ folders to the same location in new service\r\n9. Install service by opening a Powershell window in in the \\bin folder of the new service and run .\\installService.ps1 \r\n\r\n\r\n\r\nDistributed roles:\r\n==================\r\n\r\ndeployer\t\tDeployer Service role\r\n\r\n\r\nDependencies:\r\n=============\r\nN/A\r\n\r\nFixed problems:\r\n===============\r\n- CRQ-17389 -Deployer performance fixes\r\n\r\n\r\n\r\nHotfix Description\r\n===========\r\n- Allow config of maxActive, maxIdle, initialSize for the State store\r\n- Allow maxTotal, MaxIdle, minIdle for the Redis client\r\n- Do NOT use jedis.keys() as per the documentation it's slow and says: \"Don't use it in your normal code.\". Mitigated by always prefixing with a key.\r\n\r\n\r\nDisclaimer:\r\n===========\r\n\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. \r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore \r\nshould only be installed if approved by Customer Support. Hotfixes should be replaced as soon as possible by the \r\nsubsequent patch release where the problem is fixed.\r\n\r\nCopyright 2015-2020 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2c094436e1bc8257d88"
},
"hotfix_name": "ECL_8.5.0.6402",
"modified_date": {
"$date": 1520347740626
},
"problem_description": "",
"readme_text": "Release Notes for Hotfix 6402\n\nVersion:\n\tThis hotfix is intended only for Tridion External Content Library 8.5 included in Tridion 8.5.\n\nProblem description:\n\tSearch for ECL assets in XPM cause Javascript error.\n\nHotfix description:\n\tFix javascript.\n\nInstallation:\n\t1.\tStop all Tridion Content Manager Service Host and IIS Service.\n\t2.\tMove the file Tridion.ExternalContentLibrary.DomainModel.dll located in the %WINDIR%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.ExternalContentLibrary.DomainModel\\v4.0_8.5.0.116__ddfc895746e5ee6b folder\n\t3.\tCopy the Tridion.ExternalContentLibrary.DomainModel.dll file from this hotfix to the %WINDIR%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.ExternalContentLibrary.DomainModel\\v4.0_8.5.0.116__ddfc895746e5ee6b folder\n\t4.\tTake a backup of the file %TRIDION_CM_HOME%\\web\\WebUI\\Editors\\TM\\Extensions\\Views\\SiteEditEditor.Library.js and replace it with the version included in this hotfix.\n\t5.\tOpen %TRIDION_CM_HOME%\\web\\WebUI\\WebRoot\\Configuration\\System.config in a text editor.\n\t\tLocate the Configuration/servicemodel/server node in the System.config file and increase the value of its 'modification' attribute to notify client browsers to update their cache.\n\t6.\tRestart the IIS Service and Tridion Content Manager Service Host.\n\nDistributed files:\n\tTridion.ExternalContentLibrary.DomainModel.dll (File Version 8.5.0.122)\n\tSiteEditEditor.Library.js\n\tReadme.txt (this file)\n\nFixes included:\n\tCRQ-6076: If ECL URI is too long, thumbnail path length can exceed windows limit of 260 characters.\n\nDependencies:\n\tN/A\n\nDisclaimer:\n\tHotfixes are released at the discretion of SDL Tridion based on technical complexity, customer business requirements and schedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by SDL Tridion Customer Support. Hotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\n\nCopyright (c) 2017 SDL Group.",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2bc94436e1bc8257cf7"
},
"hotfix_name": "CD_8.5.0.18753",
"modified_date": {
"$date": 1586169721964
},
"problem_description": "- Commit fails but deployer constantly retries.\r\n",
"readme_text": "Release Notes for Hotfix CRQ-18753\r\n=================================\r\n\r\nVersion:\r\n========\r\nThis cumulative hotfix is intended only for SDL Web 8.5.0 customers.\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n - CRQ-18753 - Commit fails but deployer constantly retries\r\n\r\nInstallation:\r\n=============\r\nThis cumulative hotfix provides updated standalone Deployer service roles.\r\n\r\nFor the Deployer Services\r\n------------\r\n1. Stop the Service you are going to update\r\n2. Backup (or move) the folder where your standalone Service is located\r\n3. Uninstall the Service by opening a Powershell window in the \\bin folder of your service and running\r\n .\\uninstallService.ps1\r\n4. Navigate to the release\\\\service folder of this distribution\r\n5. Copy the \\standalone folder to the location where your original service was located\r\n6. Rename copied \\standalone folder to the name of your original service's folder\r\n7. Copy all files from \\config folder of your backup (see step #2) to \\config folder of a new service\r\n8. Copy custom jars (if you have any) from backup's \\services\\ folders to the same location in new service\r\n9. Install service by opening a Powershell window in the \\bin folder of the new service and run .\\installService.ps1 \r\n\r\n\r\nDistributed roles:\r\n==================\r\ndeployer\tDeployer Service roles\r\n\r\nDependencies:\r\n=============\r\nN/A\r\n\r\nFixed problems:\r\n===============\r\n- CRQ-18753 - if TridionCommitStep fails - we get infinite retries on deployer package\r\n\r\nFixed infinite retries issue. Now it's limited to preconfigured retry count value.\r\n\t\r\n\r\nProblem Description\r\n-------------------\r\n- Commit fails but deployer constantly retries.\r\n\r\nHotfix Description\r\n-------------------\r\n- Fixed infinite retries issue.\r\n\r\nDisclaimer:\r\n===========\r\n\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. \r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore \r\nshould only be installed if approved by Customer Support. Hotfixes should be replaced as soon as possible by the \r\nsubsequent patch release where the problem is fixed.\r\n\r\nCopyright 2015-2019 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.\r\n",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2b194436e1bc8257b9f"
},
"hotfix_name": "CD_11.0.0.16907",
"modified_date": {
"$date": 1572868559319
},
"problem_description": "- There were some conflicts when saving keyword meta during deployment.\r\n",
"readme_text": "Release Notes for Hotfixes CRQ-16907\r\n=================================\r\n\r\nVersion:\r\n========\r\nThis cumulative hotfix is intended only for SDL Sites 9.0 customers.\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n - CRQ-16907 - Violation of PRIMARY KEY constraint 'PK_ITEMS'. Cannot insert duplicate key in object 'dbo.ITEMS'. The duplicate key value is (1, 34472, 438)\r\n\r\nInstallation:\r\n=============\r\n\r\nServices\r\n--------\r\n1. Stop relevant Service\r\n2. Backup (or move) a folder where your standalone Service is located\r\n3. Uninstall the relevant Service by opening a Powershell window in the \\bin of your service and run .\\uninstallService.ps1\r\n4. Navigate to the release\\ folder of this distribution\r\n5. Copy \\standalone folder to the location where your original service was located\r\n6. Rename copied \\standalone folder to the name of your original service's folder\r\n7. Copy all files from \\config folder of your backup (see step #2) to \\config folder of a new service\r\n8. Copy custom jars (if you have any) from backup's \\services\\folder to a same location of a new service\r\n9. Install service by opening a Powershell window in in the location \\bin of new service and run .\\installService.ps1\r\n\r\n\r\nDistributed roles:\r\n==================\r\ndeployer - Tridion Deployer\r\n\r\n\r\nFixed problems:\r\n===============\r\n - CRQ-16907 - Violation of PRIMARY KEY constraint 'PK_ITEMS'. Cannot insert duplicate key in object 'dbo.ITEMS'. The duplicate key value is (1, 34472, 438)\r\n\r\n\r\nProblem Description\r\n-------------------\r\n- There were some conflicts when saving keyword meta during deployment.\r\n\r\n\r\nHotfix Description\r\n-------------------\r\n- Fixed conflicts when saving keyword meta during deployment.\r\n\r\nDisclaimer:\r\n===========\r\n\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. \r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore \r\nshould only be installed if approved by Customer Support. Hotfixes should be replaced as soon as possible by the \r\nsubsequent patch release where the problem is fixed.\r\n\r\nCopyright 2015-2019 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.\r\n",
"version": "Sites 9.0"
},
{
"_id": {
"$oid": "635fe2bd94436e1bc8257d07"
},
"hotfix_name": "CD_8.5.0.3922",
"modified_date": {
"$date": 1490977806451
},
"problem_description": "Failed to publish a larger number of items that contain metadata due to the error \"ORA-00060: deadlock detected while waiting for resource\"\r\n",
"readme_text": "Release Notes for Hotfix CRQ-3922\r\n=================================\r\n \r\nVersion:\r\n========\r\nThis is cumulative hotfix and is intended only for SDL Web 8.5.0\r\n \r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n - CRQ-3922 Web 8.5 - Bulk publishing failing\r\n\r\n \r\nInstallation:\r\n=============\r\nThis cumulative hotfix provides updated services.\r\n \r\n \r\nFollowing services are updated - Deployer.\r\n \r\nAll Services\r\n-----------------------\r\n1. Stop the Service you are going to upgrade\r\n2. Backup (or move) a folder where your standalone Service is located\r\n3. Uninstall the Service by opening a Powershell window in the \\bin of your service and running .\\uninstallService.ps1\r\n4. Navigate to the release\\\\service folder of this distribution\r\n5. Copy \\standalone folder to the location where your original service was located\r\n6. Rename copied \\standalone folder to the name of your original service's folder\r\n7. Copy all files from \\config folder of your backup (see step #2) to \\config folder of a new service.\r\n8. Copy custom jars (if you have any) from backup's \\services\\folder to a same location of a new service\r\n9. Install service by opening a Powershell window in in the location \\bin of new service and run .\\installService.ps1\r\n \r\nDistributed roles:\r\n==================\r\ndeployer Deployer role\r\n \r\nDependencies:\r\n=============\r\n \r\nFixed problems:\r\n===============\r\n - CRQ-3922 Web 8.5 - Bulk publishing failing\r\n \r\nProblem Description\r\n-------------------\r\nFailed to publish a larger number of items that contain metadata due to the error \"ORA-00060: deadlock detected while waiting for resource\"\r\n \r\nHotfix Description\r\n-------------------\r\nReordered resources during publishing to avoid deadlock situations.\r\n \r\nDisclaimer:\r\n===========\r\n \r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/configuration and therefore should only be installed\r\nif approved by Customer Support. Hotfixes should be replaced as soon as possible by the subsequent patch release where the problem is fixed.\r\n \r\nCopyright 2015-2017 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2b194436e1bc8257b9b"
},
"hotfix_name": "CD_11.0.0.15330",
"modified_date": {
"$date": 1564042574071
},
"problem_description": "This is a hotfix for:\r\n- CRQ-15330 Content Service database connection pool size configurable\r\nInstallation\r\nThis hotfix provides updated roles for Content, Context, Discovery, Preview, UGC and the Deployer Service.\r\nFor all Services\r\n1. Stop relevant Service\r\n2. Backup (or move) a folder where your standalone Service is located\r\n3. Uninstall the relevant Service by opening a Powershell window in the \\bin of your service and run .\\uninstallService.ps1\r\n4. Navigate to the release\\ folder of this distribution\r\n5. Copy \\standalone folder to the location where your original service was located\r\n6. Rename copied \\standalone folder to the name of your original service's folder\r\n7. Copy and merge all files from \\config folder of your backup (see step #2) to \\config folder of a new service\r\n8. Copy custom jars (if you have any) from backup's \\services\\folder to a same location of a new service\r\n9. Install service by opening a Powershell window in in the location \\bin of new service and run .\\installService.ps1\r\nDistributed roles\r\ncontent - Content\r\ncontext - Context\r\ndeployer - Deployer\r\ndiscovery - Discovery\r\npreview - Preview\r\nugc - User Generated Content\r\nFixed problems\r\n- CRQ-15330 Content Service database connection pool size configurable\r\n",
"readme_text": "Release Notes for Hotfix CRQ-15330\r\n==================================\r\n\r\nVersion\r\n=======\r\nThis is intended only for SDL Sites 9.0. The layout build number 1053\r\n\r\n\r\nDescription\r\n===========\r\nThis is a hotfix for:\r\n- CRQ-15330 Content Service database connection pool size configurable\r\n\r\n\r\nInstallation\r\n============\r\nThis hotfix provides updated roles for Content, Context, Discovery, Preview, UGC and the Deployer Service.\r\n\r\nFor all Services\r\n----------------\r\n1. Stop relevant Service\r\n2. Backup (or move) a folder where your standalone Service is located\r\n3. Uninstall the relevant Service by opening a Powershell window in the \\bin of your service and run .\\uninstallService.ps1\r\n4. Navigate to the release\\ folder of this distribution\r\n5. Copy \\standalone folder to the location where your original service was located\r\n6. Rename copied \\standalone folder to the name of your original service's folder\r\n7. Copy and merge all files from \\config folder of your backup (see step #2) to \\config folder of a new service\r\n8. Copy custom jars (if you have any) from backup's \\services\\folder to a same location of a new service\r\n9. Install service by opening a Powershell window in in the location \\bin of new service and run .\\installService.ps1\r\n\r\n\r\nDistributed roles\r\n=================\r\ncontent - Content\r\ncontext - Context\r\ndeployer - Deployer\r\ndiscovery - Discovery\r\npreview - Preview\r\nugc - User Generated Content\r\n\r\n\r\nFixed problems\r\n==============\r\n- CRQ-15330 Content Service database connection pool size configurable\r\n\r\n\r\nHotfix Description\r\n==================\r\n-\r\n\r\n\r\nDisclaimer:\r\n===========\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/configuration and therefore should only be installed\r\nif approved by Customer Support. Hotfixes should be replaced as soon as possible by the subsequent patch release where the problem is fixed.\r\n\r\nCopyright \ufffd 2015-2018 SDL Group. All Rights Reserved.\r\n\r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.\r\n",
"version": "Sites 9.0"
},
{
"_id": {
"$oid": "635fe2c094436e1bc8257db5"
},
"hotfix_name": "\u0421D_8.5.0.17783",
"modified_date": {
"$date": 1581337783474
},
"problem_description": "",
"readme_text": "Release Notes for Hotfix CRQ-17783\n=================================\n\nVersion:\n========\nThis cumulative hotfix is intended only for SDL Tridion Sites 8.5 customers.\n\nDescription:\n============\nThis is a hotfix for:\n - CRQ-17783 Some of the records of execution table is not getting cleared\n\nInstallation:\n=============\nThis cumulative hotfix provides updated Deployer service role.\n\n\nFor the Web Deployer\n------------\n1. Stop the Service you are going to update\n2. Backup (or move) the folder where your standalone Service is located\n3. Uninstall the Service by opening a Powershell window in the \\bin folder of your service and running\n .\\uninstallService.ps1\n4. Navigate to the release\\\\service folder of this distribution\n5. Copy the \\standalone folder to the location where your original service was located\n6. Rename copied \\standalone folder to the name of your original service's folder\n7. Copy all files from \\config folder of your backup (see step #2) to \\config folder of a new service\n8. Copy custom jars (if you have any) from backup's \\services\\ folders to the same location in new service\n\n\nDistributed roles:\n==================\ndeployer Deployer Service role\n\n\nDependencies:\n=============\nN/A\n\nFixed problems:\n===============\n- CRQ-17783 Some of the records of execution table is not getting cleared even though deployer hotfix (CD_8.5.0.14838) Cron job is running. \n\n\nProblem Description\n-------------------\n- Records left in state store db after cron clean job\n\nHotfix Description\n-------------------\n- Fixed default start date initialisation for executions\n\nDisclaimer:\n===========\n\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. \nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore \nshould only be installed if approved by Customer Support. Hotfixes should be replaced as soon as possible by the \nsubsequent patch release where the problem is fixed.\n\nCopyright 2015-2020 SDL Group. All Rights Reserved.\n \nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.\n",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2bd94436e1bc8257d17"
},
"hotfix_name": "CD_8.5.0.6722",
"modified_date": {
"$date": 1508513859436
},
"problem_description": "- An error occurred when passing a HashMap values in renderParameters of getContent method which is belonging to ComponentPresentationAssembler.\r\n- Java tag ComponentLink with attribute textOnFail=\"true\" rendered with double a>\r\n",
"readme_text": "Release Notes for Hotfix CRQ-6720, CRQ-6722\r\n=================================\r\n\r\nVersion:\r\n========\r\nThis is cumulative hotfix and is intended only for SDL Web 8.5.0. The layout build number 1024.\r\n\r\nDescription:\r\n============\r\nThe hotfix include the following fixes: \r\n - CRQ-6720 HF for SRQ Error happened when using Broker RESTful API\r\n - CRQ-6722 Web8.5 ComponentLink does not work properly\r\n \r\nInstallation:\r\n=============\r\nThis cumulative hotfix provides updated services: api role.\r\n\r\nFor Rest Api Role\r\n---------------------------\r\n1. Stop your rest web application\r\n2. Backup it to safe location\r\n3. Delete jars/DLLs present in your web-app\r\n4. Copy new jars/DLLs from api\\rest folder of this HF to your web-app\r\n5. Restore any custom jars or DLLs from your backup\r\n6. Start web-application\r\n\r\n\r\nDistributed roles:\r\n==================\r\napi/rest Rest API Role\r\n\r\n\r\nFixed problems:\r\n===============\r\n - CRQ-6720 HF for SRQ Error happened when using Broker RESTful API\r\n - CRQ-6722 Web8.5 ComponentLink does not work properly\r\n \r\n \r\nProblem Description\r\n-------------------\r\n- An error occurred when passing a HashMap values in renderParameters of getContent method which is belonging to ComponentPresentationAssembler.\r\n- Java tag ComponentLink with attribute textOnFail=\"true\" rendered with double a>\r\n\r\n\r\nHotfix Description\r\n-------------------\r\n- Render parameters will pass from ComponentPresentationAssemblerImpl to GetComponentPresentationContentFunction\r\n- Fixed rendering logic for ComponentLink with attribute textOnFail=\"true\"\r\n\r\n\r\nDisclaimer:\r\n===========\r\n\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by Customer Support. Hotfixes should be replaced as soon as possible by the subsequent patch release where the problem is fixed.\r\n\r\nCopyright 2016-2017 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.\r\n",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2bb94436e1bc8257ceb"
},
"hotfix_name": "CD_8.5.0.16649",
"modified_date": {
"$date": 1571435457807
},
"problem_description": "This is a hotfix for:\r\n- CRQ-16649-CIS Content Service is crashing frequently\r\n",
"readme_text": "Release Notes for Hotfix CRQ-16649\r\n=================================\r\n\r\nVersion:\r\n========\r\nThis cumulative hotfix is intended only for SDL Web 8.5.0 customers.\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n\t- CRQ-16649-CIS Content Service is crashing frequently\r\n\r\n\t\r\nInstallation:\r\n=============\r\nThis cumulative hotfix provides updated standalone service roles \r\n\r\nFor all Services\r\n------------\r\n1. Stop/uninstall the Service you are going to update\r\n2. Backup (or move) the folder where your standalone Service is located\r\n3. Uninstall the Service by opening a Powershell window in the \\bin folder of your service and running\r\n .\\uninstallService.ps1\r\n4. Navigate to the release\\\\service folder of this distribution\r\n5. Copy the \\standalone folder to the location where your original service was located\r\n6. Rename copied \\standalone folder to the name of your original service's folder\r\n7. Copy all files from \\config folder of your backup (see step #2) to \\config folder of a new service\r\n8. Copy custom jars (if you have any) from backup's \\services\\ folders to the same location in new service\r\n9. Install service by opening a Powershell window in in the \\bin folder of the new service and run .\\installService.ps1 \r\n\r\n\r\n\r\nDistributed roles:\r\n==================\r\n\r\ncontent\t\tContent Service role\r\nsession\t\tSession-enabled Content Service role\r\n\r\n\r\nDependencies:\r\n=============\r\nN/A\r\n\r\nFixed problems:\r\n===============\r\n\t- CRQ-16649-CIS Content Service is crashing frequently\r\n\r\n\r\n\r\nHotfix Description\r\n===========\r\nAdded transient to fields to eliminate cyclic references\r\n\r\n\r\nDisclaimer:\r\n===========\r\n\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. \r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore \r\nshould only be installed if approved by Customer Support. Hotfixes should be replaced as soon as possible by the \r\nsubsequent patch release where the problem is fixed.\r\n\r\nCopyright 2015-2019 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2b994436e1bc8257c7d"
},
"hotfix_name": "CD_8.1.1.13176",
"modified_date": {
"$date": 1554213014974
},
"problem_description": "- Customer was experiencing \"An established connection was aborted by the software in your host machine\" errors\r\n",
"readme_text": "Release Notes for Hotfix CRQ-13176\r\n==================================\r\n\r\nVersion:\r\n========\r\nThis is cumulative hotfix and is intended only for SDL Web 8.1.1\r\n\r\nDescription:\r\n============\r\nThe hotfix include the following fixes: \r\n - CRQ-13176 An established connection was aborted by the software in your host machine\r\n \r\nInstallation:\r\n=============\r\nThis cumulative hotfix provides updated Deployer, Content, Caching, Context, Discovery, Preview, Session and UGC roles.\r\n\r\nFor all services:\r\n-----------------------\r\n1. Stop a standalone Service\r\n2. Backup (or move) a folder where your standalone Service is located\r\n3. Uninstall the Service by opening a Powershell window in the \\bin of your service and run .\\uninstallService.ps1\r\n4. Navigate to the release\\{rolename} folder of this distribution\r\n5. Copy \\standalone folder to the location where your original service was located\r\n6. Rename copied \\standalone folder to the name of your original service's folder\r\n7. Copy all files from \\config folder of your backup (see step #2) to \\config folder of a new service\r\n8. Copy custom jars (if you have any) from backup's \\services\\folder to a same location of a new service\r\n9. Install service by opening a Powershell window in in the location \\bin of new service and run .\\installService.ps1\r\n\r\n\r\nDistributed roles:\r\n==================\r\ndeployer\t\tDeployer Service role\r\ncontent\t\t\tContent Service role\r\ncaching\t\t\tCaching Service\r\ncid\t\t\t\tContextual Image Delivery Service\r\ndiscovery \t\tDiscovery Service\r\npreview \t\tPreview Service role\r\nsession\t\t\tSession Service role\r\nugc\t\t\t\tUser Generated Content Service\t\r\n\r\nFixed problems:\r\n===============\r\n - CRQ-13176 An established connection was aborted by the software in your host machine\r\n \r\n \r\nProblem Description\r\n-------------------\r\n- Customer was experiencing \"An established connection was aborted by the software in your host machine\" errors\r\n\r\nHotfix Description\r\n-------------------\r\n- Upgraded Tomcat version\r\n\r\nDisclaimer:\r\n===========\r\n\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by Customer Support. Hotfixes should be replaced as soon as possible by the subsequent patch release where the problem is fixed.\r\n\r\nCopyright 2015-2017 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.\r\n",
"version": "Web 8.1.1"
},
{
"_id": {
"$oid": "635fe2bc94436e1bc8257cf3"
},
"hotfix_name": "CD_8.5.0.18144",
"modified_date": {
"$date": 1582888027282
},
"problem_description": "This is a hotfix for:\r\n- CRQ-18144Deployer worker unable to load module\r\nInstallation\r\nThis cumulative hotfix provides updated standalone service roles \r\nFor all Services\r\n1. Stop/uninstall the Service you are going to update\r\n2. Backup (or move) the folder where your standalone Service is located\r\n3. Uninstall the Service by opening a Powershell window in the \\bin folder of your service and running\r\n.\\uninstallService.ps1\r\n4. Navigate to the release\\\\service folder of this distribution\r\n5. Copy the \\standalone folder to the location where your original service was located\r\n6. Rename copied \\standalone folder to the name of your original service's folder\r\n7. Copy all files from \\config folder of your backup (see step #2) to \\config folder of a new service (and any extensions)\r\n8. Copy custom jars (if you have any) from backup's \\services\\ folders to the same location in new service\r\n9. Install service by opening a Powershell window in in the \\bin folder of the new service and run .\\installService.ps1 \r\nDistributed roles\r\ndeployer\tDeployer Service roles\r\nDependencies\r\nN/A\r\nFixed problems\r\n- CRQ-18144Deployer worker unable to load module\r\n",
"readme_text": "Release Notes for Hotfix CRQ-18144\r\n==================================\r\n\r\nVersion\r\n=======\r\nThis cumulative hotfix is intended only for SDL Web 8.5.0 customers.\r\n\r\nDescription\r\n===========\r\nThis is a hotfix for:\r\n- CRQ-18144Deployer worker unable to load module\r\n\r\n\t\r\nInstallation\r\n============\r\nThis cumulative hotfix provides updated standalone service roles \r\n\r\nFor all Services\r\n----------------\r\n1. Stop/uninstall the Service you are going to update\r\n2. Backup (or move) the folder where your standalone Service is located\r\n3. Uninstall the Service by opening a Powershell window in the \\bin folder of your service and running\r\n .\\uninstallService.ps1\r\n4. Navigate to the release\\\\service folder of this distribution\r\n5. Copy the \\standalone folder to the location where your original service was located\r\n6. Rename copied \\standalone folder to the name of your original service's folder\r\n7. Copy all files from \\config folder of your backup (see step #2) to \\config folder of a new service (and any extensions)\r\n8. Copy custom jars (if you have any) from backup's \\services\\ folders to the same location in new service\r\n9. Install service by opening a Powershell window in in the \\bin folder of the new service and run .\\installService.ps1 \r\n\r\n\r\nDistributed roles\r\n=================\r\ndeployer\tDeployer Service roles\r\n\r\n\r\nDependencies\r\n============\r\nN/A\r\n\r\n\r\nFixed problems\r\n==============\r\n- CRQ-18144Deployer worker unable to load module\r\n\r\n\r\nHotfix Description\r\n===========\r\nChanged implementation for dealing with Configuration objects. These are now custom objects rather than w3c Nodes -\r\nwhich are not thread-safe.\r\n\r\n\r\nDisclaimer:\r\n===========\r\n\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. \r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore \r\nshould only be installed if approved by Customer Support. Hotfixes should be replaced as soon as possible by the \r\nsubsequent patch release where the problem is fixed.\r\n\r\nCopyright 2015-2020 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2ac94436e1bc8257a7a"
},
"hotfix_name": "CME_2011.1.2.86033",
"modified_date": {
"$date": 1376918658632
},
"problem_description": "IE8 Slow Typing/Missed Characters in Format Area Fields\r\n",
"readme_text": "Release Notes for Hotfix TT# 86033\r\n\r\nVersion:\r\nThis hotfix is intended for Tridion 2011 SP1 HR2\r\n\r\nProblem description:\r\nIE8 Slow Typing/Missed Characters in Format Area Fields\r\n\r\nHotfix description:\r\nAvoid cross-window calls causing delays and lost characters while editing item fields\r\n\r\nInstallation:\r\n\t1. Move or delete the file FormatArea.js located in the %TRIDION_HOME%\\web\\WebUI\\Editors\\CME\\Scripts\\Cme\\Commands\\ folder.\r\n\t2. Move or delete the file General.js located in the %TRIDION_HOME%\\web\\WebUI\\Editors\\CME\\Scripts\\Cme\\Commands\\ folder.\r\n\t3. Copy the file FormatArea.js from this hotfix to the %TRIDION_HOME%\\web\\WebUI\\Editors\\CME\\Scripts\\Cme\\Commands\\ folder.\r\n\t4. Copy the file General.js from this hotfix to the %TRIDION_HOME%\\web\\WebUI\\Editors\\CME\\Scripts\\Cme\\Commands\\ folder.\r\n\t5. Open %TRIDION_HOME%\\web\\WebUI\\WebRoot\\Configuration\\System.config file.\r\n\t6. Locate /Configuration/servicemodel/server node in System.config file and increase the value of its 'modification' attribute to notify client browsers to update their cache.\r\n\r\n\r\nDistributed files:\r\n- FormatArea.js\r\n- General.js\r\n- Readme.txt (this file)\r\n\r\n\r\nFixes included:\r\nn/a\r\n\r\n\r\nDependencies:\r\nn/a\r\n\r\n\r\nDisclaimer:\r\n\tHotfixes are released at the discretion of SDL based on technical complexity, customer business requirements and schedules.\r\n\tHotfixes are made and tested only for the described problem on a particular environment\\configuration and therefore should only be installed if approved by Customer Support of SDL Web Content Management Solutions Division.\r\n\tHotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright 2013 SDL PLC. All Rights Reserved. All company product or service names referenced herein are properties of their respective owners.",
"version": "2011 SP1 HR#2"
},
{
"_id": {
"$oid": "635fe2b994436e1bc8257c98"
},
"hotfix_name": "CD_8.1.1.3682",
"modified_date": {
"$date": 1504275768579
},
"problem_description": "- CIL.NET does not appear to be respecting 'log-rolling' and 'log-max-log-size' values in the Web.config of the Web Application\r\n",
"readme_text": "Release Notes for Hotfix CRQ-3682\r\n=================================\r\n\r\nVersion:\r\n========\r\nThis is cumulative hotfix and is intended only for SDL Web 8.\r\n\r\nDescription:\r\n============\r\nThe hotfix include the following fixes: \r\n - CRQ-3682 CIL.NET logging issue\r\n \r\nInstallation:\r\n=============\r\nThis cumulative hotfix provides updated api service.\r\n\r\nREST API\r\n--------------\r\n1. Stop your web application.\r\n2. Replace existing .Net API libraries with latest ones.\r\n3. Set new configuration property 'log-rolling-count' in Web.config within 'appSettings' section. It's optional, if not set - 9 is used. Example: .\r\n4. Restart web application.\r\n\r\nDistributed roles:\r\n==================\r\napi\t\t\tContent Delivery API role (rest)\r\n\r\nFixed problems:\r\n===============\r\n - CRQ-3682 CIL.NET logging issue\r\n \r\nProblem Description\r\n-------------------\r\n- CIL.NET does not appear to be respecting 'log-rolling' and 'log-max-log-size' values in the Web.config of the Web Application\r\n\r\nHotfix Description\r\n-------------------\r\n- Fixed by implementing log rolling. A new optional setting 'log-rolling-count' in Web.config is now available. This property is optional and if it's not set - default value 9 is used.\r\n Example: \r\n\r\nDisclaimer:\r\n===========\r\n\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by Customer Support. Hotfixes should be replaced as soon as possible by the subsequent patch release where the problem is fixed.\r\n\r\nCopyright 2015-2016 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.",
"version": "Web 8.1.1"
},
{
"_id": {
"$oid": "635fe2ab94436e1bc8257a4a"
},
"hotfix_name": "CM_2011.1.1.82260",
"modified_date": {
"$date": 1359725992721
},
"problem_description": "IE8 Slow Typing/Missed Characters in Format Area Fields\r\n",
"readme_text": "Release Notes for Hotfix TT# 82260\r\n\r\nVersion:\r\nThis hotfix is intended for Tridion 2011 SP1 HR1\r\n\r\nProblem description:\r\nIE8 Slow Typing/Missed Characters in Format Area Fields\r\n\r\nHotfix description:\r\nAvoid cross-window calls causing delays and lost characters while editing item fields\r\n\r\nInstallation:\r\n 1. Move or delete the file FormatArea.js located in the %TRIDION_HOME%\\web\\WebUI\\Editors\\CME\\Scripts\\Cme\\Commands\\ folder.\r\n 2. Move or delete the file General.js located in the %TRIDION_HOME%\\web\\WebUI\\Editors\\CME\\Scripts\\Cme\\Commands\\ folder.\r\n 3. Copy the file FormatArea.js from this hotfix to the %TRIDION_HOME%\\web\\WebUI\\Editors\\CME\\Scripts\\Cme\\Commands\\ folder.\r\n 4. Copy the file General.js from this hotfix to the %TRIDION_HOME%\\web\\WebUI\\Editors\\CME\\Scripts\\Cme\\Commands\\ folder.\r\n 5. Open %TRIDION_HOME%\\web\\WebUI\\WebRoot\\Configuration\\System.config file.\r\n 6. Locate /Configuration/servicemodel/server node in Sytem.config file and increase the value of its 'modification' attribute to notify client browsers to update their cache.\r\n\r\n\r\nDistributed files:\r\n- FormatArea.js\r\n- General.js\r\n- Readme.txt (this file)\r\n\r\n\r\nFixes included:\r\nn/a\r\n\r\n\r\nDependencies:\r\nn/a\r\n\r\n\r\nDisclaimer:\r\nHotfixes are released at the discretion of SDL based on technical complexity, customer business requirements and schedules.\r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by SDL Customer Support.\r\nHotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright 2012 SDL PLC. All Rights Reserved. All company product or service names referenced herein are properties of their respective owners.",
"version": "2011 SP1 HR#1"
},
{
"_id": {
"$oid": "635fe2b994436e1bc8257c90"
},
"hotfix_name": "CD_8.1.1.2889",
"modified_date": {
"$date": 1481053908494
},
"problem_description": ".NET CIL is missing an absolute cache expiration setting.\r\n",
"readme_text": "Release Notes for Hotfix CRQ-2889\r\n=================================\r\n\r\nVersion:\r\n========\r\nThis is cumulative hotfix and is intended only for SDL Web 8.1.1\r\nThe hotfix include the following fixes: \r\n- CRQ-2889 Service Caching is never flushing cache\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n- CRQ-2889 Service Caching is never flushing cache\r\n\r\nInstallation:\r\n=============\r\nThis cumulative hotfix provides updated .NET API CIL artifacts.\r\n\r\nCD APIs\r\n-------\r\n\tREST:\r\n\t\t1. [.NET] - update [.NET] artifacts from release\\api\\rest\\dotNet\\bin folder.\r\n\t\t2. [.NET] - update [.NET] artifacts from release\\session\\extension-web\\rest\\dotNet\\bin folder.\r\n\r\n\r\nDistributed roles:\r\n==================\r\napi Content Delivery API rest role (.NET only)\r\nsession\t\t\t\t\tSession Enabled Content Service Web Extension (.NET only)\r\n\r\nDependencies:\r\n=============\r\n\r\n\r\nFixed problems:\r\n===============\r\n- CRQ-2889 Service Caching is never flushing cache\r\n\r\nProblem Description\r\n-------------------\r\n.NET CIL is missing an absolute cache expiration setting.\r\n\r\nHotfix Description\r\n-------------------\r\nAdded code to support configuring absolute cache expiration times in Web.config. For example:\r\n\r\n\t \r\n\t\t \r\n\t\t \r\n\t \r\n\r\nDisclaimer:\r\n===========\r\n\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/configuration and therefore should only be installed\r\nif approved by Customer Support. Hotfixes should be replaced as soon as possible by the subsequent patch release where the problem is fixed.\r\n\r\nCopyright 2015-2016 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.\r\n",
"version": "Web 8.1.1"
},
{
"_id": {
"$oid": "635fe2aa94436e1bc82579f1"
},
"hotfix_name": "CM_2011.1.0.77763",
"modified_date": {
"$date": 1332322032679
},
"problem_description": "IE8 Slow Typing/Missed Characters in Format Area Fields\r\n",
"readme_text": "Release Notes for Hotfix TT# 77763\r\n\r\nVersion:\r\nThis hotfix is intended for Tridion 2011 SP1.\r\n\r\nProblem description:\r\nIE8 Slow Typing/Missed Characters in Format Area Fields\r\n\r\nHotfix description:\r\nAvoid cross-window calls causing delays and lost characters while editing item fields\r\n\r\nInstallation:\r\n 1. Move or delete the file Item.js located in the %TRIDION_HOME%\\web\\WebUI\\Editors\\CME\\Views\\ folder.\r\n 2. Move or delete the file RibbonToolbar.js located in the %TRIDION_HOME%\\web\\WebUI\\Core\\Controls\\RibbonToolbar\\ folder.\r\n 3. Copy the file Item.js from this hotfix to the %TRIDION_HOME%\\web\\WebUI\\Editors\\CME\\Views\\ folder.\r\n 4. Copy the file RibbonToolbar.js from this hotfix to the %TRIDION_HOME%\\web\\WebUI\\Core\\Controls\\RibbonToolbar\\ folder.\r\n 5. Open %TRIDION_HOME%\\web\\WebUI\\WebRoot\\Configuration\\System.config file.\r\n 6. Locate /Configuration/servicemodel/server node in Sytem.config file and increase the value of its 'modification' attribute to notify client browsers to update their cache.\r\n\r\n\r\nDistributed files:\r\n- Item.js\r\n- RibbonToolbar.js\r\n- Readme.txt (this file)\r\n\r\n\r\nFixes included:\r\nn/a\r\n\r\n\r\nDependencies:\r\nn/a\r\n\r\n\r\nDisclaimer:\r\nHotfixes are released at the discretion of SDL based on technical complexity, customer business requirements and schedules.\r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by Customer Support of SDL Web Content Management Solutions Division.\r\nHotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright 2011 SDL PLC. All Rights Reserved. All company product or service names referenced herein are properties of their respective owners.",
"version": "2011 SP1"
},
{
"_id": {
"$oid": "635fe2bb94436e1bc8257cd7"
},
"hotfix_name": "CD_8.5.0.11360",
"modified_date": {
"$date": 1544716433027
},
"problem_description": "Deploying legacy roles such as preview, content service as .war file in Weblogic result in the error\r\n",
"readme_text": "Release Notes for Hotfix CRQ-11360\r\n=================================\r\n \r\nVersion:\r\n========\r\nThis is cumulative hotfix and is intended only for SDL Web 8.5\r\n \r\nDescription:\r\n============\r\nThe hotfix include the following fixes:\r\n - CRQ-11360 java.nio.file.FileSystemNotFoundException: Provider \"zip\" not installed\r\n \r\nInstallation:\r\n=============\r\nThis cumulative hotfix provides updated services: \r\n- content\r\n- deployer\r\n- discovery\r\n- preview\r\n- session\r\n- ugc\r\n \r\nFor micro services deployed as war\r\n---------------------------\r\n1. Stop your web application\r\n2. Backup it to a safe location\r\n3. Delete jars present in your web-app\r\n4. In a provided hotfix distributable navigate to a role you are going to install or update\r\n5. Go \\webapp\\war folder and copy *.war file\r\n6. Follow the documentation of your Web Application Server to deploy a war \r\n7. Restore your configuration files and any of custom jars you had\r\n6. Start your web-application\r\n \r\n \r\nFixed problems:\r\n===============\r\n - CRQ-11360 java.nio.file.FileSystemNotFoundException: Provider \"zip\" not \r\n \r\nProblem Description\r\n-------------------\r\nDeploying legacy roles such as preview, content service as .war file in Weblogic result in the error\r\n \r\nHotfix Description\r\n-------------------\r\nFixed issue related to finding resources inside web application servers\r\n \r\n \r\nDisclaimer:\r\n===========\r\n \r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by Customer Support. Hotfixes should be replaced as soon as possible by the subsequent patch release where the problem is fixed.\r\n \r\nCopyright \u00a9 2016-2018 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2b294436e1bc8257be6"
},
"hotfix_name": "CD_11.1.0.18528",
"modified_date": {
"$date": 1584107739240
},
"problem_description": "- Large number of tokens in ish conditions causes failure.\r\n",
"readme_text": "Release Notes for Hotfixes CRQ-18528\r\n=================================\r\n\r\nVersion:\r\n========\r\nThis cumulative hotfix is intended only for SDL Sites 9.1 customers.\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n - CRQ-18528 - Large number of tokens in ish conditions causes failure. Note that this hotfix does not contain Service itself. It includes add-on service extension for content service.\r\n\r\nInstallation:\r\n=============\r\n\r\nServices\r\n--------\r\n1. Stop relevant Service.\r\n2. Go to Service folder and cleanup 'extensions' folder.\r\n3. Uninstall the relevant Service by opening a Powershell window in the \\bin of your service and run .\\uninstallService.ps1.\r\n4. Go to add-on service interface and update udp-cis-ish-content-extension with new one provided within this hotfix.\r\n5. Install service by opening a Powershell window in in the location \\bin of new service and run .\\installService.ps1.\r\n\r\n\r\nDistributed roles:\r\n==================\r\ncontent - Tridion Content\r\n\r\n\r\nFixed problems:\r\n===============\r\n - CRQ-18528 - Large number of tokens in ish conditions causes failure. Regex pattern was optimized.\r\n\r\n\r\nProblem Description\r\n-------------------\r\n- Large number of tokens in ish conditions causes failure.\r\n\r\n\r\nHotfix Description\r\n-------------------\r\n- Optimized regex pattern.\r\n\r\nDisclaimer:\r\n===========\r\n\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. \r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore \r\nshould only be installed if approved by Customer Support. Hotfixes should be replaced as soon as possible by the \r\nsubsequent patch release where the problem is fixed.\r\n\r\nCopyright 2015-2020 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.\r\n",
"version": "Sites 9.1"
},
{
"_id": {
"$oid": "635fe2c094436e1bc8257d82"
},
"hotfix_name": "ECL_8.5.0.11098",
"modified_date": {
"$date": 1536609280278
},
"problem_description": "",
"readme_text": "Release Notes for Hotfix 11098\n\nVersion:\n\tThis hotfix is intended only for Tridion External Content Library 8.5 included in Tridion 8.5.\n\nProblem description:\n\tSaving ECL component to modify metadata throws error.\n\nHotfix description:\n\tFix ECL item save code.\n\nInstallation:\n\t1.\tStop all Tridion Content Manager Service Host and IIS Service.\n\t2.\tTake a backup of the file %TRIDION_CM_HOME%\\web\\WebUI\\Editors\\ExternalContentLibrary\\Views\\Tabs\\ExternalMetadata\\ExternalMetadata.js and replace it with the version included in this hotfix.\n\t3.\tTake a backup of the file %TRIDION_CM_HOME%\\web\\WebUI\\Editors\\ExternalContentLibrary\\Views\\Popups\\ExternalMetadata\\ExternalMetadata.aspx.js and replace it with the version included in this hotfix.\n\t4.\tOpen %TRIDION_CM_HOME%\\web\\WebUI\\WebRoot\\Configuration\\System.config in a text editor.\n\t\tLocate the Configuration/servicemodel/server node in the System.config file and increase the value of its 'modification' attribute to notify client browsers to update their cache.\n\t5.\tRestart the IIS Service and Tridion Content Manager Service Host.\n\nDistributed files:\n\tSiteEditEditor.Library.js\n\tExternalMetadata.aspx.js\n\tReadme.txt (this file)\n\nFixes included:\n\tN/A\n\nDependencies:\n\tN/A\n\nDisclaimer:\n\tHotfixes are released at the discretion of SDL Tridion based on technical complexity, customer business requirements and schedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by SDL Tridion Customer Support. Hotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\n\nCopyright (c) 2018 SDL Group.",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2be94436e1bc8257d2d"
},
"hotfix_name": "CL_8.5.0.3913",
"modified_date": {
"$date": 1490779774791
},
"problem_description": "LDAP Extended support verification check results in an exception if the LDAP source isnt exposing the supported extension listing.\r\n",
"readme_text": "Release Notes for Hotfix CRQ-3913\r\n\r\nVersion:\r\nThis hotfix is intended for Tridion Common Library 8.5.0.60\r\n\r\nProblem description:\r\nLDAP Extended support verification check results in an exception if the LDAP source isnt exposing the supported extension listing.\r\n\r\nHotfix description:\r\nTridion will now use the default value in case extended support isnt available.\r\n\r\nInstallation:\r\n 1. Stop all TCM Services, IIS Service, and the TCM COM+ Application.\r\n 2. Remove the file Tridion.Security.dll located in the %windir%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.Security\\v4.0_8.5.0.60__ddfc895746e5ee6b folder.\r\n 3. Copy the file Tridion.Security.dll from this hotfix to the %windir%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.Security\\v4.0_8.5.0.60__ddfc895746e5ee6b folder.\r\n 4. Restart the IIS Service, TCM Services and TCM COM+ Application.\r\n\r\nDistributed files:\r\n Tridion.Security.dll (file version 8.5.0.63)\r\n \r\nFixes included:\r\n NA\r\n\r\nDependencies:\r\n NA\r\n\r\nDisclaimer:\r\nHotfixes are released at the discretion of SDL based on technical complexity, customer business requirements and schedules.\r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by Customer Support of SDL Web Content Management Solutions Division.\r\nHotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright 2017 SDL PLC. All Rights Reserved. All company product or service names referenced herein are properties of their respective owners.\r\n",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2b194436e1bc8257bab"
},
"hotfix_name": "CD_11.0.1.21656",
"modified_date": {
"$date": 1605866734297
},
"problem_description": "This is a hotfix for:\r\n- CRQ-21656 - After applying CD_11.0.0.19562, SI4T startup failure for Deployer\r\n- CRQ-21847 - Deployer Failing on Committing Deployment - com.tridion.storage.Publication cannot be cast to com.tridion.storage.ComponentMeta\r\n- CRQ-21434 - Database issue after applying Surrogate key fix 9.0 \r\n",
"readme_text": "Release Notes for Hotfixes CRQ-21656 and CRQ-21847 \r\n=================================\r\n\r\nVersion:\r\n========\r\nThis cumulative hotfix is intended only for SDL Sites 9 customers.\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n - CRQ-21656 - After applying CD_11.0.0.19562, SI4T startup failure for Deployer\r\n - CRQ-21847 - Deployer Failing on Committing Deployment - com.tridion.storage.Publication cannot be cast to com.tridion.storage.ComponentMeta\r\n - CRQ-21434 - Database issue after applying Surrogate key fix 9.0 \r\n\r\nInstallation:\r\n=============\r\n\r\nServices\r\n--------\r\n1. Stop relevant Service\r\n2. Backup (or move) a folder where your standalone Service is located\r\n3. Uninstall the relevant Service by opening a Powershell window in the \\bin of your service and run .\\uninstallService.ps1\r\n4. Navigate to the release\\ folder of this distribution\r\n5. Copy \\standalone folder to the location where your original service was located\r\n6. Rename copied \\standalone folder to the name of your original service's folder\r\n7. Copy all files from \\config folder of your backup (see step #2) to \\config folder of a new service\r\n8. Copy custom jars (if you have any) from backup's \\services\\folder to a same location of a new service\r\n9. Install service by opening a Powershell window in in the location \\bin of new service and run .\\installService.ps1\r\n\r\nDatabase:\r\n---------\r\n1. Copy directories to a convenient location.\r\n2. Use ps1 scripts to perform content datastore upgrade or install as needed.\r\n\r\n\r\nDistributed roles:\r\n==================\r\napi Content Delivery API role\r\ncaching Cache Channel Service\r\ncid Contextual Image Delivery role\r\ncontent Content Service role\r\ncontext Context Service role\r\ndeployer Deployer role\r\ndiscovery Discovery service role\r\npreview Preview service role\r\nsession Session service role\r\nugc/community-service UGC Community Service role\r\nugc/moderation-service UGC Moderation Service role\r\n\r\n\r\nDisclaimer:\r\n===========\r\n\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. \r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore \r\nshould only be installed if approved by Customer Support. Hotfixes should be replaced as soon as possible by the \r\nsubsequent patch release where the problem is fixed.\r\n\r\nCopyright \u00a9 2015-2020 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.\r\n",
"version": "Sites 9.0"
},
{
"_id": {
"$oid": "635fe2ad94436e1bc8257ad3"
},
"hotfix_name": "CL_7.1.0.52.88703",
"modified_date": {
"$date": 1428916461567
},
"problem_description": "LDAP Extended support verification check results in an exception if the LDAP source isnt exposing the supported extension listing.\r\n",
"readme_text": "Release Notes for Hotfix TT88703\r\n\r\nVersion:\r\nThis hotfix is intended for Tridion Common Library 7.1.0.52 \r\n\r\nProblem description:\r\nLDAP Extended support verification check results in an exception if the LDAP source isnt exposing the supported extension listing.\r\n\r\nHotfix description:\r\nTridion will now use the default value in case extended support isnt available.\r\n\r\nInstallation:\r\n 1. Stop all TCM Services, IIS Service, and the TCM COM+ Application.\r\n 2. Remove the file Tridion.Security.dll located in the %windir%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.Security\\v4.0_7.1.0.52__ddfc895746e5ee6b folder.\r\n 3. Copy the file Tridion.Security.dll from this hotfix to the %windir%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.Security\\v4.0_7.1.0.52__ddfc895746e5ee6b folder.\r\n 4. Restart the IIS Service, TCM Services and TCM COM+ Application.\r\n\r\nDistributed files:\r\n Tridion.Security.dll (file version 7.1.0.53)\r\n \r\nFixes included:\r\n NA\r\n\r\nDependencies:\r\n NA\r\n\r\nDisclaimer:\r\nHotfixes are released at the discretion of SDL based on technical complexity, customer business requirements and schedules.\r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by Customer Support of SDL Web Content Management Solutions Division.\r\nHotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright 2015 SDL PLC. All Rights Reserved. All company product or service names referenced herein are properties of their respective owners.\r\n",
"version": "2013 SP1"
},
{
"_id": {
"$oid": "635fe2ae94436e1bc8257b26"
},
"hotfix_name": "CL_7.1.0.52.88703",
"modified_date": {
"$date": 1428916461567
},
"problem_description": "LDAP Extended support verification check results in an exception if the LDAP source isnt exposing the supported extension listing.\r\n",
"readme_text": "Release Notes for Hotfix TT88703\r\n\r\nVersion:\r\nThis hotfix is intended for Tridion Common Library 7.1.0.52 \r\n\r\nProblem description:\r\nLDAP Extended support verification check results in an exception if the LDAP source isnt exposing the supported extension listing.\r\n\r\nHotfix description:\r\nTridion will now use the default value in case extended support isnt available.\r\n\r\nInstallation:\r\n 1. Stop all TCM Services, IIS Service, and the TCM COM+ Application.\r\n 2. Remove the file Tridion.Security.dll located in the %windir%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.Security\\v4.0_7.1.0.52__ddfc895746e5ee6b folder.\r\n 3. Copy the file Tridion.Security.dll from this hotfix to the %windir%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.Security\\v4.0_7.1.0.52__ddfc895746e5ee6b folder.\r\n 4. Restart the IIS Service, TCM Services and TCM COM+ Application.\r\n\r\nDistributed files:\r\n Tridion.Security.dll (file version 7.1.0.53)\r\n \r\nFixes included:\r\n NA\r\n\r\nDependencies:\r\n NA\r\n\r\nDisclaimer:\r\nHotfixes are released at the discretion of SDL based on technical complexity, customer business requirements and schedules.\r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by Customer Support of SDL Web Content Management Solutions Division.\r\nHotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright 2015 SDL PLC. All Rights Reserved. All company product or service names referenced herein are properties of their respective owners.\r\n",
"version": "2013 SP1 HR#1"
},
{
"_id": {
"$oid": "635fe2ad94436e1bc8257ad2"
},
"hotfix_name": "CL_7.1.0.52.3995",
"modified_date": {
"$date": 1444322228174
},
"problem_description": "\"An operation error occurred\" when LDAP search response contains a LDAP referral\r\n",
"readme_text": "Release Notes for Hotfix SRQ-3995\r\n\r\nVersion:\r\nThis hotfix is intended for Tridion Common Library 7.1.0.52 \r\n\r\nProblem description:\r\n\"An operation error occurred\" when LDAP search response contains a LDAP referral\r\n\r\nHotfix description:\r\nChasing of referred server is implemented if response contains 0 entries, but Referrer has been provided instead.\r\n\r\nInstallation:\r\n 1. Stop all TCM Services, IIS Service, and the TCM COM+ Application.\r\n 2. Remove the file Tridion.Security.dll located in the %windir%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.Security\\v4.0_7.1.0.52__ddfc895746e5ee6b folder.\r\n 3. Copy the file Tridion.Security.dll from this hotfix to the %windir%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.Security\\v4.0_7.1.0.52__ddfc895746e5ee6b folder.\r\n 4. Restart the IIS Service, TCM Services and TCM COM+ Application.\r\n\r\nDistributed files:\r\n Tridion.Security.dll (file version 7.1.0.53)\r\n Readme.txt (this file)\r\n \r\nFixes included:\r\n 88703\r\n\r\nDependencies:\r\n NA\r\n\r\nDisclaimer:\r\nHotfixes are released at the discretion of SDL based on technical complexity, customer business requirements and schedules.\r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by Customer Support of SDL Web Content Management Solutions Division.\r\nHotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright 2015 SDL PLC. All Rights Reserved. All company product or service names referenced herein are properties of their respective owners.\r\n",
"version": "2013 SP1"
},
{
"_id": {
"$oid": "635fe2ae94436e1bc8257b25"
},
"hotfix_name": "CL_7.1.0.52.3995",
"modified_date": {
"$date": 1444322228174
},
"problem_description": "\"An operation error occurred\" when LDAP search response contains a LDAP referral\r\n",
"readme_text": "Release Notes for Hotfix SRQ-3995\r\n\r\nVersion:\r\nThis hotfix is intended for Tridion Common Library 7.1.0.52 \r\n\r\nProblem description:\r\n\"An operation error occurred\" when LDAP search response contains a LDAP referral\r\n\r\nHotfix description:\r\nChasing of referred server is implemented if response contains 0 entries, but Referrer has been provided instead.\r\n\r\nInstallation:\r\n 1. Stop all TCM Services, IIS Service, and the TCM COM+ Application.\r\n 2. Remove the file Tridion.Security.dll located in the %windir%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.Security\\v4.0_7.1.0.52__ddfc895746e5ee6b folder.\r\n 3. Copy the file Tridion.Security.dll from this hotfix to the %windir%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.Security\\v4.0_7.1.0.52__ddfc895746e5ee6b folder.\r\n 4. Restart the IIS Service, TCM Services and TCM COM+ Application.\r\n\r\nDistributed files:\r\n Tridion.Security.dll (file version 7.1.0.53)\r\n Readme.txt (this file)\r\n \r\nFixes included:\r\n 88703\r\n\r\nDependencies:\r\n NA\r\n\r\nDisclaimer:\r\nHotfixes are released at the discretion of SDL based on technical complexity, customer business requirements and schedules.\r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by Customer Support of SDL Web Content Management Solutions Division.\r\nHotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright 2015 SDL PLC. All Rights Reserved. All company product or service names referenced herein are properties of their respective owners.\r\n",
"version": "2013 SP1 HR#1"
},
{
"_id": {
"$oid": "635fe2b994436e1bc8257c89"
},
"hotfix_name": "CD_8.1.1.2347",
"modified_date": {
"$date": 1471430509773
},
"problem_description": "CIL - Tridion.ContentDelivery.Meta.CustomMeta.NameValues return value is incorrect for multivalue fields.\r\n",
"readme_text": "Release Notes for Hotfix CRQ-2347\r\n=================================\r\n\r\nVersion:\r\n========\r\nThis is cumulative hotfix and is intended only for SDL Web 8.1.1\r\nThe hotfix include the following fixes: \r\n - CRQ-2347 CIL - Tridion.ContentDelivery.Meta.CustomMeta.NameValues return value is incorrect for multivalue fields\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n - CRQ-2347 CIL - Tridion.ContentDelivery.Meta.CustomMeta.NameValues return value is incorrect for multivalue fields\r\n\r\nInstallation:\r\n=============\r\nThis cumulative hotfix provides updated .NET api artifacts for CD and UGC.\r\n\r\nCD API's\r\n--------\r\n\tREST:\r\n\t\t1. [.NET] - update [.NET] artifacts from release\\api\\rest\\dotNet\\bin folder.\r\n\r\n\r\n UGC Extension:\r\n\t\t1. [.NET] - update [.NET] artifacts from release\\ugc\\extension-web\\rest\\dotNet\\bin\r\n \r\nDistributed roles:\r\n==================\r\napi Content Delivery API role\r\nugc/extension-web\t\t UGC Extension role\r\n\r\nDependencies:\r\n=============\r\n\r\n\r\nFixed problems:\r\n===============\r\n- CRQ-2347\r\n\r\nProblem Description\r\n-------------------\r\nCIL - Tridion.ContentDelivery.Meta.CustomMeta.NameValues return value is incorrect for multivalue fields.\r\n\r\nHotfix Description\r\n-------------------\r\nFixed.\r\n\r\nDisclaimer:\r\n===========\r\n\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/configuration and therefore should only be installed\r\nif approved by Customer Support. Hotfixes should be replaced as soon as possible by the subsequent patch release where the problem is fixed.\r\n\r\nCopyright 2015-2016 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.\r\n",
"version": "Web 8.1.1"
},
{
"_id": {
"$oid": "635fe2b194436e1bc8257ba1"
},
"hotfix_name": "CD_11.0.0.17103",
"modified_date": {
"$date": 1574433332650
},
"problem_description": "This is a hotfix for:\r\n- CRQ-17103 New Sites 9.0 - inprocess api to load the broker content using TRIDION_HOME environment variable to load the config and lib folders are not working\r\n",
"readme_text": "Release Notes for Hotfix CRQ-17103\r\n=================================\r\n\r\nVersion:\r\n========\r\nThis cumulative hotfix is intended only for SDL Tridion Sites 9.5 customers.\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n\t- CRQ-17103 New Sites 9.0 - inprocess api to load the broker content using TRIDION_HOME environment variable to load the config and lib folders are not working\r\n\r\nInstallation:\r\n=============\r\nThis cumulative hotfix provides updated in-process api roles\r\n\r\n\r\nFor the API Roles\r\n---\r\n1. Stop your web application\r\n2. Back it up to safe location\r\n3. Delete DDLs present in your web-app\r\n4. Copy new DLLs from the api folder of this hotfix to your web-app\r\n5. Restore any custom jars or DLLs from your backup\r\n6. Restart the web-application\r\n\r\nDistributed roles:\r\n==================\r\n\r\napi in-process dotnet\r\n\r\n\r\nDependencies:\r\n=============\r\nnone\r\n\r\nFixed problems:\r\n===============\r\n\t- CRQ-17103 New Sites 9.0 - inprocess api to load the broker content using TRIDION_HOME environment variable to load the config and lib folders are not working\r\n\r\n\r\nHotfix Description\r\n===========\r\n- Fixed issue with validating TRIDION_HOME\r\n\r\nDisclaimer:\r\n===========\r\n\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. \r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore \r\nshould only be installed if approved by Customer Support. Hotfixes should be replaced as soon as possible by the \r\nsubsequent patch release where the problem is fixed.\r\n\r\nCopyright 2015-2019 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.",
"version": "Sites 9.0"
},
{
"_id": {
"$oid": "635fe2a994436e1bc82579e5"
},
"hotfix_name": "CL_6.1.0.25.85378",
"modified_date": {
"$date": 1369405173169
},
"problem_description": "LDAP Extended support verification check results in an exception if the LDAP source isnt exposing the supported extension listing.\r\n",
"readme_text": "Release Notes for Hotfix TT85378\r\n\r\nVersion:\r\nThis hotfix is intended for Tridion Common Library 6.1.0.25 \r\n\r\nProblem description:\r\nLDAP Extended support verification check results in an exception if the LDAP source isnt exposing the supported extension listing.\r\n\r\nHotfix description:\r\nTridion will now use the default value in case extended support isnt available.\r\n\r\nInstallation:\r\n 1. Stop all TCM Services, IIS Service, and the TCM COM+ Application.\r\n 2. Remove the file Tridion.Security.dll located in the %windir%\\assembly\\GAC_MSIL\\Tridion.Security\\6.1.0.25__ddfc895746e5ee6b folder.\r\n 3. Copy the file Tridion.Security.dll from this hotfix to the %windir%\\assembly\\GAC_MSIL\\Tridion.Security\\6.1.0.25__ddfc895746e5ee6b folder.\r\n 4. Restart the IIS Service, TCM Services and TCM COM+ Application.\r\n\r\nDistributed files:\r\n Tridion.Security.dll (file version 6.1.0.26)\r\n \r\nFixes included:\r\n NA\r\n\r\nDependencies:\r\n NA\r\n\r\nDisclaimer:\r\nHotfixes are released at the discretion of SDL based on technical complexity, customer business requirements and schedules.\r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by Customer Support of SDL Web Content Management Solutions Division.\r\nHotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright 2013 SDL PLC. All Rights Reserved. All company product or service names referenced herein are properties of their respective owners.",
"version": "2011 SP1"
},
{
"_id": {
"$oid": "635fe2bb94436e1bc8257ce8"
},
"hotfix_name": "CD_8.5.0.15038",
"modified_date": {
"$date": 1561998038558
},
"problem_description": "- It was not possible to access the OData parameters (including query string parameters) from a custom TagRenderer. \r\nThe TransformContext argument passed to doStartTag and doEndTag would only have a single, empty $expand variable when expanding a section such as PageContent.\r\n",
"readme_text": "Release Notes for Hotfixes CRQ-15038\r\n=================================\r\n\r\nVersion:\r\n========\r\nThis hotfix is intended only for SDL Web 8.5.0 customers.\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for CRQ-15038 (TransformContext missing OData parameters).\r\n\r\nInstallation:\r\n=============\r\nThis hotfix provides updated standalone service roles and the in-process API.\r\n\r\nFor all Services\r\n------------\r\n1. Stop the service you are going to update\r\n2. Uninstall the service by opening a Powershell window in the \\bin folder of your service and running\r\n .\\uninstallService.ps1\r\n3. Backup (or move) the folder where your standalone service is located\r\n4. Navigate to the release\\ folder of this distribution\r\n5. Copy the \\standalone folder to the location where your original service was located\r\n6. Rename copied \\standalone folder to the name of your original service's folder\r\n7. Copy all files from \\config folder of your backup (from step #3) to \\config folder of a new service\r\n8. Copy custom jars (if you have any) from backup's \\services\\ folders to the same location in new service\r\n9. Install service by opening a Powershell window in in the \\bin folder of the new service and run .\\installService.ps1 \r\n\r\nFor the API\r\n---\r\n1. Stop your web application\r\n2. Back it up to safe location\r\n3. Delete jars/DLLs present in your web-app\r\n4. Copy new jars/DLLs from the api folder of this hotfix to your web-app\r\n5. Restore any custom jars or DLLs from your backup\r\n6. Restart the web-application\r\n\r\n\r\nDistributed roles:\r\n==================\r\napi\t\t\tAPI role (in-process or REST)\r\ncontent\t\tContent Service role\r\nsession\t\tSession-enabled Content Service role\r\n\r\nDependencies:\r\n=============\r\nN/A\r\n\r\nFixed problems:\r\n===============\r\n - CRQ-15038 - TransformContext missing OData parameters\r\n \r\nProblem Description\r\n-------------------\r\n- It was not possible to access the OData parameters (including query string parameters) from a custom TagRenderer. \r\n The TransformContext argument passed to doStartTag and doEndTag would only have a single, empty $expand variable when expanding a section such as PageContent.\r\n\r\n\r\nHotfix Description\r\n-------------------\r\n- The TransformContext now includes all variables from the parent context when expanding links.\r\n\r\nDisclaimer:\r\n===========\r\n\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. \r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore \r\nshould only be installed if approved by Customer Support. Hotfixes should be replaced as soon as possible by the \r\nsubsequent patch release where the problem is fixed.\r\n\r\nCopyright 2015-2019 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.\r\n",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2c094436e1bc8257d87"
},
"hotfix_name": "ECL_8.5.0.6076",
"modified_date": {
"$date": 1520426438013
},
"problem_description": "",
"readme_text": "Release Notes for Hotfix 6076\n\nVersion:\n\tThis hotfix is intended only for Tridion External Content Library 8.5 included in Tridion 8.5.\n\nProblem description:\n\tIf ECL URI is too long, thumbnail path length can exceed windows limit of 260 characters.\n\nHotfix description:\n\tFix thumbnail name generation code.\n\nInstallation:\n\t1. Stop all Tridion Content Manager Service Host and IIS Service.\n\t2. Move the file Tridion.ExternalContentLibrary.DomainModel.dll located in the %WINDIR%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.ExternalContentLibrary.DomainModel\\v4.0_8.5.0.116__ddfc895746e5ee6b folder\n\t3. Copy the Tridion.ExternalContentLibrary.DomainModel.dll file from this hotfix to the %WINDIR%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.ExternalContentLibrary.DomainModel\\v4.0_8.5.0.116__ddfc895746e5ee6b folder\n\t4. Restart the IIS Service and Tridion Content Manager Service Host.\n\nDistributed files:\n\tTridion.ExternalContentLibrary.DomainModel.dll (File Version 8.5.0.122)\n\tReadme.txt (this file)\n\nFixes included:\n\tN/A\n\nDependencies:\n\tN/A\n\nDisclaimer:\n\tHotfixes are released at the discretion of SDL Tridion based on technical complexity, customer business requirements and schedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by SDL Tridion Customer Support. Hotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\n\nCopyright (c) 2017 SDL Group.",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2aa94436e1bc8257a14"
},
"hotfix_name": "CD_2011.1.1.83364",
"modified_date": {
"$date": 1366729923660
},
"problem_description": "When performing mass publishing action to multiple FTP destination which have limited connection availability, publishing queue slows down drastically.\r\nWhen performing mass publishing action, publishing queue halts, multiple timeout problems are reported.\r\nIn a highly multi-threaded transport environment (in this case a target with 10 destinations) we get a lot of feedback from multiple destinations causing Transport Service to attempt\r\nto update the state file from different threads at the same time. Also, in case of the same type of publishing, Transport Service is overflowing deployer with requests due to and error\r\nin calculating the available capacity (from deployer side).\r\n2 Phase publish fails when difference between publish and deploy time is too big. If the Timeout setting (by default 15 minutes) in the cd_transport_conf.xml is set to be lower than the time \r\nfor the 2nd phase, the publish job will fail after the timeout setting.\r\nIssue in the calculation of the available window size in case of 2 phase committ. For each Scheduled publish with two phases a slot from the window size was locked but never released. After a \r\nnumber of such publish actions, the transport would just hang in throttled state.\r\nIssue for FTP publishing when the time between phase one and phase two of a scheduled publishing is too small. \r\nUnable to deploy page when two destinations are part of the same publication target.\r\nIn 2011 SP1 + HR1 when having two destinations(SSHFTP) present in the same publication target the following behavior happens:\r\n- when first publishing the page, the status for both destinations will be successful;\r\n- on second publish action, for one destination, the status will be success and for the second, the status will be 'Waiting for Deployment'\r\n- on a third publish action, for both destinations, the status of the publishing action will be 'Waiting for Deployment' for both destinations.\r\nThe customer is using sshftp as their publishing protocol.\r\nAfter there is no activity on a destination controller for more then 30 minutes, destination controller stops but its threads are not closed.\r\nThis leads to increase of overall number of threads per transport service process. Eventually OS will reach its maximum number of spawned threads.\r\n",
"readme_text": "Release Notes for Hotfix TT83364\r\n================================\r\n\r\nVersion:\r\n========\r\nThis cumulative hotfix and is intended only for Tridion 2011 SP1 HR1 and only for Emirates Airlines\r\nThe hotfix includes the following fixes:\r\n- TT83364 Optimize the connection usage in case of FTP protocol and add option to be able to choose between 2009 and 2011 behavior in case of Rollback on Failure\r\n- TT83230 When performing mass publishing action, publishing queue halts\r\n- TT83136 java.util.ConcurrentModificationException when publising in transactional mode to a target with multiple destinations\r\n- TT80398 2 Phase publish fails when difference between publish and deploy time is too big.\r\n- TT81040 Unable to deploy page when two destinations (SSHFTP) are part of the same publication target.\r\n- TT81083 Errors relating to inability to create new threads.\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n- TT83364 Optimize the connection usage in case of FTP protocol and add option to be able to choose between 2009 and 2011 behavior in case of Rollback on Failure\r\n\r\nInstallation:\r\n=============\r\n1. Ensure a correct Content Magement installation with the Transport Service installed\r\n2. Stop the Tridion Content Delivery Transport Service\r\n3. Go to %TRIDION_HOME%\\lib\r\n4. Replace jars with the ones provided in this hotfix\r\n5. Start the Tridion Content Delivery Transport Service\r\n\r\nDistributed files:\r\n==================\r\ncd_core.jar (version 6.1.0.1071)\r\ncd_model.jar (version 6.1.0.1071)\r\ncd_transport.jar (version 6.1.0.1071)\r\nresources/configurations/cd_transport_conf_sample.xml\r\nresources/schemas/cd_transport_conf.xsd\r\n\r\nDependencies:\r\n=============\r\nSDL Tridion 2011 SP1 HR1\r\n\r\nFixed problems:\r\n===============\r\nTT83364\r\nProblem Description\r\n-------------------\r\nWhen performing mass publishing action to multiple FTP destination which have limited connection availability, publishing queue slows down drastically.\r\n\r\nHotfix Description\r\n-------------------\r\nMultiple fixes:\r\na. Optimized the checking of the available capacity for each destination.\r\nb. Minimized the number of parallel open connections.\r\nc. Optimized the way we check for transactions in progress on the deployer side in case of FTP transport connector.\r\nd. Sloved theoretically possible thread blocking issues.\r\ne. Adding configuration of the LegacyMode for customer that want to use 2009 behavior in case of Rollback on Failure. You can now configure it in the cd_transport_conf.xml: ..\r\nf. Introduced additional logging to help diagnosing problems with the Transport service and with the FTP connection.\r\n\r\n\r\nTT83230\r\nProblem Description\r\n-------------------\r\nWhen performing mass publishing action, publishing queue halts, multiple timeout problems are reported.\r\n\r\nHotfix Description\r\n-------------------\r\nMultiple fixes:\r\na. Making sure that the transport pooling timeout is calculated starting with the moment when the transaction is sent on the deployer side.\r\nb. Adding configuration of the SendTimeout in case the sending of the transport package over the network is too slow. You can now configure it in the cd_transport_conf.xml: ..\r\nc. Introduces additional logging to help diagnosing problems with the Transport service.\r\n\r\n\r\nTT83136\r\nProblem Description\r\n-------------------\r\nIn a highly multi-threaded transport environment (in this case a target with 10 destinations) we get a lot of feedback from multiple destinations causing Transport Service to attempt\r\nto update the state file from different threads at the same time. Also, in case of the same type of publishing, Transport Service is overflowing deployer with requests due to and error\r\nin calculating the available capacity (from deployer side).\r\n\r\nHotfix Description\r\n-------------------\r\nMultiple fixes:\r\na. Fixes the issue that causes a ConcurrentModificationException exception by ensuring only a single thread at a time can modify the same state file;\r\nb. Fixes the calculation of available capacity for the Transport service window to a more optimal level;\r\nc. Introduces additional logging to help diagnosing problems with the Transport service.\r\n\r\n\r\n\r\nTT80398\r\nProblem Description\r\n-------------------\r\n2 Phase publish fails when difference between publish and deploy time is too big. If the Timeout setting (by default 15 minutes) in the cd_transport_conf.xml is set to be lower than the time \r\nfor the 2nd phase, the publish job will fail after the timeout setting.\r\nIssue in the calculation of the available window size in case of 2 phase committ. For each Scheduled publish with two phases a slot from the window size was locked but never released. After a \r\nnumber of such publish actions, the transport would just hang in throttled state.\r\nIssue for FTP publishing when the time between phase one and phase two of a scheduled publishing is too small. \r\n\r\n\r\nHotfix Description\r\n-------------------\r\nWhen we have a 2 phase committ this is what happens: before the first phase (sending of content package) transport locks a slot of the window size, after the first phase is done we release the\r\nslot and we stop polling for information (because the package is just parked on deployer side in WAIT state) until the second phase (sending of commit package) occurs, then before the second\r\nphase occurs we lock again a window size slot so we can perform the actual transport and after deployment finished (one way or another) we finally release the window size slot.\r\nMade sure that, in case the time between the 2 phases of a scheduled publishing is too small, we properly handle second phase. Note that this solves (different) problems for both HTTP(S) and FTP deployment.\r\n\r\nTT81040\r\nProblem Description\r\n-------------------\r\nUnable to deploy page when two destinations are part of the same publication target.\r\nIn 2011 SP1 + HR1 when having two destinations(SSHFTP) present in the same publication target the following behavior happens:\r\n- when first publishing the page, the status for both destinations will be successful;\r\n- on second publish action, for one destination, the status will be success and for the second, the status will be 'Waiting for Deployment'\r\n- on a third publish action, for both destinations, the status of the publishing action will be 'Waiting for Deployment' for both destinations.\r\n\r\nThe customer is using sshftp as their publishing protocol.\r\n\r\n\r\nHotfix Description\r\n-------------------\r\nWe made sure that after each access to the SSHFTP server we properly disconnect the client thus preventing thread blocking. Also made sure that we properly handle situations when the deployer has no status yet for a given transaction.\r\n\r\nTT81083\r\nProblem Description\r\n-------------------\r\nAfter there is no activity on a destination controller for more then 30 minutes, destination controller stops but its threads are not closed.\r\nThis leads to increase of overall number of threads per transport service process. Eventually OS will reach its maximum number of spawned threads.\r\n\r\n\r\nHotfix Description\r\n-------------------\r\nOnce destination controller is stoped after inactivity period, all children threads are stopped also.\r\n\r\n\r\nDisclaimer:\r\n===========\r\nHotfixes are released at the discretion of Tridion based on technical\r\ncomplexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/\r\nconfiguration and therefore should only be installed if approved by Tridion\r\nCustomer Support. Hotfixes should be replaced as soon as possible by the\r\nsubsequent service pack where the problem is fixed.\r\n\r\n(c) 2012 SDL Tridion B.V.\r\n",
"version": "2011 SP1 HR#1"
},
{
"_id": {
"$oid": "635fe2bb94436e1bc8257ce6"
},
"hotfix_name": "CD_8.5.0.14128",
"modified_date": {
"$date": 1557336023942
},
"problem_description": "This is a hotfix for:\r\n- CRQ-14128 ConcurrentModificationException occurs in ADF Client\r\n",
"readme_text": "Release Notes for Hotfix CRQ-14128\r\n==================================\r\n\r\nVersion:\r\n--------\r\nThis is hotfix and is intended for SDL Web 8.5.0\r\nThe hotfix includes the following fixes: \r\n- CRQ-14128 ConcurrentModificationException occurs in ADF Client\r\n\r\n\r\nDescription:\r\n------------\r\nThis is a hotfix for:\r\n- CRQ-14128 ConcurrentModificationException occurs in ADF Client\r\n\r\n\r\nInstallation:\r\n-------------\r\nThis hotfix provides updated roles for the API and services.\r\n\r\n\r\nInstructions:\r\n-------------\r\n\r\nAPI\r\n---\r\n1. Stop your web application\r\n2. Backup it to safe location\r\n3. Delete jars/DLLs present in your web-app\r\n4. Copy new jars/DLLs from api folder of this hotfix to your web-app\r\n5. Restore any custom jars or DLLs from your backup\r\n6. Restart web-application\r\n\r\nServices\r\n--------\r\n1. Stop relevant Service\r\n2. Backup (or move) a folder where your standalone Service is located\r\n3. Uninstall the relevant Service by opening a Powershell window in the \\bin of your service and run .\\uninstallService.ps1\r\n4. Navigate to the release\\ folder of this distribution\r\n5. Copy \\standalone folder to the location where your original service was located\r\n6. Rename copied \\standalone folder to the name of your original service's folder\r\n7. Copy all files from \\config folder of your backup (see step #2) to \\config folder of a new service\r\n8. Copy custom jars (if you have any) from backup's \\services\\folder to a same location of a new service\r\n9. Install service by opening a Powershell window in in the location \\bin of new service and run .\\installService.ps1\r\n\r\n \r\nDistributed roles:\r\n------------------\r\n- api\t\tAPI\r\n- cid\t\tContextul Image Delivery\r\n- content\tContent\r\n- context\tContext\r\n- deployer\tDeployer\r\n- discovery\tDiscovery\r\n- preview\tPreview\r\n- session\tSession-enabled Content\r\n- template\tTemplate\r\n- ugc\t\tUser Generated Content\r\n\r\n\r\nFixed problems:\r\n---------------\r\n- CRQ-14128 ConcurrentModificationException occurs in ADF Client\r\n\r\n\r\nHotfix Description\r\n-------------------\r\n- Resolved concurrency issue within ADF Client library.\r\n\r\n\r\nDisclaimer:\r\n-----------\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and \r\nschedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration \r\nand therefore should only be installed if approved by Customer Support. Hotfixes should be replaced as soon as \r\npossible by the subsequent patch release where the problem is fixed.\r\n\r\nCopyright 2016-2019 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL \r\nGroup.\r\n",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2bb94436e1bc8257cdc"
},
"hotfix_name": "CD_8.5.0.12003",
"modified_date": {
"$date": 1542621406412
},
"problem_description": "Tridion.ContentDelivery.DynamicContent.DynamicMappingsRetriever.GetPublicationMapping(String url) is not thread safe\r\n",
"readme_text": "Release Notes for Hotfix CRQ-12003\r\n=================================\r\n\r\nVersion:\r\n========\r\nThis cumulative hotfix is intended only for SDL Web 8.5.0 customers.\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n- CRQ-12003 Tridion.ContentDelivery.DynamicContent.DynamicMappingsRetriever.GetPublicationMapping(String url) is not thread safe\r\n\r\nInstallation:\r\n=============\r\nThis cumulative hotfix provides updated api rest role for dotnet.\r\n\r\n1. Stop your REST web application\r\n2. Create backup to a safe location\r\n3. Delete DLLs present in your web-app\r\n4. Copy new DLLs from api\\rest folder of this HF to your web application\r\n5. Start web application\r\n\r\n\r\nDistributed roles:\r\n==================\r\napi\t\t\tAPI REST role (.NET)\r\n\r\nDependencies:\r\n=============\r\nN/A\r\n\r\nFixed problems:\r\n===============\r\n- CRQ-12003 Tridion.ContentDelivery.DynamicContent.DynamicMappingsRetriever.GetPublicationMapping(String url) is not thread safe\r\n\r\nProblem Description\r\n-------------------\r\nTridion.ContentDelivery.DynamicContent.DynamicMappingsRetriever.GetPublicationMapping(String url) is not thread safe\r\n\r\nHotfix Description\r\n-------------------\r\nRemoved local caching of publication mapping\r\n\r\nDisclaimer:\r\n===========\r\n\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. \r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore \r\nshould only be installed if approved by Customer Support. Hotfixes should be replaced as soon as possible by the \r\nsubsequent patch release where the problem is fixed.\r\n\r\nCopyright 2015-2018 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.\r\n",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2aa94436e1bc8257a03"
},
"hotfix_name": "CD_2011.1.1.79834",
"modified_date": {
"$date": 1334085085690
},
"problem_description": "For each different page with Personalization and Profiling enabled, a cookie was created causing in the end a multitude of cookies for each path containing P&P pages.\r\n",
"readme_text": "Release Notes for Hotfix TT79834\r\n================================\r\n\r\nVersion:\r\n========\r\nThis hotfix is intended only for SDL Tridion 2011 SP1 HR1\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n- TT79834 2011 SP1: Two cookies are being set for a single user and session when hitting two different pages enabled for Personalization and Profiling in that one session\r\n\r\nInstallation:\r\n=============\r\nDeployer environment:\r\n---------------------\r\nJava Environment:\r\n1. Ensure that you have a correct installed Content Delivery installation inside your web application\r\n2. Stop your web application server or web application containing the website\r\n3. Copy the distributed jar file inside your web application WEB-INF\\lib directory\r\n4. Start your web application server or web application\r\n\r\n\r\nDistributed files:\r\n==================\r\ncd_dynamic.jar\r\n\r\nDependencies:\r\n=============\r\nSDL Tridion 2011 SP1 HR1\r\n\r\nFixed problems:\r\n===============\r\nTT79834\r\nProblem Description\r\n-------------------\r\nFor each different page with Personalization and Profiling enabled, a cookie was created causing in the end a multitude of cookies for each path containing P&P pages.\r\n\r\nHotfix Description\r\n-------------------\r\nMade sure we only create one cookie for each user (which is common for all P&P enabled pages).\r\n\r\nDisclaimer:\r\n===========\r\nHotfixes are released at the discretion of Tridion based on technical\r\ncomplexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/\r\nconfiguration and therefore should only be installed if approved by Tridion\r\nCustomer Support. Hotfixes should be replaced as soon as possible by the\r\nsubsequent service pack where the problem is fixed.\r\n\r\n(c) 2012 SDL Tridion B.V.\r\n",
"version": "2011 SP1 HR#1"
},
{
"_id": {
"$oid": "635fe2ac94436e1bc8257a72"
},
"hotfix_name": "CD_2011.1.2.2350",
"modified_date": {
"$date": 1471023036485
},
"problem_description": "The hotfix includes a test fix for the following:\r\n- CRQ-2350 Support for alternative ciphers when using SSH FTP as transfer protocol\r\nInstallation\r\nTransport Service\r\n1. Stop Transport service\r\n2. Backup existing \\lib\\cd_transport.jar\r\n3. Rename existing j2ssh.jar to j2ssh.jar.orig in \\lib\r\n4. Copy jsch.jar and cd_transport.jar from hotfix to \\lib\r\n5. Restart Transport service\r\nDistributed files:\r\nlib\\cd_transport.jar\r\nlib\\jsch.jar\r\n",
"readme_text": "Release Notes for Hotfix CRQ-2350\r\n=================================\r\n\r\nVersion\r\n=======\r\nThis hotfix and is intended only for Tridion 2011 SP1 HR2\r\n\r\nDescription\r\n===========\r\nThe hotfix includes a test fix for the following:\r\n - CRQ-2350 Support for alternative ciphers when using SSH FTP as transfer protocol\r\n\r\nInstallation\r\n============\r\nTransport Service\r\n-----------------\r\n1. Stop Transport service\r\n2. Backup existing \\lib\\cd_transport.jar\r\n3. Rename existing j2ssh.jar to j2ssh.jar.orig in \\lib\r\n4. Copy jsch.jar and cd_transport.jar from hotfix to \\lib\r\n5. Restart Transport service\r\n\r\nDistributed files:\r\n==================\r\nlib\\cd_transport.jar\r\nlib\\jsch.jar\r\n\r\nDependencies:\r\n=============\r\nSDL Tridion 2011 SP1 HR2\r\n\r\nFixed problems\r\n==============\r\n\r\nCRQ-2350 Support for alternative ciphers when using SSH FTP as transfer protocol\r\n\r\nHotfix Description\r\n------------------\r\nThis test hotfix includes support for a new SSH FTP library which should support later ciphers.\r\n\r\n\r\nDisclaimer\r\n==========\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. \r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore \r\nshould only be installed if approved by Customer Support. Hotfixes should be replaced as soon as possible by the \r\nsubsequent patch release where the problem is fixed.\r\n\r\nCopyright \u00a9 2015-2016 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group\r\n",
"version": "2011 SP1 HR#2"
},
{
"_id": {
"$oid": "635fe2ae94436e1bc8257b1a"
},
"hotfix_name": "CD_2013.1.1.2350",
"modified_date": {
"$date": 1508335426481
},
"problem_description": "The hotfix includes a test fix for the following:\r\n- CRQ-2350 Support for alternative ciphers when using SSH FTP as transfer protocol\r\nInstallation\r\nTransport Service\r\n1. Stop Transport service\r\n2. Backup existing \\lib\\cd_transport.jar\r\n3. Rename existing j2ssh.jar to j2ssh.jar.orig in \\lib\r\n4. Copy jsch.jar and cd_transport.jar from hotfix to \\lib\r\n5. Restart Transport service\r\nDistributed files:\r\nlib\\cd_transport.jar\r\nlib\\jsch.jar\r\n",
"readme_text": "Release Notes for Hotfix CRQ-2350\r\n=================================\r\n\r\nVersion\r\n=======\r\nThis hotfix and is intended only for Tridion 2013 SP1 HR1\r\n\r\nDescription\r\n===========\r\nThe hotfix includes a test fix for the following:\r\n - CRQ-2350 Support for alternative ciphers when using SSH FTP as transfer protocol\r\n\r\nInstallation\r\n============\r\nTransport Service\r\n-----------------\r\n1. Stop Transport service\r\n2. Backup existing \\lib\\cd_transport.jar\r\n3. Rename existing j2ssh.jar to j2ssh.jar.orig in \\lib\r\n4. Copy jsch.jar and cd_transport.jar from hotfix to \\lib\r\n5. Restart Transport service\r\n\r\nDistributed files:\r\n==================\r\nlib\\cd_transport.jar\r\nlib\\jsch.jar\r\n\r\nDependencies:\r\n=============\r\nSDL Tridion 2013 SP1 HR1\r\n\r\nFixed problems\r\n==============\r\n\r\nCRQ-2350 Support for alternative ciphers when using SSH FTP as transfer protocol\r\n\r\nHotfix Description\r\n------------------\r\nThis test hotfix includes support for a new SSH FTP library which should support later ciphers.\r\n\r\n\r\nDisclaimer\r\n==========\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. \r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore \r\nshould only be installed if approved by Customer Support. Hotfixes should be replaced as soon as possible by the \r\nsubsequent patch release where the problem is fixed.\r\n\r\nCopyright \u00a9 2015-2016 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group\r\n",
"version": "2013 SP1 HR#1"
},
{
"_id": {
"$oid": "635fe2bd94436e1bc8257d19"
},
"hotfix_name": "CD_8.5.0.6896",
"modified_date": {
"$date": 1509121185345
},
"problem_description": "- Queries to database that use LOWURL field as a parameter took a long time to execute\r\n",
"readme_text": "\ufeffRelease Notes for Hotfix CRQ-6896\r\n=================================\r\n\r\nVersion:\r\n========\r\nThis is hotfix is intended only for SDL Web 8\r\n\r\nDescription:\r\n============\r\nThe hotfix include the following fixes:\r\n- CRQ-6896 The Binary Variants table misses an index on the LOWURL Column, causing drastic slowdown in the BinaryVariant.findByUrl call with large volumes\r\n\r\nInstallation:\r\n=============\r\nThis cumulative hotfix provides SQL script for updating MSSQL database indexes.\r\n\r\nFor MSSQL database\r\n---------------------------\r\n1. Create a backup of your Content Data Store database.\r\n2. Execute TCD_UPDATE_INDEXES.sql script on your Content Data Store.\r\n\r\nDistributed roles:\r\n==================\r\n\r\n\r\nFixed problems:\r\n===============\r\n - CRQ-6896 The Binary Variants table misses an index on the LOWURL Column, causing drastic slowdown in the BinaryVariant.findByUrl call with large volumes\r\n\r\nProblem Description\r\n-------------------\r\n- Queries to database that use LOWURL field as a parameter took a long time to execute\r\n\r\nHotfix Description\r\n-------------------\r\n- Update for BINARYVARIANTS table indexes.\r\n\r\n\r\nDisclaimer:\r\n===========\r\n\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by Customer Support. Hotfixes should be replaced as soon as possible by the subsequent patch release where the problem is fixed.\r\n\r\nCopyright \ufffd 2016-2017 SDL Group. All Rights Reserved.\r\n\r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.\r\n",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2ab94436e1bc8257a5a"
},
"hotfix_name": "CM_2011.1.1.84734",
"modified_date": {
"$date": 1363642767651
},
"problem_description": "Schema.GetInstanceData returns default value for external link field in wrong format\r\n",
"readme_text": "Release Notes for Hotfix TT84734\r\n\r\nVersion:\r\nThis hotfix is intended only for SDL Tridion Content Manager 2011 SP1 HR1.\r\n\r\nProblem description:\r\nSchema.GetInstanceData returns default value for external link field in wrong format\r\n\r\nHotfix description:\r\nThe external link field's default value will be returned as a xlink:href attribute as according to the XSD.\r\n\r\nInstallation:\r\n 1. Stop all TCM Services, IIS Service, and the TCM COM+ Application.\r\n 2. Remove the file Tridion.ContentManager.dll located in the %WINDIR%\\assembly\\GAC_MSIL\\Tridion.ContentManager\\6.1.0.996__360aac4d3354074b folder\r\n 3. Copy the Tridion.ContentManager.CoreService.dll file from this hotfix to the %WINDIR%\\assembly\\GAC_MSIL\\Tridion.ContentManager\\6.1.0.996__360aac4d3354074b folder\r\n 4. Restart the IIS Service, TCM Services and TCM COM+ Application.\r\n\r\nDistributed files:\r\n Tridion.ContentManager.dll (File Version 6.1.0.1010)\r\n Readme.txt (this file)\r\n\r\nFixes included:\r\n 83707\r\n\r\nDependencies:\r\n TT83010\r\n\r\nDisclaimer:\r\nHotfixes are released at the discretion of SDL based on technical complexity, customer business requirements and schedules.\r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by Customer Support of SDL Web Content Management Solutions Division.\r\nHotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n",
"version": "2011 SP1 HR#1"
},
{
"_id": {
"$oid": "635fe2ac94436e1bc8257a93"
},
"hotfix_name": "CM_2011.1.2.85438",
"modified_date": {
"$date": 1370364068633
},
"problem_description": "Unnecessary database calls when retrieving Trustee related lists due to the retrieval of allowed actions information. This is noticeable when having over 1000 repositories especially on Oracle.\r\n",
"readme_text": "Release Notes for Hotfix TT85438\r\n\r\nVersion:\r\nThis hotfix is intended only for SDL Tridion Content Manager 2011 SP1 HR2.\r\n\r\nProblem description:\r\nUnnecessary database calls when retrieving Trustee related lists due to the retrieval of allowed actions information. This is noticeable when having over 1000 repositories especially on Oracle.\r\n\r\nHotfix description:\r\nInformation will be cached and therefore only retrieved once.\r\n\r\nInstallation:\r\n 1. Stop all TCM Services, IIS Service, and the TCM COM+ Application.\r\n 2. Remove the file Tridion.ContentManager.dll located in the %WINDIR%\\assembly\\GAC_MSIL\\Tridion.ContentManager\\6.1.0.996__360aac4d3354074b folder\r\n 3. Copy the Tridion.ContentManager.CoreService.dll file from this hotfix to the %WINDIR%\\assembly\\GAC_MSIL\\Tridion.ContentManager\\6.1.0.996__360aac4d3354074b folder\r\n 4. Restart the IIS Service, TCM Services and TCM COM+ Application.\r\n\r\nDistributed files:\r\n Tridion.ContentManager.dll (File Version 6.1.0.1011)\r\n Readme.txt (this file)\r\n\r\nFixes included:\r\n N/A\r\n\r\nDependencies:\r\n N/A\r\n\r\nDisclaimer:\r\nHotfixes are released at the discretion of SDL based on technical complexity, customer business requirements and schedules.\r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by Customer Support of SDL Web Content Management Solutions Division.\r\nHotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n",
"version": "2011 SP1 HR#2"
},
{
"_id": {
"$oid": "635fe2ab94436e1bc8257a49"
},
"hotfix_name": "CM_2011.1.1.82194",
"modified_date": {
"$date": 1352721426240
},
"problem_description": "Sorting by date does not work correctly in the Publishing Queue\r\n",
"readme_text": "Release Notes for Hotfix TT# 82194\r\n\r\nVersion:\r\nThis hotfix is intended for Tridion 2011 SP1 HR1\r\n\r\nProblem description:\r\nSorting by date does not work correctly in the Publishing Queue\r\n\r\nHotfix description:\r\nThe list's sorting logic did not take account of data retrieved using alternate selectors\r\n\r\nInstallation:\r\n 1. Move or delete the file ListDefinition.js located in the %TRIDION_HOME%\\web\\WebUI\\Core\\Controls\\List\\ folder.\r\n 2. Copy the file ListDefinition.js from this hotfix to the %TRIDION_HOME%\\web\\WebUI\\Core\\Controls\\List\\ folder.\r\n 3. Open %TRIDION_HOME%\\web\\WebUI\\WebRoot\\Configuration\\System.config file.\r\n 4. Locate /Configuration/servicemodel/server node in Sytem.config file and increase the value of its 'modification' attribute to notify client browsers to update their cache.\r\n\r\n\r\nDistributed files:\r\n- ListDefinition.js\r\n- Readme.txt (this file)\r\n\r\n\r\nFixes included:\r\nn/a\r\n\r\n\r\nDependencies:\r\nn/a\r\n\r\n\r\nDisclaimer:\r\nHotfixes are released at the discretion of SDL based on technical complexity, customer business requirements and schedules.\r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by SDL Customer Support.\r\nHotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright 2012 SDL PLC. All Rights Reserved. All company product or service names referenced herein are properties of their respective owners.",
"version": "2011 SP1 HR#1"
},
{
"_id": {
"$oid": "635fe2bb94436e1bc8257cea"
},
"hotfix_name": "CD_8.5.0.16047",
"modified_date": {
"$date": 1567182177978
},
"problem_description": "- CRQ-14802 : Error occured when configuring State Store DB to use integrated authentication\r\n- CRQ-16047 : Due to ADF being not thread safe, there were errors during mass publishing or multi-threaded requests to CIS\r\n",
"readme_text": "Release Notes for Hotfixes CRQ-16047 and CRQ-14802\r\n=================================\r\n\r\nVersion:\r\n========\r\nThis is cumulative hotfix and is intended only for SDL Web 8.5.0\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n - CRQ-14802 \"Unable to acquire JDBC Connection\" error when configuring microservice DB to use integrated authentication\r\n - CRQ-16047 \"OData error constantly appears\"\r\n \r\nInstallation:\r\n=============\r\nThis cumulative hotfix provides updated api artifacts and services.\r\n\r\nCD API's REST:\r\n-----------------------\r\n1. [.NET] - update [.NET] artifacts from release\\api\\rest\\dotNet\\bin folder.\r\n2. Java - update artifacts from release\\api\\rest\\java\\lib folder.\r\n\r\n\r\nAll Services\r\n-----------------------\r\n1. Stop the Service you are going to upgrade\r\n2. Backup (or move) a folder where your standalone Service is located\r\n3. Uninstall the Service by opening a Powershell window in the \\bin of your service and running .\\uninstallService.ps1\r\n4. Navigate to the release\\\\service folder of this distribution\r\n5. Copy \\standalone folder to the location where your original service was located\r\n6. Rename copied \\standalone folder to the name of your original service's folder\r\n7. Copy all files from \\config folder of your backup (see step #2) to \\config folder of a new service.\r\n8. Copy custom jars (if you have any) from backup's \\services\\folder to a same location of a new service\r\n9. Install service by opening a Powershell window in in the location \\bin of new service and run .\\installService.ps1\r\n\r\nDistributed roles:\r\n==================\r\napi Content Delivery API role\r\ncid\t\t\t Contextual Image Delivery role\r\ncontext\t\t\t Context Service role\r\ncontent Content Service role\r\ndeployer Deployer role\r\ndiscovery Discovery service role\r\npreview Preview service role\r\nsession\t\t\t Session service role\r\nugc/community-service UGC Community Service role\r\nugc/moderation-service UGC Moderation Service role\r\ntemplate\t\t Template Service role\r\n\r\nDependencies:\r\n=============\r\n\r\n\r\nFixed problems:\r\n===============\r\n - CRQ-14802 \"Unable to acquire JDBC Connection\" error when configuring microservice DB to use integrated authentication\r\n - CRQ-16047 \"OData error constantly appears\"\r\n\r\nProblem Description\r\n-------------------\r\n - CRQ-14802 : Error occured when configuring State Store DB to use integrated authentication\r\n - CRQ-16047 : Due to ADF being not thread safe, there were errors during mass publishing or multi-threaded requests to CIS\r\n\r\n\r\nHotfix Description\r\n-------------------\r\n - CRQ-14802 : Enabled integrated authentication to be used with State Store database\r\n - CRQ-16047 : Made ADF thread safe\r\n\r\nDisclaimer:\r\n===========\r\n\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/configuration and therefore should only be installed\r\nif approved by Customer Support. Hotfixes should be replaced as soon as possible by the subsequent patch release where the problem is fixed.\r\n\r\nCopyright 2015-2019 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.\r\n",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2b094436e1bc8257b99"
},
"hotfix_name": "CD_11.0.0.14351",
"modified_date": {
"$date": 1556806113229
},
"problem_description": "This is a hotfix for:\r\n- CRQ-14351 Enable strict content type checking on Elasticsearch 5 rest requests\r\n",
"readme_text": "Release Notes for Hotfix CRQ-14351\r\n==================================\r\n\r\nVersion:\r\n--------\r\nThis is hotfix and is intended for SDL Docs 13 SP2 running against DXD 11.0\r\nThe hotfix includes the following fixes: \r\n- CRQ-14351 Enable strict content type checking on Elasticsearch 5 rest requests\r\n\r\n\r\nDescription:\r\n------------\r\nThis is a hotfix for:\r\n- CRQ-14351 Enable strict content type checking on Elasticsearch 5 rest requests\r\n\r\n\r\nInstallation:\r\n-------------\r\nThis hotfix provides updated roles for the IQ services.\r\n\r\n\r\nInstructions:\r\n-------------\r\n\r\nElasticsearch\r\n-------------\r\n1. Locate the elasticsearch.yml\r\n2. Set the following value to true:\r\n http.content_type.required: true\r\n3. Restart Elasticsearch\r\n\r\nServices\r\n--------\r\n1. Stop relevant Service\r\n2. Backup (or move) a folder where your standalone Service is located\r\n3. Uninstall the relevant Service by opening a Powershell window in the \\bin of your service and run .\\uninstallService.ps1\r\n4. Navigate to the release\\ folder of this distribution\r\n5. Copy \\standalone folder to the location where your original service was located\r\n6. Rename copied \\standalone folder to the name of your original service's folder\r\n7. Copy all files from \\config folder of your backup (see step #2) to \\config folder of a new service\r\n8. Copy custom jars (if you have any) from backup's \\services\\folder to a same location of a new service\r\n9. Install service by opening a Powershell window in in the location \\bin of new service and run .\\installService.ps1\r\n\r\n \r\nDistributed roles:\r\n------------------\r\niq - Index and Query Search Services\r\n\r\n\r\nFixed problems:\r\n---------------\r\n- CRQ-14351 Enable strict content type checking on Elasticsearch 5 rest requests\r\n\r\n\r\nHotfix Description\r\n-------------------\r\n- Added support for strict content type checking on Elasticsearch 5\r\n\r\n\r\nDisclaimer:\r\n-----------\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and \r\nschedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration \r\nand therefore should only be installed if approved by Customer Support. Hotfixes should be replaced as soon as \r\npossible by the subsequent patch release where the problem is fixed.\r\n\r\nCopyright 2016-2019 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL \r\nGroup.\r\n",
"version": "Sites 9.0"
},
{
"_id": {
"$oid": "635fe2c094436e1bc8257d84"
},
"hotfix_name": "ECL_8.5.0.13573",
"modified_date": {
"$date": 1550763320410
},
"problem_description": "",
"readme_text": "Release Notes for Hotfix 13573\n\nVersion:\n\tThis hotfix is intended only for Tridion External Content Library 8.5 included in Tridion 8.5.\n\nProblem description:\n\tPage Navigation Icons(\"<\" & \">\") Not Displayed in ECL Connector.\n\nHotfix description:\n\tAdd missing files.\n\nInstallation:\n\t1. \tCopy provided \"Pager\" directory in to %TRIDION_CM_HOME%\\web\\WebUI\\Editors\\Base\\Themes\\Carbon2\\Images\\Controls\\\n\t2.\tOpen %TRIDION_CM_HOME%\\web\\WebUI\\WebRoot\\Configuration\\System.config in a text editor.\n\t\tLocate the Configuration/servicemodel/server node in the System.config file and increase the value of its 'modification' attribute to notify client browsers to update their cache.\n\t3.\tRestart the IIS Service.\n\t\nDistributed files:\n\tpager_previous.gray.png\n\tpager_previous.png\n\tpager_next.gray.png\n\tpager_next.png\n\tpager_last.gray.png\n\tpager_last.png\n\tpager_first.gray.png\n\tpager_first.png\n\tReadme.txt (this file)\n\nFixes included:\n\tN/A\n\nDependencies:\n\tN/A\n\nDisclaimer:\n\tHotfixes are released at the discretion of SDL Tridion based on technical complexity, customer business requirements and schedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by SDL Tridion Customer Support. Hotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\n\nCopyright (c) 2019 SDL Group.",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2ab94436e1bc8257a1e"
},
"hotfix_name": "CD_2011.1.1.84849",
"modified_date": {
"$date": 1363819523058
},
"problem_description": "The .NET HTTPUpload would always report to the Transport service that there are no transactions in progress on the deployer side.\r\n",
"readme_text": "Release Notes for Hotfix TT84849\r\n================================\r\n\r\nVersion:\r\n========\r\nThis hotfix is intended only for SDL Tridion 2011 SP1 HR1\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n- TT84849 .NET HTTPUpload brakes Transport throttling\r\n\r\nInstallation:\r\n=============\r\n.NET Environment:\r\n1. Ensure the application pool of your application and/or IIS Server has been stopped;\r\n2. Copy the distributed Tridion.ContentDelivery.dll over the existing dll inside the Bin folder of your webApplication;\r\n3. Start the application pool and/or IIS Server.\r\n\r\n\r\nDistributed files:\r\n==================\r\ndotNet\\x86\\Tridion.ContentDelivery.dll (version 6.1.0.1084)\r\ndotNet\\x86_64\\Tridion.ContentDelivery.dll (version 6.1.0.1084)\r\n\r\nDependencies:\r\n=============\r\nSDL Tridion 2011 SP1 HR1\r\n\r\nFixed problems:\r\n===============\r\nTT84849\r\nProblem Description\r\n-------------------\r\nThe .NET HTTPUpload would always report to the Transport service that there are no transactions in progress on the deployer side.\r\n\r\n\r\nHotfix Description\r\n-------------------\r\nMade sure that the checking of in-progress transactions is done correctly.\r\n\r\n\r\nDisclaimer:\r\n===========\r\nHotfixes are released at the discretion of Tridion based on technical\r\ncomplexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/\r\nconfiguration and therefore should only be installed if approved by Tridion\r\nCustomer Support. Hotfixes should be replaced as soon as possible by the\r\nsubsequent service pack where the problem is fixed.\r\n\r\n(c) 2013 SDL Tridion B.V.\r\n",
"version": "2011 SP1 HR#1"
},
{
"_id": {
"$oid": "635fe2ab94436e1bc8257a5d"
},
"hotfix_name": "OE_2011.1.1.82675_Mssql",
"modified_date": {
"$date": 1350486860122
},
"problem_description": "An error \"An item with the title 'Segments' already exists in this location\" is sometimes raised when reading a Publication.\r\n",
"readme_text": "Release Notes for Hotfix TT 82675\r\n\r\nVersion:\r\nThis hotfix is intended only for Tridion Outbound Email 2.2 (2011 SP1) with Hotfix Roll-up 1 installed, on MSSQL Server.\r\n\r\nProblem description:\r\nAn error \"An item with the title 'Segments' already exists in this location\" is sometimes raised when reading a Publication.\r\n\r\nHotfix description:\r\nThis hotfix fixes an issue with the transactionality of updating the Content Manager's BluePrint information, and re-synchronizes the BluePrint information if it is out of sync.\r\n\r\n\r\nInstallation:\r\n1. Replace the current Tridion.AudienceManagement.DomainModel.dll in the Tridion\\bin folder with the one from the hotfix.\r\n2. Add the Tridion.AudienceManagement.DomainModel.dll to the GAC.\r\n3. Execute the SP_PUBLICATIONS.sql script on the Outbound E-mail management side database.\r\n\r\n\r\nDistributed files:\r\nTridion.AudienceManagement.DomainModel.dll [2.2.0.743]\r\nSP_PUBLICATIONS.sql\r\n\r\nFixes included:\r\nN.A.\r\n\r\nDependencies:\r\nN.A.\r\n\r\nDisclaimer:\r\nHotfixes are released at the discretion of SDL Tridion based on technical complexity, customer business requirements and schedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by SDL Tridion Customer Support. Hotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright (c) 2012 SDL Tridion B.V.\r\n",
"version": "2011 SP1 HR#1"
},
{
"_id": {
"$oid": "635fe2b994436e1bc8257c9f"
},
"hotfix_name": "CD_8.1.1.4630 ",
"modified_date": {
"$date": 1495619056557
},
"problem_description": "- CPU usage of RDS stuck to 100% for several minutes.\r\n",
"readme_text": "\ufeffRelease Notes for Hotfix CRQ-4630\r\n=================================\r\n \r\nVersion:\r\n========\r\nThis is hotfix is intended only for SDL Web 8\r\n \r\nDescription:\r\n============\r\nThe hotfix include the following fixes:\r\n - CRQ-4630 CPU usage rate of RDS abnormally increased on Web 8.1.1\r\n \r\nInstallation:\r\n=============\r\nThis cumulative hotfix provides SQL script for updating MSSQL database indexes.\r\n \r\nFor MSSQL database\r\n---------------------------\r\n1. Create a backup of your Content Data Store database.\r\n2. Execute TCD_UPDATE_INDEXES.sql script on your Content Data Store.\r\n \r\nDistributed roles:\r\n==================\r\n\r\n \r\nFixed problems:\r\n===============\r\n - CRQ-4630 CPU usage rate of RDS abnormally increased on Web 8.1.1\r\n \r\nProblem Description\r\n-------------------\r\n- CPU usage of RDS stuck to 100% for several minutes.\r\n \r\nHotfix Description\r\n-------------------\r\n- Update for TAXFACETS table indexes. \r\n \r\n \r\nDisclaimer:\r\n===========\r\n \r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by Customer Support. Hotfixes should be replaced as soon as possible by the subsequent patch release where the problem is fixed.\r\n \r\nCopyright \ufffd 2016-2017 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.",
"version": "Web 8.1.1"
},
{
"_id": {
"$oid": "635fe2ba94436e1bc8257ca2"
},
"hotfix_name": "CD_8.1.1.5957",
"modified_date": {
"$date": 1502989240288
},
"problem_description": "- CIL.NET incorrectly serializes ComponentLink.\r\n",
"readme_text": "Release Notes for Hotfix CRQ-5957\r\n=================================\r\n\r\nVersion:\r\n========\r\nThis is cumulative hotfix and is intended only for SDL Web 8.1.1\r\n\r\nDescription:\r\n============\r\nThe hotfix include the following fixes: \r\n - CRQ-5957 Hyperlink not getting created on Web 8 page\r\n \r\nInstallation:\r\n=============\r\nThis cumulative hotfix provides updated api artifacts.\r\n\r\nREST API\r\n--------------\r\n1. Stop your web application.\r\n2. Replace existing .Net API libraries with latest ones.\r\n3. Restart web application.\r\n\r\nDistributed roles:\r\n==================\r\napi\t\t\tContent Delivery API role (rest)\r\n\r\nFixed problems:\r\n===============\r\n - CRQ-5957 Hyperlink not getting created on Web 8 page\r\n \r\nProblem Description\r\n-------------------\r\n- CIL.NET incorrectly serializes ComponentLink.\r\n\r\nHotfix Description\r\n-------------------\r\n- Fixed serialization.\r\n\r\nDisclaimer:\r\n===========\r\n\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/configuration and therefore should only be installed\r\nif approved by Customer Support. Hotfixes should be replaced as soon as possible by the subsequent patch release where the problem is fixed.\r\n\r\nCopyright 2015-2017 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.",
"version": "Web 8.1.1"
},
{
"_id": {
"$oid": "635fe2b594436e1bc8257c3c"
},
"hotfix_name": "CD_11.5.0.21699",
"modified_date": {
"$date": 1604505809310
},
"problem_description": "This is a hotfix for:\r\n- CRQ-21699 - Migration of elasticsearch indices to Tridion 9.5 throws exception\r\n",
"readme_text": "Release Notes for Hotfixes CRQ-21699\r\n=================================\r\n\r\nVersion:\r\n========\r\nThis cumulative hotfix is intended only for DXD 9.5 customers.\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n - CRQ-21699 - Migration of elasticsearch indices to Tridion 9.5 throws exception\r\n\r\nInstallation:\r\n=============\r\nThis cumulative hotfix provides updated versions of the powershell scripts for migrating IQ and XO Elasticsearch indices.\r\n\r\n1. Copy relevant HF directory to a convenient location.\r\n2. Ensure that target Elasticsearch instance does not contain any Tridion indices.\r\n2. Use relevant migration script according to SDL documented migration procedure.\r\n\r\n\r\nDistributed roles:\r\n==================\r\niq\t\t\t\tiq role - elasticsearch directory only\r\nxo\t\t\t\txo management role - elasticsearch directory only\r\n\r\n\r\nDependencies:\r\n=============\r\nN/A\r\n\r\n\r\nDisclaimer:\r\n===========\r\n\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. \r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore \r\nshould only be installed if approved by Customer Support. Hotfixes should be replaced as soon as possible by the \r\nsubsequent patch release where the problem is fixed.\r\n\r\nCopyright 2015-2020 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.\r\n",
"version": "Sites 9.5"
},
{
"_id": {
"$oid": "635fe2ba94436e1bc8257ca1"
},
"hotfix_name": "CD_8.1.1.5747",
"modified_date": {
"$date": 1501749347403
},
"problem_description": "- CIL.NET incorrectly serializes CustomMetaDateRangeCriteria.\r\n",
"readme_text": "Release Notes for Hotfix CRQ-5747\r\n=================================\r\n\r\nVersion:\r\n========\r\nThis is cumulative hotfix and is intended only for SDL Web 8.1.1\r\n\r\nDescription:\r\n============\r\nThe hotfix include the following fixes: \r\n - CRQ-5747 CustomMetaDateRangeCriteria is not working Web 8\r\n \r\nInstallation:\r\n=============\r\nThis cumulative hotfix provides updated api artifacts.\r\n\r\nREST API\r\n--------------\r\n1. Stop your web application.\r\n2. Replace existing .Net API libraries with latest ones.\r\n3. Restart web application.\r\n\r\nDistributed roles:\r\n==================\r\napi\t\t\tContent Delivery API role (rest)\r\n\r\nFixed problems:\r\n===============\r\n - CRQ-5747 CustomMetaDateRangeCriteria is not working Web 8\r\n \r\nProblem Description\r\n-------------------\r\n- CIL.NET incorrectly serializes CustomMetaDateRangeCriteria.\r\n\r\nHotfix Description\r\n-------------------\r\n- Fixed serialization for CustomMetaDateRangeCriteria.\r\n\r\nDisclaimer:\r\n===========\r\n\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/configuration and therefore should only be installed\r\nif approved by Customer Support. Hotfixes should be replaced as soon as possible by the subsequent patch release where the problem is fixed.\r\n\r\nCopyright 2015-2017 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.",
"version": "Web 8.1.1"
},
{
"_id": {
"$oid": "635fe2bd94436e1bc8257d1e"
},
"hotfix_name": "CD_8.5.0.8270",
"modified_date": {
"$date": 1512571354305
},
"problem_description": "Service container artifacts not available to support DXA 2.\r\n",
"readme_text": "Release Notes for Hotfix CRQ-8270\r\n=================================\r\n\r\nVersion:\r\n========\r\nThis cumulative hotfix is intended only for SDL Web 8.5.0 customers.\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n- CRQ-8270 Provide template service to support DXA 2\r\n\r\nInstallation:\r\n=============\r\nThis cumulative hotfix provides a template service for use with DXA 2. Please\r\nrefer to DXA installation instructions for further details\r\n\r\nDistributed roles:\r\n==================\r\ntemplate\tService container template role\r\n\r\nDependencies:\r\n=============\r\nN/A\r\n\r\nFixed problems:\r\n===============\r\n- CRQ-8270 Provide template service to support DXA 2\r\n\r\nProblem Description\r\n-------------------\r\nService container artifacts not available to support DXA 2.\r\n\r\nHotfix Description\r\n-------------------\r\nProvide template role to support DXA 2.\r\n\r\nDisclaimer:\r\n===========\r\n\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. \r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore \r\nshould only be installed if approved by Customer Support. Hotfixes should be replaced as soon as possible by the \r\nsubsequent patch release where the problem is fixed.\r\n\r\nCopyright 2015-2017 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.\r\n",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2b894436e1bc8257c5c"
},
"hotfix_name": "DXUI_9.5.0.23511",
"modified_date": {
"$date": 1618401587002
},
"problem_description": "- When inserting a keywords into a component, nested child keywords do not load. In the Google Chrome Developer Console the request can be seen correctly but it doesn't load in the GUI.\r\n",
"readme_text": "Release Notes for Hotfix CRQ-23511\r\n\r\nVersion:\r\n- This hotfix is intended for Tridion Sites 9.5\r\n\r\nProblem description: \r\n- When inserting a keywords into a component, nested child keywords do not load. In the Google Chrome Developer Console the request can be seen correctly but it doesn't load in the GUI.\r\n\r\nHotfix description:\r\n- Issue has been resolved by removing some of Item selector's filters for Keyword item type.\r\n\r\nInstallation:\r\n\t1. Create a backup of the \"%TRIDION_HOME%\\ui\\\" folder\r\n\t2. Unzip the contents of the \"hotfix.zip\" to the \"%TRIDION_HOME%\\ui\\\" folder\r\n\t3. Restart the IIS server\r\n\r\nDistributed files:\r\n- Readme.txt (this file)\r\n- DXUI_9.5.0.23511.zip\r\n\r\nDisclaimer:\r\nHotfixes are released at the discretion of SDL based on technical complexity, customer business requirements and schedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by Customer Support of SDL Web Content Management Solutions Division. Hotfixes should be replaced as soon as possible by the subsequent patch release where the problem is fixed.\r\nCopyright \u00a9 2021 SDL PLC. All Rights Reserved. All company product or service names referenced herein are properties of their respective owners. ",
"version": "Sites 9.5"
},
{
"_id": {
"$oid": "635fe2ae94436e1bc8257b13"
},
"hotfix_name": "CD_2013.1.1.1419",
"modified_date": {
"$date": 1450268033302
},
"problem_description": "Database performance issues when deploying content to the Broker database.\r\n",
"readme_text": "Release Notes for Hotfix CRQ-1419\r\n\r\nVersion:\r\nThis hotfix is intended only for SDL Tridion 2013 SP1 HR1 running on Microsoft SQL Server.\r\n\r\nProblem description:\r\nDatabase performance issues when deploying content to the Broker database.\r\n\r\nHotfix description:\r\n Modified the indexes on the Broker database. \r\n\r\nInstallation:\r\n 1. Using Query Analyzer, osql, sqlcmd or SQL Server Management Studio, log in to the Content Delivery database using 'sa'.\r\n 2. Execute the SQL file CRQ-1419.sql.\r\n \r\nDistributed files:\r\n CRQ-1419.sql\r\n Readme.txt (this file)\r\n\r\nFixes included:\r\n None\r\n\r\nDependencies:\r\n NA\r\n\r\nDisclaimer:\r\n Hotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. Hotfixes are made\r\n and tested only for the described problem on a particular environment/configuration and therefore should only be installed\r\n if approved by Customer Support. Hotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright 2015 SDL PLC. All Rights Reserved.\r\n\r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.",
"version": "2013 SP1 HR#1"
},
{
"_id": {
"$oid": "635fe2ac94436e1bc8257a71"
},
"hotfix_name": "CD_2011.1.2.148",
"modified_date": {
"$date": 1443542318074
},
"problem_description": "Database performance issues with the throughput of Deploying to the Broker.\r\n",
"readme_text": "Release Notes for Hotfix CRQ-148\r\n\r\nVersion:\r\nThis hotfix is intended only for SDL Tridion 2011 SP1 HR2 running on Microsoft SQL Server.\r\n\r\nProblem description:\r\nDatabase performance issues with the throughput of Deploying to the Broker.\r\n\r\nHotfix description:\r\n Modified the indexes on the Broker database. \r\n\r\nInstallation:\r\n 1. Using Query Analyzer, osql, sqlcmd or SQL Server Management Studio, log in to the Content Delivery database using 'sa'.\r\n 2. Execute the SQL file CRQ-148.sql.\r\n \r\nDistributed files:\r\n CRQ-148.sql\r\n Readme.txt (this file)\r\n\r\nFixes included:\r\n None\r\n\r\nDependencies:\r\n NA\r\n\r\nDisclaimer:\r\n Hotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. Hotfixes are made\r\n and tested only for the described problem on a particular environment/configuration and therefore should only be installed\r\n if approved by Customer Support. Hotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright 2015 SDL PLC. All Rights Reserved.\r\n\r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.",
"version": "2011 SP1 HR#2"
},
{
"_id": {
"$oid": "635fe2ad94436e1bc8257ac5"
},
"hotfix_name": "OE_2013.0.0.86150",
"modified_date": {
"$date": 1378391377391
},
"problem_description": "When choosing 'No Persona overwritten' on the Preview tab of Experience Manager, an internal server error is thrown.\r\nThis issue only occurs on Asp.Net based webservers.\r\n",
"readme_text": "Release Notes for Hotfix TT86150\r\n\r\nVersion:\r\nThis hotfix is intended only for Tridion Outbound E-mail 2013 GA.\r\n\r\nProblem description:\r\nWhen choosing 'No Persona overwritten' on the Preview tab of Experience Manager, an internal server error is thrown.\r\nThis issue only occurs on Asp.Net based webservers.\r\n\r\nHotfix description:\r\nThis hotfix fixes the issue that the audiencemanager_cartridge.jar doesn't correctly handle quoted 'None' or 'Anon' values\r\nwhen checking the personaId cookie set by Experience Manager.\r\n\r\nInstallation: \r\n2. Locate the Tridion\\lib or bin\\lib folder.\r\n3. Replace the existing audiencemanager_cartridge.jar with the one from this hotfix.\r\n\r\nDistributed files:\r\naudiencemanager_cartridge.jar\r\n\r\nFixes included:\r\nN.A.\r\n\r\nDependencies:\r\nN.A.\r\n\r\nDisclaimer:\r\nHotfixes are released at the discretion of SDL Tridion based on technical complexity, customer business requirements and schedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by SDL Tridion Customer Support. Hotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright (c) 2013 SDL Tridion B.V.\r\n",
"version": "2013"
},
{
"_id": {
"$oid": "635fe2b294436e1bc8257be8"
},
"hotfix_name": "CD_11.1.0.19653",
"modified_date": {
"$date": 1601628781614
},
"problem_description": "- Broker query api didn't return results for Turkish culture (Tr-tr).\r\n",
"readme_text": "Release Notes for Hotfixes CRQ-19653\r\n====================================\r\n\r\nVersion:\r\n========\r\nThis cumulative hotfix is intended only for SDL Sites 9.1 customers.\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n - CRQ-19653 - Turkish Culture is returning no data\r\n\r\n\r\nDistributed roles:\r\n==================\r\ndotnet rest api - CIL.NET\r\n\r\n\r\nFixed problems:\r\n===============\r\n - CRQ-19653- fixed code that serialized broker query.\r\n\r\n\r\nProblem Description\r\n-------------------\r\n- Broker query api didn't return results for Turkish culture (Tr-tr).\r\n\r\n\r\nHotfix Description\r\n-------------------\r\n- During the serialization of the broker query it didn't convert some values to string invariants and as such the resultant json contained unicode characters breaking the query.\r\n\r\n\r\n\r\nDisclaimer:\r\n===========\r\n\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. \r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore \r\nshould only be installed if approved by Customer Support. Hotfixes should be replaced as soon as possible by the \r\nsubsequent patch release where the problem is fixed.\r\n\r\nCopyright 2015-2020 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.\r\n",
"version": "Sites 9.1"
},
{
"_id": {
"$oid": "635fe2ac94436e1bc8257a6a"
},
"hotfix_name": "TM_3.0.0.83651",
"modified_date": {
"$date": 1363358077248
},
"problem_description": "Creating a new translation job on large BluePrints is slow with multiple items selected.\r\n",
"readme_text": "Release Notes for Hotfix TT83651\r\n\r\nVersion:\r\nThis hotfix is intended only for SDL Tridion Translation Manager 3.0 included in Tridion 2011 SP1.\r\n\r\nProblem description:\r\nCreating a new translation job on large BluePrints is slow with multiple items selected.\r\n\r\nHotfix description:\r\nIn order to create the translation job the BluePrint of each item must be read. If the BluePrint contains several hundred publications this can be a time consuming operation. This hotfix allows the Translation Manager to read multiple items concurrently decreasing the time it takes before the translation job dialog appears.\r\nTo enable concurrent loading of BluePrints a new XML element has to be added to %TRIDION%\\Config\\TranslationManager.xml:\r\n\r\n\r\n...\r\n\t4\r\n...\r\n\r\n\r\nwhere 4 is the number of concurrent BluePrint reads that are allowed for each request made to the Translation Manager from the UI. This implies that the total number of concurrent reads can be significently higher than the number specified if several concurrent users have Translation Management rights assigned.\r\nThe optimal number of concurrent requests depends on the database load. Ensure the number is not increased beyond what delivers a noticable performance increase..\r\n\r\nIn order to support the concurrent reads in the CoreService it can be necessary to adjust %TRIDION%\\bin\\TcmServiceHost.exe.config.\r\nLocate the \"behavior\" element with the name \"Tridion.ContentManager.ServiceHost.WindowsServiceHost.CoreServiceBehavior\" and\r\nadd (or edit an existing) serviceThrottling element as follows:\r\n\r\n\r\n...\r\n \r\n\r\n...\r\n\r\n\r\nFor details on each of these properties, please see the MSDN documentation for the ServiceThrottlingBehavior Class. Again the optimal numbers depends on the environment. Ensure the numbers are not increased beyond what delivers a noticable performance increase.\r\n\r\nInstallation:\r\n1. Stop the Tridion Translation Manager Service\r\n2. Move or delete the file Tridion.TranslationManager.DomainModel.dll located in the %windir%\\assembly\\GAC_MSIL\\Tridion.TranslationManager.DomainModel\\3.0.0.116__360aac4d3354074b\\ folder (with the command prompt).\r\n3. Copy the file Tridion.TranslationManager.DomainModel.dll from this hotfix to the %windir%\\assembly\\GAC_MSIL\\Tridion.TranslationManager.DomainModel\\3.0.0.116__360aac4d3354074b\\ folder (with the command prompt).\r\n4. Copy the file Tridion.TranslationManager.DomainModel.dll from this hotfix to \"%Tridion%\\Translation Manager\" replacing the old version.\r\n5. Copy the file Tridion.TranslationManager.Service.exe from this hotfix to \"%Tridion%\\Translation Manager\" replacing the old version.\r\n6. Copy the file Tridion.TranslationManager.UI.Model.dll to \"%Tridion%\\web\\WebUI\\WebRoot\\bin\" replacing the old version.\r\n7. Copy the file Microsoft.Web.Services2.dll to %windir%\\assembly using Windows Explorer (this will register the assembly in the GAC under assembly version 2.0.3.0)\r\n8. Copy the file WSWebServices.dll to %windir%\\assembly using Windows Explorer (this will register the assembly in the GAC)\r\n9. Restart the Content Manager Explorer Web site.\r\n10. Start the Tridion Translation Manager Service\r\n\r\nDistributed files:\r\n- Tridion.TranslationManager.DomainModel.dll (version 3.0.0.200)\r\n- Tridion.TranslationManager.UI.Model.dll (version 3.0.0.200)\r\n- Tridion.TranslationManager.Service.exe (version 3.0.0.165)\r\n- Microsoft.Web.Services2.dll (file version 2.0.5050.0)\r\n- WSWebServices.dll (version 9.0.4503.21315)\r\n\r\nFixes included:\r\n TT79169: Error retrieving component with keywords if the translated keyword title does not match the keyword title in the target publication.\r\n TT80330: The Tridion Application Monitoring is not receiving heartbeats from the Translation Manager Serice.\r\n TT80837: A \"BadCredentialException\" error occurs when connecting to World Server.\r\n TT80954: Error creating a translation job from the target publication if the user does not have read access to the source publication.\r\n TT81098: Creating a translation job is slow when multiple items are selected.\r\n TT81187: Error \"Object reference not set to an instance of an object\" when creating a Translation Job with some BluePrint configurations.\r\n TT81935: Jobs retrieved from World Server workflows with sub-workflows are canceled after retrieval.\r\n TT82596: The UI will show the option of translating to a language even if no translation source is configured in a parent publication.\r\n TT82766: Once a target language has been deselected it no longer shows up in the UI.\r\n TT82987: Translation Job screen takes very long to load when creating a translation job with multiple components are selected.\r\n TT83219: The translation job title cannot be changed from the TranslationJobCreatedEvent when created with multiple items selected.\r\n TT83312: Slow initial load of the CME for non admin users.\r\nDependencies:\r\n N/A\r\n\r\nDisclaimer:\r\nHotfixes are released at the discretion of SDL Tridion based on technical complexity, customer business requirements and schedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by SDL Tridion Customer Support. Hotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright (c) 2013 SDL Tridion B.V.\r\n",
"version": "2011 SP1 HR#1"
},
{
"_id": {
"$oid": "635fe2af94436e1bc8257b5b"
},
"hotfix_name": "CM_2013.1.1.3709",
"modified_date": {
"$date": 1486727057325
},
"problem_description": "A database error occurred while executing Stored Procedure \"EDA_ITEMS.GETPUBLISHITEMS\".\r\nORA-01013: user requested cancel of current operation\r\nORA-06512: at \"TCM_SIEMENS_229319.EDA_ITEMS\", line 7397\r\nORA-06512: at \"TCM_SIEMENS_229319.EDA_ITEMS\", line 8589\r\nORA-06512: at line 1\r\nComponent: Tridion.ContentManager.Publishing\r\nErrorcode: 831\r\nUser: W08R26414\\Admin\r\nStackTrace Information Details:\r\nat Oracle.DataAccess.Client.OracleException.HandleErrorHelper(Int32 errCode, OracleConnection conn, IntPtr opsErrCtx, OpoSqlValCtx* pOpoSqlValCtx, Object src, String procedure, Boolean bCheck, Int32 isRecoverable)\r\nat Oracle.DataAccess.Client.OracleException.HandleError(Int32 errCode, OracleConnection conn, String procedure, IntPtr opsErrCtx, OpoSqlValCtx* pOpoSqlValCtx, Object src, Boolean bCheck)\r\nat Oracle.DataAccess.Client.OracleCommand.ExecuteReader(Boolean requery, Boolean fillRequest, CommandBehavior behavior)\r\nat Oracle.DataAccess.Client.OracleCommand.ExecuteDbDataReader(CommandBehavior behavior)\r\nat System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior)\r\nat Tridion.ContentManager.Data.AdoNet.DatabaseUtilities.ExecuteReader(StoredProcedureInvocation storedProcedureInvocation, CommandBehavior commandBehavior)\r\nat Tridion.ContentManager.Data.AdoNet.Oracle.OracleDatabaseUtilities.ExecuteReader(StoredProcedureInvocation storedProcedureInvocation, CommandBehavior commandBehavior)\r\nat Tridion.ContentManager.Data.AdoNet.Oracle.OracleDatabaseUtilities.ExecuteReader(StoredProcedureInvocation storedProcedureInvocation, CommandBehavior commandBehavior)\r\nat Tridion.ContentManager.Data.AdoNet.DatabaseUtilities.ExecuteReader(StoredProcedureInvocation storedProcedureInvocation)\r\nat Tridion.ContentManager.Data.AdoNet.Oracle.OracleDatabaseUtilities.ExecuteReader(StoredProcedureInvocation storedProcedureInvocation)\r\nat Tridion.ContentManager.Data.AdoNet.IdentifiableObjectDataMapper.Tridion.ContentManager.Data.IIdentifiableObjectDataMapper.GetListResolvedItems(TcmUri itemToResolve, ResolveInstructionData instructionData, IEnumerable`1 publishContexts)\r\nat Tridion.ContentManager.Publishing.Resolving.ResolverBase.ResolveDataObjects(IEnumerable`1 items, ResolveInstruction instruction, IEnumerable`1 contexts)\r\nat Tridion.ContentManager.Publishing.Resolving.ResolverBase.Resolve(IEnumerable`1 items, ResolveInstruction instruction, IEnumerable`1 contexts)\r\nat Tridion.ContentManager.Publishing.Resolving.ResolveEngine.ResolveItems(IEnumerable`1 items, ResolveInstruction instruction, IEnumerable`1 contexts)\r\nat Tridion.ContentManager.Publishing.Resolving.ResolveEngine.ResolveItem(IdentifiableObject item, ResolveInstruction instruction, PublishContext context)\r\nat Tridion.ContentManager.Publishing.Handling.DefaultPublishTransactionHandler.HandlePublishRequest(PublishTransaction publishTransaction)\r\nat Tridion.ContentManager.Publishing.Handling.DefaultPublishTransactionHandler.ProcessPublishTransaction(PublishTransaction publishTransaction)\r\nat Tridion.ContentManager.Publishing.Publisher.QueueMessageHandler.HandleMessage()\r\n",
"readme_text": "Release Notes for Hotfix CRQ-3709\r\n\r\nVersion:\r\nThis hotfix is intended only for SDL Tridion Content Manager 2013 SP1 HR1.\r\n\r\nProblem description:\r\nA database error occurred while executing Stored Procedure \"EDA_ITEMS.GETPUBLISHITEMS\".\r\nORA-01013: user requested cancel of current operation\r\nORA-06512: at \"TCM_SIEMENS_229319.EDA_ITEMS\", line 7397\r\nORA-06512: at \"TCM_SIEMENS_229319.EDA_ITEMS\", line 8589\r\nORA-06512: at line 1\r\n\r\n\r\nComponent: Tridion.ContentManager.Publishing\r\nErrorcode: 831\r\nUser: W08R26414\\Admin\r\n\r\nStackTrace Information Details:\r\n at Oracle.DataAccess.Client.OracleException.HandleErrorHelper(Int32 errCode, OracleConnection conn, IntPtr opsErrCtx, OpoSqlValCtx* pOpoSqlValCtx, Object src, String procedure, Boolean bCheck, Int32 isRecoverable)\r\n at Oracle.DataAccess.Client.OracleException.HandleError(Int32 errCode, OracleConnection conn, String procedure, IntPtr opsErrCtx, OpoSqlValCtx* pOpoSqlValCtx, Object src, Boolean bCheck)\r\n at Oracle.DataAccess.Client.OracleCommand.ExecuteReader(Boolean requery, Boolean fillRequest, CommandBehavior behavior)\r\n at Oracle.DataAccess.Client.OracleCommand.ExecuteDbDataReader(CommandBehavior behavior)\r\n at System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior)\r\n at Tridion.ContentManager.Data.AdoNet.DatabaseUtilities.ExecuteReader(StoredProcedureInvocation storedProcedureInvocation, CommandBehavior commandBehavior)\r\n at Tridion.ContentManager.Data.AdoNet.Oracle.OracleDatabaseUtilities.ExecuteReader(StoredProcedureInvocation storedProcedureInvocation, CommandBehavior commandBehavior)\r\n at Tridion.ContentManager.Data.AdoNet.Oracle.OracleDatabaseUtilities.ExecuteReader(StoredProcedureInvocation storedProcedureInvocation, CommandBehavior commandBehavior)\r\n at Tridion.ContentManager.Data.AdoNet.DatabaseUtilities.ExecuteReader(StoredProcedureInvocation storedProcedureInvocation)\r\n at Tridion.ContentManager.Data.AdoNet.Oracle.OracleDatabaseUtilities.ExecuteReader(StoredProcedureInvocation storedProcedureInvocation)\r\n at Tridion.ContentManager.Data.AdoNet.IdentifiableObjectDataMapper.Tridion.ContentManager.Data.IIdentifiableObjectDataMapper.GetListResolvedItems(TcmUri itemToResolve, ResolveInstructionData instructionData, IEnumerable`1 publishContexts)\r\n at Tridion.ContentManager.Publishing.Resolving.ResolverBase.ResolveDataObjects(IEnumerable`1 items, ResolveInstruction instruction, IEnumerable`1 contexts)\r\n at Tridion.ContentManager.Publishing.Resolving.ResolverBase.Resolve(IEnumerable`1 items, ResolveInstruction instruction, IEnumerable`1 contexts)\r\n at Tridion.ContentManager.Publishing.Resolving.ResolveEngine.ResolveItems(IEnumerable`1 items, ResolveInstruction instruction, IEnumerable`1 contexts)\r\n at Tridion.ContentManager.Publishing.Resolving.ResolveEngine.ResolveItem(IdentifiableObject item, ResolveInstruction instruction, PublishContext context)\r\n at Tridion.ContentManager.Publishing.Handling.DefaultPublishTransactionHandler.HandlePublishRequest(PublishTransaction publishTransaction)\r\n at Tridion.ContentManager.Publishing.Handling.DefaultPublishTransactionHandler.ProcessPublishTransaction(PublishTransaction publishTransaction)\r\n at Tridion.ContentManager.Publishing.Publisher.QueueMessageHandler.HandleMessage()\r\n\r\nHotfix description:\r\nIndex for ITEM_REFERENCE_PUBLICATIONS was added. SQL queries in the stored procedure COMP_GETPUBLISHITEMS were optimised.\r\n\r\nInstallation:\r\n 1. Stop all TCM Services, IIS Service, and the TCM COM+ Application.\r\n\r\n\r\n\t\tIf the Database is Oracle \r\n\t\t 1. Using SQL*Plus, connect as \"tridion_sys\" to the database instance. \r\n\t\t 2. Temporarily grant additional rights to the Tridion database user (typically TCMDBUser):\r\n\t\t\tGRANT CREATE TRIGGER TO &TCMDBUser;\r\n\t\t\tGRANT CREATE PROCEDURE TO &TCMDBUser;\r\n\t\t\tGRANT CREATE ANY TABLE TO &TCMDBUser;\r\n\t\t\tGRANT CREATE SEQUENCE TO &TCMDBUser;\r\n\t\t\tGRANT EXECUTE ON SYS.DBMS_UTILITY TO &TCMDBUser;\r\n\t\t 3. Using SQL*Plus, log in as the Tridion database user (typically TCMDBUser).\r\n\t\t 4. Execute the SQL script CM_2013.1.1.3709_ORACLE.sql.\r\n\t\t 5. Check the file CM_2013.1.1.3709.log for errors.\r\n\t\t 6. Revoke the additional rights from the Tridion database user\r\n\t\t\tREVOKE EXECUTE ON SYS.DBMS_UTILITY FROM &TCMDBUSER;\r\n\t\t\tREVOKE CREATE TRIGGER FROM &TCMDBUser;\r\n\t\t\tREVOKE CREATE PROCEDURE FROM &TCMDBUser;\r\n\t\t\tREVOKE CREATE ANY TABLE FROM &TCMDBUser;\r\n\t\t\tREVOKE CREATE SEQUENCE FROM &TCMDBUser;\r\n\r\n 2. Restart the IIS Service, TCM Services and TCM COM+ Application.\r\n\r\nDistributed files:\r\n\tIX_ITEM_REF_PUB_03_3709.sql\r\n\tEDA_ITEMS_ORACLE.sql\r\n\tCM_2013.1.1.3709_ORACLE.sql\r\n\tTCM_RECOMPILE_PACKAGES.sql\r\n\tReadme.txt (this file)\r\n\r\n\r\nFixes included:\r\n\tCM_2013.1.1.88489\r\n\tCM_2013.1.1.2015\r\n\tCM_2013.1.1.2740\r\n\r\nDependencies:\r\n\t2013 SP1 HR1\r\n\tCM_2013.1.1.88554\r\n\r\n\r\nDisclaimer:\r\n\tHotfixes are released at the discretion of SDL based on technical complexity, customer business requirements and schedules.\r\n\tHotfixes are made and tested only for the described problem on a particular environment\\configuration and therefore should only be installed if approved by Customer Support of SDL Web Content Management Solutions Division.\r\n\tHotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright 2017 SDL PLC. All Rights Reserved. All company product or service names referenced herein are properties of their respective owners.\r\n",
"version": "2013 SP1 HR#1"
},
{
"_id": {
"$oid": "635fe2ac94436e1bc8257a6e"
},
"hotfix_name": "TM_3.0.0.85204",
"modified_date": {
"$date": 1366883776229
},
"problem_description": "Translation jobs might not be completed even though all items are in Translation Content Retrieval in World Server.\r\n",
"readme_text": "Release Notes for Hotfix TT85204\r\n\r\nVersion:\r\nThis hotfix is intended only for SDL Tridion Translation Manager 3.0 included in Tridion 2011 SP1.\r\n\r\nProblem description:\r\nTranslation jobs might not be completed even though all items are in Translation Content Retrieval in World Server.\r\n\r\nHotfix description:\r\nThe Translation Manager enters a loop where it repeatedly check the status of a few projects in World Server over and over again.\r\n\r\n\r\nInstallation:\r\n1. Stop the Tridion Translation Manager Service\r\n2. Move or delete the file Tridion.TranslationManager.DomainModel.dll located in the %windir%\\assembly\\GAC_MSIL\\Tridion.TranslationManager.DomainModel\\3.0.0.116__360aac4d3354074b\\ folder (with the command prompt).\r\n3. Copy the file Tridion.TranslationManager.DomainModel.dll from this hotfix to the %windir%\\assembly\\GAC_MSIL\\Tridion.TranslationManager.DomainModel\\3.0.0.116__360aac4d3354074b\\ folder (with the command prompt).\r\n4. Copy the file Tridion.TranslationManager.DomainModel.dll from this hotfix to \"%Tridion%\\Translation Manager\" replacing the old version.\r\n5. Copy the file Tridion.TranslationManager.Service.exe from this hotfix to \"%Tridion%\\Translation Manager\" replacing the old version.\r\n6. Copy the file Tridion.TranslationManager.UI.Model.dll to \"%Tridion%\\web\\WebUI\\WebRoot\\bin\" replacing the old version.\r\n7. Copy the file Microsoft.Web.Services2.dll to %windir%\\assembly using Windows Explorer (this will register the assembly in the GAC under assembly version 2.0.3.0)\r\n8. Copy the file WSWebServices.dll to %windir%\\assembly using Windows Explorer (this will register the assembly in the GAC)\r\n9. Restart the Content Manager Explorer Web site.\r\n10. Start the Tridion Translation Manager Service\r\n\r\nDistributed files:\r\n- Tridion.TranslationManager.DomainModel.dll (version 3.0.0.227)\r\n- Tridion.TranslationManager.UI.Model.dll (version 3.0.0.226)\r\n- Tridion.TranslationManager.Service.exe (version 3.0.0.165)\r\n- Microsoft.Web.Services2.dll (file version 2.0.5050.0)\r\n- WSWebServices.dll (version 9.0.4503.21315)\r\n\r\nFixes included:\r\n TT79169: Error retrieving component with keywords if the translated keyword title does not match the keyword title in the target publication.\r\n TT80330: The Tridion Application Monitoring is not receiving heartbeats from the Translation Manager Serice.\r\n TT80837: A \"BadCredentialException\" error occurs when connecting to World Server.\r\n TT80954: Error creating a translation job from the target publication if the user does not have read access to the source publication.\r\n TT81098: Creating a translation job is slow when multiple items are selected.\r\n TT81187: Error \"Object reference not set to an instance of an object\" when creating a Translation Job with some BluePrint configurations.\r\n TT81935: Jobs retrieved from World Server workflows with sub-workflows are canceled after retrieval.\r\n TT82596: The UI will show the option of translating to a language even if no translation source is configured in a parent publication.\r\n TT82766: Once a target language has been deselected it no longer shows up in the UI.\r\n TT82987: Translation Job screen takes very long to load when creating a translation job with multiple components are selected.\r\n TT83219: The translation job title cannot be changed from the TranslationJobCreatedEvent when created with multiple items selected.\r\n TT83312: Slow initial load of the CME for non admin users.\r\n TT83819: Creating a translation job takes a long time for shared Items.\r\n TT84020: Translation retrieval stops for aggregated items when the first error is encountered.\r\n TT84516: Slow loading of translation configuration and item retrieval from World Server.\r\n TT84775: Events are not being raised when the job change state fue to processing from the Translation Manager Service.\r\n TT85137: Unable to save a translation job in Definition state if its workflow has been deleted in World Server.\r\n TT85138: Unable to send a job for translation if one or more of the added items has been deleted after the job was created.\r\n TT85167: Unable to send localized items for translation.\r\n\r\nDependencies:\r\n N/A\r\n\r\nDisclaimer:\r\nHotfixes are released at the discretion of SDL Tridion based on technical complexity, customer business requirements and schedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by SDL Tridion Customer Support. Hotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright (c) 2013 SDL Tridion B.V.\r\n",
"version": "2011 SP1 HR#1"
},
{
"_id": {
"$oid": "635fe2ac94436e1bc8257a69"
},
"hotfix_name": "TM_3.0.0.83312",
"modified_date": {
"$date": 1355391672784
},
"problem_description": "Slow initial load of the CME for non admin users.\r\n",
"readme_text": "Release Notes for Hotfix TT83312\r\n\r\nVersion:\r\nThis hotfix is intended only for SDL Tridion Translation Manager 3.0 included in Tridion 2011 SP1.\r\n\r\nProblem description:\r\nSlow initial load of the CME for non admin users.\r\n\r\nHotfix description:\r\nTranslation Manager was performing one database read per publication for non admin users to determine if the user has translation management rights in any publication. The hotfix changes Translation Manager to first do a single read to determine which publications have translation related rights defined. It will then perform a database read for these publications only. As Translation is typically only configured on a small subset of the publications this will reduce the number of database reads required on most systems.\r\n\r\n\r\nInstallation:\r\n1. Stop the Tridion Translation Manager Service\r\n2. Move or delete the file Tridion.TranslationManager.DomainModel.dll located in the %windir%\\assembly\\GAC_MSIL\\Tridion.TranslationManager.DomainModel\\3.0.0.116__360aac4d3354074b\\ folder (with the command prompt).\r\n3. Copy the file Tridion.TranslationManager.DomainModel.dll from this hotfix to the %windir%\\assembly\\GAC_MSIL\\Tridion.TranslationManager.DomainModel\\3.0.0.116__360aac4d3354074b\\ folder (with the command prompt).\r\n4. Copy the file Tridion.TranslationManager.DomainModel.dll from this hotfix to \"%Tridion%\\Translation Manager\" replacing the old version.\r\n5. Copy the file Tridion.TranslationManager.Service.exe from this hotfix to \"%Tridion%\\Translation Manager\" replacing the old version.\r\n6. Copy the file Tridion.TranslationManager.UI.Model.dll to \"%Tridion%\\web\\WebUI\\WebRoot\\bin\" replacing the old version.\r\n7. Copy the file Microsoft.Web.Services2.dll to %windir%\\assembly using Windows Explorer (this will register the assembly in the GAC under assembly version 2.0.3.0)\r\n8. Copy the file WSWebServices.dll to %windir%\\assembly using Windows Explorer (this will register the assembly in the GAC)\r\n9. Restart the Content Manager Explorer Web site.\r\n10. Start the Tridion Translation Manager Service\r\n\r\nDistributed files:\r\n- Tridion.TranslationManager.DomainModel.dll (version 3.0.0.199)\r\n- Tridion.TranslationManager.UI.Model.dll (version 3.0.0.198)\r\n- Tridion.TranslationManager.Service.exe (version 3.0.0.165)\r\n- Microsoft.Web.Services2.dll (file version 2.0.5050.0)\r\n- WSWebServices.dll (version 9.0.4503.21315)\r\n\r\nFixes included:\r\n TT79169: Error retrieving component with keywords if the translated keyword title does not match the keyword title in the target publication.\r\n TT80330: The Tridion Application Monitoring is not receiving heartbeats from the Translation Manager Serice.\r\n TT80837: A \"BadCredentialException\" error occurs when connecting to World Server.\r\n TT80954: Error creating a translation job from the target publication if the user does not have read access to the source publication.\r\n TT81098: Creating a translation job is slow when multiple items are selected.\r\n TT81187: Error \"Object reference not set to an instance of an object\" when creating a Translation Job with some BluePrint configurations.\r\n TT81935: Jobs retrieved from World Server workflows with sub-workflows are canceled after retrieval.\r\n TT82596: The UI will show the option of translating to a language even if no translation source is configured in a parent publication.\r\n TT82766: Once a target language has been deselected it no longer shows up in the UI.\r\n TT82987: Translation Job screen takes very long to load when creating a translation job with multiple components are selected.\r\n TT83219: The translation job title cannot be changed from the TranslationJobCreatedEvent when created with multiple items selected.\r\n\r\nDependencies:\r\n N/A\r\n\r\nDisclaimer:\r\nHotfixes are released at the discretion of SDL Tridion based on technical complexity, customer business requirements and schedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by SDL Tridion Customer Support. Hotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright (c) 2012 SDL Tridion B.V.\r\n",
"version": "2011 SP1 HR#1"
},
{
"_id": {
"$oid": "635fe2b094436e1bc8257b7c"
},
"hotfix_name": "TM_2013.1.1.1348",
"modified_date": {
"$date": 1449494850600
},
"problem_description": "Translation Manager does not use World Server version 11 as efficiently as possible.\r\n",
"readme_text": "Release Notes for Hotfix CRQ-1348 \r\n\r\nVersion:\r\nThis hotfix is intended only for SDL Tridion Translation Manager 7.1 included in Tridion 2013 SP1 HR1.\r\n\r\nProblem description:\r\nTranslation Manager does not use World Server version 11 as efficiently as possible.\r\n\r\nHotfix description:\r\nWorld Server version 11 introduces a new API allowing Translation Manager to communicate more efficiently with World Server. This hotfix allows translation manager to use this new API. The hotfix does not have any impact on World Server version 10, as this version does not include the new API.\r\n\r\nInstallation:\r\n1. Stop the Tridion Translation Manager Service\r\n2. Stop Content Manager Explorer Web site\r\n3. Move or delete the file Tridion.TranslationManager.DomainModel.dll located in the %windir%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.TranslationManager.DomainModel\\v4.0_7.1.0.116__360aac4d3354074b\\ folder (with the command prompt).\r\n4. Copy the file Tridion.TranslationManager.DomainModel.dll from this hotfix to the %windir%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.TranslationManager.DomainModel\\v4.0_7.1.0.116__360aac4d3354074b\\ folder (with the command prompt).\r\n5. Copy the file Tridion.TranslationManager.DomainModel.dll from this hotfix to \"%Tridion%\\Translation Manager\" replacing the old version.\r\n6. Copy the file WSWebServices.dll from this hotfix to \"%Tridion%\\Translation Manager\" replacing the old version.\r\n7. Create folder %windir%\\assembly\\GAC_MSIL\\WSWebServices\\9.0.5444.27742__c28cdb26c445c888\r\n8. Copy the file WSWebServices.dll to %windir%\\assembly\\GAC_MSIL\\WSWebServices\\9.0.5444.27742__c28cdb26c445c888\r\n9. Open %TRIDION_HOME%\\config\\TranslationManager.xml\r\n10. Change the URL in the element to point to the new API (see World Server documentation for details).\r\n11. Save %TRIDION_HOME%\\config\\TranslationManager.xml\r\n12. Restart the Content Manager Explorer Web site.\r\n13. Start the Tridion Translation Manager Service.\r\n\r\nOptionally the following configuration values can be set in %TRIDION_HOME%\\config\\TranslationManager.xml as well:\r\n\r\nloginTimeout:\r\nAttribute on the element. Specifies the timeout for logging in to World Server in seconds. The default is 20 seconds.\r\n\r\nrequestTimeout:\r\nAttribute on the element. Specifies the timeout for sending or retreiving data in seconds. The default is 5 minutes.\r\n\r\nWorldServerProxy:\r\nChild element of the root element on the following form:\r\nproxy.domain.com\r\n\r\nDistributed files:\r\n- Tridion.TranslationManager.DomainModel.dll (version 7.1.0.153)\r\n- WSWebServices.dll (version 9.0.5444.27742)\r\n\r\nFixes included:\r\n TT88454: Not all data transmitted from World Server to Tridion was compressed causing transfer of more data than necessary.\r\n TT88486: User can not create pull translation job if he does not have access to publication/folder where source configuration is configured\r\n TT88491: Translation Manager revert retrieved translation for target item in \"Reserved state\"\t\r\n TT88559: It take too long to update World Server workflow information on slow connection\r\n TT88616: It is not possible to use a local bundle to create a Pull Job with shared items\r\n (this hotfix was not independently released, it is only available with TT88617)\r\n TT88617: It is not possible to have a translation retrieved by Tridion multiple times in the translation workflow.\r\n TT88667: It is not possible to configure the translation system configuration caching interval\r\n TT88737: Unable to translate shared item from publication that has configured parents further up in the tree.\r\n\r\nDependencies:\r\n\tTridion 2013 SP1 HR1\r\n\r\nDisclaimer:\r\nHotfixes are released at the discretion of SDL Tridion based on technical complexity, customer business requirements and schedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by SDL Tridion Customer Support. Hotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright (c) 2015 SDL Group.\r\n",
"version": "2013 SP1 HR#1"
},
{
"_id": {
"$oid": "635fe2a994436e1bc82579ea"
},
"hotfix_name": "CM_2011.0.78508",
"modified_date": {
"$date": 1332316325762
},
"problem_description": "Merge Cells button is missing when editing a table in a RTF.\r\n",
"readme_text": "Release Notes for Hotfix TT78508\r\n\r\nVersion:\r\nThis hotfix is intended for SDL Tridion Content Manager Explorer 2011.\r\n\r\nProblem description:\r\nMerge Cells button is missing when editing a table in a RTF.\r\n\r\nHotfix description:\r\nMerge Cells button added to the Ribbon Toolbar on Table Editor popup.\r\n\r\nInstallation:\r\n\t1. Move or delete the file TableEditorToolbar.ascx located in the %TRIDION_HOME%\\web\\WebUI\\Editors\\CME\\Controls\\Toolbars folder.\r\n\t2. Move or delete the file ribbontoolbar.css located in the %TRIDION_HOME%\\web\\WebUI\\Editors\\CME\\Themes\\Carbon\\Controls folder.\r\n\t3. Move or delete the file ribbontoolbar.sprites.css located in the %TRIDION_HOME%\\web\\WebUI\\Editors\\CME\\Themes\\Carbon\\Controls folder.\r\n\t4. Move or delete the file contextmenu.css located in the %TRIDION_HOME%\\web\\WebUI\\Editors\\CME\\Themes\\Carbon\\Controls folder.\r\n\t5. Move or delete the file contextmenu.sprites.css located in the %TRIDION_HOME%\\web\\WebUI\\Editors\\CME\\Themes\\Carbon\\Controls folder.\r\n\t6. Move or delete the file button.css located in the %TRIDION_HOME%\\web\\WebUI\\Editors\\CME\\Themes\\Carbon\\Controls folder.\r\n\t7. Move or delete the file button.sprites.css located in the %TRIDION_HOME%\\web\\WebUI\\Editors\\CME\\Themes\\Carbon\\Controls folder.\r\n\t8. Move or delete all the files located in the %TRIDION_HOME%\\web\\WebUI\\Editors\\CME\\Themes\\Carbon\\Sprites folder.\r\n\t\r\n\t9. Copy the file TableEditorToolbar.ascx from this hotfix to the %TRIDION_HOME%\\web\\WebUI\\Editors\\CME\\Controls\\Toolbars folder.\r\n\t10. Copy the file ribbontoolbar.css from this hotfix to the %TRIDION_HOME%\\web\\WebUI\\Editors\\CME\\Themes\\Carbon\\Controls folder.\r\n\t11. Copy the file ribbontoolbar.sprites.css from this hotfix to the %TRIDION_HOME%\\web\\WebUI\\Editors\\CME\\Themes\\Carbon\\Controls folder.\r\n\t12. Copy the file contextmenu.css from this hotfix to the %TRIDION_HOME%\\web\\WebUI\\Editors\\CME\\Themes\\Carbon\\Controls folder.\r\n\t13. Copy the file contextmenu.sprites.css from this hotfix to the %TRIDION_HOME%\\web\\WebUI\\Editors\\CME\\Themes\\Carbon\\Controls folder.\r\n\t14. Copy the file button.css from this hotfix to the %TRIDION_HOME%\\web\\WebUI\\Editors\\CME\\Themes\\Carbon\\Controls folder.\r\n\t15. Copy the file button.sprites.css from this hotfix to the %TRIDION_HOME%\\web\\WebUI\\Editors\\CME\\Themes\\Carbon\\Controls folder.\r\n\t16. Copy all the files from the Sprites folder in this hotfix to the %TRIDION_HOME%\\web\\WebUI\\Editors\\CME\\Themes\\Carbon\\Sprites folder.\r\n\t17. Open %TRIDION_HOME%\\web\\WebUI\\WebRoot\\Configuration\\System.config file.\r\n\t18. Locate /Configuration/servicemodel/server node in Sytem.config file and increase the value of its 'modification' attribute to notify client browsers to update their cache.\r\n\r\nDistributed files:\r\n\r\n - Readme.txt (this file)\r\n - TableEditorToolbar.ascx\r\n - ribbontoolbar.css\r\n - ribbontoolbar.sprites.css\r\n - contextmenu.css\r\n - contextmenu.sprites.css\r\n - button.css\r\n - button.sprites.css\r\n - Sprites\r\n\t`- cme_0.png\r\n\t`- cme_1.png\r\n\t`- cme_2.png\r\n\t`- cme_3.png\r\n\t`- cme_4.png\r\n\t`- cme_5.png\r\n\t`- cme_6.png\r\n \r\nFixes included:\r\n N/A\r\n\r\nDependencies:\r\n N/A\r\n\r\nDisclaimer:\r\nHotfixes are released at the discretion of SDL Tridion based on technical complexity, customer business requirements and schedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by SDL Tridion Customer Support. Hotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright 2011 SDL PLC. All Rights Reserved. All company product or service names referenced herein are properties of their respective owners.",
"version": "2011 SP1"
},
{
"_id": {
"$oid": "635fe2aa94436e1bc8257a07"
},
"hotfix_name": "CD_2011.1.1.80995",
"modified_date": {
"$date": 1339693744601
},
"problem_description": "The Component link field type not exposed in keyword metadata when requesting keyword metadata in the broker API.\r\nWhen deploying a complex Taxonomy containing multiparent keywords and more than a few thousand keywords with many related items the deployment\r\nexceeds the transaction timeout and can take up to an hour to complete.\r\nWhen undeploying a complex transport package undeployment fails with following error message Unknown entity: com.tridion.storage.ItemMeta_$$_javassist_13.\r\nPublishing process stuck in Resolving state\r\n",
"readme_text": "Release Notes for Hotfix TT80995\r\n================================\r\n\r\nVersion:\r\n========\r\nThis cumulative hotfix and is intended only for Tridion 2011 SP1 HR1\r\nThe hotfix includes the following fixes:\r\n- TT77133 Component link field type not exposed in keyword metadata\r\n- TT78523 Publish a large package with many linked components in 2011 SP1 along with a large, nested taxonomy exceeds transaction timeout\r\n- TT79176 Error while unpublishing: Unable to remove data entity, Unknown entity: com.tridion.storage.ItemMeta_$$_javassist_13, \r\n- TT80995 Publishing process stuck in Resolving state\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n- TT80995 Publishing process stuck in Resolving state\r\n\r\nInstallation:\r\n=============\r\nDeployer environment:\r\n---------------------\r\nJava Environment with HttpUpload:\r\n1. Ensure that you have a correct installed Content Delivery installation inside your web application\r\n2. Stop your web application server or web application containing the deployer httpupload\r\n3. Copy the distributed jar files inside your web application WEB-INF\\lib directory\r\n4. Start your web application server or web application\r\n\r\n.NET Environment with HttpUpload:\r\n1. Ensure the application pool and or IIS Server has been stopped\r\n2. Copy the distributed jar files inside the IIS application directory bin\\lib directory. In case of central tridion installation please copy the distributed jar files\r\ninto the installation directory \\lib folder.\r\n3. Start the application pool and or IIS Server\r\n\r\nStandalone deployer:\r\n1. Ensure the deployer service has been stopped\r\n2. Copy the distributed jar files inside your 'Tridion installation folder'\\lib directory\r\n3. Start the deployer service\r\n\r\nDistributed files:\r\n==================\r\ncd_datalayer.jar\r\ncd_storage_conf.xsd\r\ncd_storage_conf_sample.xml\r\n\r\nDependencies:\r\n=============\r\nSDL Tridion 2011 SP1 HR1\r\n\r\n\r\nFixed problems:\r\n===============\r\nTT77133\r\nProblem Description\r\n-------------------\r\nThe Component link field type not exposed in keyword metadata when requesting keyword metadata in the broker API.\r\n\r\nHotfix Description\r\n-------------------\r\nThe issues occurs due to incorrect namespace handling of the keyword metadata in taxonomies. The link information was in a different\r\nunrecognized namespace and therefore ignored. This has been resolved by properly handling the namespace containing the link information\r\nfor the keyword.\r\n\r\n\r\nTT78523\r\nProblem Description\r\n-------------------\r\nWhen deploying a complex Taxonomy containing multiparent keywords and more than a few thousand keywords with many related items the deployment\r\nexceeds the transaction timeout and can take up to an hour to complete.\r\n\r\nHotfix Description\r\n-------------------\r\nThe cause of the issue is the related item count that is provided on API level. The related item count to a keyword is calculated during deployment\r\ntime due to the complexity of taxonomies with multi-parent keywords the query for each level of the taxonomy grows exponentially in time to execute.\r\n\r\nThe solution is to provide an option to switch of the reference counting mechanism on keywords. The following configuration option is added to the\r\nstorage configuration file under the 'Global' element:\r\n\r\n\r\nBy setting this to false the keyword reference counts are no longer calculated impacting the following api's:\r\nJava Class: com.tridion.taxonomies.Keyword and method: getReferencedContentCount\r\n.NET Class: Tridion.ContentDelivery.Taxonomies.Keyword and then property: 'ReferencedContentCount'\r\n\r\nThe impact will result in these methods returning a '0' integer return value.\r\n\r\n\r\nTT79176\r\nProblem Description\r\n-------------------\r\nWhen undeploying a complex transport package undeployment fails with following error message Unknown entity: com.tridion.storage.ItemMeta_$$_javassist_13.\r\n\r\nHotfix Description\r\n-------------------\r\nBefore Item is moved the session should be flushed prior to fetching the item by primary key.\r\n\r\n\r\nTT80995 \r\nProblem Description\r\n-------------------\r\nPublishing process stuck in Resolving state\r\n\r\nHotfix Description\r\n-------------------\r\nRemoving DynamicLinks might cause database locks. To prevent that we flush the session prior and after removing DynamicLinks.\r\n\r\n\r\nDisclaimer:\r\n===========\r\nHotfixes are released at the discretion of Tridion based on technical\r\ncomplexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/\r\nconfiguration and therefore should only be installed if approved by Tridion\r\nCustomer Support. Hotfixes should be replaced as soon as possible by the\r\nsubsequent service pack where the problem is fixed.\r\n\r\n(c) 2012 SDL Tridion B.V.\r\n",
"version": "2011 SP1 HR#1"
},
{
"_id": {
"$oid": "635fe2ac94436e1bc8257a68"
},
"hotfix_name": "TM_3.0.0.83219",
"modified_date": {
"$date": 1355301586531
},
"problem_description": "The translation job title cannot be changed from the TranslationJobCreatedEvent when created with multiple items selected.\r\n",
"readme_text": "Release Notes for Hotfix TT83219\r\n\r\nVersion:\r\nThis hotfix is intended only for SDL Tridion Translation Manager 3.0 included in Tridion 2011 SP1.\r\n\r\nProblem description:\r\nThe translation job title cannot be changed from the TranslationJobCreatedEvent when created with multiple items selected.\r\n\r\nHotfix description:\r\nThe user interface will no longer change the title after creating the job. It will assign the default title as the job is being created. This ensures the title will not be changed after the \r\n\r\n\r\nInstallation:\r\n1. Stop the Tridion Translation Manager Service\r\n2. Move or delete the file Tridion.TranslationManager.DomainModel.dll located in the %windir%\\assembly\\GAC_MSIL\\Tridion.TranslationManager.DomainModel\\3.0.0.116__360aac4d3354074b\\ folder (with the command prompt).\r\n3. Copy the file Tridion.TranslationManager.DomainModel.dll from this hotfix to the %windir%\\assembly\\GAC_MSIL\\Tridion.TranslationManager.DomainModel\\3.0.0.116__360aac4d3354074b\\ folder (with the command prompt).\r\n4. Copy the file Tridion.TranslationManager.DomainModel.dll from this hotfix to \"%Tridion%\\Translation Manager\" replacing the old version.\r\n5. Copy the file Tridion.TranslationManager.Service.exe from this hotfix to \"%Tridion%\\Translation Manager\" replacing the old version.\r\n6. Copy the file Tridion.TranslationManager.UI.Model.dll to \"%Tridion%\\web\\WebUI\\WebRoot\\bin\" replacing the old version.\r\n7. Copy the file Microsoft.Web.Services2.dll to %windir%\\assembly using Windows Explorer (this will register the assembly in the GAC under assembly version 2.0.3.0)\r\n8. Copy the file WSWebServices.dll to %windir%\\assembly using Windows Explorer (this will register the assembly in the GAC)\r\n9. Restart the Content Manager Explorer Web site.\r\n10. Start the Tridion Translation Manager Service\r\n\r\nDistributed files:\r\n- Tridion.TranslationManager.DomainModel.dll (version 3.0.0.198)\r\n- Tridion.TranslationManager.UI.Model.dll (version 3.0.0.198)\r\n- Tridion.TranslationManager.Service.exe (version 3.0.0.165)\r\n- Microsoft.Web.Services2.dll (file version 2.0.5050.0)\r\n- WSWebServices.dll (version 9.0.4503.21315)\r\n\r\nFixes included:\r\n TT79169: Error retrieving component with keywords if the translated keyword title does not match the keyword title in the target publication.\r\n TT80330: The Tridion Application Monitoring is not receiving heartbeats from the Translation Manager Serice.\r\n TT80837: A \"BadCredentialException\" error occurs when connecting to World Server.\r\n TT80954: Error creating a translation job from the target publication if the user does not have read access to the source publication.\r\n TT81098: Creating a translation job is slow when multiple items are selected.\r\n TT81187: Error \"Object reference not set to an instance of an object\" when creating a Translation Job with some BluePrint configurations.\r\n TT81935: Jobs retrieved from World Server workflows with sub-workflows are canceled after retrieval.\r\n TT82596: The UI will show the option of translating to a language even if no translation source is configured in a parent publication.\r\n TT82766: Once a target language has been deselected it no longer shows up in the UI.\r\n TT82987: Translation Job screen takes very long to load when creating a translation job with multiple components are selected.\r\n\r\nDependencies:\r\n N/A\r\n\r\nDisclaimer:\r\nHotfixes are released at the discretion of SDL Tridion based on technical complexity, customer business requirements and schedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by SDL Tridion Customer Support. Hotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright (c) 2012 SDL Tridion B.V.\r\n",
"version": "2011 SP1 HR#1"
},
{
"_id": {
"$oid": "635fe2ab94436e1bc8257a4b"
},
"hotfix_name": "CM_2011.1.1.82460",
"modified_date": {
"$date": 1352721784312
},
"problem_description": "Selection for multiple components lost when using IE7 Standards document mode in IE8 browser\r\n",
"readme_text": "Release Notes for Hotfix TT# 82460\r\n\r\nVersion:\r\nThis hotfix is intended for Tridion 2011 SP1 HR1\r\n\r\nProblem description:\r\nSelection for multiple components lost when using IE7 Standards document mode in IE8 browser\r\n\r\nHotfix description:\r\nThe width of the client area was computed incorrectly in IE7 mode. As a result, clicking on the scrollbar triggered clearing of the selection.\r\n\r\nInstallation:\r\n 1. Move or delete the file ListView.js located in the %TRIDION_HOME%\\web\\WebUI\\Core\\Controls\\List\\ folder.\r\n 2. Copy the file ListView.js from this hotfix to the %TRIDION_HOME%\\web\\WebUI\\Core\\Controls\\List\\ folder.\r\n 3. Open %TRIDION_HOME%\\web\\WebUI\\WebRoot\\Configuration\\System.config file.\r\n 4. Locate /Configuration/servicemodel/server node in Sytem.config file and increase the value of its 'modification' attribute to notify client browsers to update their cache.\r\n\r\n\r\nDistributed files:\r\n- ListView.js\r\n- Readme.txt (this file)\r\n\r\n\r\nFixes included:\r\nn/a\r\n\r\n\r\nDependencies:\r\nn/a\r\n\r\n\r\nDisclaimer:\r\nHotfixes are released at the discretion of SDL based on technical complexity, customer business requirements and schedules.\r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by SDL Customer Support.\r\nHotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright 2012 SDL PLC. All Rights Reserved. All company product or service names referenced herein are properties of their respective owners.",
"version": "2011 SP1 HR#1"
},
{
"_id": {
"$oid": "635fe2b094436e1bc8257b7e"
},
"hotfix_name": "TM_2013.1.1.1598",
"modified_date": {
"$date": 1455700628734
},
"problem_description": "Push of shared item can resolve in wrong target languages.\r\n",
"readme_text": "Release Notes for Hotfix CRQ-1598 \r\n\r\nVersion:\r\nThis hotfix is intended only for SDL Tridion Translation Manager 7.1 included in Tridion 2013 SP1 HR1.\r\n\r\nProblem description:\r\nPush of shared item can resolve in wrong target languages.\r\n\r\nHotfix description:\r\nWhen sending push jobs translation manager could select the source configuration from the shared item, instead of the source configuration of the translation job. This resulted in an incorrect list of target languages being available. This hotfix ensures Translation Manager alwaysuse the source configuration of the translation job when sending push jobs.\r\n\r\nInstallation:\r\n1. Stop the Tridion Translation Manager Service\r\n2. Stop Content Manager Explorer Web site\r\n3. Move or delete the file Tridion.TranslationManager.DomainModel.dll located in the %windir%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.TranslationManager.DomainModel\\v4.0_7.1.0.116__360aac4d3354074b\\ folder (with the command prompt).\r\n4. Copy the file Tridion.TranslationManager.DomainModel.dll from this hotfix to the %windir%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.TranslationManager.DomainModel\\v4.0_7.1.0.116__360aac4d3354074b\\ folder (with the command prompt).\r\n5. Copy the file Tridion.TranslationManager.DomainModel.dll from this hotfix to \"%Tridion%\\Translation Manager\" replacing the old version.\r\n6. Copy the file WSWebServices.dll from this hotfix to \"%Tridion%\\Translation Manager\" replacing the old version.\r\n7. Create folder %windir%\\assembly\\GAC_MSIL\\WSWebServices\\9.0.5444.27742__c28cdb26c445c888\r\n8. Copy the file WSWebServices.dll to %windir%\\assembly\\GAC_MSIL\\WSWebServices\\9.0.5444.27742__c28cdb26c445c888\r\n9. Restart the Content Manager Explorer Web site.\r\n10. Start the Tridion Translation Manager Service.\r\n\r\nDistributed files:\r\n- Tridion.TranslationManager.DomainModel.dll (version 7.1.0.154)\r\n- WSWebServices.dll (version 9.0.5444.27742)\r\n\r\nFixes included:\r\n TT88454: Not all data transmitted from World Server to Tridion was compressed causing transfer of more data than necessary.\r\n TT88486: User can not create pull translation job if he does not have access to publication/folder where source configuration is configured\r\n TT88491: Translation Manager revert retrieved translation for target item in \"Reserved state\"\t\r\n TT88559: It take too long to update World Server workflow information on slow connection\r\n TT88616: It is not possible to use a local bundle to create a Pull Job with shared items\r\n (this hotfix was not independently released, it is only available with TT88617)\r\n TT88617: It is not possible to have a translation retrieved by Tridion multiple times in the translation workflow.\r\n TT88667: It is not possible to configure the translation system configuration caching interval\r\n TT88737: Unable to translate shared item from publication that has configured parents further up in the tree.\r\n CRQ-1348: Translation Manager does not use World Server version 11 as efficiently as possible.\r\n\r\nDependencies:\r\n\tTridion 2013 SP1 HR1\r\n\r\nDisclaimer:\r\nHotfixes are released at the discretion of SDL Tridion based on technical complexity, customer business requirements and schedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by SDL Tridion Customer Support. Hotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright (c) 2016 SDL Group.\r\n",
"version": "2013 SP1 HR#1"
},
{
"_id": {
"$oid": "635fe2bf94436e1bc8257d6b"
},
"hotfix_name": "CM_8.5.0.22126",
"modified_date": {
"$date": 1607355250945
},
"problem_description": "Performance degradation on opening publication or list of the categories.\r\n",
"readme_text": "Release Notes for Hotfix CRQ-22126\r\n\r\nVersion: \r\n This hotfix is intended for SDL Web 8.5\r\n\r\nProblem description:\r\n Performance degradation on opening publication or list of the categories.\r\n\r\nHotfix description:\r\n Skip calculation number of the keywords in places where we actually don't need that.\r\n \r\nInstallation:\r\n 1. Stop all TCM Services, IIS Service, and the TCM COM+ Application.\r\n 2. Remove the file Tridion.ContentManager.Data.dll located in the %WINDIR%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.ContentManager.Data\\v4.0_8.5.0.466__ddfc895746e5ee6b folder\r\n 3. Copy the Tridion.ContentManager.Data.dll file from this hotfix to the %WINDIR%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.ContentManager.Data\\v4.0_8.5.0.466__ddfc895746e5ee6b folder \r\n 4. Remove the file Tridion.ContentManager.Data.AdoNet.dll located in the %WINDIR%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.ContentManager.Data.AdoNet\\v4.0_8.5.0.466__ddfc895746e5ee6b folder\r\n 5. Copy the Tridion.ContentManager.Data.AdoNet.dll file from this hotfix to the %WINDIR%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.ContentManager.Data.AdoNet\\v4.0_8.5.0.466__ddfc895746e5ee6b folder \r\n 6. Remove the file Tridion.ContentManager.dll located in the %WINDIR%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.ContentManager\\v4.0_8.5.0.466__360aac4d3354074b folder\r\n 7. Copy the Tridion.ContentManager.dll file from this hotfix to the %WINDIR%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.ContentManager\\v4.0_8.5.0.466__360aac4d3354074b folder \r\n 8. Restart the IIS Service, TCM Services and TCM COM+ Application.\r\n\r\nDistributed files:\r\n Tridion.ContentManager.Data.dll (File Version 8.5.0.635/Assembly version 8.5.0.466)\r\n Tridion.ContentManager.Data.AdoNet.dll (File Version 8.5.0.635/Assembly version 8.5.0.466)\r\n Tridion.ContentManager.dll (File Version 8.5.0.635/Assembly version 8.5.0.466)\r\n Readme.txt (this file)\r\n\r\nFixes included:\r\n CM_8.5.0.8406\r\n CM_8.5.0.8103\r\n CM_8.5.0.6678\r\n CM_8.5.0.6356\r\n CM_8.5.0.14857\r\n CM_8.5.0.19193\r\n \r\n CM_8.5.0.8618\r\n CM_8.5.0.14856\r\n CM_8.5.0.17329\r\n \r\n CM_8.5.0.8749\r\n\r\nDependencies:\r\n CM_8.5.0.10699(Oracle version) or CM_8.5.0.10663(MS SQL version)\r\n CM_8.5.0.14116\r\n\r\nDisclaimer:\r\n Hotfixes are released at the discretion of SDL based on technical complexity, customer business requirements and schedules.\r\n Hotfixes are made and tested only for the described problem on a particular environment\\configuration and therefore should only be installed if approved by Customer Support of SDL Tridion Sites Content Management Solutions Division.\r\n Hotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright \u00a9 2020 SDL PLC. All Rights Reserved. All company product or service names referenced herein are properties of their respective owners.\r\n",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2bc94436e1bc8257cf0"
},
"hotfix_name": "CD_8.5.0.17761",
"modified_date": {
"$date": 1580913718859
},
"problem_description": "This is a hotfix include \r\n- CRQ-17548: DynamicContentProvider may use cache for method List getPublicationUrls(int publicationId)\r\n- CRQ-17761: DB server spikes/content service latency when publishing just a few pages\r\n- CRQ-17547: Fix ArrayIndexOutOfBoundException\r\n- CRQ-17549: Fix NPE\r\n",
"readme_text": "\ufeffRelease Notes for Hotfix CRQ-17761\r\n==================================\r\n\r\nVersion:\r\n========\r\n\tThis is a cumulative hotfix and is intended only for SDL Web 8.5. The layout build number 1116.\r\n\r\nDescription:\r\n============\r\nThis is a hotfix include \r\n - CRQ-17548: DynamicContentProvider may use cache for method List getPublicationUrls(int publicationId)\r\n - CRQ-17761: DB server spikes/content service latency when publishing just a few pages\r\n - CRQ-17547: Fix ArrayIndexOutOfBoundException\r\n - CRQ-17549: Fix NPE\r\n\r\nInstallation:\r\n=============\r\nThis cumulative hotfix provides updated API artifacts and services.\r\n In-Process:\r\n 1. Java - update artifacts from release\\api\\in-process\\java\\lib folder.\r\n \r\n All services:\r\n 1. Stop the Service you are going to upgrade\r\n 2. Backup (or move) a folder where your standalone Service is located\r\n 3. Uninstall the Service by opening a Powershell window in the \\bin of your service and running .\\uninstallService.ps1\r\n 4. Navigate to the release\\\\service folder of this distribution\r\n 5. Copy \\standalone folder to the location where your original service was located\r\n 6. Rename copied \\standalone folder to the name of your original service's folder\r\n 7. Copy all files from \\config folder of your backup (see step #2) to \\config folder of a new service\r\n 8. Copy custom jars (if any) from backup's \\services\\folder to the same location of a new service\r\n 9. Install service by opening a Powershell window in the location \\bin of new service and run .\\installService.ps1\r\n\r\nDistributed roles:\r\n==================\r\n api Content Delivery API role (8.5.0-1120)\r\n content Content Service role (8.5.0-1138)\r\n preview Session Preview Service (8.5.0-1151)\r\n session Session Content Service (8.5.0-1151)\r\n\r\n\r\nDependencies:\r\n=============\r\n\r\n\r\nFixed problems:\r\n===============\r\n- CRQ-17548: DynamicContentProvider may use cache for method List getPublicationUrls(int publicationId)\r\n- CRQ-17761: DB server spikes/content service latency when publishing just a few pages\r\n- CRQ-17547: Fix ArrayIndexOutOfBoundException from parent logs\r\n\t(...ERROR ODataFunctionProcessorImpl - Unexpected exception when executing a function. java.lang.ArrayIndexOutOfBoundsException: -1...)\r\n- CRQ-17549: Fix NPE from parent logs\r\n\t(...ERROR ODataFunctionProcessorImpl - Unexpected exception when executing a function. java.lang.NullPointerException: null at com.sdl.web.discovery.delivery.configuration.ODataConfigurationItemWrapper.getConfigurations(ODataConfigurationItemWrapper.java:150)...)\r\n\r\n\r\nHotfix Description\r\n-------------------\r\nCRQ-17548: added cache for DynamicContentProvider.getPublicationUrls and DynamicContentProvider.getPublicationMappingFromUrl calls \r\nCRQ-17761: optimized database queries produced by Broker Criteria API\r\nCRQ-17547: issue with multithreading fixed\r\nCRQ-17549: issue with multithreading fixed\r\n\r\nDisclaimer:\r\n Hotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. Hot fixes are made\r\n and tested only for the described problem on a particular environment/configuration and therefore should only be installed\r\n if approved by Customer Support. Hotfixes should be replaced as soon as possible by the subsequent patch release where the problem is fixed.\r\n\r\nCopyright \u00a9 2015-2020 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2ac94436e1bc8257a66"
},
"hotfix_name": "TM_3.0.0.82766",
"modified_date": {
"$date": 1351694084906
},
"problem_description": "Once a target language has been deselected it no longer shows up in the UI.\r\n",
"readme_text": "Release Notes for Hotfix TT82766\r\n\r\nVersion:\r\nThis hotfix is intended only for SDL Tridion Translation Manager 3.0 included in Tridion 2011 SP1.\r\n\r\nProblem description:\r\nOnce a target language has been deselected it no longer shows up in the UI.\r\n\r\nHotfix description:\r\nThis hotfix ensures all available publications are displayed in the UI even if they are not selected.\r\n\r\nInstallation:\r\n1. Stop the Tridion Translation Manager Service\r\n2. Move or delete the file Tridion.TranslationManager.DomainModel.dll located in the %windir%\\assembly\\GAC_MSIL\\Tridion.TranslationManager.DomainModel\\3.0.0.116__360aac4d3354074b\\ folder (with the command prompt).\r\n3. Copy the file Tridion.TranslationManager.DomainModel.dll from this hotfix to the %windir%\\assembly\\GAC_MSIL\\Tridion.TranslationManager.DomainModel\\3.0.0.116__360aac4d3354074b\\ folder (with the command prompt).\r\n4. Copy the file Tridion.TranslationManager.DomainModel.dll from this hotfix to \"%Tridion%\\Translation Manager\" replacing the old version.\r\n5. Copy the file Tridion.TranslationManager.Service.exe from this hotfix to \"%Tridion%\\Translation Manager\" replacing the old version.\r\n6. Copy the file Microsoft.Web.Services2.dll to %windir%\\assembly using Windows Explorer (this will register the assembly in the GAC under assembly version 2.0.3.0)\r\n7. Copy the file WSWebServices.dll to %windir%\\assembly using Windows Explorer (this will register the assembly in the GAC)\r\n8. Restart the Content Manager Explorer Web site.\r\n9. Start the Tridion Translation Manager Service\r\n\r\nDistributed files:\r\n- Tridion.TranslationManager.DomainModel.dll (version 3.0.0.179)\r\n- Tridion.TranslationManager.Service.exe (version 3.0.0.165)\r\n- Microsoft.Web.Services2.dll (file version 2.0.5050.0)\r\n- WSWebServices.dll (version 9.0.4503.21315)\r\n\r\nFixes included:\r\n TT79169: Error retrieving component with keywords if the translated keyword title does not match the keyword title in the target publication.\r\n TT80330: The Tridion Application Monitoring is not receiving heartbeats from the Translation Manager Serice.\r\n TT80837: A \"BadCredentialException\" error occurs when connecting to World Server.\r\n TT80954: Error creating a translation job from the target publication if the user does not have read access to the source publication.\r\n TT81098: Creating a translation job is slow when multiple items are selected.\r\n TT81187: Error \"Object reference not set to an instance of an object\" when creating a Translation Job with some BluePrint configurations.\r\n TT81935: Jobs retrieved from World Server workflows with sub-workflows are canceled after retrieval.\r\n TT82596: The UI will show the option of translating to a language even if no translation source is configured in a parent publication.\r\n\r\nDependencies:\r\n N/A\r\n\r\nDisclaimer:\r\nHotfixes are released at the discretion of SDL Tridion based on technical complexity, customer business requirements and schedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by SDL Tridion Customer Support. Hotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright (c) 2012 SDL Tridion B.V.\r\n",
"version": "2011 SP1 HR#1"
},
{
"_id": {
"$oid": "635fe2ab94436e1bc8257a40"
},
"hotfix_name": "CM_2011.1.1.81183",
"modified_date": {
"$date": 1345221550079
},
"problem_description": "Blueprint Viewer does not allow to include custom ItemTypes. \r\n",
"readme_text": "Release Notes for Hotfix TT#81183\r\n\r\nVersion:\r\nThis hotfix is intended for SDL Tridion Content Manager Explorer 2011 SP1.\r\n\r\nProblem description:\r\nBlueprint Viewer does not allow to include custom ItemTypes. \r\n\r\nHotfix description:\r\nRefactoring Done to allow external items to be embedded into Blueprint Viewer\r\n\r\nInstallation:\r\n 1. Move or delete the file BluePrintViewer.js located in the %TRIDION_HOME%\\web\\WebUI\\Editors\\CME\\Views\\BluePrintViewer\\ folder.\r\n 2. Copy the file BluePrintViewer.js from this hotfix to the %TRIDION_HOME%\\web\\WebUI\\Editors\\CME\\Views\\BluePrintViewer\\ folder.\r\n 3. Move or delete the file BlueprintHierarchy.js located in the %TRIDION_HOME%\\web\\WebUI\\Models\\TCM54\\Client\\ContentManager\\ folder.\r\n 4. Copy the file BlueprintHierarchy.js from this hotfix to the %TRIDION_HOME%\\web\\WebUI\\Models\\TCM54\\Client\\ContentManager\\ folder.\r\n 5. Move or delete the file Item.js located in the %TRIDION_HOME%\\web\\WebUI\\Models\\TCM54\\Client\\ContentManager\\ folder.\r\n 6. Copy the file Item.js from this hotfix to the %TRIDION_HOME%\\web\\WebUI\\Models\\TCM54\\Client\\ContentManager\\ folder.\r\n 7. Move or delete the file ListParentPublications.js located in the %TRIDION_HOME%\\web\\WebUI\\Models\\TCM54\\Client\\ContentManager\\ folder.\r\n 8. Copy the file ListParentPublications.js from this hotfix to the %TRIDION_HOME%\\web\\WebUI\\Models\\TCM54\\Client\\ContentManager\\ folder.\r\n 9. Move or delete the file Publication.js located in the %TRIDION_HOME%\\web\\WebUI\\Models\\TCM54\\Client\\ContentManager\\ folder.\r\n 10. Copy the file Publication.js from this hotfix to the %TRIDION_HOME%\\web\\WebUI\\Models\\TCM54\\Client\\ContentManager\\ folder.\r\n 11. Move or delete the file VersionedItem.js located in the %TRIDION_HOME%\\web\\WebUI\\Models\\TCM54\\Client\\ContentManager\\ folder.\r\n 12. Copy the file VersionedItem.js from this hotfix to the %TRIDION_HOME%\\web\\WebUI\\Models\\TCM54\\Client\\ContentManager\\ folder.\r\n 13. Open %TRIDION_HOME%\\web\\WebUI\\WebRoot\\Configuration\\System.config file.\r\n 14. Locate \\Configuration\\servicemodel\\server node in Sytem.config file and increase the value of its 'modification' attribute to notify client browsers to update their cache. \r\n \r\nDistributed files:\r\n- BluePrintViewer.js\r\n- BlueprintHierarchy.js\r\n- Item.js\r\n- ListParentPublications.js\r\n- Publication.js\r\n- VersionedItem.js\r\n- Readme.txt (this file)\r\n\r\nFixes included:\r\n N\\A\r\n\r\nDependencies:\r\n N\\A\r\n\r\nDisclaimer:\r\nHotfixes are released at the discretion of SDL based on technical complexity, customer business requirements and schedules.\r\nHotfixes are made and tested only for the described problem on a particular environment\\configuration and therefore should only be installed if approved by Customer Support of SDL Web Content Management Solutions Division.\r\nHotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright 2011 SDL PLC. All Rights Reserved. All company product or service names referenced herein are properties of their respective owners.",
"version": "2011 SP1 HR#1"
},
{
"_id": {
"$oid": "635fe2b194436e1bc8257bc6"
},
"hotfix_name": "CM_9.0.0.25042",
"modified_date": {
"$date": 1626272124019
},
"problem_description": "Cannot remove \"IX_ITEMS_05\" index if it does not exist.\r\n",
"readme_text": "Release Notes for Hotfix CRQ-C25042\r\n\r\nVersion: \r\n This hotfix is intended for SDL Web 9.0, 9.1, 9.5 for MS SQL version only.\r\n\r\nProblem description:\r\n Cannot remove \"IX_ITEMS_05\" index if it does not exist.\r\n\r\nHotfix description:\r\n Added checking of existance of \"IX_ITEMS_05\" index before deletion.\r\n \r\nInstallation:\r\n 1. Owerwrite file EDT_INDEXES.sql in the database scripts folder \\Scripts\\mssql\\Upgrade\\86_90 before starting database upgrade.\r\n\r\nDistributed files:\r\n EDT_INDEXES.sql\r\n Readme.txt (this file)\r\n\r\nFixes included:\r\n None\r\n \r\nDependencies:\r\n None\r\n\r\nDisclaimer:\r\n Hotfixes (as defined under the relevant RWS product release policy) are released at RWSs discretion based on technical complexity, customer business requirements and schedules. \r\n Hotfixes are made and tested only for the described problem on a particular environment/configuration in accordance with the Software Documentation and therefore should only be installed if approved by RWS Technical Support. \r\n Hotfixes should be replaced as soon as possible by the subsequent cumulative update where the problem is fixed.\r\n \r\nCopyright 2021 All Rights Reserved by the RWS Group for and on behalf of its affiliates and subsidiaries. All company product or service names referenced herein are properties of their respective owners.\r\n",
"version": "Sites 9.0"
},
{
"_id": {
"$oid": "635fe2b394436e1bc8257bf1"
},
"hotfix_name": "CME_9.1.0.18859",
"modified_date": {
"$date": 1607095991079
},
"problem_description": "Notification Hub functionality might not be used by particular implementation, but it requires\r\nadditional resources, especially, in the cloud environment.\r\n",
"readme_text": "\ufeffRelease Notes for Hotfix CRQ-18859\r\n\r\nVersion:\r\nThis hotfix is intended for SDL Tridion Sites 9.1\r\n\r\nProblem description: \r\nNotification Hub functionality might not be used by particular implementation, but it requires\r\nadditional resources, especially, in the cloud environment.\r\n\r\nHotfix description:\r\nDisabled notification hub event subscription, added DisableNotificationHub attribute to \r\ndisable notification hub. \r\n\r\nInstallation:\r\n\t1. Create a backup of %TRIDION_HOME%\\web\\WebUI\\WebRoot\\bin\\Tridion.Web.UI.CME.TcmExtensions.dll and %TRIDION_HOME%\\web\\WebUI\\WebRoot\\bin\\Tridion.Web.UI.Core.dll.\r\n\t2. Copy the Tridion.Web.UI.CME.TcmExtensions.dll and Tridion.Web.UI.Core.dll files from this hotfix to %TRIDION_HOME%\\web\\WebUI\\WebRoot\\bin folder.\r\n\t3. Create a backup of %TRIDION_HOME%\\web\\WebUI\\Editors\\Base\\Views\\ImageEditor\\ImageEditor.aspx.js\r\n\t4. Copy ImageEditor.aspx.js from this hotfix to %TRIDION_HOME%\\web\\WebUI\\Editors\\Base\\Views\\ImageEditor folder.\r\n\t5. Locate \\Configuration\\servicemodel\\server node in the %TRIDION_HOME%\\web\\WebUI\\WebRoot\\Configuration\\System.config file and increase the value of its 'modification' attribute to notify client browsers to update their cache.\r\n\t6. Add attribute DisableNotificationHub with value \"true\" in %TRIDION_HOME%\\web\\WebUI\\WebRoot\\Configuration\\System.config\r\n \r\n \r\n\t7. Add in %TRIDION_HOME%\\hubs\\notificationHub\\Web.config:\r\n\t\t\t\r\n\t\t\t\t\r\n\t\t\t\t \r\n\t\t\t\t\r\n\t\t\t\r\n\t8. Comment out following line in the %TRIDION_HOME%\\web\\WebUI\\Models\\TCM54\\Configuration\\TCM54.Config:\r\n \r\n\t\t\t\tSDL.Web.UI.Editors.XPMCore.Utils\r\n\t\t\t\r\n\t\t\r\n\r\n\t9. Locate \\Configuration\\commands node in SiteEditEditor.config file and add the following commandset there:\r\n\r\n\t\t\r\n\t\t\t\r\n\t\t\t\r\n\r\n\t\t\t\r\n\t\t\t\tSDL.Web.UI.Editors.XPM.Commands.Publishing\r\n\t\t\t\r\n\t\t\r\n\r\n\t10. Locate \\Configuration\\resources\\groups\\group node with name \"SDL.Web.UI.Editors.XPM.CommandSets.All\" in SiteEditEditor.config file and add the following file in the fileset node:\r\n\r\n\t\tSDL.Web.UI.Editors.XPM.CommandSets.Publishing\r\n\r\n\t11. Locate \\Configuration\\contextmenus\\cmenu:menudeclaration\\cmenu:ContextMenuItem node with id \"cm_publish\" in SiteEditEditor.config file and change its command attribute to \"SEPublish\".\r\n\r\n\t12. Locate \\Configuration\\contextmenus\\cmenu:menudeclaration\\cmenu:ContextMenuItem node with id \"cm_unpublish\" in SiteEditEditor.config file and change its command attribute to \"SEUnPublish\".\r\n\r\n\t13. Open %TRIDION_HOME%\\web\\WebUI\\WebRoot\\Configuration\\System.config file.\r\n\r\n\t14. Locate \\Configuration\\servicemodel\\server node in System.config file and increase the value of its 'modification' attribute to notify client browsers to update their cache.\r\n\r\n\t15. Recycle the application pool or restart your IIS service\r\n\r\nDistributed files:\r\n\r\n-Readme.txt (this file)\r\n-SEPublish.js\r\n-SEUnPublish.js\r\n-contextmenu.css\r\n-ribbontoolbar.css\r\n-Editor.aspx\r\n-Editor.aspx.js\r\n\r\nFixes included:\r\nn.a.\r\n\r\nDependencies:\r\nn.a.\r\n\r\nDisclaimer:\r\nHotfixes are released at the discretion of SDL based on technical complexity, customer business requirements and schedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by Customer Support of SDL Web Content Management Solutions Division. Hotfixes should be replaced as soon as possible by the subsequent patch release where the problem is fixed.\r\nCopyright 2016 SDL PLC. All Rights Reserved. All company product or service names referenced herein are properties of their respective owners. ",
"version": "Web 8.1.1"
},
{
"_id": {
"$oid": "635fe2ae94436e1bc8257af9"
},
"hotfix_name": "CM_2013.1.0.88250",
"modified_date": {
"$date": 1412329841050
},
"problem_description": "Resolver for 'Republish Only' on a Dynamic component template includes items that were not published to the chosen target.\r\nMS SQL Server specific.\r\nSteps to reproduce:\r\n1. Go to a publication where you have a dynamic component template published (as part of some CP with a component) to a particular target. \r\n2. Create a new component1 from a schema associated to this CT. Save it but do not publish.\r\n3. Create a new component2 from a schema associated to this CT and publish it to a different target. \r\n4. Publish the CT from the publication and leave 'Republish only' checked. See the items to publish and it will include new items and items published to other targets.\r\n",
"readme_text": "Release Notes for Hotfix TT88250\r\n\r\n\r\nVersion:\r\nThis hotfix is intended only for SDL Tridion Content Manager 2013 Service Pack 1.\r\n\r\n\r\nProblem description:\r\nResolver for 'Republish Only' on a Dynamic component template includes items that were not published to the chosen target.\r\nMS SQL Server specific.\r\nSteps to reproduce:\r\n1. Go to a publication where you have a dynamic component template published (as part of some CP with a component) to a particular target. \r\n2. Create a new component1 from a schema associated to this CT. Save it but do not publish.\r\n3. Create a new component2 from a schema associated to this CT and publish it to a different target. \r\n4. Publish the CT from the publication and leave 'Republish only' checked. See the items to publish and it will include new items and items published to other targets.\r\n\r\n\r\nHotfix description:\r\nLogic in stored procedure to determine if specific component was published to specified publication target with specified component template was incorrect.\r\n\r\n\r\nInstallation:\r\n 1. Stop all TCM Services, IIS Service, and the TCM COM+ Application.\r\n 2. Using SQL Server Management Studio, log in to the SDL Tridion database using 'sa'.\r\n 3. Execute EDA_ITEMS.sql file\r\n 4. Restart the IIS Service, TCM Services and TCM COM+ Application.\r\n\r\nDistributed files:\r\n\tEDA_ITEMS.sql\r\n\tReadme.txt (this file)\r\n\r\n\r\nFixes included:\r\n\tNone\r\n\t\r\nDependencies:\r\n\tTT87401\r\n\r\nDisclaimer:\r\n\tHotfixes are released at the discretion of SDL based on technical complexity, customer business requirements and schedules.\r\n\tHotfixes are made and tested only for the described problem on a particular environment\\configuration and therefore should only be installed if approved by Customer Support of SDL Web Content Management Solutions Division.\r\n\tHotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright 2014 SDL PLC. All Rights Reserved. All company product or service names referenced herein are properties of their respective owners.\r\n",
"version": "2013 SP1"
},
{
"_id": {
"$oid": "635fe2b994436e1bc8257c85"
},
"hotfix_name": "CD_8.1.1.2237",
"modified_date": {
"$date": 1467204836973
},
"problem_description": "The SDL Web 8.1.1 Discovery Service fails with error \"failed to lazily initialize a collection of role\" when running command java -jar discovery-registration.jar update and when Topology Manager contains many website mappings (Add-TtmWebsite).\r\n",
"readme_text": "Release Notes for Hotfix CRQ-2237\r\n=================================\r\n\r\nVersion:\r\n========\r\nThis is cumulative hotfix and is intended only for SDL Web 8.1.1\r\nThe hotfix include the following fixes: \r\n - CRQ-2237 Discovery registration update exception\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n - CRQ-2237 Discovery registration update exception\r\n\r\nInstallation:\r\n=============\r\n\r\nSDL Web Discovery Service:\r\n-----------------------\r\n1. Stop SDL Web Discovery Service.\r\n2. Backup (or move) a folder where your Standalone Discovery Service is located.\r\n3. Uninstall the SDL Web Discovery Service by opening a Powershell window in the \\bin of your service and run .\\uninstallService.ps1.\r\n4. Navigate to the release\\content folder of this distributable\r\n5. Copy \\standalone folder to the location where your original service was located\r\n6. Rename copied \\standalone folder to the name of your original service's folder\r\n7. Copy all files from \\config folder of your backup (see step #2) to \\config folder of a new service. \r\n8. Copy custom jars(if you have any) from backup's \\services\\folder to a same location of a new service.\r\n9. Install service by opening a Powershell window in in the location \\bin of new service and run .\\installService.ps1\r\n\r\nSDL Web Discovery Web Application:\r\n------------------------------------------------------\r\n1. Backup Discovery web-app folder.\r\n2. Reinstall Discovery web-app using content-service.war delivered by this hotfix.\r\n4. Restore original web.xml.\r\n5. Restore Discovery web-app configuration files.\r\n6. Restore custom jars (if you have any) from your backup to a new application\r\n6. Restart Discovery Web Application.\r\n\r\n\r\nDistributed files:\r\n==================\r\ncontent/standalone - Discovery service Standalone\r\ncontent/webapp - Discovery service WebApp\r\n\r\nDependencies:\r\n=============\r\n\r\n\r\nFixed problems:\r\n===============\r\n- CRQ-2237\r\n\r\nProblem Description\r\n-------------------\r\nThe SDL Web 8.1.1 Discovery Service fails with error \"failed to lazily initialize a collection of role\" when running command java -jar discovery-registration.jar update and when Topology Manager contains many website mappings (Add-TtmWebsite).\r\n\r\nHotfix Description\r\n-------------------\r\nFixes made in Discovery Service.\r\n\r\nDisclaimer:\r\n===========\r\n\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/configuration and therefore should only be installed\r\nif approved by Customer Support. Hotfixes should be replaced as soon as possible by the subsequent patch release where the problem is fixed.\r\n\r\nCopyright 2015-2016 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.\r\n",
"version": "Web 8.1.1"
},
{
"_id": {
"$oid": "635fe2b094436e1bc8257b83"
},
"hotfix_name": "TM_2013.1.1.8207",
"modified_date": {
"$date": 1512124372253
},
"problem_description": "Tridion 2013 SP1 HR1 with World Server 11.x using RestAPI: Errors on retrieval\r\n",
"readme_text": "Release Notes for Hotfix CRQ-8207\r\n\r\nVersion:\r\nThis hotfix is intended only for SDL Tridion Translation Manager 7.1 included in Tridion 2013 SP1 HR1.\r\n\r\nProblem description:\r\nTridion 2013 SP1 HR1 with World Server 11.x using RestAPI: Errors on retrieval\r\n\r\nHotfix description:\r\nFix responce parsing for WS.11 REST API\r\n\r\nInstallation:\r\n1.\tStop the Tridion Translation Manager Service\r\n2.\tStop Content Manager Explorer Web site\r\n3.\tMove or delete the file Tridion.TranslationManager.DomainModel.dll located in the %windir%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.TranslationManager.DomainModel\\v4.0_7.1.0.116__360aac4d3354074b\\ folder (with the command prompt).\r\n4.\tCopy the file Tridion.TranslationManager.DomainModel.dll from this hotfix to the %windir%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.TranslationManager.DomainModel\\v4.0_7.1.0.116__360aac4d3354074b\\ folder (with the command prompt).\r\n5.\tCopy the file Tridion.TranslationManager.DomainModel.dll from this hotfix to \"%Tridion%\\Translation Manager\" replacing the old version.\r\n6.\tCopy the file Sdl.Cmt.BeGlobal.Portable.dll from this hotfix to \"%Tridion%\\Translation Manager\" replacing the old version.\r\n7.\tCopy the file Sdl.Cmt.BeGlobal.Portable.dll from this hotfix to \"%Tridion%\\web\\WebUI\\WebRoot\\bin \" replacing the old version.\r\n8.\tCopy the file WSWebServices.dll from this hotfix to \"%Tridion%\\Translation Manager\" replacing the old version.\r\n9.\tCreate folder %windir%\\assembly\\GAC_MSIL\\WSWebServices\\9.0.5444.27742__c28cdb26c445c888\r\n10.\tCopy the file WSWebServices.dll to %windir%\\assembly\\GAC_MSIL\\WSWebServices\\9.0.5444.27742__c28cdb26c445c888\r\n11.\tRestart the Content Manager Explorer Web site.\r\n12.\tStart the Tridion Translation Manager Service.\r\n\r\nDistributed files:\r\n- Tridion.TranslationManager.DomainModel.dll (version 7.1.0.185)\r\n- Sdl.Cmt.BeGlobal.Portable.dll (version 7.1.0.185)\r\n- WSWebServices.dll (version 9.0.5444.27742)\r\n\r\nFixes included:\r\n TT88454: \tNot all data transmitted from World Server to Tridion was compressed causing transfer of more data than necessary.\r\n TT88486: \tUser can not create pull translation job if he does not have access to publication/folder where source configuration is configured\r\n TT88491: \tTranslation Manager revert retrieved translation for target item in \"Reserved state\"\t\r\n TT88559: \tIt take too long to update World Server workflow information on slow connection\r\n TT88616: \tIt is not possible to use a local bundle to create a Pull Job with shared items\r\n (this hotfix was not independently released, it is only available with TT88617)\r\n TT88617: \tIt is not possible to have a translation retrieved by Tridion multiple times in the translation workflow.\r\n TT88667: \tIt is not possible to configure the translation system configuration caching interval\r\n TT88737: \tUnable to translate shared item from publication that has configured parents further up in the tree. (It was possible in TM 2.0)\r\n CRQ-2325:\tCertificates for old BeGlobal(Language Cloud) URL \"https://api.beglobal.com/\" has expired.\r\n CRQ-3449:\tComponent not sent to translate if it is also included in page in same translation job with \"translate components\" checkbox turned off on structure group.\r\n CRQ-3563:\tNullReferenceException on retrieve when two targets have same language.\r\n \r\nDependencies:\r\n\tTridion 2013 SP1 HR1\r\n\r\nDisclaimer:\r\nHotfixes are released at the discretion of SDL Tridion based on technical complexity, customer business requirements and schedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by SDL Tridion Customer Support. Hotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright (c) 2017 SDL Tridion B.V.\r\n",
"version": "2013 SP1 HR#1"
},
{
"_id": {
"$oid": "635fe2ba94436e1bc8257cbf"
},
"hotfix_name": "ECL_8.1.1.5014",
"modified_date": {
"$date": 1496751224367
},
"problem_description": "",
"readme_text": "Release Notes for Hotfix 5014\n\nVersion:\n\tThis hotfix is intended only for Tridion External Content Library 8.1.1 included in Tridion 8.1.1.\n\nProblem description:\n\tError querying publish queue from GUI when MM item is shown multiple times\n\nHotfix description:\n\tFix item grouping for parallel load. \n\nInstallation:\n\t1. Stop all Tridion Content Manager Service Host and IIS Service.\n\t2. Move the file Tridion.ExternalContentLibrary.DomainModel.dll located in the %WINDIR%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.ExternalContentLibrary.DomainModel\\v4.0_8.1.0.211__ddfc895746e5ee6b folder\n\t3. Copy the Tridion.ExternalContentLibrary.DomainModel.dll file from this hotfix to the %WINDIR%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.ExternalContentLibrary.DomainModel\\v4.0_8.1.0.211__ddfc895746e5ee6b folder\n\t4. Move the file Tridion.ExternalContentLibrary.IconLoader.dll located in the %WINDIR%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.ExternalContentLibrary.IconLoader\\v4.0_8.1.0.211__ddfc895746e5ee6b folder\n\t5. Copy the Tridion.ExternalContentLibrary.IconLoader.dll file from this hotfix to the %WINDIR%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.ExternalContentLibrary.IconLoader\\v4.0_8.1.0.211__ddfc895746e5ee6b folder\n\t6. Restart the IIS Service and Tridion Content Manager Service Host.\n\nDistributed files:\n\tTridion.ExternalContentLibrary.DomainModel.dll (File Version 8.1.0.244)\n\tTridion.ExternalContentLibrary.IconLoader.dll (File Version 8.1.0.244)\n\tReadme.txt (this file)\n\nFixes included:\n\tCRQ-2176: Memory leak in microsoft image manipulation library.\n\nDependencies:\n\tN/A\n\nDisclaimer:\n\tHotfixes are released at the discretion of SDL Tridion based on technical complexity, customer business requirements and schedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by SDL Tridion Customer Support. Hotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\n\nCopyright (c) 2017 SDL Group.",
"version": "Web 8.1.1"
},
{
"_id": {
"$oid": "635fe2b894436e1bc8257c71"
},
"hotfix_name": "CD_8.1.0.1470",
"modified_date": {
"$date": 1456999791075
},
"problem_description": "HTTPS was not supported by transport service\r\n",
"readme_text": "Release Notes for Hotfix CRQ-1470\r\n=================================\r\n\r\nVersion:\r\n========\r\nThis hotfix is intended only for SDL Web 8\r\nThe hotfix include the following fixes:\r\n - CRQ-1470 HTTPS support for transport service\r\n \r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n- CRQ-1470 HTTPS support for transport service\r\n\r\nInstallation:\r\n=============\r\n\r\nSDL Web Transport Service:\r\n\r\n1. Stop transport service\r\n2. Go to \\lib\r\n3. Remove cd_transport.jar\r\n4. Copy cd_transport.jar from cd_transport\\lib directory \r\n5. Start transport service\r\n\r\nDistributed files:\r\n==================\r\ncd_transport/lib/\r\n\r\nDependencies:\r\n=============\r\n\r\n\r\nFixed problems:\r\n===============\r\nCRQ-1470 HTTPS support for transport service\r\n\r\nProblem Description\r\n-------------------\r\nHTTPS was not supported by transport service\r\n\r\nHotfix Description\r\n-------------------\r\nImplemented HTTPS support for transport service.\r\n\r\nDisclaimer:\r\n===========\r\nHotfixes are released at the discretion of Tridion based on technical\r\ncomplexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/\r\nconfiguration and therefore should only be installed if approved by Tridion\r\nCustomer Support. Hotfixes should be replaced as soon as possible by the\r\nsubsequent service pack where the problem is fixed.\r\n\r\nCopyright \u00a9 2016 SDL PLC. All Rights Reserved. All company product or service names referenced herein are properties of their respective owners.\r\n",
"version": "Web 8"
},
{
"_id": {
"$oid": "635fe2ab94436e1bc8257a57"
},
"hotfix_name": "CM_2011.1.1.84206",
"modified_date": {
"$date": 1361191438451
},
"problem_description": "Login performance for non-administrator users is slower than administrators.\r\n",
"readme_text": "Release Notes for Hotfix TT84206\r\n\r\nVersion:\r\nThis hotfix is intended only for SDL Tridion Content Manager 2011 SP1 HR1 on Oracle.\r\n\r\nProblem description:\r\nLogin performance for non-administrator users is slower than administrators.\r\n\r\nHotfix description:\r\nremoved T_XML_ATTRIBUTES, in-memory parsing will be used.\r\n\r\nInstallation:\r\n 1. Stop all TCM Services, IIS Service, and the TCM COM+ Application.\r\n 2. Using SQL*Plus, connect as \"tridion_sys\" to the database instance. \r\n 3. Temporarily grant additional rights to the Tridion database user (typically TCMDBUser):\r\n\tGRANT CREATE TRIGGER TO &TCMDBUser;\r\n\tGRANT CREATE PROCEDURE TO &TCMDBUser;\r\n \tGRANT CREATE ANY TABLE TO &TCMDBUser;\r\n\tGRANT CREATE SEQUENCE TO &TCMDBUser;\r\n\tGRANT EXECUTE ON SYS.DBMS_UTILITY TO &TCMDBUser;\r\n 4. Using SQL*Plus, log in as the Tridion database user (typically TCMDBUser).\r\n 5. Execute the SQL script CM_6.1.0.84206_ORACLE.sql.\r\n 6. Check the file CM_6.1.0.84206.log for errors.\r\n 7. Revoke the additional rights from the Tridion database user\t\r\n\tREVOKE EXECUTE ON SYS.DBMS_UTILITY FROM &TCMDBUSER;\r\n\tREVOKE CREATE TRIGGER FROM &TCMDBUser;\t \r\n\tREVOKE CREATE PROCEDURE FROM &TCMDBUser;\r\n\tREVOKE CREATE ANY TABLE FROM &TCMDBUser;\r\n\tREVOKE CREATE SEQUENCE FROM &TCMDBUser;\r\n 8. Restart the IIS Service, TCM Services and TCM COM+ Application.\r\n\r\nDistributed files:\r\n CM_6.1.0.84206_ORACLE.sql\r\n EDA_TRUSTEES.sql\r\n TCM_RECOMPILE_PACKAGES.sql\r\n Readme.txt (this file)\r\n\r\n \r\nFixes included:\r\n\t83085\r\n\r\nDependencies:\r\n\tNone\r\n \r\nDisclaimer:\r\nHotfixes are released at the discretion of SDL based on technical complexity, customer business requirements and schedules.\r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by Customer Support of SDL Web Content Management Solutions Division.\r\nHotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright 2013 SDL PLC. All Rights Reserved. All company product or service names referenced herein are properties of their respective owners.",
"version": "2011 SP1 HR#1"
},
{
"_id": {
"$oid": "635fe2ae94436e1bc8257b04"
},
"hotfix_name": "TM_2013.1.0.87611",
"modified_date": {
"$date": 1392132598617
},
"problem_description": "Whitespaces are inserted into the Rich Text Field translations when sending content to SDL TMS.\r\n",
"readme_text": "Release Notes for Hotfix TT87611\r\n\r\nVersion:\r\nThis hotfix is intended only for SDL Tridion Translation Manager 7.1 included in Tridion 2013SP1.\r\n\r\nProblem description:\r\nWhitespaces are inserted into the Rich Text Field translations when sending content to SDL TMS.\r\n\r\nHotfix description:\r\nWhen Translation Manager sends the content from Tridion to SDL TMS it is reformatting the XML inserting extra whitespaces between the markup XML elements. This only affact markup elements identified by a \"withinText\" ITS rule specified in %Tridion%\\Configuration\\TranslationManager.XHTML.ITS.Rules.xml.\r\n\r\n\r\nInstallation:\r\n1. Stop the Tridion Translation Manager Service\r\n2. Move or delete the file Tridion.TranslationManager.DomainModel.dll located in the %windir%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.TranslationManager.DomainModel\\v4.0_7.1.0.116__360aac4d3354074b\\ folder (with the command prompt).\r\n3. Copy the file Tridion.TranslationManager.DomainModel.dll from this hotfix to the %windir%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.TranslationManager.DomainModel\\v4.0_7.1.0.116__360aac4d3354074b\\ folder (with the command prompt).\r\n4. Copy the file Tridion.TranslationManager.DomainModel.dll from this hotfix to \"%Tridion%\\Translation Manager\" replacing the old version.\r\n5. Restart the Content Manager Explorer Web site.\r\n6. Start the Tridion Translation Manager Service.\r\n7. Configure the Content Type in SDL TMS to use the pre-processing tool named \"W3C ITS Compliant\" (replacing the pre-processing tool named \"SDL Tridion ITS\").\r\n\r\n\r\nDistributed files:\r\n- Tridion.TranslationManager.DomainModel.dll (version 7.1.0.119)\r\n\r\n\r\nFixes included:\r\n N/A\r\n\r\n\r\nDependencies:\r\n N/A\r\n\r\nDisclaimer:\r\nHotfixes are released at the discretion of SDL Tridion based on technical complexity, customer business requirements and schedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by SDL Tridion Customer Support. Hotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright (c) 2014 SDL Tridion B.V.\r\n",
"version": "2013 SP1"
},
{
"_id": {
"$oid": "635fe2bd94436e1bc8257d21"
},
"hotfix_name": "CD_8.5.0.9206",
"modified_date": {
"$date": 1520510788439
},
"problem_description": "CPU server spikes of 100%\r\n",
"readme_text": "Release Notes for Hotfix CRQ-9206\r\n=================================\r\n\r\nVersion:\r\n========\r\nThis cumulative hotfix is intended only for SDL Web 8.5.0 customers.\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n- CRQ-2906 Sdl.Web.Delivery.Caching.dll not thread safe - causing CPU server spikes of 100%\r\n\r\nInstallation:\r\n=============\r\nThis cumulative hotfix provides updated api rest role for dotnet.\r\n\r\n1. Stop your REST web application\r\n2. Create backup to a safe location\r\n3. Delete DLLs present in your web-app\r\n4. Copy new DLLs from api\\rest folder of this HF to your web application\r\n5. Start web application\r\n\r\n\r\nDistributed roles:\r\n==================\r\napi\t\t\tAPI REST role\r\n\r\nDependencies:\r\n=============\r\nN/A\r\n\r\nFixed problems:\r\n===============\r\n- CRQ-8403 Sdl.Web.Delivery.Caching.dll not thread safe - causing CPU server spikes of 100%\r\n\r\nProblem Description\r\n-------------------\r\nCPU server spikes of 100%\r\n\r\nHotfix Description\r\n-------------------\r\nThis fix resolves some threading issues in the .NET CIL.\r\n\r\nDisclaimer:\r\n===========\r\n\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. \r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore \r\nshould only be installed if approved by Customer Support. Hotfixes should be replaced as soon as possible by the \r\nsubsequent patch release where the problem is fixed.\r\n\r\nCopyright 2015-2018 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.\r\n",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2b994436e1bc8257c95"
},
"hotfix_name": "CD_8.1.1.3597",
"modified_date": {
"$date": 1483977341561
},
"problem_description": "- Deployer locks \"incoming\" subfolders blocking entire publishing queue\r\n",
"readme_text": "Release Notes for Hotfix CRQ-3597\r\n=================================\r\n\r\nVersion:\r\n========\r\nThis is cumulative hotfix and is intended only for SDL Web 8.1.1\r\n\r\nDescription:\r\n============\r\nThe hotfix include the following fixes: \r\n - CRQ-3597 Deployer locks \"incoming\" subfolders blocking entire publishing queue\r\n \r\nInstallation:\r\n=============\r\nThis cumulative hotfix provides updated Deployer Service role.\r\n\r\nSDL Web Deployer Service\r\n-----------------------\r\n1. Stop SDL Web Deployer Service\r\n2. Backup (or move) a folder where your standalone Deployer Service is located\r\n3. Uninstall the SDL Web Deployer Service by opening a Powershell window in the \\bin of your service and run .\\uninstallService.ps1\r\n4. Navigate to the release\\deployer folder of this distribution\r\n5. Copy \\standalone folder to the location where your original service was located\r\n6. Rename copied \\standalone folder to the name of your original service's folder\r\n7. Copy all files from \\config folder of your backup (see step #2) to \\config folder of a new service\r\n8. Copy custom jars (if you have any) from backup's \\services\\folder to a same location of a new service\r\n9. Install service by opening a Powershell window in in the location \\bin of new service and run .\\installService.ps1\r\n\r\n\r\nDistributed roles:\r\n==================\r\ndeployer\t\tDeployer Service role\r\n\r\nFixed problems:\r\n===============\r\n - CRQ-3597 Deployer locks \"incoming\" subfolders blocking entire publishing queue\r\n \r\n \r\nProblem Description\r\n-------------------\r\n- Deployer locks \"incoming\" subfolders blocking entire publishing queue\r\n\r\nHotfix Description\r\n-------------------\r\n- Removed max size check which is trying to access files while it is locked because of internal processing.\r\n\r\nDisclaimer:\r\n===========\r\n\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by Customer Support. Hotfixes should be replaced as soon as possible by the subsequent patch release where the problem is fixed.\r\n\r\nCopyright 2015-2017 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.\r\n",
"version": "Web 8.1.1"
},
{
"_id": {
"$oid": "635fe2ba94436e1bc8257cc2"
},
"hotfix_name": "MMC_1.4_9320",
"modified_date": {
"$date": 1521205024297
},
"problem_description": "High memory consumption during thumbnail generation of large images\r\n",
"readme_text": "Release Notes for Hotfix 9320\r\n\r\nVersion:\r\nThis hotfix is intended only for SDL Tridion Connector for SDL Media Manager version 1.4.\r\n\r\nProblem description:\r\nHigh memory consumption during thumbnail generation of large images\r\n\r\nHotfix description:\r\nUse Media Manager to resize images.\r\n\r\nInstallation:\r\n 1. Stop all TCM Services, IIS Service, and the TCM COM+ Application.\r\n 2. Move the file SdlMediaManagerConnector.dll located in the %ALLUSERSPROFILE%\\SDL\\SDL Tridion\\External Content Library\\AddInPipeline\\AddIns\\SdlMediaManagerConnector folder\r\n 3. Copy the SdlMediaManagerConnector.dll file from this hotfix to the %ALLUSERSPROFILE%\\SDL\\SDL Tridion\\External Content Library\\AddInPipeline\\AddIns\\SdlMediaManagerConnector folder\r\n 4. Delete the AddIns.store file from %ALLUSERSPROFILE%\\SDL\\SDL Tridion\\External Content Library\\AddInPipeline\\AddIns\r\n 5. Restart the IIS Service, TCM Services and TCM COM+ Application.\r\n\r\n \r\nDistributed files:\r\n SdlMediaManagerConnector.dll (File Version 1.4.0.65)\r\n Readme.txt (this file)\r\n\r\nFixes included:\r\n\tN/A\r\n\r\nDependencies:\r\n\tN/A\r\n\r\nDisclaimer:\r\nHotfixes are released at the discretion of SDL based on technical complexity, customer business requirements and schedules.\r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by Customer Support of SDL Web Content Management Solutions Division.\r\nHotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright (c) 2018 SDL Group.",
"version": "Web 8.1.1"
},
{
"_id": {
"$oid": "635fe2ab94436e1bc8257a4e"
},
"hotfix_name": "CM_2011.1.1.83085",
"modified_date": {
"$date": 1352907988724
},
"problem_description": "ORA-01002: fetch out of sequence when the user non-admin user tries to publish several items.\r\n",
"readme_text": "Release Notes for Hotfix TT83085\r\n\r\nVersion:\r\nThis hotfix is intended only for SDL Tridion Content Manager 2011 SP1 HR1 on Oracle.\r\n\r\nProblem description:\r\nORA-01002: fetch out of sequence when the user non-admin user tries to publish several items.\r\n\r\nHotfix description:\r\nOptimized the stored procedures responsible for gathering user permissions.\r\n\r\nInstallation:\r\n 1. Stop all TCM Services, IIS Service, and the TCM COM+ Application.\r\n 2. Using SQL*Plus, connect as \"tridion_sys\" to the database instance. \r\n 3. Temporarily grant additional rights to the Tridion database user (typically TCMDBUser):\r\n\tGRANT CREATE TRIGGER TO &TCMDBUser;\r\n\tGRANT CREATE PROCEDURE TO &TCMDBUser;\r\n \tGRANT CREATE ANY TABLE TO &TCMDBUser;\r\n\tGRANT CREATE SEQUENCE TO &TCMDBUser;\r\n\tGRANT EXECUTE ON SYS.DBMS_UTILITY TO &TCMDBUser;\r\n 3. Using SQL*Plus, log in as the Tridion database user (typically TCMDBUser).\r\n 4. Execute the SQL script CM_6.1.0.83085_ORACLE.sql.\r\n 5. Check the file CM_6.1.0.83085.log for errors.\r\n 6. Revoke the additional rights from the Tridion database user\t\r\n\tREVOKE EXECUTE ON SYS.DBMS_UTILITY FROM &TCMDBUSER;\r\n\tREVOKE CREATE TRIGGER FROM &TCMDBUser;\t \r\n\tREVOKE CREATE PROCEDURE FROM &TCMDBUser;\r\n\tREVOKE CREATE ANY TABLE FROM &TCMDBUser;\r\n\tREVOKE CREATE SEQUENCE FROM &TCMDBUser;\r\n 7. Restart the IIS Service, TCM Services and TCM COM+ Application.\r\n\r\nDistributed files:\r\n CM_6.1.0.83085_ORACLE.sql\r\n EDA_TRUSTEES.sql\r\n TCM_RECOMPILE_PACKAGES.sql\r\n Readme.txt (this file)\r\n\r\nFixes included:\r\n TT78035\r\n\r\nDependencies:\r\n NA\r\n\r\nDisclaimer:\r\nHotfixes are released at the discretion of SDL based on technical complexity, customer business requirements and schedules.\r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by Customer Support of SDL Web Content Management Solutions Division.\r\nHotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright 2012 SDL PLC. All Rights Reserved. All company product or service names referenced herein are properties of their respective owners.",
"version": "2011 SP1 HR#1"
},
{
"_id": {
"$oid": "635fe2a994436e1bc82579e6"
},
"hotfix_name": "CM_2011.0.1.77526",
"modified_date": {
"$date": 1330444896188
},
"problem_description": "Missing description and schema reference id field when using a system-wide list.\r\n",
"readme_text": "Release Notes for Hotfix TT77526\r\n\r\nVersion:\r\nThis hotfix is intended only for SDL Tridion Content Manager 2011 SP1.\r\n\r\nProblem description:\r\nMissing description and schema reference id field when using a system-wide list.\r\n\r\nHotfix description:\r\nThe System-wide list now includes the description and schema reference id field.\r\n\r\nInstallation:\r\n 1. Stop all TCM Services, IIS Service, and the TCM COM+ Application.\r\n\r\n\r\nIf the Database is Microsoft SQL Server\r\n 1. Using Query Analyzer, osql, sqlcmd or SQL Server Management Studio, log in to the SDL Tridion database using 'sa'.\r\n 2. Execute the SQL file EDA_ITEMS_SQL.sql.\r\n\r\n\r\nIf the Database is Oracle \r\n 1. Using SQL*Plus, connect as \"tridion_sys\" to the database instance. \r\n 2. Temporarily grant additional rights to the Tridion database user (typically TCMDBUser):\r\n\tGRANT CREATE TRIGGER TO &TCMDBUser;\r\n\tGRANT CREATE PROCEDURE TO &TCMDBUser;\r\n \tGRANT CREATE ANY TABLE TO &TCMDBUser;\r\n\tGRANT CREATE SEQUENCE TO &TCMDBUser;\r\n\tGRANT EXECUTE ON SYS.DBMS_UTILITY TO &TCMDBUser;\r\n 3. Using SQL*Plus, log in as the Tridion database user (typically TCMDBUser).\r\n 4. Execute the SQL script CM_6.1.0.77526_ORACLE.sql.\r\n 5. Check the file CM_6.1.0.77526.log for errors.\r\n 6. Revoke the additional rights from the Tridion database user\t\r\n\tREVOKE EXECUTE ON SYS.DBMS_UTILITY FROM &TCMDBUSER;\r\n\tREVOKE CREATE TRIGGER FROM &TCMDBUser;\t \r\n\tREVOKE CREATE PROCEDURE FROM &TCMDBUser;\r\n\tREVOKE CREATE ANY TABLE FROM &TCMDBUser;\r\n\tREVOKE CREATE SEQUENCE FROM &TCMDBUser;\r\n\r\n\r\n 3. Move or Backup the file Tridion.ContentManager.dll located in the %WINDIR%\\assembly\\GAC_MSIL\\Tridion.ContentManager\\6.1.0.996__360aac4d3354074b folder\r\n 4. Copy the Tridion.ContentManager.dll file from this hotfix to the %WINDIR%\\assembly\\GAC_MSIL\\Tridion.ContentManagerr\\6.1.0.996__360aac4d3354074b folder\r\n 5. Move or Backup the file Tridion.ContentManager.Data.AdoNet.dll located in the %WINDIR%\\assembly\\GAC_MSIL\\Tridion.ContentManager.Data.AdoNet.dll\\6.1.0.996__360aac4d3354074b folder\r\n 6. Copy the Tridion.ContentManager.Data.AdoNet.dll file from this hotfix to the %WINDIR%\\assembly\\GAC_MSIL\\Tridion.ContentManager.Data.AdoNet.dll\\6.1.0.996__360aac4d3354074b folder\r\n 7. Restart the IIS Service, TCM Services and TCM COM+ Application.\r\n\r\nDistributed files:\r\n CM_6.1.0.77526_ORACLE.sql\r\n EDA_ITEMS_ORACLE.sql \r\n TCM_RECOMPILE_PACKAGES.sql\r\n EDA_ITEMS_SQL.sql\r\n Readme.txt (this file)\r\n Tridion.ContentManager.dll (file version 6.1.0.1001)\r\n Tridion.ContentManager.Data.AdoNet.dll (file version 6.1.0.997)\r\n\r\nFixes included:\r\n 77580\r\n\r\nDependencies:\r\n 78532\r\n\r\nDisclaimer:\r\nHotfixes are released at the discretion of SDL based on technical complexity, customer business requirements and schedules.\r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by Customer Support of SDL Web Content Management Solutions Division.\r\nHotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright 2012 SDL PLC. All Rights Reserved. All company product or service names referenced herein are properties of their respective owners.\r\n",
"version": "2011 SP1"
},
{
"_id": {
"$oid": "635fe2b594436e1bc8257c26"
},
"hotfix_name": "TM_9.1.0.18479",
"modified_date": {
"$date": 1583505318020
},
"problem_description": "Error \"Unable to determine if valid translation job can be created\" for non admin user.\r\n",
"readme_text": "Release Notes for Hotfix CRQ-18479\r\n\r\nVersion: \r\n\tThis hotfix is intended for SDL Tridion Sites 9.1.\r\n\r\nProblem description:\r\n\tError \"Unable to determine if valid translation job can be created\" for non admin user.\r\n\r\nHotfix description:\r\n\tFix code taht load users.\r\n\r\nInstallation:\r\n\t1.\tStop the SDL Web Translation Manager Service\r\n\t2.\tStop \"SDL Web Content Manager Service Host\" service and all dependent services\r\n\t3.\tStop Content Manager Explorer Web site\r\n\t4.\tNavigate to the versioned Tridion.TranslationManager.DomainModel folder in your Global Assembly Cache (typically C:\\Windows\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.TranslationManager.DomainModel\\v4.0_9.1.0.0__360aac4d3354074b)\r\n\t5.\tTake a backup of the existing Tridion.TranslationManager.DomainModel.dll file.\r\n\t6.\tReplace the file with the version included in this hotfix.\r\n\t7.\tRestart the Content Manager Explorer Web site.\r\n\t8.\tStart \"SDL Web Content Manager Service Host\" service and all dependent services.\r\n\t9.\tStart the SDL Web Translation Manager Service.\r\n\r\nDistributed files:\r\n\t- Tridion.TranslationManager.DomainModel.dll (File version: 9.1.0.21)\r\n \t- Readme.txt (this file)\r\n\r\nFixes included:\r\n\tCRQ-17009:\tXLIFF parser does not support TMS comments.\r\n\tCRQ-14886:\t\"The item v0 does not exist\" error during publish on retrieve.\r\n\t\r\n\t\r\nDependencies:\r\n\tn.a.\r\n\r\nDisclaimer:\r\n\tHotfixes are released at the discretion of SDL based on technical complexity, customer business requirements and schedules.\r\n\tHotfixes are made and tested only for the described problem on a particular environment\\configuration and therefore should only be installed if approved by Customer Support of SDL Web Content Management Solutions Division.\r\n\tHotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright 2020 SDL PLC. All Rights Reserved. All company product or service names referenced herein are properties of their respective owners.\r\n",
"version": "Sites 9.1"
},
{
"_id": {
"$oid": "635fe2ae94436e1bc8257b23"
},
"hotfix_name": "CEC_2013.1.1.1402",
"modified_date": {
"$date": 1450191035580
},
"problem_description": "",
"readme_text": "Release Notes for Hotfix cwd_2013.1.1.1402 of the Context Engine\r\n\r\nVersion:\r\nThis hotfix is intended only for SDL Tridion release 2013 SP1\r\n\r\nHotfix description:\r\nThis hotfix addresses the following issues:\r\n* [TCD-8297] - Added fix to support Nokia Lumia devices with `like iPhone` within their user agent string\r\n* [TCD-8030] - Tridion 2013 SP1 fails for update with - Property definition not found for device.4g\r\n* [TCD-8031] - Update vocabulary in v7 release to include device.4g property AND set user agent based on build version\r\n* [TCWD-1273] - Allow pre-existing claims to be treated as evidence that can resolve context properties with a configurable trust level\r\n* [TCWD-1132] - Improve usability of Context Engine with Experience Manager\r\n* [TCWD-1698] - Make all Context Engine Claims request scoped\r\n\r\nInstallation:\r\n\r\n1. Copy the files with the \"jar\" extension to the bin\\lib\\ (.NET) or WEB-INF/lib/ (Java) sub-folder of your Web\r\n application.\r\n\r\n2. Open a command shell and navigate to the bin\\ folder (.NET) or WEB-INF/ folder (Java) of your Web application.\r\n\r\n3. Move the repository folder to a backup location\r\n\r\n4. Re-generate the device database as follows:\r\n(Windows)\r\n java -Xms1024m -jar lib\\cwd_engine.jar http://context.sdl.com/seed\r\n(Unix)\r\n java -Xms1024m -jar lib/cwd_engine.jar http://context.sdl.com/seed\r\n\r\n5. Restart your Context Engine application.\r\n\r\nYou have now updated the SDL Tridion Context Engine.\r\n\r\nDistributed files:\r\nreadme.txt (this file)\r\ncwd_engine.jar\r\nhttpclient.jar\r\nhttpcore.jar\r\n\r\nDependencies:\r\nN/A\r\n\r\nDisclaimer:\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules.\r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore\r\nshould only be installed if approved by Customer Support. Hotfixes should be replaced as soon as possible by the\r\nsubsequent service pack where the problem is fixed.\r\nCopyright \u00a9 2015 SDL Group. All Rights Reserved. Nothing contained herein may be reproduced, copied, modified or\r\nadapted, without the prior written consent of SDL Group.\r\n",
"version": "2013 SP1 HR#1"
},
{
"_id": {
"$oid": "635fe2a994436e1bc82579e4"
},
"hotfix_name": "CD_2011.1.0.79212",
"modified_date": {
"$date": 1331028668679
},
"problem_description": "The Component link field type not exposed in keyword metadata when requesting keyword metadata in the broker API.\r\nWhen deploying a complex Taxonomy containing multiparent keywords and more than a few thousand keywords with many related items the deployment\r\nexceeds the transaction timeout and can take up to an hour to complete.\r\nWhen undeploying a complex transport package undeployment fails with following error message Unknown entity: com.tridion.storage.ItemMeta_$$_javassist_13.\r\nDeployer locks up after \"The process cannot access the file\" Error\r\n",
"readme_text": "Release Notes for Hotfix TT79212\r\n================================\r\n\r\nVersion:\r\n========\r\nThis cumulative hotfix and is intended only for Tridion 2011 SP1\r\nThe hotfix includes the following fixes:\r\n- TT77133 Component link field type not exposed in keyword metadata\r\n- TT78523 Publish a large package with many linked components in 2011 SP1 along with a large, nested taxonomy exceeds transaction timeout\r\n- TT79176 Error while unpublishing: Unable to remove data entity, Unknown entity: com.tridion.storage.ItemMeta_$$_javassist_13,\r\n- TT79212 Deployer locks up after \"The process cannot access the file\" Error \r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n- TT79212 Deployer locks up after \"The process cannot access the file\" Error \r\n\r\nInstallation:\r\n=============\r\nDeployer environment:\r\n---------------------\r\nJava Environment with HttpUpload:\r\n1. Ensure that you have a correct installed Content Delivery installation inside your web application\r\n2. Stop your web application server or web application containing the deployer httpupload\r\n3. Copy the distributed jar files inside your web application WEB-INF\\lib directory\r\n4. Start your web application server or web application\r\n\r\n.NET Environment with HttpUpload:\r\n1. Ensure the application pool and or IIS Server has been stopped\r\n2. Copy the distributed jar files inside the IIS application directory bin\\lib directory. In case of central tridion installation please copy the distributed jar files\r\ninto the installation directory \\lib folder.\r\n3. Start the application pool and or IIS Server\r\n\r\nStandalone deployer:\r\n1. Ensure the deployer service has been stopped\r\n2. Copy the distributed jar files inside your 'Tridion installation folder'\\lib directory\r\n3. Start the deployer service\r\n\r\nDistributed files:\r\n==================\r\ncd_datalayer.jar\r\ncd_storage_conf.xsd\r\ncd_storage_conf_sample.xml\r\n\r\nDependencies:\r\n=============\r\nIncluded hotfix TT77133 Component link field type not exposed in keyword metadata\r\nIncluded hotfix TT78523 Publish a large package with many linked components in 2011 SP1 along with a large, nested taxonomy exceeds transaction timeout\r\nIncluded hotfix TT79176 Error while unpublishing: Unable to remove data entity, Unknown entity: com.tridion.storage.ItemMeta_$$_javassist_13,\r\nIncluded hotfix TT79212 Deployer locks up after \"The process cannot access the file\" Error \r\n\r\nFixed problems:\r\n===============\r\nTT77133\r\nProblem Description\r\n-------------------\r\nThe Component link field type not exposed in keyword metadata when requesting keyword metadata in the broker API.\r\n\r\nHotfix Description\r\n-------------------\r\nThe issues occurs due to incorrect namespace handling of the keyword metadata in taxonomies. The link information was in a different\r\nunrecognized namespace and therefore ignored. This has been resolved by properly handling the namespace containing the link information\r\nfor the keyword.\r\n\r\nTT78523\r\nProblem Description\r\n-------------------\r\nWhen deploying a complex Taxonomy containing multiparent keywords and more than a few thousand keywords with many related items the deployment\r\nexceeds the transaction timeout and can take up to an hour to complete.\r\n\r\nHotfix Description\r\n-------------------\r\nThe cause of the issue is the related item count that is provided on API level. The related item count to a keyword is calculated during deployment\r\ntime due to the complexity of taxonomies with multi-parent keywords the query for each level of the taxonomy grows exponentially in time to execute.\r\n\r\nThe solution is to provide an option to switch of the reference counting mechanism on keywords. The following configuration option is added to the\r\nstorage configuration file under the 'Global' element:\r\n\r\n\r\nBy setting this to false the keyword reference counts are no longer calculated impacting the following api's:\r\nJava Class: com.tridion.taxonomies.Keyword and method: getReferencedContentCount\r\n.NET Class: Tridion.ContentDelivery.Taxonomies.Keyword and then property: 'ReferencedContentCount'\r\n\r\nThe impact will result in these methods returning a '0' integer return value.\r\n\r\nTT79176\r\nProblem Description\r\n-------------------\r\nWhen undeploying a complex transport package undeployment fails with following error message Unknown entity: com.tridion.storage.ItemMeta_$$_javassist_13.\r\n\r\nHotfix Description\r\n-------------------\r\nBefore Item is moved the session should be flushed prior to fetching the item by primary key.\r\n\r\nTT79212\r\nProblem Description\r\n-------------------\r\nDeployer locks up after \"The process cannot access the file\" Error\r\n\r\nHotfix Description\r\n-------------------\r\nIn case that commit failes rollback was not done properly what caused deployer locks. The problem is solved by executing rollback in case deployment fails in commit phase.\r\n\r\nDisclaimer:\r\n===========\r\nHotfixes are released at the discretion of Tridion based on technical\r\ncomplexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/\r\nconfiguration and therefore should only be installed if approved by Tridion\r\nCustomer Support. Hotfixes should be replaced as soon as possible by the\r\nsubsequent service pack where the problem is fixed.\r\n\r\n(c) 2012 SDL Tridion B.V.\r\n",
"version": "2011 SP1"
},
{
"_id": {
"$oid": "635fe2bd94436e1bc8257d22"
},
"hotfix_name": "CD_8.5.0.9378",
"modified_date": {
"$date": 1521734975534
},
"problem_description": "- CRQ-9365 Not able to update context repository when using proxy connection.\r\n- CRQ-9378 Not able to use encrypted SSL related passwords within application properties.\r\n",
"readme_text": "Release Notes for Hotfix CRQ-9365, CRQ-9378\r\n=================================\r\n\r\nVersion:\r\n========\r\nThis cumulative hotfix is intended only for SDL Web 8.5.0 customers.\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n - CRQ-9365 SDL Web 8.5 - Context Service device database\r\n - CRQ-9378 Fix to allow encrypted server.ssl.key-store-password system property\r\n\r\nInstallation:\r\n=============\r\nThis cumulative hotfix provides updated standalone service roles.\r\n\r\nAll Services\r\n------------\r\n1. Stop the Service you are going to update\r\n2. Backup (or move) the folder where your standalone Service is located\r\n3. Uninstall the Service by opening a Powershell window in the \\bin folder of your service and running\r\n .\\uninstallService.ps1\r\n4. Navigate to the release\\\\service folder of this distribution\r\n5. Copy the \\standalone folder to the location where your original service was located\r\n6. Rename copied \\standalone folder to the name of your original service's folder\r\n7. Copy all files from \\config folder of your backup (see step #2) to \\config folder of a new service\r\n8. Copy custom jars (if you have any) from backup's \\services\\ folders to the same location in new service\r\n9. Install service by opening a Powershell window in in the \\bin folder of the new service and run .\\installService.ps1\r\n\r\n\r\nDistributed roles:\r\n==================\r\ncaching\t\tCache Channel Service role\r\ncid\t\t\tContextual Image Delivery Service role\r\ncontent\t\tContent Service role\r\ncontext\t\tContext Service role\r\ndeployer\tDeployer Service roles\r\ndiscovery\tDiscovery Service role\r\nmonitoring\tMonitoring Service role\r\npreview\t\tPreview Service role\r\nsession\t\tSession-enabled Content Service role\r\nugc\t\t\tUGC Service roles\r\n\r\nDependencies:\r\n=============\r\nN/A\r\n\r\nFixed problems:\r\n===============\r\n - CRQ-9365 SDL Web 8.5 - Context Service device database\r\n - CRQ-9378 Fix to allow encrypted server.ssl.key-store-password system property\r\n\r\nProblem Description\r\n-------------------\r\n - CRQ-9365 Not able to update context repository when using proxy connection.\r\n - CRQ-9378 Not able to use encrypted SSL related passwords within application properties.\r\n\r\nHotfix Description\r\n-------------------\r\n - CRQ-9365 Using another HTTP client to allow using proxy.\r\n - CRQ-9378 Added ability to use encrypted SSL related passwords within application properties.\r\n\r\nDisclaimer:\r\n===========\r\n\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules.\r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore\r\nshould only be installed if approved by Customer Support. Hotfixes should be replaced as soon as possible by the\r\nsubsequent patch release where the problem is fixed.\r\n\r\nCopyright \ufffd 2015-2017 SDL Group. All Rights Reserved.\r\n\r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.\r\n",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2ae94436e1bc8257b18"
},
"hotfix_name": "CD_2013.1.1.1663",
"modified_date": {
"$date": 1457693607737
},
"problem_description": "Need a provision to set minimum evictable idle time and validation query in cd_storage_config.xml.\r\n",
"readme_text": "Release Notes for Hotfix CRQ-1663\r\n================================\r\n\r\nVersion:\r\n========\r\nThis is hotfix and is intended only for Tridion 2013 SP1 HR1\r\nThe hotfix include the following fixes:\r\n\t- CRQ-1663 (SRQ-4662) Limited ability to configure DBCP Connection Pool while defining CD Storage Configuration\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n- CRQ-1663 (SRQ-4662) Limited ability to configure DBCP Connection Pool while defining CD Storage Configuration\r\n\r\nProblem Description\r\n====================\r\nNeed a provision to set minimum evictable idle time and validation query in cd_storage_config.xml.\r\n\r\nHotfix Description\r\n====================\r\nAdd MinEvictableIdleTimeout integer property and ValidationQuery string property to Pool configuration.\r\n\r\n\r\nInstallation:\r\n=============\r\n\r\nTridion CD environment:\r\n-----------------------\r\n1. Stop any Tridion CD processes.\r\n2. Replace the existing cd_datalayer.jar and cd_storage_conf.xsd in your environment with the new JAR and XML schema delivered by this hotfix.\r\n3. Restart any Tridion CD processes.\r\n\r\nDistributed files:\r\n==================\r\ncd_datalayer.jar\r\ncd_storage_conf.xsd\r\n\r\nDependencies:\r\n=============\r\nSDL Tridion 2013 SP1 HR1\r\n\r\nDisclaimer:\r\n===========\r\nHotfixes are released at the discretion of Tridion based on technical\r\ncomplexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/\r\nconfiguration and therefore should only be installed if approved by Tridion\r\nCustomer Support. Hotfixes should be replaced as soon as possible by the\r\nsubsequent service pack where the problem is fixed.\r\n\r\nCopyright 2016 SDL PLC. All Rights Reserved.\r\n\r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.\r\n",
"version": "2013 SP1 HR#1"
},
{
"_id": {
"$oid": "635fe2c094436e1bc8257d89"
},
"hotfix_name": "MMC_1.4_9320",
"modified_date": {
"$date": 1521205024297
},
"problem_description": "High memory consumption during thumbnail generation of large images\r\n",
"readme_text": "Release Notes for Hotfix 9320\r\n\r\nVersion:\r\nThis hotfix is intended only for SDL Tridion Connector for SDL Media Manager version 1.4.\r\n\r\nProblem description:\r\nHigh memory consumption during thumbnail generation of large images\r\n\r\nHotfix description:\r\nUse Media Manager to resize images.\r\n\r\nInstallation:\r\n 1. Stop all TCM Services, IIS Service, and the TCM COM+ Application.\r\n 2. Move the file SdlMediaManagerConnector.dll located in the %ALLUSERSPROFILE%\\SDL\\SDL Tridion\\External Content Library\\AddInPipeline\\AddIns\\SdlMediaManagerConnector folder\r\n 3. Copy the SdlMediaManagerConnector.dll file from this hotfix to the %ALLUSERSPROFILE%\\SDL\\SDL Tridion\\External Content Library\\AddInPipeline\\AddIns\\SdlMediaManagerConnector folder\r\n 4. Delete the AddIns.store file from %ALLUSERSPROFILE%\\SDL\\SDL Tridion\\External Content Library\\AddInPipeline\\AddIns\r\n 5. Restart the IIS Service, TCM Services and TCM COM+ Application.\r\n\r\n \r\nDistributed files:\r\n SdlMediaManagerConnector.dll (File Version 1.4.0.65)\r\n Readme.txt (this file)\r\n\r\nFixes included:\r\n\tN/A\r\n\r\nDependencies:\r\n\tN/A\r\n\r\nDisclaimer:\r\nHotfixes are released at the discretion of SDL based on technical complexity, customer business requirements and schedules.\r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by Customer Support of SDL Web Content Management Solutions Division.\r\nHotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright (c) 2018 SDL Group.",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2ac94436e1bc8257a80"
},
"hotfix_name": "CME_2011.1.2.87192",
"modified_date": {
"$date": 1386334314351
},
"problem_description": "Error message does not show when in processed items tab of the PublishTransaction when more than one template is used\r\n",
"readme_text": "Release Notes for Hotfix 87192\r\n\r\nVersion:\r\nThis hotfix is intended for SDL Tridion Content Manager Explorer 2011 SP1 HR2.\r\n\r\nProblem description:\r\nError message does not show when in processed items tab of the PublishTransaction when more than one template is used\r\n\r\nHotfix description:\r\nChanged the way how we recognize selected item\r\n\r\nInstallation:\r\n\r\n 1. Move or delete the file PublishTransaction.js located in the %TRIDION_HOME%\\web\\WebUI\\Editors\\CME\\Views\\Popups\\PublishTransaction\\ folder.\r\n 2. Copy the file PublishTransaction.js from this hotfix to the %TRIDION_HOME%\\web\\WebUI\\Editors\\CME\\Views\\Popups\\PublishTransaction\\folder.\r\n 3. Move or delete the file publishtransaction-head.xml located in the %TRIDION_HOME%\\web\\WebUI\\Editors\\CME\\Xml\\ListDefinitions\\ folder.\r\n 4. Copy the file publishtransaction-head.xml from this hotfix to the %TRIDION_HOME%\\web\\WebUI\\Editors\\CME\\Xml\\ListDefinitions\\folder.\r\n 5. Open %TRIDION_HOME%\\web\\WebUI\\WebRoot\\Configuration\\System.config file.\r\n 6. Locate /Configuration/servicemodel/server node in Sytem.config file and increase the number of it's modification attribute to notify client browsers to update their cache.\r\n\r\nDistributed files:\r\n\r\n - Readme.txt (this file)\r\n - PublishTransaction.js\r\n - publishtransaction-head.xml\r\n\r\nFixes included:\r\n N/A\r\n\r\nDependencies:\r\n N/A\r\n\r\nDisclaimer:\r\n\tHotfixes are released at the discretion of SDL based on technical complexity, customer business requirements and schedules.\r\n\tHotfixes are made and tested only for the described problem on a particular environment\\configuration and therefore should only be installed if approved by Customer Support of SDL Web Content Management Solutions Division.\r\n\tHotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright 2013 SDL PLC. All Rights Reserved. All company product or service names referenced herein are properties of their respective owners.\r\n",
"version": "2011 SP1 HR#2"
},
{
"_id": {
"$oid": "635fe2ba94436e1bc8257cb9"
},
"hotfix_name": "CM_8.1.1.5445",
"modified_date": {
"$date": 1500025665983
},
"problem_description": "When \"If other published Components link to a Component you are publishing, republish those Components\" checkbox enabled during publishing, \r\nnon-published components are resolved for publishing (while only previously published ones should be resolved).\r\n",
"readme_text": "Release Notes for Hotfix CRQ-5445.\r\n\r\nVersion:\r\nThis hotfix is intended only for SDL Web 8 Cumulative Update 1 and MS SQL Server database.\r\n\r\nProblem description:\r\nWhen \"If other published Components link to a Component you are publishing, republish those Components\" checkbox enabled during publishing, \r\nnon-published components are resolved for publishing (while only previously published ones should be resolved).\r\n\r\nHotfix description:\r\nIssue was in resolving logic. Republishing of dynamic component presentation led to republish dynamic component template and all DCPs \r\nregardless of the publish state of the components.\r\n\r\nInstallation:\r\n 1. Stop all TCM Services, IIS Service, and the TCM COM+ Application.\r\n 2. Database actions:\r\n a. Using Query Analyzer, osql, sqlcmd or SQL Server Management Studio, log in to the SDL Tridion database using 'sa'.\r\n b. Execute the SQL file EDA_ITEMS.sql\r\n 3. Restart the IIS Service, TCM Services and TCM COM+ Application.\r\n\r\nDistributed files:\r\n EDA_ITEMS.sql\r\n Readme.txt (this file)\r\n\r\n\r\nFixes included:\r\n None\r\n\r\nDependencies:\r\n SDL Web 8 Cumulative Update 1\r\n\r\nDisclaimer:\r\n\tHotfixes are released at the discretion of SDL based on technical complexity, customer business requirements and schedules.\r\n\tHotfixes are made and tested only for the described problem on a particular environment\\configuration and therefore should only be installed if approved by Customer Support of SDL Web Content Management Solutions Division.\r\n\tHotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright 2017 SDL PLC. All Rights Reserved. All company product or service names referenced herein are properties of their respective owners.\r\n",
"version": "Web 8.1.1"
},
{
"_id": {
"$oid": "635fe2b594436e1bc8257c27"
},
"hotfix_name": "TM_9.1.0.19638",
"modified_date": {
"$date": 1604061136354
},
"problem_description": "Tridion Translation Manager marks a job as cancelled while its corresponding project is still in TCR on Worldserver.\r\n",
"readme_text": "Release Notes for Hotfix CRQ-19638\r\n\r\nVersion: \r\n\tThis hotfix is intended for SDL Tridion Sites 9.1.\r\n\r\nProblem description:\r\n\tTridion Translation Manager marks a job as cancelled while its corresponding project is still in TCR on Worldserver.\r\n\r\nHotfix description:\r\n\tLog information about responce retrieved at the time of cancelation.\r\n\tLog request/responce information during error.\r\n\r\nInstallation:\r\n\t1.\tStop the SDL Web Translation Manager Service\r\n\t2.\tStop \"SDL Web Content Manager Service Host\" service and all dependent services (SDL Web Content Manager Workflow Agent, SDL Web Content Manager Publisher, SDL Web Content Manager Batch Processor, SDL Web Content Manager Search Indexer)\r\n\t3.\tStop Content Manager Explorer Web site\r\n\t4.\tNavigate to the versioned Tridion.TranslationManager.DomainModel folder in your Global Assembly Cache (typically C:\\Windows\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.TranslationManager.DomainModel\\v4.0_9.1.0.0__360aac4d3354074b)\r\n\t5.\tTake a backup of the existing Tridion.TranslationManager.DomainModel.dll file.\r\n\t6.\tReplace the file with the version included in this hotfix.\r\n\t7.\tRestart the Content Manager Explorer Web site.\r\n\t8.\tStart \"SDL Web Content Manager Service Host\" service and all dependent services.\r\n\t9.\tStart the SDL Web Translation Manager Service.\r\n\r\nDistributed files:\r\n\t- Tridion.TranslationManager.DomainModel.dll (File version: 9.1.0.34)\r\n \t- Readme.txt (this file)\r\n\r\nFixes included:\r\n\tCRQ-17009:\tXLIFF parser does not support TMS comments.\r\n\tCRQ-14886:\t\"The item v0 does not exist\" error during publish on retrieve.\r\n\tCRQ-17149:\tUnable to retrieve translations if the TMS item has comments on it. The retrieval fails with the error 'unknown tag {urn:oasis:names:tc:xliff:document:1.2}mrk'.\r\n\tCRQ-18479:\tError \"Unable to determine if valid translation job can be created\" for non admin user.\r\n\tCRQ-21087:\tHandle WorldServer HTTP 409 (Conflict) errors.\r\n\tCRQ-21479:\tTranslation of ECL items fails after installing TM_9.0.0.19638 hotfix\r\n\t\r\nDependencies:\r\n\tn.a.\r\n\r\nDisclaimer:\r\n\tHotfixes are released at the discretion of SDL based on technical complexity, customer business requirements and schedules.\r\n\tHotfixes are made and tested only for the described problem on a particular environment\\configuration and therefore should only be installed if approved by Customer Support of SDL Web Content Management Solutions Division.\r\n\tHotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright 2020 SDL PLC. All Rights Reserved. All company product or service names referenced herein are properties of their respective owners.\r\n",
"version": "Sites 9.1"
},
{
"_id": {
"$oid": "635fe2c094436e1bc8257d93"
},
"hotfix_name": "TM_8.5.0.11627",
"modified_date": {
"$date": 1539017641791
},
"problem_description": "PRIMARY KEY constraint Error on TMSJOBS_ITEMS when shared item has circular links\r\n",
"readme_text": "Release Notes for Hotfix CRQ-11627\r\n\r\nVersion: \r\n\tThis hotfix is intended for SDL Web 8.5.\r\n\r\nProblem description:\r\n\tPRIMARY KEY constraint Error on TMSJOBS_ITEMS when shared item has circular links\r\n\r\nHotfix description:\r\n\tFix item resolving mechanism.\r\n\r\nInstallation:\r\n\t1.\tStop the SDL Web Translation Manager Service\r\n\t2.\tStop \"SDL Web Content Manager Service Host\" service and all dependent services\r\n\t3.\tStop Content Manager Explorer Web site\r\n\t4.\tNavigate to the versioned Tridion.TranslationManager.DomainModel folder in your Global Assembly Cache (typically C:\\Windows\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.TranslationManager.DomainModel\\v4.0_8.5.0.146__360aac4d3354074b)\r\n\t5.\tTake a backup of the existing Tridion.TranslationManager.DomainModel.dll file.\r\n\t6.\tReplace the file with the version included in this hotfix.\r\n\t7.\tCopy the file Tridion.TranslationManager.TcmExtension.dll from this hotfix to \"%Tridion%\\Translation Manager\" replacing the old version.\r\n\t8.\tCopy the file Tridion.TranslationManager.UI.Model.dll from this hotfix to \"%Tridion%\\web\\WebUI\\WebRoot\\bin \" replacing the old version.\r\n\t9.\tCopy the file Tridion.TranslationManager.V2.TmService.dll from this hotfix to \"%Tridion%\\bin \" replacing the old version.\r\n\t10.\tTake a backup of the file %Tridion%\\web\\WebUI\\Editors\\TM\\Scripts\\Commands\\Translate.js and replace it with the version included in this hotfix.\r\n\t11.\tTake a backup of the file %Tridion%\\web\\WebUI\\Models\\TM\\Scripts\\Model\\TranslationJobCreationOptions.js and replace it with the version included in this hotfix.\r\n\t12.\tOpen %TRIDION_CM_HOME%web\\WebUI\\WebRoot\\Configuration\\System.config in a text editor.\r\n\t\tLocate the Configuration/servicemodel/server node in the System.config file and increase the value of its 'modification' attribute to notify client browsers to update their cache.\r\n\t13.\tRestart the Content Manager Explorer Web site.\r\n\t14.\tStart \"SDL Web Content Manager Service Host\" service and all dependent services.\r\n\t15.\tStart the SDL Web Translation Manager Service.\r\n\r\nDistributed files:\r\n\t- Tridion.TranslationManager.DomainModel.dll (File version: 8.5.0.197)\r\n\t- Tridion.TranslationManager.TcmExtension.dll (File version: 8.5.0.197)\r\n\t- Tridion.TranslationManager.UI.Model.dll (File version: 8.5.0.197)\r\n\t- Tridion.TranslationManager.V2.TmService.dll (File version: 8.5.0.197)\r\n\t- Translate.js\r\n\t- TranslationJobCreationOptions.js\r\n \t- Readme.txt (this file)\r\n\r\nFixes included:\r\n\tCRQ-3782\t\"The given key was not present in the dictionary.\" error when parsing XLiff document from TMS 11.1\r\n\t\t\t\tEnable intermediate retrieval of translation items from TMS\r\n\tCRQ-3875\tUI fails to load translation configuration or translation job if World Server workflow step have name that starts with 3-4 letter word. (e.g \"Set Asset Translation Status\")\r\n\tCRQ-4127\tTranslation manager slowdown publishing process\r\n\tCRQ-3832\tSlow performance opening Components in large BluePrints.\r\n\tCRQ-4544\tSlow performance in workflow related operations.\r\n\tCRQ-4997\tRetrieve from translation a bundle with an item that has already been translated and the parent item also has a minor version and get a DB error in TM DB.\r\n\tCRQ-5231\tItem resolve mechanism does not resolve container items by default.\r\n\tCRQ-8863\tAttempting to send a minor, reserved state version of a page to translate sends the last major version.\r\n\tCRQ-9170\tUI fails to send translation job if World Server workflow step have name that starts with 3-4 letter word.\r\n\tCRQ-9870\tUnable to retrieve aggregated items with a classic edit workflow defined.\r\n\tCRQ-10991\tTranslate popup takes around 1 minute to open.\r\n\tCRQ-11182\tTake too much time to open the translation job screen.\r\n\tCRQ-11520\tUnable to reconfigure failed translation configuration.\r\n\r\nDependencies:\r\n\tn.a.\r\n\r\nDisclaimer:\r\n\tHotfixes are released at the discretion of SDL based on technical complexity, customer business requirements and schedules.\r\n\tHotfixes are made and tested only for the described problem on a particular environment\\configuration and therefore should only be installed if approved by Customer Support of SDL Web Content Management Solutions Division.\r\n\tHotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright 2018 SDL PLC. All Rights Reserved. All company product or service names referenced herein are properties of their respective owners.\r\n",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2b194436e1bc8257bb0"
},
"hotfix_name": "CME_9.0.0.19056",
"modified_date": {
"$date": 1588668855511
},
"problem_description": "XSS vulnerability via \"url\" query parameter.\r\n",
"readme_text": "Release Notes for Hotfix CRQ-19056\r\n\r\nVersion:\r\nThis hotfix is intended for SDL Web 9.0\r\n\r\nProblem description: \r\nXSS vulnerability via \"url\" query parameter.\r\n\r\nHotfix description:\r\nDom-Based Cross-Site Scripting.\r\nCross Site Scripting (XSS) vulnerabilities occur when data submitted to the application is not\r\nproperly handled before being embedded within the application's response or stored for later retrieval.\r\nExample URL:\r\nhttps://localhost/SDL/#app=wcm&entry=cme&url=javascript:alert(\"hi\")\r\n\r\nInstallation:\r\n\t1. Create a backup of %TRIDION_HOME%\\web\\SDL\\Common\\ApplicationHost\\configuration.xml\r\n\t2. Copy the configuration.xml file from this hotfix to %TRIDION_HOME%\\web\\SDL\\Common\\ApplicationHost\\\r\n\t3. Create a backup of %TRIDION_HOME%\\web\\SDL\\Common\\ApplicationHost\\Packages\\SDL.Client.UI.ApplicationHost.txt\r\n\t4. Copy the SDL.Client.UI.ApplicationHost.txt file from this hotfix to %TRIDION_HOME%\\web\\SDL\\Common\\ApplicationHost\\Packages\\\r\n\t5. Create a backup of %TRIDION_HOME%\\web\\SDL\\Common\\ApplicationHost\\version.txt\r\n\t6. Copy the version.txt file from this hotfix to %TRIDION_HOME%\\web\\SDL\\Common\\ApplicationHost\\\r\n\t7. Restart IIS\r\n\r\nDistributed files:\r\n- Readme.txt (this file)\r\n- configuration.xml\r\n- SDL.Client.UI.ApplicationHost.txt\r\n- version.txt\r\n\r\nFixes included:\r\nn/a\r\n\r\nDependencies:\r\nn/a\r\n\r\nDisclaimer:\r\nHotfixes are released at the discretion of SDL based on technical complexity, customer business requirements and schedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by Customer Support of SDL Web Content Management Solutions Division. Hotfixes should be replaced as soon as possible by the subsequent patch release where the problem is fixed.\r\nCopyright 2020 SDL PLC. All Rights Reserved. All company product or service names referenced herein are properties of their respective owners. ",
"version": "Sites 9.0"
},
{
"_id": {
"$oid": "635fe2c094436e1bc8257d97"
},
"hotfix_name": "TM_8.5.0.14886",
"modified_date": {
"$date": 1560255392845
},
"problem_description": "Errors during publishing when workflow procces is finished.\r\n",
"readme_text": "Release Notes for Hotfix CRQ-14886\r\n\r\nVersion: \r\n\tThis hotfix is intended for SDL Web 8.5.\r\n\r\nProblem description:\r\n\tErrors during publishing when workflow procces is finished.\r\n\r\nHotfix description:\r\n\tBetter handling of workflow procces loading.\r\n\r\nInstallation:\r\n\t1.\tStop the SDL Web Translation Manager Service\r\n\t2.\tStop \"SDL Web Content Manager Service Host\" service and all dependent services\r\n\t3.\tStop Content Manager Explorer Web site\r\n\t4.\tNavigate to the versioned Tridion.TranslationManager.DomainModel folder in your Global Assembly Cache (typically C:\\Windows\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.TranslationManager.DomainModel\\v4.0_8.5.0.146__360aac4d3354074b)\r\n\t5.\tTake a backup of the existing Tridion.TranslationManager.DomainModel.dll file.\r\n\t6.\tReplace the file with the version included in this hotfix.\r\n\t7.\tCopy the file Tridion.TranslationManager.TcmExtension.dll from this hotfix to \"%TRIDION_CM_HOME%\\Translation Manager\" replacing the old version.\r\n\t8.\tCopy the file Tridion.TranslationManager.UI.Model.dll from this hotfix to \"%TRIDION_CM_HOME%\\web\\WebUI\\WebRoot\\bin \" replacing the old version.\r\n\t9.\tCopy the file Tridion.TranslationManager.UI.DataExtenders.dll from this hotfix to \"%TRIDION_CM_HOME%\\web\\WebUI\\WebRoot\\bin \" replacing the old version.\r\n\t10.\tCopy the file Tridion.TranslationManager.V2.TmService.dll from this hotfix to \"%TRIDION_CM_HOME%\\bin \" replacing the old version.\r\n\t11.\tTake a backup of the file %TRIDION_CM_HOME%\\web\\WebUI\\Editors\\TM\\Scripts\\Commands\\Translate.js and replace it with the version included in this hotfix.\r\n\t12.\tTake a backup of the file %TRIDION_CM_HOME%\\web\\WebUI\\Models\\TM\\Scripts\\Model\\TranslationJobCreationOptions.js and replace it with the version included in this hotfix.\r\n\t13.\tOpen %TRIDION_CM_HOME%web\\WebUI\\WebRoot\\Configuration\\System.config in a text editor.\r\n\t\tLocate the Configuration/servicemodel/server node in the System.config file and increase the value of its 'modification' attribute to notify client browsers to update their cache.\r\n\t14.\tRestart the Content Manager Explorer Web site.\r\n\t15.\tStart \"SDL Web Content Manager Service Host\" service and all dependent services.\r\n\t16.\tStart the SDL Web Translation Manager Service.\r\n\r\nDistributed files:\r\n\t- Tridion.TranslationManager.DomainModel.dll (File version: 8.5.0.240)\r\n\t- Tridion.TranslationManager.TcmExtension.dll (File version: 8.5.0.240)\r\n\t- Tridion.TranslationManager.UI.Model.dll (File version: 8.5.0.240)\r\n\t- Tridion.TranslationManager.UI.DataExtenders.dll (File version: 8.5.0.240)\r\n\t- Tridion.TranslationManager.V2.TmService.dll (File version: 8.5.0.240)\r\n\t- Translate.js\r\n\t- TranslationJobCreationOptions.js\r\n \t- Readme.txt (this file)\r\n\r\nFixes included:\r\n\tCRQ-3782\t\"The given key was not present in the dictionary.\" error when parsing XLiff document from TMS 11.1\r\n\t\t\t\tEnable intermediate retrieval of translation items from TMS\r\n\tCRQ-3875\tUI fails to load translation configuration or translation job if World Server workflow step have name that starts with 3-4 letter word. (e.g \"Set Asset Translation Status\")\r\n\tCRQ-4127\tTranslation manager slowdown publishing process\r\n\tCRQ-3832\tSlow performance opening Components in large BluePrints.\r\n\tCRQ-4544\tSlow performance in workflow related operations.\r\n\tCRQ-4997\tRetrieve from translation a bundle with an item that has already been translated and the parent item also has a minor version and get a DB error in TM DB.\r\n\tCRQ-5231\tItem resolve mechanism does not resolve container items by default.\r\n\tCRQ-8863\tAttempting to send a minor, reserved state version of a page to translate sends the last major version.\r\n\tCRQ-9170\tUI fails to send translation job if World Server workflow step have name that starts with 3-4 letter word.\r\n\tCRQ-9870\tUnable to retrieve aggregated items with a classic edit workflow defined.\r\n\tCRQ-10991\tTranslate popup takes around 1 minute to open.\r\n\tCRQ-11182\tTake too much time to open the translation job screen.\r\n\tCRQ-11520\tUnable to reconfigure failed translation configuration.\r\n\tCRQ-11627\tPRIMARY KEY constraint Error on TMSJOBS_ITEMS when shared item has circular links\r\n\tCRQ-12990\tEditors unable to use Translation Manager UI. When using Group Synchronization.\r\n\tCRQ-13992\tError seen in logs: \"Collection was modified; enumeration operation may not execute.\"\r\n\tCRQ-14590\tTranslation Manager - creates duplicate job in TMS when chunking translation job.\r\n\r\nDependencies:\r\n\tn.a.\r\n\r\nDisclaimer:\r\n\tHotfixes are released at the discretion of SDL based on technical complexity, customer business requirements and schedules.\r\n\tHotfixes are made and tested only for the described problem on a particular environment\\configuration and therefore should only be installed if approved by Customer Support of SDL Web Content Management Solutions Division.\r\n\tHotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright 2019 SDL PLC. All Rights Reserved. All company product or service names referenced herein are properties of their respective owners.\r\n",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2bb94436e1bc8257cda"
},
"hotfix_name": "CD_8.5.0.11891",
"modified_date": {
"$date": 1544461305737
},
"problem_description": "This is a hotfix for:\r\n- CRQ-11891 Deployment fails for scheduled publishing\r\n",
"readme_text": "Release Notes for Hotfix CRQ-11891\r\n==================================\r\n\r\nVersion:\r\n--------\r\nThis is cumulative hotfix and is intended for SDL Web 8.5.0\r\nThe hotfix includes the following fix: \r\n- CRQ-11891 Deployment fails for scheduled publishing\r\n\r\nDescription:\r\n------------\r\nThis is a hotfix for:\r\n- CRQ-11891 Deployment fails for scheduled publishing\r\n\r\nInstallation:\r\n-------------\r\nThis hotfix provides updated roles for Deployer Service (worker or combined depends on your installation).\r\n\r\nInstructions:\r\n-------------\r\n1. Stop SDL Web Deployer Service\r\n2. Backup (or move) a folder where your standalone Deployer Service is located\r\n3. Uninstall the SDL Web Deployer Service by opening a Powershell window in the \\bin of your service and run .\\uninstallService.ps1\r\n4. Navigate to the release\\deployer-combined or release\\deployer-worker folder of this distribution\r\n5. Copy \\standalone folder to the location where your original service was located\r\n6. Rename copied \\standalone folder to the name of your original service's folder\r\n7. Copy all files from \\config folder of your backup (see step #2) to \\config folder of a new service\r\n8. Copy custom jars (if you have any) from backup's \\services\\folder to a same location of a new service\r\n9. Install service by opening a Powershell window in in the location \\bin of new service and run .\\installService.ps1\r\n\r\n\r\nDistributed roles:\r\n------------------\r\nDeployer Service\r\n\r\n\r\nFixed problems:\r\n---------------\r\n- CRQ-11891 Deployment fails for scheduled publishing\r\n\r\nHotfix Description\r\n-------------------\r\n- Fixes deployment of scheduled publishing\r\n\r\nDisclaimer:\r\n-----------\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and \r\nschedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration \r\nand therefore should only be installed if approved by Customer Support. Hotfixes should be replaced as soon as \r\npossible by the subsequent patch release where the problem is fixed.\r\n\r\nCopyright 2016-2018 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL \r\nGroup.\r\n",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2b994436e1bc8257c8f"
},
"hotfix_name": "CD_8.1.1.2886",
"modified_date": {
"$date": 1480599421813
},
"problem_description": "- CRQ-2886 Service returns error when publishing packages.\r\n",
"readme_text": "Release Notes for Hotfix CRQ-2886\r\n=================================\r\n\r\nVersion:\r\n========\r\nThis is cumulative hotfix and is intended only for SDL Web 8.1.1\r\nThe hotfix include the following fixes: \r\n - CRQ-2886 Deployer still shows Request Entity Too Large with https after adding application.properties file\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n - CRQ-2886 Deployer still shows Request Entity Too Large with https after adding application.properties file\r\n\r\nInstallation:\r\n=============\r\n\r\nSDL Web Deployer Service:\r\n-----------------------\r\n1. Stop SDL Web Deployer Service.\r\n2. Backup (or move) a folder where your SDL Web Deployer Service is located.\r\n3. Uninstall the SDL Web Deployer Service by opening a Powershell window in the \\bin of your service and run .\\uninstallService.ps1.\r\n4. Navigate to the release\\deployer folder of this distributable\r\n5. Copy \\standalone folder to the location where your original service was located\r\n6. Rename copied \\standalone folder to the name of your original service's folder\r\n7. Navigate to \\config folder of your backup (see step #2) and remove application.properties file if exists. \r\n8. Copy all files from \\config folder of your backup to \\config folder of a new service.\r\n9. Copy custom jars(if you have any) from backup's \\services\\folder to a same location of a new service.\r\n10. Install service by opening a Powershell window in in the location \\bin of new service and run .\\installService.ps1\r\n\r\n\r\nDistributed files:\r\n==================\r\ndeployer/standalone - Deployer Service Standalone\r\ndeployer/webapp - Deployer Service Web Application\r\n\r\nDependencies:\r\n=============\r\n\r\n\r\nFixed problems:\r\n===============\r\n- CRQ-2886\tService returns error when publishing packages.\r\n\r\nProblem Description\r\n-------------------\r\n- CRQ-2886 Service returns error when publishing packages.\r\n\r\nHotfix Description\r\n-------------------\r\n- CRQ-2886 Fixed BinaryStorage size calculation.\r\n\r\nDisclaimer:\r\n===========\r\n\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/configuration and therefore should only be installed\r\nif approved by Customer Support. Hotfixes should be replaced as soon as possible by the subsequent patch release where the problem is fixed.\r\n\r\nCopyright 2015-2016 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.\r\n",
"version": "Web 8.1.1"
},
{
"_id": {
"$oid": "635fe2b594436e1bc8257c28"
},
"hotfix_name": "TM_9.1.0.21087",
"modified_date": {
"$date": 1601470235200
},
"problem_description": "Handle WorldServer HTTP 409 (Conflict) errors.\r\n",
"readme_text": "Release Notes for Hotfix CRQ-21087\r\n\r\nVersion: \r\n\tThis hotfix is intended for SDL Tridion Sites 9.1.\r\n\r\nProblem description:\r\n\tHandle WorldServer HTTP 409 (Conflict) errors.\r\n\r\nHotfix description:\r\n\tRetry tasks/complete call in case of HTTP 409 (Conflict) error.\r\n\r\nInstallation:\r\n\t1.\tStop the SDL Web Translation Manager Service\r\n\t2.\tStop \"SDL Web Content Manager Service Host\" service and all dependent services (SDL Web Content Manager Workflow Agent, SDL Web Content Manager Publisher, SDL Web Content Manager Batch Processor, SDL Web Content Manager Search Indexer)\r\n\t3.\tStop Content Manager Explorer Web site\r\n\t4.\tNavigate to the versioned Tridion.TranslationManager.DomainModel folder in your Global Assembly Cache (typically C:\\Windows\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.TranslationManager.DomainModel\\v4.0_9.1.0.0__360aac4d3354074b)\r\n\t5.\tTake a backup of the existing Tridion.TranslationManager.DomainModel.dll file.\r\n\t6.\tReplace the file with the version included in this hotfix.\r\n\t7.\tRestart the Content Manager Explorer Web site.\r\n\t8.\tStart \"SDL Web Content Manager Service Host\" service and all dependent services.\r\n\t9.\tStart the SDL Web Translation Manager Service.\r\n\r\nDistributed files:\r\n\t- Tridion.TranslationManager.DomainModel.dll (File version: 9.1.0.30)\r\n \t- Readme.txt (this file)\r\n\r\nFixes included:\r\n\tCRQ-17009:\tXLIFF parser does not support TMS comments.\r\n\tCRQ-14886:\t\"The item v0 does not exist\" error during publish on retrieve.\r\n\tCRQ-17149:\tUnable to retrieve translations if the TMS item has comments on it. The retrieval fails with the error 'unknown tag {urn:oasis:names:tc:xliff:document:1.2}mrk'.\r\n\tCRQ-18479:\tError \"Unable to determine if valid translation job can be created\" for non admin user.\r\n\t\r\n\t\r\nDependencies:\r\n\tn.a.\r\n\r\nDisclaimer:\r\n\tHotfixes are released at the discretion of SDL based on technical complexity, customer business requirements and schedules.\r\n\tHotfixes are made and tested only for the described problem on a particular environment\\configuration and therefore should only be installed if approved by Customer Support of SDL Web Content Management Solutions Division.\r\n\tHotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright 2020 SDL PLC. All Rights Reserved. All company product or service names referenced herein are properties of their respective owners.\r\n",
"version": "Sites 9.1"
},
{
"_id": {
"$oid": "635fe2ae94436e1bc8257aea"
},
"hotfix_name": "CM_2013.1.0.87500",
"modified_date": {
"$date": 1405694201176
},
"problem_description": "Cannot add an item to a bundle after workflow is started on bundle and the bundle is localized in a child.\r\n",
"readme_text": "Release Notes for Hotfix TT 87500\r\n\r\nVersion: \r\n\tThis hotfix is intended for SDL Tridion 2013 SP1.\r\n\r\nProblem description:\r\n\tCannot add an item to a bundle after workflow is started on bundle and the bundle is localized in a child.\r\n\r\nHotfix description:\r\n\tCannot add an item to a bundle after workflow is started on bundle and the bundle is localized in a child\r\n\r\n\t1. Create a bundle in parent publication.\r\n\t2. Add an existing or new item to the bundle.\r\n\t3. Localize the bundle in a child publication.\r\n\t4. Start workflow on the bundle in the parent publication.\r\n\t5. Try to add a new or existing item to the bundle while workflow is started. It does not work. You get the error:\r\n\r\n\tThe item tcm:0-20789-64 does not exist.\r\n\r\n\r\nInstallation:\r\n \t1. Stop all TCM Services, IIS Service, and the TCM COM+ Application.\r\n 2. Replace assembly in the folder %GACDIR%\\GAC_MSIL\\Tridion.ContentManager\\v4.0_7.1.0.1290__360aac4d3354074b with assembly Tridion.ContentManager.dll provided with this hotfix (%GACDIR% can refer to %WINDIR%\\assembly or %WINDIR%\\Microsoft.Net\\assembly)\r\n \t3. Restart the IIS Service, TCM Services and TCM COM+ Application.\r\n\r\nDistributed files:\r\n \tTridion.ContentManager.dll (File Version 7.1.0.1297)\r\n \tReadme.txt (this file)\r\n\r\nFixes included:\r\n\tTT87411\r\n\r\nDependencies:\r\n\tn.a.\r\n\r\nDisclaimer:\r\n\tHotfixes are released at the discretion of SDL based on technical complexity, customer business requirements and schedules.\r\n\tHotfixes are made and tested only for the described problem on a particular environment\\configuration and therefore should only be installed if approved by Customer Support of SDL Web Content Management Solutions Division.\r\n\tHotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright 2014 SDL PLC. All Rights Reserved. All company product or service names referenced herein are properties of their respective owners.\r\n",
"version": "2013 SP1"
},
{
"_id": {
"$oid": "635fe2af94436e1bc8257b54"
},
"hotfix_name": "CM_2013.1.1.2014",
"modified_date": {
"$date": 1464969678258
},
"problem_description": "Blueprint restructuring skips duplicate category xml name conflict.\r\n",
"readme_text": "Release Notes for CRQ-2016\r\n\r\nVersion:\r\nThis hotfix is intended only for SDL Tridion Content Manager 2013 SP1 HR1.\r\n\r\nProblem description:\r\nBlueprint restructuring skips duplicate category xml name conflict.\r\n\r\nHotfix description:\r\nThis hotfix adds an additional check for category xml names during Blueprint restructuring.\r\n\r\n\r\nInstallation:\r\n 1. Stop all TCM Services, IIS Service, and the TCM COM+ Application.\r\n\r\n\t\tDatabase actions:\r\n\t\t 1. Using Query Analyzer, osql, sqlcmd or SQL Server Management Studio, log in to the SDL Tridion database using 'sa'.\r\n\t\t 2. Execute the SQL file EDA_PUBLICATIONS.sql\r\n 2. Replace assembly in the folder %WINDIR%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.ContentManager\\v4.0_7.1.0.1290__360aac4d3354074b with assembly Tridion.ContentManager.dll provided with this hotfix\r\n 3. Replace assembly in the folder %WINDIR%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.ContentManager.Localization\\v4.0_7.1.0.1290__360aac4d3354074b with assembly Tridion.ContentManager.Localization.dll provided with this hotfix\r\n 4. Restart the IIS Service, TCM Services and TCM COM+ Application.\r\n\r\nDistributed files:\r\n EDA_PUBLICATIONS.sql\r\n Tridion.ContentManager.dll (File version: 1428)\r\n Tridion.ContentManager.Localization.dll (File version: 1428)\r\n Readme.txt (this file)\r\n\r\n\r\nFixes included:\r\n CM_2013.1.1.1929\r\n CM_2013.1.1.88313\r\n CM_2013.1.1.88790\r\n CM_2013.1.1.88798\r\n CM_2013.1.1.1619\r\n\r\nDependencies:\r\n 2013 SP1 HR1\r\n CM_2013.1.1.88554\r\n CM_2013.1.1.716\r\n\r\n\r\nDisclaimer:\r\n\tHotfixes are released at the discretion of SDL based on technical complexity, customer business requirements and schedules.\r\n\tHotfixes are made and tested only for the described problem on a particular environment\\configuration and therefore should only be installed if approved by Customer Support of SDL Web Content Management Solutions Division.\r\n\tHotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright 2016 SDL PLC. All Rights Reserved. All company product or service names referenced herein are properties of their respective owners.\r\n",
"version": "2013 SP1 HR#1"
},
{
"_id": {
"$oid": "635fe2c094436e1bc8257da5"
},
"hotfix_name": "TM_8.5.0.5231",
"modified_date": {
"$date": 1498225330570
},
"problem_description": "Item resolve mechanism does not resolve container items by default.\r\n",
"readme_text": "Release Notes for Hotfix CRQ-5231\r\n\r\nVersion: \r\n\tThis hotfix is intended for SDL Web 8.5.\r\n\r\nProblem description:\r\n\tItem resolve mechanism does not resolve container items by default.\r\n\r\nHotfix description:\r\n\tFix resolving mechanism.\r\n\r\nInstallation:\r\n\t1.\tStop the SDL Web Translation Manager Service\r\n\t2.\tStop \"SDL Web Content Manager Service Host\" service and all dependent services\r\n\t3.\tStop Content Manager Explorer Web site\r\n\t4.\tNavigate to the versioned Tridion.TranslationManager.DomainModel folder in your Global Assembly Cache (typically C:\\Windows\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.TranslationManager.DomainModel\\v4.0_8.5.0.146__360aac4d3354074b)\r\n\t5.\tTake a backup of the existing Tridion.TranslationManager.DomainModel.dll file.\r\n\t6.\tReplace the file with the version included in this hotfix.\r\n\t7.\tCopy the file Tridion.TranslationManager.TcmExtension.dll from this hotfix to \"%Tridion%\\Translation Manager\" replacing the old version.\r\n\t8.\tCopy the file Tridion.TranslationManager.UI.Model.dll from this hotfix to \"%Tridion%\\web\\WebUI\\WebRoot\\bin \" replacing the old version.\r\n\t9.\tTake a backup of the file %Tridion%\\web\\WebUI\\Editors\\TM\\Scripts\\Commands\\Translate.js and replace it with the version included in this hotfix.\r\n\t10.\tTake a backup of the file %Tridion%\\web\\WebUI\\Models\\TM\\Scripts\\Model\\TranslationJobCreationOptions.js and replace it with the version included in this hotfix.\r\n\t11.\tOpen %TRIDION_CM_HOME%web\\WebUI\\WebRoot\\Configuration\\System.config in a text editor.\r\n\t\tLocate the Configuration/servicemodel/server node in the System.config file and increase the value of its 'modification' attribute to notify client browsers to update their cache.\r\n\t12.\tRestart the Content Manager Explorer Web site.\r\n\t13.\tStart \"SDL Web Content Manager Service Host\" service and all dependent services.\r\n\t14.\tStart the SDL Web Translation Manager Service.\r\n\r\nDistributed files:\r\n\t- Tridion.TranslationManager.DomainModel.dll (File version: 8.5.0.173)\r\n\t- Tridion.TranslationManager.TcmExtension.dll (File version: 8.5.0.173)\r\n\t- Tridion.TranslationManager.UI.Model.dll (File version: 8.5.0.173)\r\n\t- Translate.js\r\n\t- TranslationJobCreationOptions.js\r\n \t- Readme.txt (this file)\r\n\r\nFixes included:\r\n\tCRQ-3782\t\"The given key was not present in the dictionary.\" error when parsing XLiff document from TMS 11.1\r\n\t\t\t\tEnable intermediate retrieval of translation items from TMS\r\n\tCRQ-3875\tUI fails to load translation configuration or translation job if World Server workflow step have name that starts with 3-4 letter word. (e.g \"Set Asset Translation Status\")\r\n\tCRQ-4127\tTranslation manager slowdown publishing process\r\n\tCRQ-3832\tSlow performance opening Components in large BluePrints.\r\n\tCRQ-4544\tSlow performance in workflow related operations.\r\n\tCRQ-4997\tRetrieve from translation a bundle with an item that has already been translated and the parent item also has a minor version and get a DB error in TM DB.\r\n\r\nDependencies:\r\n\tn.a.\r\n\r\nDisclaimer:\r\n\tHotfixes are released at the discretion of SDL based on technical complexity, customer business requirements and schedules.\r\n\tHotfixes are made and tested only for the described problem on a particular environment\\configuration and therefore should only be installed if approved by Customer Support of SDL Web Content Management Solutions Division.\r\n\tHotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright 2017 SDL PLC. All Rights Reserved. All company product or service names referenced herein are properties of their respective owners.\r\n",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2bf94436e1bc8257d70"
},
"hotfix_name": "CM_8.5.0.5889",
"modified_date": {
"$date": 1502465575588
},
"problem_description": "Indexing components with PDF files fails with error \"The operation has timed out\".\r\n",
"readme_text": "Release Notes for Hotfix CRQ-5889\r\n\r\nVersion:\r\n\tThis hotfix is intended only for SDL Web 8.5.\r\n\r\nProblem description:\r\n\tIndexing components with PDF files fails with error \"The operation has timed out\".\r\n\r\nHotfix description:\r\n\tThe hotfix upgrades fontbox library to version 1.8.12.\r\n\r\nInstallation:\r\n\t1. Stop \"SDL Web Content Manager Search Host\" Service.\r\n\t2. Create backup of %TRIDION_HOME%\\solr-home\\lib folder.\r\n\t3. Copy fontbox-1.8.12.jar into the %TRIDION_HOME%\\solr-home\\lib folder.\r\n\t4. Remove %TRIDION_HOME%\\solr-home\\lib\\fontbox.jar (as new 1.8.12 version of jar was just installed).\r\n\t5. Start \"SDL Web Content Manager Search Host\" Service.\r\n\r\nDistributed files:\r\n\tfontbox-1.8.12.jar\r\n\tReadme.txt (this file)\r\n \r\nFixes included:\r\n\tNA\r\n\r\nDependencies:\r\n\tNA\r\n\r\nDisclaimer:\r\n\tHotfixes are released at the discretion of SDL based on technical complexity, customer business requirements and schedules.\r\n\tHotfixes are made and tested only for the described problem on a particular environment\\configuration and therefore should only be installed if approved by Customer Support of SDL Web Content Management Solutions Division.\r\n\tHotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright 2017 SDL PLC. All Rights Reserved. All company product or service names referenced herein are properties of their respective owners.\r\n",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2ba94436e1bc8257cb4"
},
"hotfix_name": "CME_8.1.1.9491",
"modified_date": {
"$date": 1522757498512
},
"problem_description": "View on Site feature does not work on Chrome\r\n",
"readme_text": "Release Notes for Hotfix CRQ-9491\r\n\r\nVersion:\r\nThis hotfix is intended for SDL Web 8.1.1\r\n\r\nProblem description: \r\nView on Site feature does not work on Chrome\r\n\r\nHotfix description:\r\nThere was no required dependent resource configured for knockout.binding.handlers.js file. \r\nIt was still sometimes working due to the side effect of other resources configurations.\r\nBack-ported the changes from 8.2 version since it already has a fix.\r\n\r\nInstallation:\r\n\r\n\t1. Move or delete the _Config.xml file from the folder %TRIDION_HOME%\\web\\WebUI\\Editors\\Base\\Libraries\r\n\t2. Copy _Config.xml file from this hotfix to the folder %TRIDION_HOME%\\web\\WebUI\\Editors\\Base\\Libraries\r\n\t3. Recycle the application pool or restart your IIS service\r\n\r\nDistributed files:\r\n- Readme.txt (this file)\r\n- _Config.xml\r\n\r\nFixes included:\r\n-\r\n\r\nDependencies:\r\n-\r\n\r\nDisclaimer:\r\nHotfixes are released at the discretion of SDL based on technical complexity, customer business requirements and schedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by Customer Support of SDL Web Content Management Solutions Division. Hotfixes should be replaced as soon as possible by the subsequent patch release where the problem is fixed.\r\nCopyright \ufffd 2018 SDL PLC. All Rights Reserved. All company product or service names referenced herein are properties of their respective owners. ",
"version": "Web 8.1.1"
},
{
"_id": {
"$oid": "635fe2b794436e1bc8257c4b"
},
"hotfix_name": "CME_9.5.0.26650",
"modified_date": {
"$date": 1636073158000
},
"problem_description": "Under Load balancer login to CME with AccessManagement redirects to http instead of https\r\n",
"readme_text": "Release Notes for Hotfix CRQ-26650\r\n\r\nVersion:\r\nThis hotfix is intended for SDL Web 9.5\r\n\r\nProblem description: \r\nUnder Load balancer login to CME with AccessManagement redirects to http instead of https\r\n\r\nHotfix description:\r\nProcessing the request's \"X-Forwarded-Proto\" header if it is forwarded from the load balancer.\r\n\r\nInstallation:\r\n\t1. Backup files Tridion.Web.UI.Core.dll from %TRIDION_HOME%\\web\\WebUI\\WebRoot\\bin folder.\r\n\t2. Replace files Tridion.Web.UI.Core.dll in %TRIDION_HOME%\\web\\WebUI\\WebRoot\\bin folder with file from this hotfix. If any extesnions or services uses Tridion.Web.UI.Core.dll, please check and replace as well.\r\n\t3. Recycle the application pool or restart your IIS service.\r\n\r\nDistributed files:\r\n- Readme.txt (this file)\r\n- Tridion.Web.UI.Core.dll (File Version 9.5.0.5824/Assembly version 9.5.0.0)\r\n\r\nDependencies:\r\nn/a\r\n\r\nIncludes:\r\nCME_9.5.0.24498\r\nCME_9.5.0.25218\r\nCME_9.5.0.26252\r\n\r\nDisclaimer:\r\nHotfixes (as defined under the relevant RWS product release policy) are released at RWS\u2019s discretion based on technical complexity, customer business requirements and schedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration in accordance with the Software Documentation and therefore should only be installed if approved by RWS Technical Support. Hotfixes should be replaced as soon as possible by the subsequent cumulative update where the problem is fixed.\r\n\r\nCopyright \u00a9 2021 All Rights Reserved by the RWS Group for and on behalf of its affiliates and subsidiaries. All company product or service names referenced herein are properties of their respective owners.",
"version": "Sites 9.5"
},
{
"_id": {
"$oid": "635fe2b594436e1bc8257c40"
},
"hotfix_name": "CD_11.5.0.22824",
"modified_date": {
"$date": 1612775770534
},
"problem_description": "- ComponentPresentationAssembler not render content correctly as like in web8.5\r\n",
"readme_text": "\ufeffRelease Notes for Hotfix CRQ-22824\r\n==================================\r\n\r\n\r\nVersion\r\n=======\r\nThis cumulative hotfix is intended only for SDL Sites 9.5 customers.\r\n\r\n\r\nDescription\r\n===========\r\nThis is a hotfix for:\r\n - CRQ-22824 ComponentPresentationAssembler not render content correctly as like in web8.5\r\n\r\n\r\nInstallation\r\n============\r\nThis hotfix involves a change to one of the JARs, that is used in multple services.\r\n\r\n\r\nServices\r\n--------\r\n1. Ensure relevant Service is stopped\r\n2. Backup (or move) a folder where your standalone Service is located\r\n3. Uninstall the relevant Service by opening a Power-shell window in the \\bin of your service and run .\\uninstallService.ps1\r\n4. Navigate to the release\\ folder of this distribution\r\n5. Copy \\standalone folder to the location where your original service was located\r\n6. Rename copied \\standalone folder to the name of your original service's folder\r\n7. Copy all files from \\config folder of your backup (see step #2) to \\config folder of a new service\r\n8. Copy custom jars (if you have any) from backup's \\services\\folder to a same location of a new service\r\n9. Re-install service by opening a Powershell window in in the location \\bin of new service and run .\\installService.ps1\r\n\r\nAdd-ons\r\n-------\r\nIt is recommended that customers using our default add-ons use the versions provided in this hotfix (contained within the /add-ons folders). \r\n\r\nDistributed roles\r\n=================\r\ncontent Content Service role\r\nsession Session service role\r\n\r\nFixed problems\r\n==============\r\n\r\nProblem Description\r\n-------------------\r\n - ComponentPresentationAssembler not render content correctly as like in web8.5\r\n\r\nHotfix Description\r\n-------------------\r\n- Did changes on CIS so ComponentPresentationAssembler renders content the same way as it was in web8.5 regardless if we setup pageId for ComponentPresentationAssembler or not.\r\n\r\n\r\nDisclaimer\r\n==========\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. \r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore \r\nshould only be installed if approved by Customer Support. Hotfixes should be replaced as soon as possible by the \r\nsubsequent patch release where the problem is fixed.\r\n\r\nCopyright \ufffd 2015-2021 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.\r\n",
"version": "Sites 9.5"
},
{
"_id": {
"$oid": "635fe2c094436e1bc8257d7f"
},
"hotfix_name": "CM_CME_8.5.0.9968",
"modified_date": {
"$date": 1526057064293
},
"problem_description": "Loading \"Create a new Site\" very slow with 200 websites.\r\n",
"readme_text": "Release Notes for Hotfix CRQ-9968\r\n\r\nVersion:\r\n\tThis hotfix is intended for SDL Web 8.5\r\n\r\nProblem description:\r\n\tLoading \"Create a new Site\" very slow with 200 websites.\r\n\r\nHotfix description:\r\n\tFix correct 2 places:\r\n\t\tGetWebApplicationsForEnvironments \r\n\t\tGetScopedTopologyItems\r\n\tAdded ToList() method to not invoke topology manager methods only once - not in a loop.\r\n\r\nInstallation:\r\n 1. Stop all TCM Services, IIS Service, and the TCM COM+ Application.\r\n 2. Remove the file Tridion.TopologyManager.dll located in the %windir%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.TopologyManager\\v4.0_8.5.0.466__ddfc895746e5ee6b folder.\r\n 3. Copy the file Tridion.TopologyManager.dll from this hotfix to the %windir%\\Microsoft.NET\\assembly\\GAC_MSIL\\Tridion.TopologyManager\\v4.0_8.5.0.466__ddfc895746e5ee6b folder.\r\n 4. Remove the file Tridion.Web.UI.Models.TTM.dll located in the %TRIDION_HOME%\\web\\WebUI\\WebRoot\\bin folder.\r\n 5. Copy the file Tridion.Web.UI.Models.TTM.dll from this hotfix to the %TRIDION_HOME%\\web\\WebUI\\WebRoot\\bin folder.\r\n 6. Restart the IIS Service, TCM Services and TCM COM+ Application.\r\n\r\nDistributed files:\r\n Tridion.TopologyManager.dll (Assembly version 8.5.0.466, Product version 8.5.0.505, File version 8.5.0.505)\r\n Tridion.Web.UI.Models.TTM.dll (Assembly version 8.5.0.22656, Product version 8.5.0.22656, File version 8.5.0.56969)\r\n Readme.txt (this file)\r\n \r\nFixes included:\r\n NA\r\n\r\nDependencies:\r\n NA\r\n\r\nDisclaimer:\r\n\tHotfixes are released at the discretion of SDL based on technical complexity, customer business requirements and schedules.\r\n\tHotfixes are made and tested only for the described problem on a particular environment\\configuration and therefore should only be installed if approved by Customer Support of SDL Web Content Management Solutions Division.\r\n\tHotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright 2018 SDL PLC. All Rights Reserved. All company product or service names referenced herein are properties of their respective owners.\r\n",
"version": "Web 8.5"
},
{
"_id": {
"$oid": "635fe2b394436e1bc8257bee"
},
"hotfix_name": "CME_9.1.0.16804",
"modified_date": {
"$date": 1573196476913
},
"problem_description": "XSS vulnerability via \"url\" query parameter.\r\n",
"readme_text": "Release Notes for Hotfix CRQ-16804\r\n\r\nVersion:\r\nThis hotfix is intended for SDL Web 9.1\r\n\r\nProblem description: \r\nXSS vulnerability via \"url\" query parameter.\r\n\r\nHotfix description:\r\nDom-Based Cross-Site Scripting.\r\nCross Site Scripting (XSS) vulnerabilities occur when data submitted to the application is not\r\nproperly handled before being embedded within the application's response or stored for later retrieval.\r\nExample URL:\r\nhttps://localhost/SDL/#app=wcm&entry=cme&url=javascript:alert(\"hi\")\r\n\r\nInstallation:\r\n\t1. Create a backup of %TRIDION_HOME%\\web\\SDL\\Common\\ApplicationHost\\configuration.xml\r\n\t2. Copy the configuration.xml file from this hotfix to %TRIDION_HOME%\\web\\SDL\\Common\\ApplicationHost\\\r\n\t3. Create a backup of %TRIDION_HOME%\\web\\SDL\\Common\\ApplicationHost\\Packages\\SDL.Client.UI.ApplicationHost.txt\r\n\t4. Copy the SDL.Client.UI.ApplicationHost.txt file from this hotfix to %TRIDION_HOME%\\web\\SDL\\Common\\ApplicationHost\\Packages\\\r\n\t5. Create a backup of %TRIDION_HOME%\\web\\SDL\\Common\\ApplicationHost\\version.txt\r\n\t6. Copy the version.txt file from this hotfix to %TRIDION_HOME%\\web\\SDL\\Common\\ApplicationHost\\\r\n\t7. Restart IIS\r\n\r\nDistributed files:\r\n- Readme.txt (this file)\r\n- configuration.xml\r\n- SDL.Client.UI.ApplicationHost.txt\r\n- version.txt\r\n\r\nFixes included:\r\nn/a\r\n\r\nDependencies:\r\nn/a\r\n\r\nDisclaimer:\r\nHotfixes are released at the discretion of SDL based on technical complexity, customer business requirements and schedules. Hotfixes are made and tested only for the described problem on a particular environment/configuration and therefore should only be installed if approved by Customer Support of SDL Web Content Management Solutions Division. Hotfixes should be replaced as soon as possible by the subsequent patch release where the problem is fixed.\r\nCopyright 2019 SDL PLC. All Rights Reserved. All company product or service names referenced herein are properties of their respective owners. ",
"version": "Sites 9.1"
},
{
"_id": {
"$oid": "635fe2ae94436e1bc8257b16"
},
"hotfix_name": "CD_2013.1.1.147",
"modified_date": {
"$date": 1435753271694
},
"problem_description": "Deploying metadata to the file system is extremely slow due to large number of 'listFiles' calls\r\n(SRQ-3065) Deadlock and javax.persistence.OptimisticLockException apparently on metadata leading to a failed transaction\r\n(SRQ-3583) Publishing Linked component within Keywords Metadata causing errors\r\n(SRQ-3575) Continued failed transactions during load publishing: \"javax.persistence.OptimisticLockException\"\r\n",
"readme_text": "Release Notes for Hotfix CRQ-147\r\n================================\r\n\r\nVersion:\r\n========\r\nThis is cumulative hotfix and is intended only for Tridion 2013 SP1 HR1\r\nThe hotfix include the following fixes:\r\n - TT88564 Deploying metadata to the file system is extremely slow due to large number of 'listFiles' calls\r\n - TT88660 (SRQ-3065) Deadlock and javax.persistence.OptimisticLockException apparently on metadata leading to a failed transaction\r\n - CRQ-145 (SRQ-3583) Publishing Linked component within Keywords Metadata causing errors\r\n\r\nDescription:\r\n============\r\nThis is a hotfix for:\r\n- CRQ-147 (SRQ-3575) Continued failed transactions during load publishing: \"javax.persistence.OptimisticLockException\"\r\n\r\nInstallation:\r\n=============\r\n\r\nTridion CD environment:\r\n-----------------------\r\n1. Stop any Tridion CD processes.\r\n2. Replace the existing cd_datalayer.jar in your environment with the new cd_datalayer.jar delivered by this hotfix.\r\n3. Restart any Tridion CD processes.\r\n\r\nJava web application using Tridion CD dynamic content:\r\n------------------------------------------------------\r\n1. Replace the original Tridion 2013 SP1 cd_datalayer.jar in the WEB-INF/lib directory of your web application with the new cd_datalayer.jar delivered by this hotfix.\r\n\r\n\r\nDistributed files:\r\n==================\r\ncd_datalayer.jar\r\n\r\nDependencies:\r\n=============\r\nSDL Tridion 2013 SP1 HR1\r\n\r\n\r\nFixed problems:\r\n===============\r\nTT88564\r\nProblem Description\r\n-------------------\r\nDeploying metadata to the file system is extremely slow due to large number of 'listFiles' calls\r\n\r\nHotfix Description\r\n-------------------\r\nDeployer is hanging due to large componentpresentionmeta folder - this is an optimization improvement which should speed up the deployer iteration over these files. \r\n\r\n\r\nTT88660\r\nProblem Description\r\n-------------------\r\n(SRQ-3065) Deadlock and javax.persistence.OptimisticLockException apparently on metadata leading to a failed transaction\r\n\r\nHotfix Description\r\n-------------------\r\n(SRQ-3065) Deadlock and javax.persistence.OptimisticLockException apparently on metadata leading to a failed transaction\"\r\nSee SRQ-3065 (https://jira.sdl.com/browse/SRQ-3065).\r\nDeadlock and javax.persistence.OptimisticLockException apparently on metadata leading to a failed transaction.\r\nThere will be a deadlock as such:\r\n2015-03-02 15:02:14,840 DEBUG SqlExceptionHelper - ORA-00060: deadlock detected while waiting for resource\r\n[n/a]\r\njava.sql.SQLException: ORA-00060: deadlock detected while waiting for resource\r\n\r\n\r\nCRQ-145\r\nProblem Description\r\n-------------------\r\n(SRQ-3583) Publishing Linked component within Keywords Metadata causing errors\r\n\r\nHotfix Description\r\n-------------------\r\nProperly strip out the namespace from xml attributes name.\r\n\r\n\r\nCRQ-147\r\nProblem Description\r\n-------------------\r\n(SRQ-3575) Continued failed transactions during load publishing: \"javax.persistence.OptimisticLockException\"\r\n\r\nHotfix Description\r\n-------------------\r\nIntermittent failed transactions on the deployer during mild load with \"javax.persistence.OptimisticLockException: org.hibernate.StaleStateException: Batch update returned unexpected row count from update [0]; actual row count: 0; expected: 1\"\r\n\r\nDisclaimer:\r\n===========\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. Hotfixes are made\r\nand tested only for the described problem on a particular environment/configuration and therefore should only be installed\r\nif approved by Customer Support. Hotfixes should be replaced as soon as possible by the subsequent service pack where the problem is fixed.\r\n\r\nCopyright 2015 SDL PLC for and on behalf of subsidiaries and affiliates. All Rights Reserved. All company product or service names referenced herein are properties of their respective owners.\r\n",
"version": "2013 SP1 HR#1"
},
{
"_id": {
"$oid": "635fe2b294436e1bc8257be7"
},
"hotfix_name": "CD_11.1.0.19562",
"modified_date": {
"$date": 1602250200315
},
"problem_description": "- Violation of primary keys\r\n- Inefficient caching\r\n- Sorting in GraphQL by custom metadata field values issues\r\n- GraphQL paged queries can be slow in some situations\r\n- JSON format for BinaryContent different to previous version\r\n- Slow GraphQL query filtering on Custom Meta\r\n",
"readme_text": "\ufeffRelease Notes for Hotfix CRQ-19562\r\n==================================\r\n\r\n\r\nVersion\r\n=======\r\nThis cumulative hotfix is intended only for SDL Sites 9.1 customers.\r\n\r\n\r\nDescription\r\n===========\r\nThis is a hotfix for:\r\n - CRQ-19562 - Implement surrogate keys (11.1)\r\n - CRQ-16907 - Violation of PRIMARY KEY constraint 'PK_ITEMS'. Cannot insert duplicate key in object 'dbo.ITEMS'. The duplicate key value is (1, 34472, 438)\r\n - CRQ-14973 - Unable to sort on custom metadata field values in GraphQL \r\n - CRQ-20949 - PCA GraphQL call takes too much time\r\n - CRQ-20998 - When retrieving BinaryContents in JSON format, the response is different between web 8.1 and tridion 9.1\r\n - CRQ-21415 - Slow CIS query on SK 11.1\r\n\r\n\r\nInstallation\r\n============\r\nThis hotfix involves a change to the database schema. New columns have been added to some tables, together with some updated indexes and constraints.\r\nThis hotfix should be applied as follows.\r\n\r\nDatabase\r\n--------\r\n1. Stop existing services. In particular any service that may write to the database (i.e. Deployer, Session and Preview).\r\n2. Make a back up your database(s). If you use separate databases for Session, Discovery and Broker, you should back each up individually.\r\n3. Open Windows PowerShell from the Windows Start Menu.\r\n4. In PowerShell, depending on your database navigate to one of the following folders on the installation media:\r\n For a Microsoft SQL Server, navigate to db\\mssql\\\r\n For an Oracle database, navigate to db\\oracle\\\r\n5. Type the following command to upgrade your Content Data Store:\r\n & '.\\Upgrade Content Data Store.ps1' \r\n6. Follow the instructions in the PowerShell console to upgrade the database.\r\n7. Wait for the database upgrade to be completed. This may take a few hours on a large database.\r\n8. Repeat for other databases that you are upgrading.\r\n\r\nFurther information about database upgrade is described here:\r\nhttps://docs.sdl.com/LiveContent/content/en-US/SDL%20Tridion%20Sites-v2/GUID-ADCB5392-91B3-4F56-9E59-548E52885DFA\r\n\r\nServices\r\n--------\r\n1. Ensure relevant Service is stopped\r\n2. Backup (or move) a folder where your standalone Service is located\r\n3. Uninstall the relevant Service by opening a Power-shell window in the \\bin of your service and run .\\uninstallService.ps1\r\n4. Navigate to the release\\ folder of this distribution\r\n5. Copy \\standalone folder to the location where your original service was located\r\n6. Rename copied \\standalone folder to the name of your original service's folder\r\n7. Copy all files from \\config folder of your backup (see step #2) to \\config folder of a new service\r\n8. Copy custom jars (if you have any) from backup's \\services\\folder to a same location of a new service\r\n9. Re-install service by opening a Powershell window in in the location \\bin of new service and run .\\installService.ps1\r\n\r\nAdd-ons\r\n-------\r\nIt is essential that customers using our default add-ons use the versions provided in this hotfix (contained within the /add-ons folders). \r\n\r\nLive upgrade\r\n------------\r\nAlternatively, if you wish to upgrade a running instance with minimal downtime, the recommended procedure is:\r\n1. Create a duplicate database of the live database(s)\r\n2. Upgrade each database as described above\r\n3. Create new copies of the services, as described above\r\n4. Point the new services to the new database endpoint(s)\r\n5. Stop the old services\r\n6. Start the new services\r\n7. Remove the original services and database(s) once you have confirmed that the new services are working correctly\r\n\r\nRollback\r\n--------\r\nIf you experience problems following the update, follow this procedure to rollback:\r\n1. Stop services\r\n2. Restore original database(s)\r\n3. Restore original services\r\n4. Restart services\r\n\r\nModified JARs\r\n-------------\r\nPart of this hotfix involved changes to our standard JARS.\r\n\r\nThe following JARs have been removed in this hotfix (where xxxx is a 4 digit build number):\r\n- udp-model.11.1.0-xxxx.jar\r\n\r\nThe following JARs are new in this hotfix:\r\n- udp-storage-api-11.1.0-xxxx.jar\r\n- udp-data-model-compatible-11.1.0-xxxx.jar\r\n- udp-data-legacy-transport-11.1.0-xxxx.jar\r\n\r\nCustomers building extensions against our services will need to include the new JARs in order to run the extensions.\r\n\r\n\r\nDistributed roles\r\n=================\r\napi Content Delivery API role\r\ncid Contextual Image Delivery role\r\ncontext Context Service role\r\ncontent Content Service role\r\ndeployer Deployer role\r\ndiscovery Discovery service role\r\npreview Preview service role\r\nsession Session service role\r\nugc/community-service UGC Community Service role\r\nugc/moderation-service UGC Moderation Service role\r\nxo\t\t \t\t\t\t XO role\r\n\r\n\r\nFixed problems\r\n==============\r\n\r\nProblem Description\r\n-------------------\r\n - Violation of primary keys\r\n - Inefficient caching\r\n - Sorting in GraphQL by custom metadata field values issues\r\n - GraphQL paged queries can be slow in some situations\r\n - JSON format for BinaryContent different to previous version\r\n - Slow GraphQL query filtering on Custom Meta\r\n\r\nHotfix Description\r\n-------------------\r\n- Introduced surrogate keys support\r\n- Improved queries for using for efficient indexes\r\n- Fixed sorting issue in GraphQL API\r\n- Fixed caching issues\r\n- Resolved performance issue with GraphQL paged queries\r\n- Aligned JSON format of BinaryContent\r\n- Fixed query performance with GraphQL filtering on Custom Meta\r\n\r\n\r\nDisclaimer\r\n==========\r\nHotfixes are released at our discretion based on technical complexity, customer business requirements and schedules. \r\nHotfixes are made and tested only for the described problem on a particular environment/configuration and therefore \r\nshould only be installed if approved by Customer Support. Hotfixes should be replaced as soon as possible by the \r\nsubsequent patch release where the problem is fixed.\r\n\r\nCopyright \ufffd 2015-2020 SDL Group. All Rights Reserved.\r\n \r\nNothing contained herein may be reproduced, copied, modified or adapted, without the prior written consent of SDL Group.\r\n",
"version": "Sites 9.1"
}
]
}