Known Issues

The following are known issues in this version.

Web/App/DB Servers
  • The IshReplaceTitle PI inside GlossaryEntry is not replaced when creating a new object.
  • Limitation: the maximum PublicationOutput storage size for PDFs and ZIPs in the database is limited to 2GB.
  • 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]
  • API read functions like PublicationOutput25.RetrieveMetadata can handle element name retrieval for controlled fields through the @ishvaluetype attribute. The CTPUBLICATIONOUTPUT field FISHPUBLNGCOMBINATION is a special field, that is linked to the DLANGUAGE field 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.SetMetadata will save an incoming entry like EUR, AFR, EUR, ASA, EUR, EUR to a multi-value string field as EUR, AFR, ASA because a unique filter is applied before persisting in the database. [TS-9560]
  • This warning Trisoft.InfoShare.BackgroundTask.Entities.NewProcessTaskHost.SendForceShutdown Calling ServiceMustClose resulted in exception System.ServiceModel.EndpointNotFoundException is logged if the parent process is asked to stop (either console CTRL-C or service panel). The parent BackgroundTask.exe communicates to all its running tasks to stop. In case a running task is handled through a new process, so a child BackgroundTaskIso.exe, it can happen that the BackgroundTaskIso.exe process is already stopped when the disposal of the newproc task happens, resulting in the above warning. [TS-9037]
  • Light weight Windows Authentication based on ISHSTS is not Network Load Balancing (NLB) ready. We only describe the steps to set up a single FrontEnd Web/App server when using our ISHSTS for Windows Authentication. The reason is that making ISHSTS NLB-friendly requires a big investment to something we do not consider our core business - there are free alternatives like Microsoft Active Directory Federated Services (ADFS) provided as a free role with a Windows Server.
  • When using a web browser to ISHSTS, therefore using Content Manager as your identity provider with registry entry AuthMaximumPasswordAge enabled, the system can return the message Your password has expired. Please enter a new password or contact your system administrator. The Client Tools rely on the active protocol (WS-Trust) for authentication where we cannot easily distinguish between a regular no access or a no access because your password is expired like we could do for the Web Client which is based on the passive protocol (WS-Federation). So when a user has a doubt about password expiration, he should use his Web Client where he will also find a Change Password link on the login page. [TS-9465|TS-9433]
  • We strongly advise to redirect your custom integration to DocumentObj25/PublicationOutput25 instead of using the deprecated classes DocumentObj20/Publication20/PublicationOutput20. When throughput is important, the 2.0 code base might throw timeout errors like Trisoft.InfoShare.API25.InfoShareException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. If you use both the 2.0 and the 2.5 code base, you might also see errors like System.Data.SqlClient.SqlException (0x80131904): Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out. The main reason is that the COM+-based 2.0 calls force Serializable on the transaction, potentially making all calls wait. This problem is solved when you switch your custom code to the 2.5 API calls. This is what we did for all of our client tools (Publication Manager, Authoring Bridge, Content Importer, etc). [TS-8739]
  • Failed transactions block any further update on locked content objects (DocumentObj) or publication outputs (PublicationOutput) requiring manual actions to roll back the transaction. The following characteristics identify the problem:
    • ORA-01591: lock held by in-doubt distributed transaction trans_id or ORA-02049: time-out: distributed transaction waiting for lock in the log files.
    • The Microsoft Component Services panel holds entries marked with (only failed to notify) in the Distributed Transaction Coordinator > Local DTC > Transaction List. For example ISAuthor.CPublicationOutput (only failed to notify) or ISAuthor.CDocument (only failed to notify).
    All environments having this problem have the Oracle password expiration options set for our designated database user - typically isource. Usually near expiration time you'll see the messages appear like ORA-28001: the password has expired or ORA-28002: the password will expire within x days. We advise you to contact your DBA on this, the following statements are provided for convenience only:
    1. First check which profile ISOURCE is using: SELECT profile FROM dba_users WHERE username='ISOURCE';
    2. Optional query to show all the limit settings of this profile: SELECT resource_name,limit FROM dba_profiles WHERE profile='DEFAULT';
    3. Change the default profile to set the password lifetime to unlimited: ALTER PROFILE DEFAULT LIMIT PASSWORD_LIFE_TIME UNLIMITED;
    4. After setting the password lifetime you have to reset the password again. You can set it to the same password as it was: ALTER USER isource IDENTIFIED BY isource;
    5. We advise you to restart the database and any web/app server.
  • In case of network stability or connection problems (such as ORA-03113 end-of-file on communication channel) we advise you to setup the Oracle Microsoft Transaction Server (MTS) Recovery Service as documented on http://docs.oracle.com/cd/E11882_01/win.112/e26104/recovery.htm#NTMTS003. This service resolves in-doubt Microsoft Transaction Server transactions. [TS-7822]
  • The EventMonitor logging system potentially shows the wrong final status FAILED in the overview when it actually was a SUCCESS. A failure is logged, but then the generic or the PublishService retry mechanism is started, that potentially results in a success. The EventMonitor logging system then CALCULATEs the result in the overview. [TS-8560]
  • The automated shut down of the Trisoft-InfoShare-AuthorIso failed application sometimes results in Invalid syntax. You can ignore this message.
  • Renaming languages in settings area will not adapt @xml:lang and 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:lang attribute 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.
  • 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 StartReindex.bat and restart the Trisoft InfoShare Crawler service.
