Documentation Center

Fixed Issues in 12.0.0 Client Tools

The following issues are fixed in Content Manager 12.0.0 compared to 11.0.0.

Client Tools and XML

  • When you have multiple accounts, and at startup you get prompted for your credentials, but you Cancel this operation, it resulted in a cosmetic unwanted error Microsoft .Net Framework - Unhandled exception has occurred in a component in your application. [TS-10440]
  • While in edit mode of a tree node or a list view in the Client Tools - like for example Folder rename - all keyboard short cuts are blocked or don't do what is expected. For example during a folder rename the Del key will remove characters and not ask to delete the folder. [TS-10556]
  • When doing a Batch Metadata operation, the resulting Update window does not always show the information. For example it could end with a window stating Update Completed with 3 Errors but you had to click the Refresh button to actually see the entries. [TS-9545|SRQ-3233]
  • Client Tools will no longer allow a protocol handshake using the SSL3 protocol. This change should avoid a vulnerability known as the "POODLE" attack where it is possible for an attacker to forcefully downgrade the SSL/TLS protocol used by a client/server connection until the peers choose to communicate over SSL3. This allows an attacker to eavesdrop on information exchanged between the parties over SSL connection using SSL3. The attack is identified by CVE-2014-3566. By default the .NET framework runtime (System.Net.ServicePointManager.SecurityProtocol) allows a handshake using protocol SSL3 or TLS (1.0). By configuration we force a handshake among protocols: TLS (1.0), TLS11 (1.1) and TLS12 (1.2). [TS-9114|TS-9428]
  • Configuration change in file metadataconfig.xml to avoid that the FDESCRIPTION field is emptied when creating new versions. The configuration now separates new version by the introduction of the Properties_NewVersion_* forms from Check In As or Duplicate operations. [SRQ-2942|TS-9450|TS-9469]
  • Some list view title fields are cut off and shown as "..." in Search results/Repository folder content while they have a proper title available. The most likely cause of this were CR/LF in the metadata field. Those are now normalized for rendering purposes to a single space. [TS-8703|TS-9045]
  • Browse repository version selection should be cleared if no object is selected in the list view. [SCTS-756|TS-8828]
  • Check out (In Context Edit) from Publication Manager doesn't refresh the publication's resource libraries for variable inserting. [SRQ-2098|TS-8558|TS-8967]
  • Additional checks in Client Tools browse repository result in errors and in the folder not being opened, showing warnings such as The conref range “xxx" is invalid!. [SRQ-2404|TS-8790|TS-8938]
  • The multi value assist, configured on fields such as fall back languages didn't respect the order. The assist on the FallbackLanguageField field is now configured in MetadataConfig.xml to no longer do sorting on its values. [TS-8934|TS-9046]
  • Inserting a <topicref> to a Library Topic now sets @format attribute to dita and not to typical file extension xml which confuses DITA-OT downstream. This was altered in MetadataConfig.xml by adapting the <script> block in <ishfrmfield id="HRefField".... [TS-9091|TS-9086|SRQ-2548]
  • Offline working from local storage was interrupted by a message stating An error has occurred while opening external DTD 'file:///.... [TS-8796|TS-8969|SRQ-2260]
  • When having more than one account configured, it could be that Authoring Bridge actions Set Condition, Insert Image, Insert Conref and Update Conref unintentionally use the default account instead of the account connected to the open document. [TS-9228|TS-9218]

Preview

  • Preview resolving link text will no longer render a superfluous Link text cannot be resolved if the <xref> holds an image. [TS-9781]
  • Space between <tm> tag and <ph> tag is not displayed in the preview. [TS-9284|SRQ-2747]
  • When a user requests to Cancel a Preview, the cancel action will message the ContentResolver which in turn cancels redundant web service calls so that a long-running preview or preview switch reacts faster. [TS-9691|SRQ-3190]
  • Preview does not resolve @conref having a case-sensitive @conref/@id combination. This can happen when you switch the default configuration of BlobExtractMetadata IWrite plugins parameter DocumentUpperCase to No for ISHSYSTARGETSTOMETADATA and ISHSYSFRAGMENTLINKSTOMETADATA. [TS-10079|TS-10080|SRQ-3770]

