Skip to main content

priint:suite - Patch 165 - Change Log

This patch, released on November 13th, 2025, includes ongoing feature enhancements and several bug fixes identified during end-to-end testing. It serves as a final preparation step for the upcoming 4.7 release, improving stability and overall readiness. This patch includes a critical patch for the priint:planner application: Bulk edit document stage erased plannings and templates from documents. The build name on FTP: 4.6.0.918

Software

Windows:
PubServer_Install_Update_4.6.0.918.zip

Linux:
PubServer_Update_4.6.0.918_UbuntuLinux.deb

Release Notes

The Admin application

Issue KeySummaryRelease Notes
ADMIN-2680Apply UI library to Create Role pageApplied the latest UI library build to the Role page.
ADMIN-2701Assigning a new user to a publication and its child items is not working correctlyAssigning users to a publication and its folders/subfolders now works correctly. The checkbox assignment is properly applied across all levels.
ADMIN-2700Bug list for AdminUIUser page: fixed delete and assignment issues; minor UI improvements. Publication Rights: fixed missing tree and sub-folder icons; updated team assignment behavior. Content module: sorting enabled in Text tab; fixed Media Asset validation; improved Bucket handling (reload, icons, dummy data, uncheck behavior); resolved process and panel issues; UI refinements applied.
ADMIN-2686Add "Copy ID and EntityID to clipboard" for content entitiesAdded a context menu action to copy both ID and EntityID for buckets, media assets, links, texts, and key values.
ADMIN-2678Cannot delete unused Publication Types with metadata assignedFixed issue preventing deletion when the publication type had metadata but was not used in any publication.
ADMIN-2677Time and Date metadata default values cannot be savedFixed issue that prevented saving metadata entries when default Time or Date values were set.

The priint:planner application

Issue keySummaryRelease notes
PRIINT-12239Neowise - Publication Window - Cannot assign permissions for FoldersPermissions for Folders can again be correctly assigned.
PRIINT-12224Backport PRIINT-12219 to 4.6When checking out a document template in InDesign, an error ("Error when getting parent of publication of '0'...") was shown. This is fixed.
PRIINT-12209Neowise notes should segregate users by comet project.Neowise notes segregated users by comet project.
PRIINT-12206Parameters are not cleared after changing the search method in Combobox (FlatPlan ->Contenet)Parameters are cleared after changing the plugin method in dynamic UI panel.
PRIINT-12181Change updatedOn field of a document after rendering.Document file (indd or w2ml) check-in now updates the updatedOn date in puc_document.
PRIINT-12071Neowise preview table does not work on full page modeFor a very long or very wide tables, the full-page preview mode did not work as expected. Fixed.
PRIINT-12123Skipping client-side S3 bucket name validations for GCS bucket names with underscoresYou can now opt-out of the client-side bucket name validations of our s3-compatible object-storage client. This should be enough if you plan on using buckets with names that don’t follow s3 guidelines. To skip the validations, set the flag skipBucketNameValidation to equal true both in PubServer’s object storage xml configuration and in rendering-service’s yaml object-storage configuration, see code snippets below
PRIINT-12345Bulk edit document stage erases plannings and templatesBulk edit document stage erased plannings and templates from documents. Solved
<minioConfiguration>
<endpoint>...</endpoint>
<accessKey>...</accessKey>
<secretKey>...</secretKey>
<region>...</region>
<skipBucketNameValidation>true</skipBucketNameValidation>
</minioConfiguration>
priint:
objectstore:
minio:
# By default, our s3 client makes sure bucket naming rules (https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucketnamingrules.html)
# are strictly followed. You can switch that validation off if you plan on using an object storage solution that is more permissive.
# This should come in handy if your GCS buckets use underscores ('_') in their names.
skipBucketNameValidation: true