Non-Western Language Searches
  • Solr uses the Boolean OR operator 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 AND operator between words instead of the default OR operator.
  • To specify the Boolean AND operator in these instances, add <str name="q.op">AND</str> in the <lst name="invariants"> part of the requestHandler section 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 AND operator is applied instead of the OR operator. 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 Boolean OR operator. [TS-6497]
Client Tools and XML
  • Only 64 bit versions of the XML editors are supported.
  • 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 where 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].
  • When conreffing a glossentry which is part of a glossgroup topic, a glossentry is created with an incorrect value in the conref attribute. Publish warns that there is an unresolvable conref during publish because the conref value is incorrect. [TS-4630]
  • The @id attribute 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]
  • 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]
  • 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 @navtitle attribute to <navtitle> element conversion immediately removes these unwanted default attributes. This stripping does not affect the @processing-role attribute on the <keydef> element. You can either disable the <stylesheet> or tweak the XSLT file to your needs. [TS-8692]
  • Although multiple third-party XML editors are supported in this release of Content Manager, use of a single third-party editor is recommended. SDL 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, SDL 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]
  • Although not supported, when installing Client Tools 10.0.3 on a Server 10.0.0/10.0.1/10.0.2 you might run into a compatibility issue. The reason is that the Trisoft.Utilities.ServiceReferences.dll assembly has been extended with a new class to do WCF http compression in the .NET 3.5 world. The Client Tools MSIs are not always allowed to overwrite the server-side's older version of the assembly. This results in messages in the line of Unable to establish a connection with the web services on or Could not load type 'Trisoft.Utilities.ServiceReferences.WebClients.CompressibleHttpRequestCreator' [TS-7169]
  • Search > Advanced options; searching on a version is always done on AllVersions [TS-4222]
  • 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]
  • In ServiceReferences there is no check about the ability of a user to enter the application. So the authentication works but Content Manager or Collaborative Review might still block authorization by a ProfileMismatchException. [TS-4292]
  • Client Tools using SSL might crash when using a URL that doesn’t match the certificate. [TS-571]
  • Client Tools cannot handle Content Manager accounts that contain a slash (/) or backslash (\) because it confuses them while handling other authentication requests coming from Secure Token Services or Proxies that potentially require NTLM/Windows authentication. [TS-8312]
  • When using a secured proxy, the client tools browser component could popup an extra authentication dialog. [TS-4680]
  • 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 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.Containing first calculates the baselines in which the logical object is present (see Baseline.Containing). These baselines are used to retrieve the publication versions (see PublicationOutput.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 @conrefs with 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 current list of elements explicitly resulting in resolved link text in the Client Tools preview are: <xref>, <link>, <topicref> and their basic @class attribute based specializations. Many other elements like the <mapref>, <topicsetref>, <anchorref>, <topicgroup>, <topicset> elements or <navref> will not be resolved while previewing. [TS-8298]
Content Editor
PTC Arbortext Editor
  • With Arbortext 7.1, trying to change an href attribute from the Document Map fails to open the "Browse Repository" dialog. Workaround: right-click on the element and select Modify attributes, then select to open the 'Browse Repository' dialog [SCTCT-255].
  • The SDL Tridion Docs menu and the Insert Markup action to insert elements works and will trigger the necessary Authoring Bridge dialogs. All other functionality such as the direct Insert menu items cannot properly be redirected to the RepositoryAdapter and pops-up with Arbortext Editor's file system integration.
  • Conrefend attribute is not displaying in the Modify attributes window.

    The conref attribute was removed from the Modify Attributes dialog. Use the menu option, SDL Tridion Docs > Conref > Insert Conref in the editor to insert a conref or a conref range. [TS-5593]

  • The conref attribute was removed from the Modify Attributes dialog when you have a Content Manager document opened in the Arbortext Editor. Users must use the menu item, SDL Tridion Docs > Conref > Insert Conref, to insert a conref or a conref range in their document.
JustSystems XMetaL
  • When using the Find in Files functionality in XMetaL 12, performing a replacement requires that you create a new version or branch for the Released (and checked in) objects. Then XMetaL produces an Unable to make changes... error when trying to perform the replacement in the new version or branch. You need to redo Edit > Find in Files to let XMetaL include the new version or branch.
  • When using, from the SDL 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 Tools > DITA Options 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 DITA Options > Refresh xref/related-links 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):
    • File > Generate Output for DITA Map...
    • File > Generate Output for DITA Topic...
    • File > View Output Log...
    • File > Preview in Browser...
  • Local Publish with a Topic/task etc. which has an xref inside 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 object when a xref topic contains unresolved references. [TS-4438]
  • Do remember that like in SDL LiveContent Architect 2013 when installing the Authoring Bridge for XMetaL on Windows machines 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 ishcondition attribute that contains the following special characters ", <, >, & in the Tags On View and Normal View with their corresponding XML predefined entities &quot;, &lt;, &gt;, &amp;. Note that all other characters should not be shown as XML character entities.

    For example the following ishcondition value: Department='R&D' and version > 3.1.1 will show up as: Department='R&amp;D' and version &gt; 3.1.1. [TS-8004]

  • Inserting a conref to 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 SDL Tridion Docs menu will remain in the menu bar, with all menu options greyed out. The user must start XMetaL while pressing the CTRL key in order to have XMetaL clean up the menu bar and remove the SDL Tridion Docs menu. [TS-10128]