Search

  • Number of hits found for the same search query in Web Client and Client Tools differs. This problem only occurs when images with LanguageApplicability (also known as multi-lingual) are part of the result set. The full text index query is now optimized so that this problem is avoided when searching with one language. The problem is a lot less frequent when searching with search criteria holding multiple languages. [TS-7646|TS-9044|SRQ-1972]
  • Navigating search results suddenly shows You have reached the maximum number of hits '4998' allowed by a search. while there are more pages available according to the search results control. The search results was hardcoded to 5000 hits spread over a maximum of 50 pages using the default page size of 100. Because of LanguageApplicability you even got less pages causing the 4998 vs actual 5000 difference. Now the search can go beyond this hardcoded value allowing you to browse the full result set if desired. The initial result set retrieves enough information to fill up the first 3 search results pages. When you request page 4, the search will be re-issued requesting for 3 times the earlier total hit size. So the initial 3 pages of 100 results (300) will trigger a search of 3 times 300 results (900) when requesting page 4, and so on. [TS-8490|TS-9055|SRQ-1970]
  • The order in the result lists of Client Tools and Web Client is different. This has been corrected. [TS-8664|TS-9042]

Publication Manager

  • Query Folder containing Publications fails with Parameter 'name' or 'text' is required. [TS-10562]
  • Improved behavior when moving expanded nested topics in the tree view. This could cause the application to freeze. [TS-10502|SRQ-4236]
  • Autocomplete using options Candidate for baseline or Baseline is fine tuned regarding non-recursive and recursive version calculation. [TS-10038|TS-10039|SRQ-3736|TS-10053|TS-10074]
  • the message for circular references Warning: The object x is mentioned within the object itself, creating a circular reference has been removed. The preview will render a This conref is not defined. [TS-3449]
  • When using Remote Desktop Services (mstsc/rdp), you could run into hte error System.Runtime.InteropServices.ExternalException (0x80004005): A generic error occured in GDI+. when navigating the tree view. This cosmetic error is now handled appropriately. [TS-8933]
  • The Variables listing doesn't show all variable assignments (@varid) and variable references (@varref) present in the publication. So some This variable is defined 2 times. and This variable is not defined. are potentially missing. [TS-9822|TS-9802|SRQ-3359]
  • Creating new publication version ignored the account's default language setting but used the user's language. We adapted MetadataConfig.xml ishfrmfield name="PublicationSourceLanguageField by switching from variable currentuserlanguage to defaultlanguage. This is typically noticed on environments that rely on multiple source languages for editing. [TS-9725|TS-9723|SRQ-3227]
  • When creating a branch 1.1.1 of publication version 1, the baseline is not duplicated, it picks up the recent available version rather than mirroring the baseline of the branched version. The fix consists in a Publication Manager change and a server-side change on API call PublicationOutput25.Create. [TS-9618|TS-9617|SRQ-3133]
  • Publication Manager freezes with an unresponsive dialog asking for The local storage contains a writable copy of <name>. Do you want to Leave the local file. Actually the local storage was locked, which also affected the Authoring Bridge in your XML editor, resulting in messages warning you that you should wait or even Server Busy messages. [TS-8886|SRQ-2294|TS-8615]
  • Status messages such as Retrieving objects (2700 of 24474)... that were suppressed because of multi threading changes are now restored. [TS-8863]
  • Unexpected revision. A more recent revision was expected when retrieving the content. is shown in Publication Manager preview after a Checkout with... to the XML editor and when you immediately do a Checkin again (within 30 seconds). The 30 seconds cache value is now lowered to 5 seconds and the routine of retrieving the file from the repository, saving it, previewing it, checking it in and saving the final result after plugins has been tweaked. [TS-8827|TS-8678|SRQ-2418]
  • While previewing images of type 3DXML or SWF (Adobe Flash), the preview actually rendered an HTML statement starting with <!DOCTYPE html PUBLIC ... instead of triggering the plugin that is capable of rendering the provided image binary. [TS-8966|TS-8944]
  • The commenting Refresh button was disabled, now it is always enabled. [TS-9040|TS-8685]
  • Refreshing a Publication Manager session could result in Object reference not set to an instance of an object when the root DITA map of the publication was replaced in another Publication Manager session meanwhile. [TS-9013|TS-9088]
  • Adding a newly created topic to the tree can result in warning Cannot resolve link text for topic reference '<logicalid>'. A version is required to use this operation.. This issue is caused by a timing conflict between the refresh of the preview and the automatic version selection process (auto-complete). [TS-9087|TS-9027]

