Known issues in Content Manager
The following are known issues in Content Manager.
Web/App/DB Servers
- After you have applied Update 1 to Tridion Docs 15.1, you must remove the parameter
DatabaseUserswith the Access Management database upgrade script for Microsoft SQL Server, Upgrade Access Management database.ps1, which is located in the Database\InfoShareAM\MSSQL\. - The
IshReplaceTitlePI insideGlossaryEntryis not replaced when creating a new object. - Limitation: the maximum
PublicationOutputstorage size for PDFs and ZIPs in the database is limited to 2GB. - Renaming languages in settings area will not adapt
@xml:langand language combinations. Avoid changing the label of a language (for example, from en to EN or en-us) when it is in use, because the following problems can occur [TS-6472]:- When changing the label of the language, the existing files in that language are not automatically adapted, and therefore become invalid. This happens because the
@xml:langattribute and the processing-instruction no longer match the label of the language. In this case, you have to resubmit each file. - The publication outputs that have a language combination containing the modified language become invalid and must be recreated.
- When changing the label of the language, the existing files in that language are not automatically adapted, and therefore become invalid. This happens because the
- The Trisoft InfoShare Crawler service is responsible, among other things, for keeping the full-text index up-to-date. The service submits updated content to the full-text index, and it deletes outdated records from the full-text index, as well as from the database. At least one instance of the Trisoft InfoShare Crawler service should always be running to avoid issues with deleted objects. If the Trisoft InfoShare Crawler service is not running or if it lags, removing and then adding again the same language to an illustration with multiple languages can throw the following exception: Violation of PRIMARY KEY constraint 'ISH_CONTENTOBJECT_PK'. Cannot insert duplicate key in object 'dbo.ISH_CONTENTOBJECT'.... This issue may occur when the service has already deleted the language record from the full-text index, but it has not performed the same operation on the corresponding database record yet. [TS-9089]
- Remember, some of the content in the full-text index are labels from list of values (e.g. status,...) or referenced objects (e.g. users, EDTs, ...) which are used as metadata on the objects. Whenever the labels of those objects (e.g. users) or list of values (e.g. status,...) are changed, a reindex of the full-text index should be triggered manually, otherwise the full-text index will not find objects using the new label. In order to trigger a full reindex you should stop the Trisoft InfoShare Crawler service, run the
ISHDeploycmdlet invocationInvoke-ISHFullTextIndexMaintenance -ReIndexand restart the Trisoft InfoShare Crawler service.
API usage
- API read functions like
PublicationOutput25.RetrieveMetadatacan handle element name retrieval for controlled fields through the@ishvaluetypeattribute. TheCTPUBLICATIONOUTPUTfieldFISHPUBLNGCOMBINATIONis a special field, that is linked to theDLANGUAGEfield on the application level, while most other fields are linked in the database. So you cannot retrieve something like VLANGUAGEEN+VLANGUAGENL+VLANGUAGEFR, you will get the label "en+nl+fr" and you'll have to parse it yourself if required. [TS-10382] - API write functions like
DocumentObj25.SetMetadatawill save an incoming entry likeEUR, AFR, EUR, ASA, EUR, EURto a multi-value string field asEUR, AFR, ASAbecause a unique filter is applied before persisting in the database. [TS-9560]
Authentication
Security Token Service for externalized authentication and Single Sign-On is deprecated as of Tridion Docs 15.
- The ISHSTS (ThinkTecture IdentityServer) user interface allows selection of certificates by subject name. If however you have multiple certificates in your certificate store with the same subject name but with different thumbprint, the code will simply resolve this to the first hit provided by the certificate store. So in case of a certificate roll over, it could be that you are unlucky and select the expired certificate instead of the fresh certificate. Workaround exists in removing the conflicting certificate from the certificate store. [TS-11686|SRQ-5424]
Collective Spaces
- Collective Spaces status icons cut off in Firefox
- In the Mozilla Firefox browser, the status icons used in the outline view appear partially cut off. They appear correctly in other supported browsers.
- Collective Spaces user interfaces render only the first conreffed element in a conref range
- If a series of reusable elements is referenced from a topic as a conref range (for example, several consecutive steps in a Library Topic being referenced through a single conref range), then Draft Space and Review Space only shows the first referenced element in the range.
- Collective Spaces does not resolve
keyreforconkeyrefelements -
Draft Space and Review Space display a
keyrefelement by showing itskeyrefattribute value, rather than the referenced content. Similarly, Draft Space and Review Space display aconkeyrefelement by showing its default text. - Collective Spaces is not guaranteed to render table rows correctly that are referenced through a
conref -
Draft Space and Review Space should not be expected to not render a row in a table correctly if that row is a
conrefreference to arowelement in another resource (typically a Library Topic). The same is true for other table elements, like individual cells.
Organize Space
- Duplicate entries in Added Items
- The Translation Job user interface will show duplicate entries in the Added Items section, such as for example two times the same publication version. This is a cosmetic issue, the repository only holds one entry. [TS-10476]
- Downloading deleted item
- When using Organize Space on Firefox, there is no error message shown when a user tries to download an item that has already been deleted.
- Deeplink URL too long when too many items are selected
- When selecting multiple items in Organize Space Explore view or Object Details view, there is a URL generated for deep linking. This URL contains the IDs of all selected items, and if the number of selected items is too high, the URL can become too long to open.
- Filter selector and sorting dropdown popups not showing in third-party modal dialog used in an extension
-
This issue occurs if all of the following is true:
- You have created a user interface extension with a button that opens a third-party modal dialog,
- Your modal dialog implementation uses the
useItemSelectorhook from the Tridion Docs extensions library and opens the item selector.
Non-Western Language Searches
- Solr uses the Boolean
ORoperator when multiple words are detected in a search. Note also that for non-Western languages, Solr uses language analysis features to break down terms into smaller components, so if you enter a Japanese search for リンク解析 Solr breaks it into two words: リンク and 解析. In this case, the default behavior is to search for リンク OR 解析. This may not return the expected results. - Therefore, when you search in non-Western languages such as Japanese, Solr can be configured to use the Boolean
ANDoperator between words instead of the defaultORoperator. - To specify the Boolean
ANDoperator in these instances, add<str name="q.op">AND</str>in the<lst name="invariants">part of therequestHandlersection in the \TrisoftSolrLucene\SolrLuceneCatalog\conf\solrconfig.xml file. - If this is done, when Solr uses its language analysis features to break down a term into smaller components, the Boolean
ANDoperator is applied instead of theORoperator. However note that this does not affect words entered with a space between them as the search criteria. A whitespace between words still assumes use of the default BooleanORoperator. [TS-6497]
Client Tools and XML editors
- General
-
- All Client Tools require 64-bit Operating Systems and a 64-bit flavor of xml editors. We do not offer the 32-bit versions anymore.
- Taxonomy: when inserting a taxonomy tag in a list of existing tags in the properties dialog, sometimes the tag is not inserted at the position of the cursor. You need to re-position it manually [SCTCT-306].
- When creating a folder you can assign a UserGroup that the current user has no access to. The folder will be created, but any refresh action afterwards will not show you that folder and potentially can trigger an error message such as
The object does not exist. [c:"894969"][TS-8652] - When the Browser Repository dialog is opened from a third-party XML editor, the clipboard keyboard shortcuts (CTRL-C, CTRL-V, ...) cannot be used in the search field of this dialog's Search tab. The Del key cannot be used either in that field [TS-11221|SRQ-4898].
- Depending on your content architecture, the feature Dynamic Link Text resolving can have a negative performance impact to show you the accurate values in a preview. A safety mechanism will avoid infinite recursion. [TS-5966|SRQ-1200]
- Refresh operations might function incorrectly if the content object in question is created in multiple phases. Typically all content objects are created with logical-version-language levels in one go. Technically it is possible to create each level on its own, which can confuse the refresh operation. The advice is to adapt the routines that perform separate level creation. [SRQ-2432]
- You cannot connect with a second user to the same data source if the first user was already connected to the same data source. You can have two accounts, so two usernames, pointing to the same repository. You just cannot be connected at the same time. Switching accounts requires a client tools restart. [TS-8656]
- Although multiple third-party XML editors are supported in this release of Content Manager, use of a single third-party editor is recommended. RWS is not responsible for how the third-party editors handle XML and DITA and the behavior might differ for each XML editor. As a result, if you use more than one, you may find cross-compatibility issues with the way the different editors handle DITA. If you decide to use multiple third-party XML editors and find cross-compatibility issues with DITA, RWS recommends that you interact with the vendor of the XML editor to resolve the issue. [ TS-4957|TS-5260]
- Uninstalling the Authoring Bridge for XMetaL causes a problem when you then try to upgrade to the new installation. You must first uninstall XMetaL then you can uninstall Authoring Bridge. Reinstall XMetaL, then upgrade or reinstall the Authoring Bridge. [SCTS-380]
- ; searching on a version is always done on AllVersions [TS-4222]
- In
ServiceReferencesthere is no check about the ability of a user to enter the application. So the authentication works but Content Manager might still block authorization by aProfileMismatchException. [TS-4292] - Client Tools using SSL might crash when using a URL that does not match the certificate. [TS-571]
- Avoid opening multiple instances of editors (so there is only one process of the editor running) to prevent possible locking of files in the profile folder of the Mozilla Gecko renderer component. [TS-4682]
- Where Used Report [TS-7037] known issues. When doing a where used on an object in the client tools, be aware that the shown publications are determined by performing a PublicationOutput25.Containing API method. This means:
- The
PublicationOutput25.Containingfirst calculates the baselines in which the logical object is present (seeBaseline.Containing). These baselines are used to retrieve the publication versions (seePublicationOutput.UsingBaseline). As a consequence, when the baseline is shared between multiple publications, the result can contain publications in which the topic is not used. - Selecting a specific version of a map forces version selection for all referenced topics. Changing the version of a map can give less referenced topics, but those topics could still be in the baseline. This can result in publications shown in the report where the topic is no longer used.
- If a library contains
@conrefswith illustrations or links to other topics, all referenced objects will be returned as part of the publication even if they are not used. - If a library contains variable definitions with illustrations or links to other topics, all referenced objects will be returned as part of the publication even if they are not used.
- Conditional filtering is ignored!
- The
- DITA
-
- Only references to DITA topics and DITA maps are supported. References to images and other formats (for example, PDF, DOC) are not properly supported or not supported at all. [TS-5731]
- When using the
<stylesheet>element in StyleSheets.xml at<download>time, you are actually forcing an XSLT processor to handle the file from the repository. The XSLT processor will always add default attributes - like@class,@domains,@ishlabelxpath, etc - to the resulting XML file. Our typically configured Filters/Dita11ToDita12.xsl which takes care of automated@navtitleattribute to<navtitle>element conversion immediately removes these unwanted default attributes. This stripping does not affect the@processing-roleattribute on the<keydef>element. You can either disable the<stylesheet>or tweak the XSLT file to your needs. [TS-8692] - The current list of elements explicitly resulting in resolved link text in the Client Tools preview are:
<xref>,<link>,<topicref>and their basic@classattribute based specializations. Many other elements like the<mapref>,<topicsetref>,<anchorref>,<topicgroup>,<topicset>elements or<navref>will not be resolved while previewing. [TS-8298] - When conreffing a
glossentrywhich is part of aglossgrouptopic, aglossentryis created with an incorrect value in theconrefattribute. Publish warns that there is an unresolvable conref during publish because the conref value is incorrect. [TS-4630] - The
@idattribute cannot contain OASIS DITA control characters like slash (/) and hash (#) - even on the<resourceid>element as the parsing engine cannot distinguish it anymore when using the OASIS DITA linking system (e.g.LOGICALID#TOPICID/ANCHORID). If you use this construct, it could give unexpected results in the Publication Manager tree list views like Baseline, Folders, WhereUsed, etc. [TS-10488|TS-10540|TS-10553|SRQ-4015]
- JustSystems XMetaL
-
- When attempting a search-and-replace on a file that either has a Released-type status or that is not checked out, a dialog with the following error may appear:
MFOResultObject.prototype.XMReplace() = Error: Invalid document object. If you encounter this error, create a new version of any Released topic you want to modify, and check out any topic that is checked in. Then try the search-and-replace again. [SCTCT-1833] - When using, from the RWS menu, the Browse Repository dialog, in the Advanced options of the Search tab, the drop-down lists of values cannot be closed by clicking outside the list. You need to use the arrow again to collapse the list [SCTCT-142].
- When you open a map and open a referenced (RELEASED) file from within the map, you get an unrelated message
Please choose a topicref to a DITA topic. The message is not blocking, just select OK. [SCTCT-265]. - The DEL key and CTRL-V key combination do not work in the search text field of a Browse Repository dialog. [TS-4117|TS-11220|SCTCT-141|SCTCT-142]
- When using XMetaL Resource Manager on a DITA Map holding an equal sign (
=) in its metadata title field (FTITLE) functionality like opening and saving might return unexpected results and throw messages in the line of 'mapApp' is null or not an object or A Dita Map was not selected or A specialized map was selected. As a workaround, use the full editor view. [TS-10541] - Using the ALT-TAB key combination to another application while doing a checkout/checkin/keep checked out of an item with (con)keyref blocks XMetaL. The XMetaL Configure Key Space Association dialog pops up when (re)opening the item, but the focus is on the main XMetaL window, which makes it impossible to close the Configure Key Space Association dialog. When trying to close XMetaL, it detects that there is still a script/dialog running and it cannot close. Using Microsoft Windows Task Manager you can kill the Configure Key Space Association dialog; you can also disable that dialog in XMetaL's on the tab named Update Content: Uncheck the checkbox marked Prompt if the document is not associated with a key space when refreshing references. [TS-5641]
- Dynamic Link Text Resolving of
<related-links>are sometimes not resolved from the referenced document if no text was given, although is enabled. This is caused by unwanted whitespace, it can be worked around in the .CTM files by disabling the pretty print options. [TS-9788] - Publishing from within XMetaL is not supported. The following menu items are not fully supported (may not work):
- Local Publish with a Topic/task etc. which has an
xrefinside it does not work. [TS-5182|TS-5184] - The Page Preview view is not supported (may not work). [TS-5526]
- Page Preview produces an error
null is null or not an objectwhen axreftopic contains unresolved references. [TS-4438] - Do remember that installing the Authoring Bridge for XMetaL on Windows machines requires you have to have full access to folders C:\Program Files (x86)\Common Files\XMetaL Shared and C:\Program Files (x86)\XMetaL x.y before performing the installation.
- XMetaL will show the value of an
ishconditionattribute that contains the following special characters",<,>,&in the Tags On View and Normal View with their corresponding XML predefined entities",<,>,&. Note that all other characters should not be shown as XML character entities.For example the following
ishconditionvalue:Department='R&D' and version > 3.1.1will show up as:Department='R&D' and version > 3.1.1. [TS-8004] - Inserting a
conrefto a multimedia object is not always resolved correctly. Either it shows you the object twice or it shows a blue outlined diamond. [TS-8458|TS-8663] - If the Authoring Bridge is uninstalled, the Tridion Docs menu will remain in the menu bar, with all menu options greyed out. The user must start XMetaL while pressing the
CTRLkey in order to have XMetaL clean up the menu bar and remove the Tridion Docs menu. [TS-10128]
- When attempting a search-and-replace on a file that either has a Released-type status or that is not checked out, a dialog with the following error may appear:
- Oxygen XML Author/Editor
-
- Multi select insert via Topic Ref isn't working as the XML editor's
InputURLChooserCustomizercan only handle one. [TS-9449] - Issues may arise with Find and Replace when used on a DITA map. A common error made when doing a find/replace on map is setting the wrong filter in the Include Files field of the UI. When performing a find/replace on a map, users should change the filter to the asterisk wildcard character,
*. The default is*.*. (Only on 15.2) - The Add account window does not disappear after pressing Cancel. This is a known issue when using remote desktop technologies. [TS-5654]
- Oxygen XML Author/Editor performs a save operation on all your open files when you access an Authoring Bridge menu, which allows you to CheckIn or CheckOut. This issue is caused by a difference in threading paradigm between the JAVA based XML editor and the .NET-based Authoring Bridge SDK components.
- Oxygen XML Author/Editor is only available on a Microsoft Windows platform because the Authoring Bridge SDK is made of .NET libraries
- Oxygen XML Author/Editor menu items and buttons do not get disabled when a document is visible in the editor but not checked out. The user can still access the dialogs and perform actions, which can be confusing because the document is locked and cannot be edited. [TS-5140]
- Multi select insert via Topic Ref isn't working as the XML editor's
- Publication Manager
-
- Checking in a previewed map that is already checked in may cause Publication Manager to return errors and crash. Clicking on the error
Checking in of the object '{Map name}' failed. Object has to be checked out.can allow you to continue the session. - When a
conrefis made to an image in the same topic, an erroneous message is displayed for circular references:Warning: The object <x> is mentioned within the object itself, creating a circular reference. [TS-3449] - Find option (CTRL+F) in Publication Manager for the current document no longer has the option to Match whole word. The find on a whole word functionality was dropped; it is not supported by the new browser component (Gecko). [SCTS-469]
- After checking in topics, there is a delay before the changes can be found by the search. When using the scope Current Publication it will be asked to check in the topics, but even then changes might not be part of the search results. There is a delay between checking in and the indexing into the full text index. A refresh of the search result pane will resolve the problem after the index is generated for the checked in topics. [TS-8322]
- There is no cursor when adding or replying to a comment in the Publication Manager. Typically happens when you switch to another application and then move back to Publication Manager. The issue is caused by a bug in the Gecko renderer component.
- Inbox gives an error when one of the files in the list has a
conref-conrefendpair that don't refer to the same document. The error is:Begin and end id require to be in the same document when a bookmark is given. [TS-2207]
- Checking in a previewed map that is already checked in may cause Publication Manager to return errors and crash. Clicking on the error
- Content Importer
-
- When files to be imported include images that have the same name but not the same format, with a resolution map that attributes a different resolution for each image format, only one resolution is imported instead of one per format. [SCTCT-472]
- The user interface shows a possibility for Default resolution which never gets used because the system always expects a mapping from file extension to Electronic Document Type (EDT) to be configured. Unconfigured file extensions will simply be ignored. [SRQ-3216]
- In Content Importer, changing the resolution of a selected image is not available. For setting a new resolution, you need to delete the image and reload it with the new resolution. [TS-7705]
When importing multiple versions, languages or resolutions of the same logical object and the logical object does not exist, you might get
ObjectNotFoundexception. This is caused by both files trying to create the same logical object and for one of them this will fail withObjectAlreadyExists. The automatic retry in Content Importer is to do an update of the failing one, but this will throwObjectNotFoundbecause only the logical level already exists. A manual retry will import the failing objects without issues. The advice to prevent this is to split the initial creation of a logical object in one version and language, from the other versions, languages and resolutions.Workaround for failed import with a language level entry with error on preview or not all langs/resolutions imported:
1) Check files still exist in CI 'source' folder and CI remains open.
2) Delete the version of the object which has failed, do not delete the logical object. Deleting the language level will always fail.3) Re-import the same files.
- Preview
-
- The image files of type SVGZ are not rendered. You can submit and use them throughout the application. The only exception is that the client tools will render an embedded SVGZ in the preview. Organize Space preview of SVGZ results in an XML parsing error. The XML parsing error is caused by the mime type. The mime type for both SVGZ is
text/xml+svg. Thetext/xmlportion of the mime type enables SDL product components to process the content as XML. However, the SVGZ content is actually a zip archive of SVG content. That is, the format is not XML, but a zip archive of XML text. The zip archive of XML content causes the parsing or loading error. [SCTS-532|TS-7667] - WMF and TIFF files are not displayed in the preview. They cannot be rendered by any client tool.
- The image files of type SVGZ are not rendered. You can submit and use them throughout the application. The only exception is that the client tools will render an embedded SVGZ in the preview. Organize Space preview of SVGZ results in an XML parsing error. The XML parsing error is caused by the mime type. The mime type for both SVGZ is
Publishing
- All PublishService output formats are delivered as examples. We expect all customers to skin and apply company layout and logos. We package improvements on a best effort basis without guarantees. [SRQ-3139]
- The conversion from XML to HTML performed by the
ishditadeliveryplugin has the following limitations:<topicmeta>elements inside the DITA XML content are transformed to<head><meta>elements in the HTML files that are uploaded. Any content inside the head cannot be viewed.- For dynamic conditioning (conditional display of the content when the end user selects condition values when reading), we are persisting the
ishconditionattributes from the XML to the generated HTML elements. When it cannot be done because the element does not produce an output in the HTML, we add a<tcdl:If condition="">element. However in some cases we had to abandon the element, therefore the condition is ignored (the end user can not use the condition and all content is visible).In topics, the conditions set on these elements are dropped:<titlealts>and all its child elements.<prolog>and all its child elements.<metadata>and all its child elements.<data>and all its child elements: These elements are not rendered in the output XHTML as stated by the DITA Language specifications.- All child elements of
<area>other than<xref>, as they are rendered as attributes (e.g.shape,coords, etc.). - All child elements of
<object>, as they are rendered as attributes. <alt>and all its child elements, as they are rendered as attributes.- All child elements of
<syntaxdiagram>. <desc>and all its children, as they are currently rendered as<alt>or<hover>attributes.
In maps, the conditions set on these elements are dropped:<topicmeta>elements.<navtitle>elements.<reltable>elements and their child elements are not propagated to the topic's related links section.
- The
<anchor>,<anchorref>and<navref>elements are not rendered, as the DITA specification states that these elements are primarily designed for the Eclipse Help output format.
- When the
<xref>element does not contain text and thehrefattribute refers to a XML element that does not contain a<title>element (e.g.<xref href="GUID-X#GUID-X/OL1"/>), theishditadeliverystylesheets will show thehrefattribute value (soGUID-X#GUID-X/OL1) as hyperlink text in the resulting HTML page. - During a publish of changed content, if the Remote Status of the publication output is set to Online, a user can potentially see an intermediate state of the content, including finding through search a topic that has been removed.
- An
<indexterm>element with no content will cause the publish to Dynamic Delivery output format to fail - For some elements like
<alt>or<desc>, only the text is put in the HTML, so child elements are ignored. Note that these child elements might have had a condition.<image xxx><alt>An image of the longest river, the <ph ishcondition="Europe">Volga River</ph><ph ishcondition="Africa">Nile River</ph></alt></image> - For DITA maps, any
ishconditionattributes on the<topicmeta>or<navtitle>elements are not propagated to the Table of Content<naventry>/<title>elements. - For DITA maps, any
ishconditionattributes on the<reltable>element or any child element of<reltable>are not propagated to the topic related links section. - We don't do anything for DITA conditions (neither while applying conditions when publishing nor allowing the user to apply them dynamically)
- A map with
<topicref>elements referring to topics having the<toc>attribute set to<no>are not kept in the Table of Content ( as in standard DITA), but the pages for those topics are uploaded. - As the DITA spec states that
<anchor>,<anchorref>and<navref>might not render for every output format (and are mainly intended for the "Eclipse Help" output format), we do not render them in our "DITA Delivery" output. - Conditions around key definitions should be evaluated during publishing. The key definition will not be resolved and applied correctly when the conditions around the key definition would be set dynamically by the web site end user.
- If you republish a publication, we use eventual consistency, so we do not take the publication offline in the web app. This means a user can potentially see an intermediate situation. Note that we don't delete any content in CD stack when republishing, so topics that were present in the original publication and are not referenced from the Table of Content anymore might still be found as a result of a search.
- We did not solve the fixed texts in the stylesheets that might disappear during dynamic delivery: For example, a text like "Related links" is hardcoded as text in the XSL stylesheets and is not a
<div class="rellinks">with styling yet, so depending on what the webapp will do if no links are left after dynamic conditioning, it can be hard to remove by CSS styling. The same goes for menu cascades with conditions: "Edit" > "Indent" > "Increase line indent", as the>characters are hardcoded texts added by the stylesheets, if one of the parts before or after the>would be conditionally filtered away dynamically, the>between them should be removed as well. - MathML is not supported, SVG in doubt. Imagemaps do not work,
<object>and<embed>elements are not tested.
Translating
When files are sent to WorldServer for translation, some special characters are not recognized as valid by WorldServer if they are used in the file's title. In this case WorldServer changes the file name to tmp making it impossible to match the WorldServer task back to the translation job item. When this happens, the job receives the SendingFailed status. [TS-12482]