There was a recent issue that prevented assignments with no context map set from loading. We addressed that and now even when an assignment doesn't have a context map set, it loads as expected.

In the Remedy section of a Troubleshooting Topic, it is now possible to add the steps-unordered and steps-informal elements in the Content Editor by using the Replace Element option.

In a long code block element that has some code bolded, the Content Editor no longer scrolls up when you try editing the code block element. ✅

We addressed a behavior that prevented you from deleting ID attributes in the Attributes tab.

We fixed a recent issue that caused file names and titles to be invisible on smaller screens or when multiple custom columns were added to your Content Library. Now, when you work on a smaller screen or have multiple custom columns enabled, you see file names and titles at all times.

When you create a Source Package with the Only Changed Resources option selected and no changed resources are present for the publication, you now get a notification informing you that the package can't be created due to no changed resources being available for the localization job. 🏖️

When uploading source and, sometimes, XLIFF packages with at least a few locales for a larger, complex publication, sometimes the upload process would stall or fail. We addressed that behavior and now larger, more complex publications upload as expected.

Please note that even with this fix in place, large localization packages with multiple locales might still fail to upload due to the sheer amount of data that needs to be processed in a single upload operation. If you need to upload multiple locales for a large, complex publication, we recommend uploading a couple to a few locales at a time. 📤

When using an XLIFF package for translating files with code block elements, there was an issue that was preventing those files from registering as being translated. That issue is gone now. 🇬🇴🇳🇪 💨

If in your publication there was a file that had code block elements that did not contain a data element or translate attribute, you wouldn't be able to create an XLIFF package for that publication. We've fixed that and now the presence or absence of the data element and translate attribute doesn't affect your ability to create XLIFF Packages. 📦

We addressed an edge case where when using the PDF Generator preview to preview a topic that content-references (conrefs) two phrase elements from one topic, the preview would fail. It no longer does.