Content Importer

  • When using re-GUID-ize on lower-cased filenames, the initial lower-cased guid was not replaced. [TS-9883]
  • <xref> elements won't pull the target title text from an element within a topic like <figure>, <table>, etc. It will show TopicGUID#TopicGUID/ElementID instead. The xml_code_fragments.txt file contains a specific topic that failed to be imported due to the fact that it includes the comma-space character sequence in its <title> element. [TS-9275|TS-9274|TS-9276]
  • When using ContentImporter.xsl to give the DOC-LANGUAGE field multiple values like da-DK, de-DE, en-GB, en-US, fr-FR, it-IT, pt-BR to import images, you received the error The LovValue da-DK, de-DE, en-GB, en-US, fr-FR, it-IT, pt-BR does not exist. [label:"da-DK, de-DE, en-GB, en-US, fr-FR, it-IT, pt-BR"] [102001;InvalidObject]. The rewritten, faster DocumentObj25 API offer a DocumentObj25.TryGetMetadata which returns the above error when submitting multiple languages. When language applicability is used, Content Importer will now use DocumentObj25.RetrieveLanguageMetadata to decide if it needs to Update existing or Create new content objects. [TS-9480|TS-9489|SRQ-2957]
  • Double clicking on a row makes the application crash with Application not found. [ST-8424|TS-9119]
  • Content Importer prepares the title metadata field (FTITLE) for import but will now strip any carriage return (CR) characters that it extracts from the XML <title> value. [TS-7997|SRQ-722|TS-9116]
  • The filemap.xml is built recursively by first inserting all files of a folder in alphabetical order, starting with the to-be-imported root folder, then the folders in alphabetical order. Content Importer now imports files according to the filemap.xml file. [TS-9120|TS-7657|SRQ-1036]
  • The status of imported objects can be changed by using the Post conversion XSL where you specify a metadata XSL file like for example ContentImporter.xsl. Content Importer can now also use @valueType on <ishfield>. [TS-9129|TS-7053]
  • Importing multiple image resolutions (e.g. carwash.png and carwash.eps) resulted in two different logical objects in the repository when the wizard's Back button was used or when you used the re-GUID-ize option. When moving through the wizard the image resolutions will be imported into the same logical object identifier. [TS-9110|TS-9109|TS-9111|SRQ-2544]
  • Content Importer is unable to resolve non-XML objects on <xref>, <link>, <longdescref>. Following the OASIS DITA specification on http://docs.oasis-open.org/dita/v1.2/os/spec/common/theformatattribute.html the @format attribute can be used to determine to which object type an @href is referring to. [TS-8091|TS-9131]
  • Content Importer hangs after conversion when there is an apostrophe ' in a folder name. [TS-7203|SRQ-695]
  • Content Importer does not update or create the import.status after an import. File import.status will be adapted when importing pre-converted files. [TS-9170|TS-9169|SRQ-2610]