<oXygen/> XML Author/Editor
  • Multi select insert via Topic Ref isn't working as the XML editor's InputURLChooserCustomizer can 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]
Content Editor
  • Inline elements are not pasted into codeblocks, or other space-preserving elements. Only the text, and not the accompanying inline elements are pasted when you are pasting into a codeblock or other space-preserving elements. For example if you were copying a code sample that includes an inline b (bold) element and then tried to paste this, the result is only the text of the code sample will be pasted. We do not paste the bold or other inline elements.
  • Selecting a range of contiguous conref targets is not supported in Content Editor. [LCDE-385|LCD-2229]
  • When copying content in the tags on view in Internet Explorer, the text of the tags is copied to the clipboard as well.
  • Processing instructions for placeholders (xm-replace_text) inserted using the API after loading the document are not recognized as placeholders.
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 conref is 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]
  • When you change the Review End Date of a publication output in Publication Manager or Web Client after the output was already published, the status is changed to Out of date (working as designed). Note that when any metadata field is changed on the publication output, the status of the publication output is changed to Out of date. This happens because the metadata (in this example, the Review End Date) may have been used in the publication (e.g. on the front page), therefore the published result can now be out of date. [TS-3093]
  • 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.
  • Comments pane title in Publication Manager does not resize correctly. For screen resolution settings 1024x768 and lower, the Comments pane display in Publication Manager may have display issues. [SCTS-168]
  • Inbox gives an error when one of the files in the list has a conref - conrefend pair 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]
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]
Web Client
  • The List Views in the Web Client cannot display taxonomy fields. As a consequence, a search or a report cannot return results based on taxonomy. [SRQ-9456]
  • When using the properties dialog for any object from the Web client using Microsoft Edge, placing the cursor over the dialog closing buttons Modify and Close displays a link that partially covers the buttons. This makes using the buttons difficult [SCTW-818].
  • List Of Values entries holding a single (') or double (") quote could cause unexpected behavior in some locations. In general we suggest to avoid these characters in values for readability. For example a single quote in a status will make the Initial Statuses page return HTTP 500. [TS-10462]
  • 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]
  • You can create a logical ID with spaces. However, when you try to use a template to create the initial document, this will return errors in the line of The object "JIRA TS 2031" contains invalid XML or Multiple names found in attribute value when only one was expected. The OASIS DITA document types specify the @id attribute as a true identifier, blocking spaces in the identifier. In a future version we will completely forbid usage of spaces in identifiers. [TS-2110]
  • The sorting result on Inbox items is not correct. Uppercased letters come before lowercased ones, which is the typically ASCII sorting order based on their numerical (not alpha) representation. [TS-2933]
  • Actions triggered through the web client don't allow to update baseline entries. A triggered web client will reuse any existing baseline and initiate an auto complete action when required. For example, creating a publication in the web client and trying to get it to status Released will not work because at no point in time the baseline received version entries. [TS-8633]
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. Web client 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. The text/xml portion 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 or the web client.
Publishing
  • Using PublishService with options Keep DTD system ID off and Keep fixed attributes off will not work because post processing is not resolving the DTD when loading the XML. This causes exceptions such as loading and converting file: C:\...\PublishingService\Data\DataExports\GUID-...\...\en\workset\...=GUID-...=1=en=.xml ERR ISHPublUtil::ResolveFileNames -> Unable to load file [C:\...\PublishingService\Data\DataExports\GUID-...\...\en\workset\...=GUID-...=1=en=.xml] into a DOM document for converting the link statements. Following error occured: -2146697210 [TS-10431]
  • 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 Web Help output format might contain too many XML or image files. For example images could still be present that are part of the super-publication but might no longer be accessible through content object navigation because of conditional filtering. [SRQ-3035|SRQ-3139]
Publishing to Dynamic Delivery
  • The conversion from XML to HTML performed by the ishditadelivery plugin 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 ishcondition attributes 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 Eclips Help output format.
  • When the <xref> element does not contain text and the href attribute refers to a XML element that does not contain a <title> element (e.g. <xref href="GUID-X#GUID-X/OL1"/>), the ishditadelivery stylesheets will show the href attribute value (so GUID-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
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]