This article is an active list of known and fixed issues affecting Typefi Writer users. Not all issues are necessarily posted here, but we'll do our best to update this article in a timely manner.
For information about Typefi support for third-party applications, see Typefi product support lifecycle.
If you are experiencing an issue with Typefi Writer that is not documented here, please contact us.
Known issues
| Issue | Workaround |
|---|---|
|
30 January 2023 If you attempt to open or publish a Word document that contains a variable like {$input:first}, you are presented with the following error: Writer64: Unexpected character encountered while parsing value <. Path “, line 0, position 0. Server File.JsonTSS. When you click OK, you may resume editing. However, the error prevents you from attaching a workflow to an unassigned Word document. |
When opening a Word document, click OK when the error message appears. You may resume editing or publishing. When attaching a workflow, duplicate an existing, attached Word document, then copy and paste the desired content into the duplicated Word document. Alternatively, you may remove the variable with Making template changes and refreshing still works. 3 February 2023 Our team has found the cause of the issue, and it is currently in QA for testing. We apologise for the inconvenience, and we will release a Typefi Server upgrade—version 8.9—to fix this issue soon. |
| Value cannot be null error when trying to publish with Writer 8.7.4. This is an unexpected side-effect of detecting hard- and soft returns in field codes. Some customers have empty fieldcodes. |
Use Tags🠖Show/Hide field codes and look for empty codes that look like {}. Delete these and your job will run. We are working on an 8.7.5 release to fix this issue and are aiming to make this available quickly. |
| Unable to use the Typefi Character style panel to apply styles in Writer 8.7.4 This is an unexpected side-effect of our efforts to prevent the application of paragraph styles to Typefi Tags. |
Use the "regular" Word styles panel instead. We are working on an 8.7.5 release to fix this issue and are aiming to make this available quickly. |
| You receive "Server not responding" errors from Typefi Print Manager when using the 32-bit version of Typefi Writer 8.7.0 |
We have received scattered reports of this issue, and it is related to the Typefi Cloud security update. |
| Multiple index entries referencing the same bookmark does not work as documented and causes job failures. | Requires updates to both Writer and the Microsoft Word plugin. No workaround known at this time. |
| In some environments, Typefi Writer and Microsoft Word may not correctly identify Excel elements within a Word document. As a result, you may not be able to edit Excel elements. | To edit Excel elements:
|
| Microsoft Word automatically translates the names of its built-in styles (for example, English: Heading 1 → Spanish: Título 1) based on the display language setting (File → Options → Language → Display Language), which causes Writer to omit these styles if the translated style name differs from the name used in your Adobe InDesign template. | Rename your InDesign styles to match the translated equivalents for all built-in Microsoft Word styles. |
| Text effects (Outline, Shadow, Reflection, or Glow) are not preserved when converting to Content XML. | Create a character style in the InDesign template. |
| If Create InDesign document uses InDesign Server 2020, 2021 or 2022, you cannot insert a video Element and publish it to PDF. If you try to publish a document with a video Element, you get this error message: Error: Request failed because the underlying functionality is no longer available in the current version of the application. This error occurs because Adobe now blocks Flash content from running. | Adobe will not support Flash in PDF anymore. Use Conditions to add links to video content in your PDF, and actual video in supported formats like EPUB. |
Fixed issues
This table lists recent fixed issues. All fixed issues can be found in the release notes.
| Issue | Fix version |
|---|---|
| In Writer 64-bit 8.7.2 we removed the end tag to the Table of contents. Unfortunately a bug in the DOCX to ContentXML transform causes all sections after the Table of contents to not appear in the output | Typefi Writer 8.7.4 |
If you are using the Utility plugin v16 and your workflow contains Conditions, you may receive a warning Required parameter (Value) is missing when trying to remove a condition from an element that previously had one applied |
Typefi Writer 8.7.4 |
| Cross-reference tags to paragraphs in Typefi Writer 8.7.1 and 8.7.2 do not generate actual cross-references in the output. Typefi Writer 64-bit/32-bit 8.7.0 are not affected. | Typefi Writer 8.7.3 |
| Copying and pasting a Typefi component may cause issues with the Content XML IDs. | Typefi Writer 8.7.2 now regenerates IDs when using CTRL-V for pasting. Pasting via a right-click does not allow us to regenerate IDs. We recommend only using CTRL-V for pasting. Typefi Writer 8.7.2 also has improved ID regeneration using Explore Document |
| When publishing a subset of your Sections, only the last Section is published. | Typefi Writer 8.7.2 |
| When publishing a document with Track Changes turned on, all Typefi Field codes appear as changed, even though the Field Codes weren't changed. | Typefi Writer 8.7.2 |
| When opening a Typefi Writer document, you see a ‘Macros have been disabled’ security warning in a yellow message bar. | Typefi Writer 8.7.2 |
| Long filenames are not visible when editing an Image, Audio, or Video Element via the Edit Element dialogue. | Typefi Writer 8.7.1 |
| When editing an Element Field, the Edit Element dialogue is empty. | Typefi Writer 8.7.1 |
Comments
0 comments
Please sign in to leave a comment.