Release Notes for Studio Server 10

The Release Notes for Studio Server 10 contain information about the new features, changes, fixed issues, known issues, and upgrade instructions for each release of Studio Server 10.

The versions are sorted by version number in descending order. Use the Navigation block to the right of the page to quickly navigate to the information of a released version, or filter the article by version to only show that version.

Studio Server 10.24.0

Studio Server version 10.24.0 build 413

Release date: 7 March 2023

Downloads

New features

Changes

Documentation

Known issues

Fixed issues

Installation

Downloads

The download files for this version of Studio Server can be found in the Release announcement.

New features

No features have been added in this release of Studio Server.

Changes

The following changes have been made in this release of Studio Server:

• Support added for Microsoft SQL Server 2022, support dropped for 2016. Studio Server can now also be used with Microsoft SQL Server 2022, while support for Microsoft SQL Server 2016 has been dropped.

• Improved detection of HTTPS connections. Web servers have several ways of detecting if a connection runs over HTTPS. Studio Server has been relying on the HTTPS attribute. Its detection has now been expanded with the following:
• HTTP_X_FORWARDED_SSL
• HTTP_X_FORWARDED_PROTO
• REQUEST_SCHEME

These are more common for Apache / NGINX Web servers and also detect SSL forwarding, for example by load balancers.

• Deprecated functions have been removed and replaced. The following deprecated functions have been removed and replaced by a new method:

Documentation

The following changes to the documentation have been made in this release of Studio Server:

• Compatibility of Studio Server 10.24 - new
• Upgrading an existing installation of Studio Server - updated

Known issues

The following known issues exist in this release of Studio Server:

• High severity issue found in the external library guzzlehttp/promises in combination with PHP 8.1. An issue has been found in the external library guzzlehttp/promises in combination with PHP 8.1. The issue causes the sending of the Webhooks to fail. We advise customers to use PHP 7.4 in combination with Studio Server 10.23 when the Webhook functionality is used. A fix for this issue is planned for Studio Server 10.25 (mid April).

• The Server plug-ins Maintenance page appears blank or shows an error. Studio Server provides a tool to generate connector files for custom plug-ins. How it works is described in the Enterprise/config/plugin-templates/readme.txt file. For PHP 8.1, no connector file is generated for the following connectors:

• DbModel_EnterpriseConnector
• CustomObjectMetaData_EnterpriseConnector

When un-commenting these connectors in the PluginInfo.php file and subsequently accessing the Server plug-ins Maintenance page, the page appears blank or the following error appears: 'The plug-in contains errors. Please repair and refresh the Server Plug-ins page to reload your fixes. (S1120)'.

Fixed issues

The following issues have been fixed in this release of Studio Server:

WSS-13332 Make the UpdateProgress event work for RabbitMQ.

Installation

Choose one of the following installation paths:

• Installing Studio Server on a system on which it is not yet installed
• Upgrading an existing installation of Studio Server
• Upgrading from Enterprise Server

Studio Server 10.23.0

Studio Server version 10.23.0 build 411

Release date: 14 February 2023

Downloads

New features

Changes

Documentation

Known issues

Fixed issues

Installation

Downloads

The download files for this version of Studio Server can be found in the Release announcement.

New features

No features have been added in this release of Studio Server.

Changes

The following changes have been made in this release of Studio Server:

• Changes to the compatibility with other systems. Various changes to the compatibility of Studio Server with other systems have been made. These are listed in the following table.

• Assets Server integration: Re-archived Digital articles are now archived in their own folder. When archiving a Digital article from Studio, restoring it and archiving it again, previous versions of Studio Server always archived the article within the folder that was used when first archiving the article. This could make a re-archived article more difficult to find, for example when it is used in a different Brand compared to the article that was first archived. Now, the re-archived article is always stored in its own folder.

• PHP 8: The php_gd2.dll file on Windows has been renamed. In PHP 8.x, the following file that is required for integrating PHP with Studio Server has been renamed:
• Old name: php_gd2.dll
• New name: php_gd.dll

This file is referred to in the steps for integrating PHP with Studio Server on Windows.

• PHP 8: The class \Match has been renamed to \Compare. Calls to methods of the Match class (such as in custom plug-ins) have to be replaced to calls to the methods of the Compare class. Method names have not changed.

• Error logging: The ent_log_errors.htm file now also logs messages of type 'DEPRECATED'. When messages are written to the ent_log_errors.htm file, messages of type 'DEPRECATED' are now also logged. This makes it more visible that the affected feature is scheduled to be deprecated and that steps should be taken to phase out the use of that feature.

• Error logging: Health Check tests now use the log level of the DEBUGLEVEL option instead of the log level of the acting user. When running tests on the Health Check page and log files are required for further assistance or analysis, it is advisable to set the log level in the DEBUGLEVELS option while setting the log level on the User Maintenance page for the user defined in the TESTSUITE option to NONE. Should the log level in the TESTSUITE option still be set, this is now ignored and the log level of the DEBUGLEVEL option is now always used.

This makes the results more predictable and avoids inconsistencies between the test items when different log levels are configured for the TESTSUITE user and the general DEBUGLEVELS option.

• Functions have been deprecated and replaced. The following function has been deprecated and replaced by a new method which provides better performance.

• Localization: French translations of 'uploading' have been changed to 'envoyer'. To better match the real-world use of the French translation of 'uploading', all references (such as 'télécharger') have been changed to 'envoyer'.

Note: Similar changes have been made to references in Studio. To see these changes, Studio 11.136 or higher is required.

Documentation

The following changes to the documentation have been made in this release of Studio Server:

• Compatibility of Studio Server 10.23 - new
• Upgrading an existing installation of Studio Server - updated
• Installing and configuring PHP for use with Studio Server - updated
• Studio Server full installation - updated
• Logging server activity in Studio Server 10.14 or higher – Concept - updated

Known issues

The following known issues exist in this release of Studio Server:

• High severity issue found in the external library guzzlehttp/promises in combination with PHP 8.1. An issue has been found in the external library guzzlehttp/promises in combination with PHP 8.1. The issue causes the sending of the Webhooks to fail. We advise customers to use PHP 7.4 in combination with Studio Server 10.23 when the Webhook functionality is used. A fix for this issue is planned for Studio Server 10.25 (mid April).

• The Server plug-ins Maintenance page appears blank or shows an error. Studio Server provides a tool to generate connector files for custom plug-ins. How it works is described in the Enterprise/config/plugin-templates/readme.txt file. For PHP 8.1, no connector file is generated for the following connectors:

• DbModel_EnterpriseConnector
• CustomObjectMetaData_EnterpriseConnector

When un-commenting these connectors in the PluginInfo.php file and subsequently accessing the Server plug-ins Maintenance page, the page appears blank or the following error appears: 'The plug-in contains errors. Please repair and refresh the Server Plug-ins page to reload your fixes. (S1120)'.

Fixed issues

The following issues have been fixed in this release of Studio Server:

WSS-8141 When generating a PDF for a Print article in Studio after changing its Editions in InDesign, the process is never completed.

WSS-10651 'This application cannot be launched because you do not have sufficient access rights (S1077)' message shown when logging in to Studio Server using the full user name.

WSS-12328 Too much information is requested by Studio when dragging an image from Assets to Studio.

WSS-12919 Using the 'Copy layout' option in Studio does not work correctly when all Editions in the layout are selected.

WSS-13246 Change French translation of 'uploading' to 'envoyer'.

Installation

Choose one of the following installation paths:

• Installing Studio Server on a system on which it is not yet installed
• Upgrading an existing installation of Studio Server
• Upgrading from Enterprise Server

Studio Server 10.22.0

Studio Server version 10.22.0 build 407

Release date: 12 January 2023

Downloads

New features

Changes

Documentation

Known issues

Fixed issues

Installation

Downloads

The download files for this version of Studio Server can be found in the Release announcement.

New features

No features have been added in this release of Studio Server.

Changes

The following changes have been made in this release of Studio Server:

• Functions that were already deprecated are now logged as DEPRECATED. The functions listed below were deprecated in earlier versions of Studio Server because a newer function is preferred for a better performance. Calling these functions will now result in a DEPRECATED message in the log files.

• Additional functions have been deprecated. The functions listed below have been deprecated. Calling these functions will result in a DEPRECATED message in the log files. These functions were deprecated because a newer function is preferred for a better performance. They will be removed in a future version of Studio Server.

Documentation

The following changes to the documentation have been made in this release of Studio Server:

• Compatibility of Studio Server 10.22 - new

Known issues

No known issues exist for this release of Studio Server.

Fixed issues

The following issues have been fixed in this release of Studio Server:

WSS-12706 InDesign Server configuration is not updated by the InDesign Server Health Check test when no high-prio jobs are configured.

WSS-12938 The validatecontact.js.php file prevents setting the X-Content-Type-Options setting in the httpd.conf file to 'nosniff'.

Installation

Choose one of the following installation paths:

• Installing Studio Server on a system on which it is not yet installed
• Upgrading an existing installation of Studio Server
• Upgrading from Enterprise Server

Studio Server 10.21.0

Studio Server version 10.21.0 build 405

Release date: 15 December 2022

Downloads

New features

Changes

Documentation

Known issues

Fixed issues

Installation

Downloads

The download files for this version of Studio Server can be found in the Release announcement.

New features

No features have been added in this release of Studio Server.

Changes

The following changes have been made in this release of Studio Server:

• Removal of the Laminas Console and Laminas CLI libraries. As part of preparing Studio Server for upcoming versions of PHP, the following has been removed from the server/vendor folder:
• The Laminas Console. This console is deprecated (and discontinued in PHP 8) and usages in Studio Server are replaced by the Symfony Console library.
• The Laminas CLI libraries. These libraries are no longer used by Studio Server.

Custom server plug-ins that rely on the presence of any PHP classes defined in these libraries must be updated to remain compatible with Studio Server.

Documentation

The following changes to the documentation have been made in this release of Studio Server:

• Compatibility of Studio Server 10.21 - new
• Upgrading an existing installation of Studio Server - updated

Known issues

No known issues exist for this release of Studio Server.

Fixed issues

The following issues have been fixed in this release of Studio Server:

WSS-13183 Previewing an article may fail when the article workspace on the server was deleted too soon.

Installation

Choose one of the following installation paths:

• Installing Studio Server on a system on which it is not yet installed
• Upgrading an existing installation of Studio Server
• Upgrading from Enterprise Server

Studio Server 10.20.0

Studio Server version 10.20.0 build 404

Release date: 17 November 2022

Downloads

New features

Changes

Documentation

Known issues

Fixed issues

Installation

Downloads

The download files for this version of Studio Server can be found in the Release announcement.

New features

No features have been added in this release of Studio Server.

Changes

The following changes have been made in this release of Studio Server:

• Stored user settings can now be reset for Studio users who cannot log in anymore because of corrupted settings. Users of Smart Connection, Studio, and Studio for InDesign and InCopy can store settings for search filters, panels, column settings, and more. In some cases, these settings can get corrupted which prevents Studio users from logging in to Studio.

This can now be resolved by resetting these settings to their default state by clicking Reset Stored Settings on the User Maintenance page of the user in Studio Server.

For details, see Managing user accounts in Studio Server. Note that this also resets the settings for the users of Studio for InDesign and InCopy, and users of Smart Connection.

• When logging server activity, the full stack of calling functions can now also logged. When an alert is logged, by default only the error message itself is logged. Now, the full stack of calling functions can also be logged, thereby providing much more information about the cause of the error.

This can be done by configuring the following option:

• Option: LOG_STACK_ON_ALERT
• File: configserver.php file (recommended: config_overrule.php file)
  
  
• Possible value:
• null. Default value. Stacks are included in the log file on alerts when the applied log level is set to DEBUG.
• true. Stacks are included in the log file on alerts, regardless of the applied log level.
• false. Stacks are never included in the log file.
• Default value: null
• Example:

define( 'LOG_STACK_ON_ALERT', null );

For full details, see Logging server activity in Studio Server 10.14 or higher – Configuration.

• Server methods have been removed or marked as deprecated as part of improving Studio Server performance. To improve performance, the following BizClasses methods have been removed or marked as deprecated:

Documentation

The following changes to the documentation have been made in this release of Studio Server:

• Compatibility of Studio Server 10.20 - new
• Managing user accounts in Studio Server - updated
• Logging in to Studio - updated
• Logging server activity in Studio Server 10.14 or higher – Configuration - updated

Known issues

No known issues exist for this release of Studio Server.

Fixed issues

The following issues have been fixed in this release of Studio Server:

WSS-12242 MySQL - Database Upgrade script fails for database names with a dash.

WSS-12987 Make it possible to reset user preferences to resolve issues with corrupted user settings.

WSS-13070 Performance: Improve execution time of filtered searches without losing performance on searches that are not filtered.

WSS-13105 Add a configuration option for logging stacks.

Installation

Choose one of the following installation paths:

• Installing Studio Server on a system on which it is not yet installed
• Upgrading an existing installation of Studio Server
• Upgrading from Enterprise Server

Studio Server 10.19.0 build 401 Quick Patch

Studio Server version 10.19.0 build 401

Release date: 1 November 2022

Downloads

Fixed issues

Installation

Downloads

The download files for this version of Studio Server can be found in the Release announcement.

Fixed issues

The following issues have been fixed in this release of Studio Server:

WSS-13153 Performance: Improve execution time of filtered searches without losing performance on searches that are not filtered.

Note: This performance degradation was observed when upgrading to Studio Server 10.16 or later. The level of degradation depended on several factors and could cause severe performance issues in some environments.

Installation

Choose one of the following installation paths:

• Installing Studio Server on a system on which it is not yet installed
• Upgrading an existing installation of Studio Server
• Upgrading from Enterprise Server

Studio Server 10.19.0

Studio Server version 10.19.0 build 399

Release date: 20 October 2022

Downloads

New features

Changes

Documentation

Known issues

Fixed issues

Installation

Downloads

The download files for this version of Studio Server can be found in the Release announcement.

New features

No features have been added in this release of Studio Server.

Changes

The following changes have been made in this release of Studio Server:

• The maximum number of characters of the 'Description' property of a file has been raised to 10,000. The maximum number of characters that can be stored in the 'Description' property of a file has been raised from 2,040 to 10,000 characters. This brings it in line with the number or characters that the same property in Assets Server can hold.

• Assets Server integration: The 'Page' property now stores the 'page order' value of the page on which a file is placed instead of the 'page number' value. When placing a file from the Production Zone in Assets Server onto a layout, the 'page order' value is now stored in the Page property. In previous versions, the 'page number' value was stored.

• Archiving to Assets Server: During archiving, the 'Page range' property is now populated for all articles, images, spreadsheets, and adverts that are placed on a layout. When archiving a layout and its placed objects, all articles, images, spreadsheets, and adverts that are placed on a layout now have the 'Page range' property populated. In previous versions, this property was only populated for the layout and its PDF or EPS files. The value used is the 'Page (order)' value of the page on which the object is placed.

Note for upgraded systems with an Assets Server integration: The page range value for objects that were archived before the upgrade to Studio Server 10.19.0 remains empty. Only objects that are archived using Studio Server 10.19.0 or higher will have this property populated.

Documentation

The following changes to the documentation have been made in this release of Studio Server:

• Compatibility of Studio Server 10.19 - new
• Metadata mapping between Studio Server and Assets Server - updated

Known issues

No known issues exist for this release of Studio Server.

Fixed issues

The following issues have been fixed in this release of Studio Server:

WSS-11752 When placing an article component on a layout on which it is already placed, no warning is given when the layout only contains one Edition.

WSS-11955 Preview optimizations: Reduce the requestInfo call for a login request in the IDPreview.jsx file.

WSS-12954 Unable to deactivate an SSO-user.

WSS-12984 Performance: Too many SQL statements are called to retrieve Workflow Statuses.

WSS-12986 Performance: Too many SQL statements are called for save layout operations to resolve duplicate placements.

WSS-13011 Performance: Too many SQL statements are called for save layout operation to determine placed relations to be deleted.

WSS-13044 Extend the 'Description' field of a file to 10,000 characters.

Installation

Choose one of the following installation paths:

• Installing Studio Server on a system on which it is not yet installed
• Upgrading an existing installation of Studio Server
• Upgrading from Enterprise Server

Studio Server 10.18.0

Studio Server version 10.18.0 build 398

Release date: 8 September 2022

Downloads

New features

Changes

Documentation

Known issues

Fixed issues

Installation

Downloads

The download files for this version of Studio Server can be found in the Release announcement.

New features

No features have been added in this release of Studio Server.

Changes

The following changes have been made in this release of Studio Server:

• Centralized logging: The fields structure now only supports the ECS standard. With the introduction of centralized logging in Studio Server 10.14.0, the structure for the ECS fields was unfortunately not respecting the ECS standard and therefore implemented incorrectly.

As a result, the field names were logged in a flat concatenated structure instead of a hierarchical structure as defined by the ECS standard.

Support for the new ECS field structure was then added to Studio Server 10.14.1, together with the LOG_CENTRALIZED_CONCATENATED_ECS_FIELDS option which made it possible to temporarily use the old/incorrect structure and to update the 3rd-party logging monitoring system to the new structure at a later point.

Now, only the new ECS field structure is supported. The LOG_CENTRALIZED_CONCATENATED_ECS_FIELDS option has therefore been removed.

When upgrading from a previous version in which this option is still set in the config_overrule.php file or configserver.php file, the 'PHP' Health Check test will give a warning. In case the 3rd-party logging monitoring system is not adjusted to the new field structure, note that the monitoring system will not work; the logs will not appear as expected.

• Updated database definition for improved performance. When upgrading from a previous version of Studio Server, the database definition is updated. This change is required to improve the performance of Studio Server. The 'Database' test on the Health Check page will show a notification that the update has been implemented; no action is required.

• Server methods/functions: Improvement in performance by removing and/or replacing Inefficient BizClasses methods. To improve performance, the following BizClasses methods have been removed and where possible replaced by methods that are more efficient and require less database access:

Documentation

The following changes to the documentation have been made in this release of Studio Server:

• Compatibility of Studio Server 10.18 - new

Known issues

No known issues exist for this release of Studio Server.

Fixed issues

The following issues have been fixed in this release of Studio Server:

WSS-12687 Performance: Opening the 'Inbox' and the 'Checked-out files' pages in Studio is very slow.

WSS-12702 Performance: Drop-down lists in the Create dialog take a long time to populate.

WSS-12887 Security: Update the guzzlehttp/guzzle package.

WSS-12982 Performance: 32 SQL statements are called for Create and Save operations to validate the Status and Category.

WSS-12992 An object can be created in a Workflow Status that is configured for a different object type in the same Brand.

WSS-12997 Migration script is failing because some fields in old databases are using Full User Name instead of the Short User Name.

WSS-13016 Performance: improve the LogOn Service - getPublicationInfos process.

Installation

Choose one of the following installation paths:

• Installing Studio Server on a system on which it is not yet installed
• Upgrading an existing installation of Studio Server
• Upgrading from Enterprise Server

Studio Server 10.17.0

Studio Server version 10.17.0 build 396

Release date: 11 August 2022

Downloads

New features

Changes

Documentation

Known issues

Fixed issues

Installation

Downloads

The download files for this version of Studio Server can be found in the Release announcement.

New features

No features have been added in this release of Studio Server.

Changes

The following changes have been made in this release of Studio Server:

• Support for Solr 7 has been dropped. Support for Solr 7.7 has been dropped in Studio Server 10.17; this version of Solr has reached its end of life some time ago. Supported versions of Solr for Studio Server 10.17 are 8.8 and 8.11. Solr indexes any file in the system for quick access whenever a search is performed.

• Validation added for users with duplicate e-mail addresses. In Studio Server, users are identified by using the values of their name, full name, and e-mail address. When multiple users exist in the system with the same e-mail address, the user settings can become corrupted (especially when used in combination with Single Sign-On or LDAP). The e-mail address of each user in the system should therefore be unique. To prevent user accounts from becoming corrupted because of duplicate e-mail addresses, the following is now done:
• When adding an email-address that is already used by another user to a new or existing user, a message is shown to indicate this.
• The 'Authentication' test on the Health Check page now provides a warning when multiple users with the same e-mail address are detected.

• RabbitMQ repair operations are now mentioned in the Health Check test. When a repair operation for RabbitMQ was required in previous versions of Studio Server (such as when creating a missing RabbitMQ virtual host), the operation was performed but no notification was given. Now, when such an action is performed, a notification is given as part of the 'Messaging (RabbitMQ)' test.

Documentation

The following changes to the documentation have been made in this release of Studio Server:

• Compatibility of Studio Server 10.17 - new
• Managing user accounts in Studio Server - updated
• Integrating LDAP in Studio Server - updated
• Implementing single sign-on in Studio Server using Amazon Cognito - updated
• Implementing single sign-on in Studio Server using Okta - updated

Known issues

No known issues exist for this release of Studio Server.

Fixed issues

The following issues have been fixed in this release of Studio Server:

WSS-12888 Health Check: Multi-byte test fails to connect to RabbitMQ when running it the first time.

WSS-12289 LDAP Users with same email-address get corrupted.

Installation

Choose one of the following installation paths:

• Installing Studio Server on a system on which it is not yet installed
• Upgrading an existing installation of Studio Server
• Upgrading from Enterprise Server

Studio Server 10.16.0

Studio Server version 10.16.0 build 394

Release date: 19 July 2022

Downloads

New features

Changes

Documentation

Known issues

Fixed issues

Installation

Downloads

The download files for this version of Studio Server can be found in the Release announcement.

New features

The following has been added in this release of Studio Server:

• Support for Solr 8.11. Studio Server 10.16.0 now also supports Solr 8.11. Solr indexes any file in the system for quick access whenever a search is performed.

Changes

The following changes have been made in this release of Studio Server:

• Assets Server integration: deleted users are recreated when restoring a file. When restoring an archived file from Assets Server to Studio Server, any users associated with the file that were removed from Studio Server are recreated as deactivated users. This is because users that are part of the workflow (for example as the user who created, modified, or deleted the file) have to exist as a user in the system. Deactivated users are hidden by default on the Overview of Users Maintenance page, but can be shown again by clicking 'Show Deactivated Users' at the bottom of the page.

• Assets Server integration: Database change related to removed users when restoring files on Studio Server 10.15. Since Studio Server 10.15, users or user groups that are still part of the workflow (for example as the user who created, modified, or deleted the file) cannot be deleted anymore. When upgrading from Studio Server versions older than Studio Server 10.15, objects could exist that had a user associated with it that no longer existed in the system. The upgrade process of Studio Server 10.15 therefore restored all removed users that were still part of the workflow. However, when restoring an archived file from Assets Server to Studio Server 10.15, such a process was not in place and therefore still resulted in a file with an associated user that did not exist in the system.

When upgrading from Studio Server 10.15 to 10.16, a check is done for removed users and corrected when found. This check is performed by the 'Database Connection' Health Check test which will direct you to the Database Setup page on which the update can be run.

Note: The update needs to be run on each Studio Server 10.15 system that is upgraded, even when no files have been restored or Assets Server is not integrated.

During this process, all removed users and user groups that are still part of the workflow are recreated as deactivated users (note that user groups are also recreated as users). As mentioned above, deactivated users are hidden by default on the Overview of Users Maintenance page, but can be shown again by clicking 'Show Deactivated Users' at the bottom of the page.

Documentation

The following changes to the documentation have been made in this release of Studio Server:

• Compatibility of Studio Server 10.16 - new
• Archiving files from Studio Server 10.13.1 or higher to Assets Server - updated

Known issues

The following issues exist for this release of Studio Server:

• Upgrading from Studio Server version 10.13 or lower fails. When upgrading from Studio Server version 10.13 or lower, the upgrade fails with the following error:

Database upgrade failed

The log files will show the following error:

ERROR    mysql           MySQL: 1054:Unknown column 'loglevel' in 'field list'
WARN     BizException    Message: Error: Failed to insert the user in the database.

These errors are caused by an upgrade script that recreates non-existing users; it expects specific database fields which are not yet present at that time.

To resolve this, do one of the following:

• First upgrade to Studio Server 10.14.x and then to version 10.16.0.

• Update the following script:

<your server>/server/dbscripts/dbupgrades/RecreateMissingWorkflowUsers.class.php

by changing the beforeUpdateModel method to return false. The method can be found on line number 58; the end result looks as follows:

public function beforeUpdateModel(): bool
{
	return false;
}

• Archiving from Studio Server to Assets Server: When archiving a Digital article, the following fields are populated but cannot yet be shown in the Metadata panel in Assets:
• Character count
• Line count
• Paragraph count

This requires an update in Assets Server and will be available in a future release of Assets Server.

Fixed issues

The following issues have been fixed in this release of Studio Server:

WSS-12802 Slow search performance when the user has no Brand or type selected.

Installation

Choose one of the following installation paths:

• Installing Studio Server on a system on which it is not yet installed
• Upgrading an existing installation of Studio Server
• Upgrading from Enterprise Server

Studio Server 10.15.0

Studio Server version 10.15.0 build 391

Release date: 21 June 2022

Downloads

New features

Changes

Documentation

Known issues

Fixed issues

Installation

Downloads

The download files for this version of Studio Server can be found in the Release announcement.

New features

The following has been added in this release of Studio Server:

• Support for RabbitMQ 3.9. Studio Server 10.15.0 now also supports RabbitMQ 3.9.
  
  (With RabbitMQ integrated in Studio Server, message notifications — such as when a user updates the properties of a file — can be pushed to client views of all users who are connected to Studio Server. This ensures that users immediately see the changes that other users make.)

• Deactivated users can now be hidden. Should the list of users on the Overview of Users Maintenance page contain deactivated users, these deactivated users can now be hidden or shown using the 'Hide Deactivated Users' and 'Show Deactivated Users' options at the bottom of the page.

Note: Deactivated users are hidden by default.

• Additional metadata fields are now populated when archiving from Studio Server to Assets Server. When archiving files from Studio Server to Assets Server, various metadata fields are populated with information that describes how and where the file was used in Studio Server. Many fields were already populated, but the following Assets Server fields are now included as well:
• copyright
• credit
• edition
• issueIdentifier
• issueName
• numberOfCharacters
• numberOfLines
• numberOfParagraphs
• pageRange
• publicationChannel
• publicationName
• section
• wordCount

If and when a field is populated depends on the archive schema that is used (digital, Dossier, or print schema) and the type of file. For more information, see Metadata mapping between Studio Server and Assets Server.

Changes

The following changes have been made in this release of Studio Server:

• Codes used in the ticket tracking system have been changed from 'EN' to 'WSS'. Historically, tickets for tracking bugs and improvements for the server started with 'EN-' (short for 'Enterprise'). With the renaming of the product to Studio Server some time ago, 'EN-' has now been changed to 'WSS-' (short for WoodWing Studio Server).

All tickets related to Studio Server will therefore now start with 'WSS-'. In addition, all existing tickets that started with 'EN-' have also been changed to 'WSS-'. For this, new tickets had to be created. This also means that the original number has changed (for example: 'EN-12345' could now be 'WSS-67890').

Note: Apart from the change in the codes, the rest of the ticket handling process has not changed. If you have submitted an 'EN' ticket which has now been renamed to 'WSS' and renumbered, you will of course still receive notifications for that ticket.

• Users and user groups that are still associated with an object can no longer be deleted. When a user or user group is still associated with a workflow object in Studio Server, it can no longer be deleted. These associations are:
• Users who are listed as the person who has created, modified, or deleted an object.
• Users who have locked an object.
• Users or user groups who have objects routed to them.

When trying to delete such a user or user group, a message is now shown. To resolve the issue, the user should be deactivated, or the objects should be removed from being routed to the user group.

For more information, see:

• Managing user accounts in Studio Server
• Managing user groups in Studio Server

• Database change related to removed users that are still part of the workflow. Studio Server 10.15 and higher prevents deleting users or user groups that are still part of the workflow (see above). For existing systems that have been upgraded, objects can exist that have a user or user group associated with it that no longer exists in the system. To prevent issues that this can cause in the system and as a first step to future optimizations, the database needs to be updated.

This is done as part of the upgrade process by running the Health Check tests. The 'Database Connection' test will now fail and direct you to the Database Setup page on which the update can be run.

During this process, all removed users and user groups that are still part of the workflow are recreated as deactivated users (note that user groups are also recreated as users). As mentioned above, deactivated users are hidden by default on the Overview of Users Maintenance page, but can be shown again by clicking 'Show Deactivated Users' at the bottom of the page.

• Removal of obsolete Solr facet settings from the code. In Content Station, Solr facets were used for grouping search results. With the discontinuation of Content Station some time ago, the Solr facet settings listed below that were still present in the code have now been removed.

Note: The ‘Solr Search Server’ Health Check will give a warning if any of these settings are still used.

• SOLR_ARTICLE_FACETS
• SOLR_AUDIO_FACETS
• SOLR_DOSSIERITEMS_FACETS
• SOLR_GENERAL_FACETS
• SOLR_IMAGE_FACETS
• SOLR_INTEGER_RANGE
• SOLR_LAYOUT_FACETS
• SOLR_LENGTHCHARS_RANGE
• SOLR_LENGTHLINES_RANGE
• SOLR_LENGTHWORDS_RANGE
• SOLR_RATING_RANGE
• SOLR_SPREADSHEET_FACETS
• SOLR_VIDEO_FACETS

• Upgrade of JavaScript libraries. The following JavaScript libraries have been upgraded to make use of the security and performance improvements that these versions provide:

Documentation

The following changes to the documentation have been made in this release of Studio Server:

• Compatibility of Studio Server 10.15 - new
• Managing user accounts in Studio Server - updated
• Managing user groups in Studio Server - updated
• Metadata mapping between Studio Server and Assets Server - updated

Known issues

The following issues exist for this release of Studio Server:

• Upgrading from Studio Server version 10.13 or lower fails. When upgrading from Studio Server version 10.13 or lower, the upgrade fails with the following error:

Database upgrade failed

The log files will show the following error:

ERROR    mysql           MySQL: 1054:Unknown column 'loglevel' in 'field list'
WARN     BizException    Message: Error: Failed to insert the user in the database.

These errors are caused by an upgrade script that recreates non-existing users; it expects specific database fields which are not yet present at that time.

To resolve this, do one of the following:

• First upgrade to Studio Server 10.14.x and then to version 10.15.0.

• Update the following script:

<your server>/server/dbscripts/dbupgrades/RecreateMissingWorkflowUsers.class.php

by changing the beforeUpdateModel method to return false. The method can be found on line number 58; the end result looks as follows:

public function beforeUpdateModel(): bool
{
	return false;
}

• Archiving from Studio Server to Assets Server: When archiving a Digital article, the following fields are populated but cannot yet be shown in the Metadata panel in Assets:
• Character count
• Line count
• Paragraph count

This requires an update in Assets Server and will be available in a future release of Assets Server.

Fixed issues

The following issues have been fixed in this release of Studio Server:

WSS-11549 Upgrade jQueryUI 1.12.1 to 1.13.1.

WSS-11550 Upgrade to jQuery 3.5.1 / jsTree 3.3.10.

WSS-11931 InDesign Server jobs fail when a user that has last modified the layout has been deleted.

WSS-12311 When copying a Brand and leaving the Brand name empty, nothing happens when clicking Copy to create the Brand.

WSS-12674 After a database upgrade and with DEBUG enabled, users are unable to log in (Uncaught throwable "TypeError").

WSS-12686 Having a large number of Brands configured impacts authorization checks made by workflow services.

WSS-12700 Studio Server integration: Some fields under the 'Publication' section are not populated for the archived objects in Assets.

WSS-12701 Unexpected search results when sorting columns when files include layouts that are flagged.

WSS-12768 Security: Prevent using the FILTER_VALIDATE_FLOAT filter

WSS-12804 LDAP users are unable to log in after a server upgrade (Uncaught throwable "TypeError").

Installation

Choose one of the following installation paths:

• Installing Studio Server on a system on which it is not yet installed
• Upgrading an existing installation of Studio Server
• Upgrading from Enterprise Server

Studio Server 10.14.1

Studio Server version 10.14.1 build 380

Release date: 21 April 2022

Downloads

New features

Changes

Documentation

Known issues

Fixed issues

Installation

Downloads

The download files for this version of Studio Server can be found in the Release announcement.

New features

No features have been added in this release of Studio Server.

Changes

The following changes have been made in this release of Studio Server:

• Assets Server integration: metadata fields 'Page range' and 'Publication date' are now also stored when archiving a layout. When archiving files from Studio Server to Assets Server, values from various metadata fields are stored. When a layout is archived, the values from the following metadata fields are now also stored:
• Page range
• Publication date

• Centralized logging: Option added for configuring the used ECS field structure. With the introduction of centralized logging in Studio Server 10.14.0, the structure for the ECS fields was unfortunately not respecting the ECS standard and therefore implemented incorrectly.

As a result, the field names were logged in a flat concatenated structure instead of a hierarchical structure as defined by the ECS standard.

Because implementing the correct structure would break existing installations, the LOG_CENTRALIZED_CONCATENATED_ECS_FIELDS option has been introduced. It is used for matching the configuration of your 3rd-party logging monitoring system:

• It should be enabled when the old/incorrect structure of the ECS field is used.
• It should be disabled when the new/correct structure of the ECS field is used.

Possible values:

• true - Default value. The old/incorrect structure of the ECS field is used.
• false - Recommended value. The new/correct structure of the ECS field is used.

if( !defined('LOG_CENTRALIZED_CONCATENATED_ECS_FIELDS') ) {
define( 'LOG_CENTRALIZED_CONCATENATED_ECS_FIELDS', true );
}

Documentation

The following changes to the documentation have been made in this release of Studio Server:

• Metadata mapping between Studio Server and Assets Server - updated

Known issues

No known issues exist for this release of Studio Server.

Fixed issues

The following issues have been fixed in this release of Studio Server:

EN-93684 When the order number of Issues is set to zero, the sorting order is set alphabetically in Studio Server but not in the client applications.

EN-93997 solrconfig.xml file: The comment for setting the 'mm' value contains an incorrect example.

EN-94114 Health Check: PHP errors in the Server Plug-ins test when a plug-in does not provide connectors.

EN-94159 User names appear multiple times in the Username list when configuring a Studio Server Job.

EN-94178 Logging: Replacing an image in Studio is incorrectly logged as a Warning.

EN-94216 Upgrading: Database error because of a duplicate alter table statement.

EN-94402 The ionCube Loader Wizard fails for PHP 7.4.

EN-94414 Studio panel in Studio for InDesign and InCopy is not updated when replacing an article or image in Studio.

EN-94446 Searching: Sorting On 'Dimensions' in Studio results in an empty view and an error in the log file.

EN-94455 LDAP/AD: Admin user needs to be included in Brand authorizations to get access to the Admin Maintenance pages.

EN-94475 LDAP/AD: User with a comma in the name cannot log on.

EN-94495 Archiving: Using a Custom property as the place holder for including the year and month in a folder name in the Archive Zone is no longer working.

EN-94561 MadeToPrint: The Route To field for a file is not set, even though automatic routing is enabled.

EN-94563 Assets: Custom metadata is cleared in Assets after synchronization by Studio.

EN-94584 Studio: Using a forward slash ('/') in a tag results in two tags instead of one.

EN-94614 New message event ObjectFlagCleared causes an exception in the Studio plug-ins.

EN-94653 After copying a layout, a warning 'Trying to get property 'Format' of non-object' is added to the log files.

EN-94675 Mandatory Dossier field can be bypassed when creating a new article in Studio.

EN-94796 Search: Using an empty 'Route To' option in the search filter returns zero results.

EN-94774 MadeToPrint: Allow customization to cater for multiple Status IDs and manipulate the Edition ID.

EN-94881 Assets Server integration: Publication Date and Page Range metadata fields are not stored when archiving a layout.

EN-94887 Solr: QueryObjects for a publication and type will list all workflow states of the system in the Solr request.

EN-94971 MadeToPrint: No subsequent job is triggered when a processed job sets a status and a job exists for that status.

EN-95028 Studio Print editor: 'Access denied' error and no layout preview is shown when the user does not have Write access to a layout and an image is placed on the layout and added to Studio.

EN-95040 LDAP: The 'EXCLUDE_USERNAME' option incorrectly excludes users.

EN-95055 Maintenance pages: Full user name not shown at the bottom of the menu when accessing the User Maintenance page.

EN-95184 Security: Hide sensitive HTTP header content in the phpinfo.htm file.

EN-95186 Maintenance pages: The value for OPENID_CLIENT_SECRET is not obfuscated.

EN-95214 Logging: Improve Studio Server logging to make it more compatible with Cloudwatch.

EN-95239 Security: login credentials are leaked via the phpinfo.htm file.

EN-95323 Security: An error message is not sanitized before displaying, thereby making it sensitive for an XSS-attack.

EN-95404 Upgrade guzzlehttp/psr7 to version 1.8.5 to avoid vulnerabilities found in the package.

Installation

Choose one of the following installation paths:

• Installing Studio Server on a system on which it is not yet installed
• Upgrading an existing installation of Studio Server
• Upgrading from Enterprise Server

Studio Server 10.14.0

Studio Server version 10.14.0 build 373

Release date: 13 January 2022

Downloads

New features

Changes

Documentation

Known issues

Fixed issues

Installation

Downloads

The download files for this version of Studio Server can be found in the Release announcement.

New features

The following features have been added in this release of Studio Server:

• Compatibility with Adobe 2022. Studio Server 10.14.0 or higher is compatible with Adobe 2022.

Note: This requires Studio for InDesign, InDesign Server and InCopy for Adobe 2022 (planned release Q1 of 2022).

• Improvements to server logging. To improve the functionality of logging server activity, the following has been added:

• Log files can now be output or streamed to a central location. When multiple instances of Studio Server are used, errors, warnings and information about the use of deprecated features can now be logged in a central location outside of Studio Server. This makes it easier and more efficient to detect problems from multiple servers from just one location.

• Controlling the logging detail for an individual user via the User Maintenance page. When server logging is used for investigating technical issues that a user experiences, the level of detail to log can now be controlled via the User Maintenance page for that user. This is done by setting any of the DEBUGLEVEL options (ERROR, WARN, INFO, or DEBUG) in the new Log Level field.

This has the following advantages:

• It prevents having to configure the log level in the configserver.php file to which few people have access.
• The generated log files are smaller in size and contain only data based on the actions performed by the user. The data is thereby more relevant and easier to analyze.

• New loglevel field in the smart_users table. To support the new Log Level field on the User Maintenance page, a new field named 'loglevel' has been added to the smart_users table. User logging is set to NONE by default, including when upgrading to Studio Server 10.14.0.

• LogLevel has been added to the Admin WSDL. Integrators using the admin web services can define the log level for a user in the SmartConnectionAdmin.wsdl file. A 'LogLevel' option has been added to the 'User'. Affected web services such as Create/Modify/Get/Copy-users will now have a 'LogLevel' item: Users[]->LogLevel.

<xsd:simpleType name="LogLevel">
    <xsd:restriction base="string">
        <xsd:enumeration value="NONE"/>
        <xsd:enumeration value="ERROR"/>
        <xsd:enumeration value="WARN"/>
        <xsd:enumeration value="DEPRECATED"/>
        <xsd:enumeration value="INFO"/>
        <xsd:enumeration value="DEBUG"/>
    </xsd:restriction>
</xsd:simpleType>

More information about server logging is available in the following articles:

Note: It is particularly recommended to read the article explaining the concept to get a good understanding of the way the configuration is interpreted by the system.

• Logging server activity in Studio Server 10.14 or higher – Concept
• Logging server activity in Studio Server 10.14 or higher – Configuration
• Logging server activity in Studio Server 10.14 or higher – Viewing log files
• Managing user accounts in Studio Server

Changes

The following changes have been made in this release of Studio Server:

• Changes to server logging. The following changes have been made:

• Logging deprecated features. Features that have been marked as deprecated can now be specifically tracked by either setting the DEBUGLEVEL option or the ‘Log Level’ field on the User Maintenance page to DEPRECATED or higher. In previous versions this could only be done by using the highest log level DEBUG. The DEPRECATED option can be used to see if a user or implementation still makes use of such a feature and to then take appropriate steps to move the used process to a supported feature.

• DEBUGLEVEL option 'NONE' does not always mean that logging is disabled. Setting the DEBUGLEVEL to NONE does not always mean that logging is disabled. This is because the log level can now also be adjusted or set on the User Maintenance page. Disabling logging is now solely done by clearing the value of the OUTPUTDIRECTORY option.

• Support dropped for outputting log files to disk in JSON format. Outputting log files in JSON format is now only done when logging to a central location. The JSON format cannot be configured anymore as a format for storing log files on disk.

Note: When upgrading from an instance of Studio Server in which the LOGFILE_FORMAT is set to ‘json’, upgrade steps are required. For more information, see Upgrading an existing installation of Studio Server.

• New value 'null' for the options LOGSQL, LOG_INTERNAL_SERVICES, and LOG_RABBITMQ_SERVICES. The options LOGSQL, LOG_INTERNAL_SERVICES, and LOG_RABBITMQ_SERVICES can now also be set to value 'null'. When doing so, the system then only logs SQL statements, internal services and RabbitMQ services respectively when the log level that is used by the system is DEBUG.

• Change in behavior of the value 'true' for the options LOGSQL, LOG_INTERNAL_SERVICES, and LOG_RABBITMQ_SERVICES. Setting the options LOGSQL, LOG_INTERNAL_SERVICES, and LOG_RABBITMQ_SERVICES to 'true' now means that the system only logs SQL statements, internal services and RabbitMQ services respectively when the log level that is used by the system is INFO or DEBUG.

• Changes to the ent_log_errors.htm file in the server log folder. This file is created when a log message of level ERROR, WARN, or DEPRECATED is logged while the applied log level is DEBUG or INFO. This makes it possible to:
• Manually check if the log message contain errors or warnings.
• Let the Health Check automatically detect if one of its tests indirectly causes warnings or errors even though the test itself may be OK.

When centralized logging is enabled, this file is only present when the log level that is used by the system is INFO or DEBUG.

• When server logging is enabled, no 'Running in DEBUG mode' message is shown anymore on the Log In screen.

More information about server logging is available in the following articles:

Note: It is particularly recommended to read the article explaining the concept to get a good understanding of the way the configuration is interpreted by the system.

• Logging server activity in Studio Server 10.14 or higher – Concept
• Logging server activity in Studio Server 10.14 or higher – Configuration
• Logging server activity in Studio Server 10.14 or higher – Viewing log files
• Managing user accounts in Studio Server

• Support for SVG images. Images in SVG format are now supported by default by including it in the EXTENSIONMAP settings of the configserver.php file. This format therefore does not have to be added manually anymore, for example when wanting to make use of features such as adding images in SVG format to a Digital article in Studio.

The following requirements and limitations exist:

• The use of SVG images is supported in InDesign 2020 or higher and Studio 11.100 or higher.
• The embedded text is not searchable.
• Previews and thumbnails are in JPEG format.

• Removal of UPDATE_GEOM_SAVE option. When an article is placed on a layout and a change is made to that article or layout, users of InDesign and InCopy need to be informed of that change to verify if it affects their work. In previous versions of the server and the plug-ins for InDesign and InCopy, this was controlled through the UPDATE_GEOM_SAVE option in the configserver.php file. With the improvements made in the plug-ins for Adobe 2020 and higher, this functionality has changed and the UPDATE_GEOM_SAVE option is not used anymore. It has therefore been removed, together with the following public methods:
• BizRelation::isPlacedArticleRelation()
• BizObjectLock::isLockedByDifferentUser()

• Removal of the WW_Utils_IpAddressRange class. As a result of making improvements to the code, the WW_Utils_IpAddressRange class has been replaced by the WW_Utils_IpAddressRangeChecker class.

Documentation

The following changes to the documentation have been made in this release of Studio Server:

• Compatibility of Studio Server 10.14 - new (all other relevant compatibility matrix articles have been updated as well)
• File formats supported by Studio Server - updated
• Logging server activity in Studio Server 10.14 or higher – Concept - new
• Logging server activity in Studio Server 10.14 or higher – Configuration - new
• Logging server activity in Studio Server 10.14 or higher – Viewing log files - new
• Managing user accounts in Studio Server - updated
• Upgrading an existing installation of Studio Server - updated
• Upgrading Enterprise Server to Studio Server 10.10 or higher - updated

Known issues

No known issues exist for this release of Studio Server.

Fixed issues

No issues have been fixed in this release of Studio Server.

Installation

Choose one of the following installation paths:

• Installing Studio Server on a system on which it is not yet installed
• Upgrading an existing installation of Studio Server
• Upgrading from Enterprise Server

Studio Server 10.13.1

Studio Server version 10.13.1 build 363

Release date: 8 September 2021

Downloads

New features

Changes

Documentation

Known issues

Fixed issues

Installation

Downloads

The download files for this version of Studio Server can be found in the Release announcement.

New features

No features have been added in this release of Studio Server.

Changes

The following changes have been made in this release of Studio Server:

• Archiving files to Assets Server: The following changes have been made:
• It is now possible to keep files in Studio Server after they have been archived to Assets Server. Deleting the files from Studio Server used to be an implicit step that was part of the archive operation, but has now become a configurable option that can enabled or disabled.

For this, a new option named 'After archiving' is added to the configuration options of each archive schema. It contains 2 settings to choose from:

1. Delete files. When selected, the archived files are deleted from Studio Server. Note that files are purged; they cannot be found in the Trash Can and cannot be restored.
2. Send files to next Status. When selected, the layout, Digital article, or Dossier is sent to the next Workflow Status. (Only applicable when the Delete files option is not selected, else it has no effect.)

• It is now possible to send files to the next Workflow Status. When a layout, Digital article, or Dossier is kept in Studio Server after archiving, it is sent to the next Workflow Status.

• It is now possible to automate tasks on files in Studio Server after archiving. Combining the two options above, files can be kept in Studio Server and sent to the next Status. This makes it possible for integrators to automate tasks on these files such as modifying them in a way which results in versions that are not suited for archiving, converting print layouts to digital articles, and so on.

• The period at which the archiving should start can now be defined in hours instead of days for better control of the archiving process. For this, the option 'Archive after (days)' has been renamed to 'Archive after (hours)'.

• The option 'Archive after (hours)' now also applies when Trigger 'Status Based' is chosen. This makes it possible for this method of archiving to keep the files in the system for a short while to perform specific actions on them and to prevent that they are archived instantly.

• The archiving process can now be started before the trigger is reached by setting a negative value in hours.

• When archiving layouts, Collections are now created to represent the Dossier structure. Layouts are typically part of multiple Dossiers: one for each Story consisting of the layout, an article that is placed on the layout, some images that are placed on the layout, and additional reference files. To represent this structure in the archive, Collections are now created in the archive folder: one for each Dossier that contains the layout as well as the article and any other files that are placed on the layout.

• Compatibility with Elvis Server increased to version 6.44 or higher. Because of the added functionality of creating Collections when archiving layouts, the compatibility with Elvis Server has been increased to version 6.44 or higher.

For more information about archiving, see Archiving files from Studio Server 10.13.1 or higher to Assets Server.

Note: When upgrading previous versions of Studio Server, archive settings are automatically updated to the new options and set to the default value (which reflects the configuration of the version that is upgraded from).

Documentation

The following changes to the documentation have been made in this release of Studio Server:

• Archiving files from Studio Server 10.13.1 or higher to Assets Server - new
• Compatibility of Studio Server 10.13 - updated
• Compatibility of Elvis 6 - updated

Known issues

No known issues exist for this release of Studio Server.

Fixed issues

The following issues have been fixed in this release of Studio Server:

EN-94157 No hierarchical view is shown in the Studio panel of Studio for InDesign after making a change in the planning interface.

EN-94169 MadeToPrint: No MadeToPrint job is created when multiple layouts are set to a status that should trigger a job (manually or via Send to Next Status).

EN-94305 Unable to activate a license for Studio Server.

EN-94310 Studio: When sorting on an unsupported column in the Search results of a user defined Named Query, a database error is shown and Studio becomes unusable.

EN-94321 Allow character set utf8mb3 next to utf8 in the Health Check to support MySQL 8.0.24+.

EN-94338 Error 'Undefined index: id' is logged when deleting a Workflow Status.

EN-94340 Error 'Undefined variable' is logged when exporting an image.

EN-94346 Breadcrumb link is missing on Service Logs - Details page.

EN-94347 Security: Vulnerability found in "phpseclib" library used by "php-amqplib" library.

EN-94348 Security: Vulnerability found in "phpseclib" library used by "php-amqplib" library.

EN-94367 Assets Server integration: When updating the status for multiple files in Studio, the status for the files in Assets Server is not updated.

EN-94393 Assets Server integration: When updating the status for a file in Studio via the context menu, the status for the file in Assets Server is not updated.

EN-94413 Image position on the layout changes after cropping or moving it in the Studio Print editor.

EN-94451 Asset Server integration: Images imported from Assets Server get corrupted when config_elvis.php file contains an incorrect header.

EN-94481 Improve query performance by adding additional indices to the smart_objects table.

EN-94487 Error 'Missing function parameter (S1000)' appears in Studio when previewing a layout and layout and placed article are in multiple Dossiers.

EN-94492 Upgrading: Incorrect statement for 'masterticketid' field in some SQL files in the dbscripts folder.

EN-94493 Upgrading: Incorrect statement for 'masterticketid' field in some SQL files in the dbscripts folder.

EN-94502 Archiving - Studio Server metadata properties are not or only partly set when archiving files to Assets.

EN-94571 Deleted files are still shown in a Dossier.

EN-94617 Studio panel blanks and error 'Invalid column name 'fulname' is logged when sorting on 'Modified By' column.

Installation

Choose one of the following installation paths:

• Installing Studio Server on a system on which it is not yet installed
• Upgrading an existing installation of Studio Server
• Upgrading from Enterprise Server

Studio Server 10.13.0 build 352 Quick Patch

Studio Server version 10.13.0 build 352

Release date: 21 July 2021

Downloads

Fixed issues

Installation

Downloads

The download files for this version of Studio Server can be found in the Release announcement.

Fixed issues

The following issues have been fixed in this release of Studio Server:

EN-94463 MadeToPrint: No MadeToPrint jobs created when sendToNext or multiSetObjectProperties are changed for multiple layouts.

EN-94521 'Missing function parameter (s1000)' message is shown when previewing a layout if layout and article are in multiple Dossiers.

Installation

Choose one of the following installation paths:

• Installing Studio Server on a system on which it is not yet installed
• Upgrading an existing installation of Studio Server
• Upgrading from Enterprise Server

Studio Server 10.13.0

Studio Server version 10.13.0 build 351

Release date: 3 June 2021

Downloads

New features

Changes

Documentation

Known issues

Fixed issues

Installation

Downloads

The download files for this version of Studio Server can be found in the Release announcement.

New features

The following has been added in this release of Studio Server:

• Support for Webhooks. A Webhook listens for specific triggers and then performs a predetermined action. Webhooks can now be used for adding customizations to Studio Server.

Important: This feature is currently experimental, incomplete and subject to change. Nevertheless, we invite you to experiment with it. Based on your feedback we can refine and shape this feature into the right direction.

Background information

In previous versions of the server, adding customizations was solely done through the use of custom Server plug-ins. Such plug-ins sit directly on top of the Studio Server technology stack (PHP version, Studio Server version, and so on) and as a result can make server upgrades problematic because manual attention may be required by the integrators to make them compatible with the upgraded technology stack.

By introducing the Webhooks concept, we enable our partners and integrators to use modern integration platforms such as Workato.

Webhook calls made by Studio Server travel over HTTP to the integration platform which makes the customizations built for Studio sit on top of the technology stack of that integration platform rather than the one of Studio Server. Studio Server can then also be upgraded without the need to migrate the customizations because these are now hosted by the integration platform.

Note: The Webhooks concept does not make the custom server plug-ins concept obsolete because there are many pros and cons between using each concept. Many customizations are currently made with custom server plug-ins that are simply unachievable by using Webhooks because of various technical reasons. Webhooks should therefore be positioned as a good alternative, when technically feasible.

What is implemented?

Some basic workflow services of Studio Server are now pushing event data into the Event Bus. Also, the following has been added:

• A Server plug-in named Webhooks.
• A configuration file: config/config_webhooks.php.
• Options (prefixed with EVENT_BUS_ ) in the config/configserver.php file.
• A message queue named Event Bus to RabbitMQ (added by Studio Server).
• A message queue for each Webhook registration to RabbitMQ (added by Studio Server).
• An event processor for the Event Bus queue (to be executed with a scheduler).
• An event processor for the Webhooks queues (to be executed with a scheduler).

More information

For more information, see the Webhooks page in the Web Services Guide.

Changes

The following changes have been made in this release of Studio Server:

• Compatibility Matrix. Compared to Studio Server 10.12, the following changes have been made to the compatibility between Studio Server and other systems:

• Support for creating catalogs removed (Datasource integration). Support for creating catalogs that was marked as deprecated in Studio Server 10.12.0 has now been fully removed.

The integration was offered through the following web service interfaces:

• Data Source (workflow Data Source). Used for integrating any external storage carrying structured catalog data.
• Data Source admin. Administered the data such as creating, getting, and saving queries used in the Data Source interface.

These interfaces have now been removed. As a result, the services under these interfaces cannot be called anymore, even when they have their own integrations / plug-ins.

Next to the components and functionality that were removed in Studio Server 10.12, the items below have now also been removed.

The following Web Services have been removed:

• The Admin Data Source interface (StudioServer/server/interfaces/PlutusAdmin.wsdl)
• The Data Source interface (StudioServer/server/interfaces/PlutusDatasource.wsdl)

No services related to the Data Source can be called anymore.

The following files have been removed:

• StudioServer/server/bizclasses/BizAdmDatasource.class.php
• StudioServer/server/bizclasses/BizDatasource.class.php
• StudioServer/server/bizclasses/BizDatasourceUtils.php
• StudioServer/server/dbclasses/DBDatasource.class.php

The following Studio business connector has been removed:

• DataSource_EnterpriseConnector

This means that in the custom server plug-in, in the <pluginName>/PluginInfo.php file, the following entry cannot be called anymore in the getConnectorInterfaces() function:

final public function getConnectorInterfaces() 
{ 
     return array( 'DataSource_EnterpriseConnector'  );
}

The following web service connectors have been removed:

Because the Admin DataSource and Workflow DataSource interfaces have been removed, the web services connected to them are also no longer supported.

This means that in the custom server plug-in, in the <pluginName>/PluginInfo.php file, the Ads*_EnterpriseConnector and Dat*_EnterpriseConnector entries cannot be called in the getConnectorInterfaces() function anymore.

final public function getConnectorInterfaces() 
{ 
     return array( 'AdsGetSettings_EnterpriseConnector'  );
}

final public function getConnectorInterfaces() 
{ 
     return array( 'DatGetRecords_EnterpriseConnector'  );
}

The following database tables have been removed:

• smart_datasources
• smart_dsobjupdates
• smart_dspublications
• smart_dsqueries
• smart_dsqueryfamilies
• smart_dsqueryfields
• smart_dsqueryplacements
• smart_dssettings
• smart_dsupdates

The following Maintenance page has been removed:

• Integrations > Data sources

• Axaio MadeToPrint integration: manipulating Edition IDs. The signature of one of the Enterprise Connector methods of the MadeToPrint integration has been changed to make it possible for customization scripts to manipulate the Edition ID.

It involves the following method:

\AxaioMadeToPrintDispatcher_EnterpriseConnector::queueLayoutObjectFilterEditions()

Its signature has been changed from:

queueLayoutObjectFilterEditions( array $layEditions ....

to:

queueLayoutObjectFilterEditions( array &$layEditions ....

Documentation

The following changes to the documentation have been made in this release of Studio Server:

• Compatibility of Studio Server 10.13 - new
• Archiving files from Studio Server 10.13.0 to Assets Server - new
• Studio Server database tables - updated
• Web Services Guide - updated

Known issues

No known issues exist for this release of Studio Server.

Fixed issues

The following issues have been fixed in this release of Studio Server:

EN-31825 Configuration: Default value for ATTACHMENTDIRECTORY for Windows is incorrect.

EN-90992 Brand Maintenance page: Blank page is shown when creating a new Brand, leaving Name field empty and clicking Update.

EN-92771 Workflow Maintenance page: Missing function parameter error when enabling 'Skip InDesign Server Automation' for articles and clicking Update.

EN-92781 AutomatedPrintWorkflow script folder contains a __MACOSX folder.

EN-93125 Health Check page: WoodWing Assets Content Source test show 'Elvis' instead of 'Assets' in error message.

EN-93161 Solr: Fall back on database search when Solr is indexing.

EN-93168 Routing e-mail template: custom date type field's are displaying as type datetime with T00:00:00.

EN-93172 InDesign Server: improve the extraction of the Adobe version of a layout.

EN-93258 ExifTool integration: Metadata extraction for EPS and AI files by ExifTool results in warning in server log.

EN-93373 Health Check page: OPCache error in server logging when user opens page (or clicks links on page).

EN-93401 The WSDLs seems no longer compatible with modern .NET clients.

EN-93537 User Maintenance page: When setting the 'Password Expiration in Days’ field, the database field ‘expirepassdate’ should also get updated/re-calculated.

EN-93585 Breadcrumbs: Enable breadcrumb navigation when new entity is added.

EN-93589 Client applications: Brands are not arranged alphabetically if no display order is defined.

EN-93599 Planning interface: Layout created via planning interface has no preview when the pages use a non-arabic numbering system.

EN-93655 Security: SQL Injection in User Inbox.

EN-93656 Security: SQL Injection via the HaveVersion ID Parameter.

EN-93699 Replace article: No error reported by InDesign Server on macOS.

EN-93702 Access Profiles: remove the 'Content Station Pro - Edition' access right.

EN-93718 Add support for archiving Adverts from Studio Server to Assets Server.

EN-93726 Control characters in the Name field of an object are replaced with a space.

EN-93822 Preview performance optimization: delete master spreads while generating previews on InDesign Server.

EN-93858 'Not sufficient access rights' message S1077 shown when user logs in to the server using the full name.

EN-93891 Add support for Status based archiving.

EN-94014 Solr search is not used when searching in a Dossier.

EN-94122 Assets Server: 'Send to next status' property is not updated in Assets Server.

EN-94196 Limit the use of temporary tables to resolve read access rights in case of database searches.

EN-94217 Axaio MadeToPrint: Allow the customization script to manipulate the Edition ID.

EN-94218 Axaio MadeToPrint: Cater for multiple status IDs (instead of one ID) in 'MtpConfig'.

EN-94240 The default HOLIDAYS definition in configserver.php is outdated (2012-2014).

EN-94243 Health Check: Allow character set utf8mb3 next to UTF-8 to support MySQL 8.0.24+.

Installation

Choose one of the following installation paths:

• Installing Studio Server on a system on which it is not yet installed
• Upgrading an existing installation of Studio Server
• Upgrading from Enterprise Server

Studio Server 10.12.0

Studio Server version 10.12.0 build 333

Release date: 20 January 2021

Downloads

New features

Changes

Documentation

Known issues

Fixed issues

Installation

Downloads

The download files for this version of Studio Server can be found in the Release announcement.

New features

No features have been introduced in this release of Studio Server.

Changes

The following sections list the changes that have been made in this release of Studio Server.

final public function getConnectorInterfaces() 
{ 
     return array( 'PubPublishing_EnterpriseConnector'  );
}

<simpleType name="Action”>

<enumeration value="PublishDossier"/>  
<enumeration value="UpdateDossier"/>  
<enumeration value="UnPublishDossier"/> 
<enumeration value="SetPublishProperties"/> 

Documentation

The following changes to the documentation have been made in this release of Studio Server:

• Compatibility of Studio Server 10.12 - new
• Studio Server database tables - updated
• The Web Services SDK of Studio Server - updated
• Studio Server plug-ins - updated

Known issues

No known issues exist for this release of Studio Server.

Fixed issues

The following issues have been fixed in this release of Studio Server:

EN-16009 Performance/JournalSuite: Improve performance of the planning overview in JournalDesigner.

EN-91829 Brand and Issue Maintenance pages: The field labels 'Reading Order Reversed" and 'Reading Order' are swapped.

EN-91948 User Authorization report: The tooltip for the Back button is not shown.

EN-92052 Publication Channel Maintenance page: When creating or copying a new Brand, the focus is not set to the Name field.

EN-93426 Performance: Add index to smart_objects table on 'publication and 'type'.

Installation

Choose one of the following installation paths:

• Installing Studio Server on a system on which it is not yet installed
• Upgrading an existing installation of Studio Server
• Upgrading from Enterprise Server

Studio Server 10.11.5

Studio Server version 10.11.5 build 376

Release date: 16 March 2022

Downloads

New features

Changes

Documentation

Known issues

Fixed issues

Installation

Downloads

The download files for this version of Studio Server can be found in the Release announcement.

New features

The following features have been added in this release of Studio Server:

• Compatibility with InDesign Server 2022. Studio Server 10.11.5 or any higher version of version 10.11 is compatible with Adobe InDesign Server 2022.

Changes

The following changes have been made in this release of Studio Server:

• Removal of UPDATE_GEOM_SAVE option. When an article is placed on a layout and a change is made to that article or layout, users of InDesign and InCopy need to be informed of that change to verify if it affects their work. In previous versions of the server and the plug-ins for InDesign and InCopy, this was controlled through the UPDATE_GEOM_SAVE option in the configserver.php file. With the improvements made in the plug-ins for Adobe 2020 and higher, this functionality has changed and the UPDATE_GEOM_SAVE option is not used anymore. It has therefore been removed, together with the following public methods:
• BizRelation::isPlacedArticleRelation()
• BizObjectLock::isLockedByDifferentUser()

• MadeToPrint: A subsequent job is now triggered when a processed job sets a status and a job exists for that status. When a processed MadeToPrint job is completed, the file is set to another Workflow Status to move it along in the workflow process.

When another job exists for that new status, this job is now automatically triggered. In previous versions, the job was only triggered when the file was manually re-set to the status.

• Workflow: TicketHash added to the CheckTicket workflow service. The workflow service CheckTicket now provides a TicketHash in its response. This is specified in the SCEnterprise.wsdl file accordingly (in a backwards compatible manner to not break existing client applications that are unaware of this change). This ticket hash can be used by Studio to compare it with the ticket hash that arrives through an event message. When the same, Studio may conclude that the event was caused by the client app itself and thus may be ignored (to avoid applying the same change in the UI twice).

Documentation

The following changes to the documentation have been made in this release of Studio Server:

• Compatibility of Studio Server 10.11 - updated
• Integrating MadeToPrint in Studio Server - updated

Known issues

No known issues exist for this release of Studio Server.

Fixed issues

The following issues have been fixed in this release of Studio Server:

EN-94114 Health Check: PHP errors in the Server Plug-ins test when a plug-in does not provide connectors.

EN-94178 Logging: Replacing an image in Studio is incorrectly logged as a Warning.

EN-94216 Upgrading: Database error because of a duplicate alter table statement.

EN-94414 Studio panel in Studio for InDesign and InCopy is not updated when replacing an article or image in Studio.

EN-94446 Searching: Sorting On 'Dimensions' in Studio results in an empty view and an error in the log file.

EN-94455 LDAP/AD: Admin user needs to be included in Brand authorizations to get access to the Admin Maintenance pages.

EN-94475 LDAP/AD: User with a comma in the name cannot log on.

EN-94495 Archiving: Using a Custom property as the place holder for including the year and month in a folder name in the Archive Zone is no longer working.

EN-94561 MadeToPrint: The Route To field for a file is not set, even though automatic routing is enabled.

EN-94563 Assets: Custom metadata is cleared in Assets after synchronization by Studio.

EN-94584 Studio: Using a forward slash ('/') in a tag results in two tags instead of one.

EN-94614 New message event ObjectFlagCleared causes an exception in the Studio plug-ins.

EN-94653 After copying a layout, a warning 'Trying to get property 'Format' of non-object' is added to the log files.

EN-94675 Mandatory Dossier field can be bypassed when creating a new article in Studio.

EN-94774 MadeToPrint: Allow customization to cater for multiple Status IDs and manipulate the Edition ID.

EN-94887 Solr: QueryObjects for a publication and type will list all workflow states of the system in the Solr request.

EN-94971 MadeToPrint: No subsequent job is triggered when a processed job sets a status and a job exists for that status.

EN-95040 LDAP: The 'EXCLUDE_USERNAME' option incorrectly excludes users.

EN-95055 Maintenance pages: Full user name not shown at the bottom of the menu when accessing the User Maintenance page.

EN-95186 Maintenance pages: The value for OPENID_CLIENT_SECRET is not obfuscated.

Installation

Choose one of the following installation paths:

• Installing Studio Server on a system on which it is not yet installed
• Upgrading an existing installation of Studio Server
• Upgrading from Enterprise Server

Studio Server 10.11.4

Studio Server version 10.11.4 build 358

Release date: 18 August 2021

Downloads

New features

Changes

Documentation

Known issues

Fixed issues

Installation

Downloads

The download files for this version of Studio Server can be found in the Release announcement.

New features

No features have been added in this release of Studio Server.

Changes

The following changes have been made in this release of Studio Server:

• Archiving files to Assets Server: The following changes have been made:
• It is now possible to keep files in Studio Server after they have been archived to Assets Server. Deleting the files from Studio Server used to be an implicit step that was part of the archive operation, but has now become a configurable option that can enabled or disabled.

For this, a new option named 'After archiving' is added to the configuration options of each archive schema. It contains 2 settings to choose from:

1. Delete files. When selected, the archived files are deleted from Studio Server. Note that files are purged; they cannot be found in the Trash Can and cannot be restored.
2. Send files to next Status. When selected, the layout, Digital article, or Dossier is sent to the next Workflow Status. (Only applicable when the Delete files option is not selected, else it has no effect.)

• It is now possible to send files to the next Workflow Status. When a layout, Digital article, or Dossier is kept in Studio Server after archiving, it is sent to the next Workflow Status.

• It is now possible to automate tasks on files in Studio Server after archiving. Combining the two options above, files can be kept in Studio Server and sent to the next Status. This makes it possible for integrators to automate tasks on these files such as modifying them in a way which results in versions that are not suited for archiving, converting print layouts to digital articles, and so on.

• The period at which the archiving should start can now be defined in hours instead of days for better control of the archiving process. For this, the option 'Archive after (days)' has been renamed to 'Archive after (hours)'.

• The option 'Archive after (hours)' now also applies when Trigger 'Status Based' is chosen. This makes it possible for this method of archiving to keep the files in the system for a short while to perform specific actions on them and to prevent that they are archived instantly.

• The archiving process can now be started before the trigger is reached by setting a negative value in hours.

• When archiving layouts, Collections are now created to represent the Dossier structure. Layouts are typically part of multiple Dossiers: one for each Story consisting of the layout, an article that is placed on the layout, some images that are placed on the layout, and additional reference files. To represent this structure in the archive, Collections are now created in the archive folder: one for each Dossier that contains the layout as well as the article and any other files that are placed on the layout.

• Compatibility with Elvis Server increased to version 6.44 or higher. Because of the added functionality of creating Collections when archiving layouts, the compatibility with Elvis Server has been increased to version 6.44 or higher.

For more information about archiving, see Archiving files from Studio Server 10.11.4 or higher to Assets Server.

Note: When upgrading previous versions of Studio Server, archive settings are automatically updated to the new options and set to the default value (which reflects the configuration of the version that is upgraded from).

Documentation

The following changes to the documentation have been made in this release of Studio Server:

• Archiving files from Studio Server 10.11.4 or higher to Assets Server - new
• Compatibility of Elvis 6 - updated
• Compatibility of Studio Server 10.11 - updated

Known issues

No known issues exist for this release of Studio Server.

Fixed issues

The following issues have been fixed in this release of Studio Server:

EN-94157 The Studio panel of Studio for InDesign in hierarchical view mode does not show an expander for the layout after making a change in the planning interface for that layout.

EN-94169 MadeToPrint: No MadeToPrint job is created when multiple layouts are set to a status that should trigger a job (manually or via Send to Next Status).

EN-94305 Unable to activate a license for Studio Server.

EN-94310 Studio: When sorting on an unsupported column in the Search results of a user defined Named Query, a database error is shown and Studio becomes unusable.

EN-94321 Allow character set utf8mb3 next to utf8 in health check to support MySQL 8.0.24+.

EN-94348 Security: Vulnerability found in the 'phpseclib' library used by the 'php-amqplib' library.

EN-94367 Assets Server integration: When updating the status for multiple files in Studio, the status for the files in Assets Server is not updated.

EN-94393 Assets Server integration: When a file is set to the next status via the context menu 'Send to next status', the status for the file in Assets Server is not updated.

EN-94413 Image position on the layout changes after cropping or moving it in the Studio Print editor.

EN-94492 Upgrading: Incorrect statement for 'masterticketid' field in some SQL files in the dbscripts folder.

EN-94502 Archiving - Fixes for metadata of archived assets.

Installation

Choose one of the following installation paths:

• Installing Studio Server on a system on which it is not yet installed
• Upgrading an existing installation of Studio Server
• Upgrading from Enterprise Server

Studio Server 10.11.3

Studio Server version 10.11.3 build 338

Release date: 13 April 2021

Downloads

New features

Changes

Documentation

Known issues

Fixed issues

Installation

Downloads

The download files for this version of Studio Server can be found in the Release announcement.

New features

The following has been introduced in this release of Studio Server:

• Archiving Adverts. Support for archiving Adverts from Studio Server to Assets Server has been added. They are typically archived as part of the layout on which they are placed, but unplaced Adverts can also be archived as part of the process of archiving Dossiers.

Take note of the following:

• An Advert is archived as an image, not as an Advert object. The archived image will have the original Workflow Status of the Advert object. When the image is restored, it will be assigned the default Workflow Status for images, as configured in Studio Server.
• To archive an Advert, a high-resolution version of the Advert should be available (typically in the form of a PDF file). This file should not be stored on an external drive but in the File Store folder of Studio Server.
• When an Advert is placed on a layout, it will get archived through the print based archiving schema.
• When an Advert is not placed on a layout but is part of a Dossier, it will get archived through the Dossier based archiving schema.
• When an Advert is not placed on a layout and is not part of a Dossier, it is not archived.

For more information about archiving, see Archiving files from Studio Server 10.11.1 – 10.11.3 or higher to Assets Server.

Changes

The following changes have been made in this release of Studio Server:

• Archiving: A layout that contains a planned image is considered to be incomplete and therefore not ready for archiving. When the archiving process is run, the process for that layout now fails and an error is shown to the user.

Documentation

The following changes to the documentation have been made in this release of Studio Server:

• Archiving files from Studio Server 10.11.1 – 10.11.3 or higher to Assets Server - updated

Known issues

The following known issues exist for this release of Studio Server:

EN-94077 Assets Server integration, archiving Adverts. When restoring a layout containing an Advert, the restored Advert in the form of an image is unlinked. During this process, the following message appears:

The following files could not be restored from Assets Server and were unlinked from the layout

This issue is planned to be fixed in the upcoming patch version for Adobe 2020 (Studio for InDesign and InCopy 15.2.1) and Adobe 2021 (Studio for InDesign and InCopy 16.1.0).

Fixed issues

The following issues have been fixed in this release of Studio Server:

EN-93815 Image frame fitting settings in the layout are overridden by Studio.

Installation

Choose one of the following installation paths:

• Installing Studio Server on a system on which it is not yet installed
• Upgrading an existing installation of Studio Server
• Upgrading from Enterprise Server

Studio Server 10.11.2

Studio Server version 10.11.2 build 335

Release date: 9 March 2021

Downloads

New features

Changes

Documentation

Known issues

Fixed issues

Installation

Downloads

The download files for this version of Studio Server can be found in the Release announcement.

New features

The following has been introduced in this release of Studio Server:

• Compatibility: Support for Adobe 2021 added. Studio Server 10.11.2 is compatible with InDesign 2021, InDesign Server 2021, and InCopy 2021.

Note: The use of these applications requires Studio for InDesign and InCopy 2021 (version 16.0.0).

• Archiving based on Workflow Status: Archiving files to Assets Server can now also be done based on a dedicated Workflow Status such as 'Ready for Archiving'. Any file that is set to that status is automatically archived. This archiving method is known as 'Status based' archiving and is in addition to the already existing Continuous and Issue based archiving in which files are archived when a defined number of days has passed since a specific date.

Status based archiving is used for archiving files when they are ready to be archived and makes it possible for example to prepare periodic publications well in advance of the actual publication (such as a Christmas edition that is prepared during the summer), or tweak publications after they have been published (such as modifying layouts for XML export).

Note: Although Status based archiving is a manual way of archiving files, the actual archiving process is a scheduled process and therefore determined by how often this process is run. Technically it is therefore also time based.

To make Status Based archiving work, the following has been added:

• On the Brand Maintenance page: a Trigger named 'Status Based'. When enabling this for a Digital article, Dossier, or layout, files are archived when they are assigned to a dedicated Workflow Status.

• On the Workflow Maintenance page: an option named 'Send to Archive'. Enabling this for a Workflow Status indicates that any file that is set to that status is marked for archiving based on the Status Based archiving method.

Figure: The Send to Archive option on the Workflow Maintenance page. Here. a Workflow Status 'Ready for Archiving' has been created for which the option is enabled.

For more information, see Archiving files from Studio Server 10.11.1 – 10.11.3 or higher to Assets Server.

Changes

The following changes have been made in this release of Studio Server:

• Preview performance optimization: master spreads are deleted when previews are generated on InDesign Server. The performance of the Layout preview in the Print editor of Studio has been optimized by deleting unused master spreads from the layout when the preview is generated. We have observed that layouts that contain many master spreads with content can significantly delay the preview generation of that layout.

This change is implemented in the IDPreview.jsx script that is run by InDesign Server.

Note: The master spreads are only removed from the local copy for InDesign Server; it does not affect the layout that is saved in Studio Server.

• Archiving: When the process to see if candidate layouts are available for archiving is run, layouts that are found are now first checked to see if they are part of an InDesign Server Job. When this is the case, these layouts are then not archived and an error is raised to make the user aware of this.

• Access Rights: The Access Right 'Content Station Pro - Edition' has been removed; support for Content Station in combination with Studio Server was already dropped. The access right will be removed from the database during the upgrade.

Documentation

The following changes to the documentation have been made in this release of Studio Server:

• Compatibility of Studio Server 10.11 - updated
• Archiving files from Studio Server 10.11.1 – 10.11.3 or higher to Assets Server - updated
• Creating Workflow Statuses in Studio Server - updated
• Workflow Status settings in Studio Server - updated

Known issues

No known issues exist for this release of Studio Server.

Fixed issues

The following issues have been fixed in this release of Studio Server:

EN-31825 Configuration: Default value for ATTACHMENTDIRECTORY for Windows is incorrect.

EN-90992 Brand Maintenance page: Blank page is shown when creating a new Brand, leaving Name field empty and clicking Update.

EN-92771 Workflow Maintenance page: Missing function parameter error when enabling 'Skip InDesign Server Automation' for articles and clicking Update.

EN-92781 The AutomatedPrintWorkflow script folder contains hidden files and MACOSX internal folders/files.

EN-93168 Routing e-mail template: custom date type fields are displaying as type 'datetime' with 'T00:00:00'.

EN-93125 Health Check page: 'Elvis' is shown instead of 'Assets' in error message.

EN-93172 InDesign Server: improve the extraction of the Adobe version of a layout.

EN-93258 ExifTool integration: Metadata extraction for EPS and AI files by ExifTool results in warning in server log.

EN-93401 The WSDLs seems no longer compatible with modern .NET clients.

EN-93537 User Maintenance page: When setting the 'Password Expiration in Days’ field, the database field ‘expirepassdate’ should also get updated/re-calculated.

EN-93585 Breadcrumbs: enable breadcrumb navigation when new entity is added.

EN-93589 Client applications: Brands are not arranged alphabetically if no display order is defined.

EN-93599 Planning interface: Layout created via planning interface has no preview when the pages use non-arabic numbering system.

EN-93655 Security: SQL Injection in User Inbox.

EN-93656 Security: SQL Injection via the HaveVersion ID Parameter.

EN-93699 Replace article: no error reported by InDesign Server on macOS.

EN-93702 Access Profiles: Remove 'Content Station Pro - Edition' Access Right.

EN-93726 Control characters in the Name field of an object are replaced with a space.

EN-93858 'Not sufficient access rights' message S1077 shown when user logs in to the server using the full name.

EN-93882 Preview performance optimization: delete master spreads when generating previews on InDesign Server.

Installation

Choose one of the following installation paths:

• Installing Studio Server on a system on which it is not yet installed
• Upgrading an existing installation of Studio Server
• Upgrading from Enterprise Server

Studio Server 10.11.1 build 327 Quick Patch

Studio Server version 10.11.1 build 327

Release date: 2 November 2020

Downloads

Fixed issues

Installation

Downloads

The download files for this version of Studio Server can be found in the Release announcement.

Fixed issues

The following issues have been fixed in this release of Studio Server:

EN-93573 Unable to log in to Studio because of a PHP security fix.

Installation

Choose one of the following installation paths:

• Installing Studio Server on a system on which it is not yet installed
• Upgrading an existing installation of Studio Server
• Upgrading from Enterprise Server

Studio Server 10.11.1

Studio Server version 10.11.1 build 326

Release date: 27 October 2020

Downloads

New features

Changes

Documentation

Known issues

Fixed issues

Installation

Downloads

The download files for this version of Studio Server can be found in the Release announcement.

New features

The following feature has been introduced in this release of Studio Server:

• Archiving Dossiers to Assets Server. Dossiers can now be archived to Assets Server in the following ways:
• When a layout or Digital article is archived, all files in the Dossier of which the layout or Digital article is part can now also be archived.
• Dossiers that do not contain a layout or Digital article (such as Dossiers containing reference material or a Print article) can now also be archived.

For more information, see Archiving files from Studio Server 10.11.1 – 10.11.3 or higher to Assets Server.

Changes

The following changes have been made in this release of Studio Server:

• Archiving files to Asset Server. The following changes have been made:

• Digital articles do not have to be placed in a Dossier anymore to be archived.

• Archiving layouts and Digital articles can now also be based on a custom number of days that have passed since the layout was last modified.

• When setting up the Archive Zone folder using wildcards, the year, month, and day of the publication date of the Issue can now be included in the folder name by using the following wildcard:

${publicationdate:Y-m-d}

• This wildcard is ignored when the layout, Digital article, or Dossier is not targeted for an Issue.
• When a layout, Digital article, or Dossier is targeted to more than one Issue, the name of the first Issue is taken.

For more information, see Archiving files from Studio Server 10.11.1 – 10.11.3 or higher to Assets Server.

• Integration with Assets Server: password settings validation. In previous versions, the password restrictions that were defined in the configserver.php file (such as the required number of characters) were not validated. When not making use of authentication providers such as LDAP/Active Directory, Okta or AWS Cognito, it was possible therefore to create user accounts that did not adhere to these restrictions This has now been fixed.

We advice to have all users reset their passwords for logging in to Studio Server. Note that this is only needed when all of the following is true:

• No third-party authentication providers such as LDAP/Active Directory, Okta, or AWS Cognito are used.

• The WoodWing Assets plug-in is enabled.

• Changes have been made to the default settings of the Password management configuration in the configserver.php or config_overrule.php file.

• Display order of Brands. When setting up Brands, the order in which the Brands are displayed can be defined by assigning a number to each Brand. When multiple Brands have the same number, these Brands are now sorted alphabetically. In previous versions they were sorted by creation date or sometimes randomly.

• Searching: sorting on status. When Solr was not enabled in previous versions, and the user sorted the search results on the Status column, the results were sorted by their order as set on the Workflow Status page. Now, the sorting is done alphabetically by status name.

If sorting on status order is still preferred, set the following option in the configserver.php/config_overrule.php file to 'true':

SORT_ON_STATE_ORDER'

Note: The 'SORT_ON_STATE_ORDER' setting is not new but was ignored when Solr was not enabled.

• Web Services: AdmCopyPublications service enabled. The AdmCopyPublications service which used to be commented out in the WSDL has now been enabled. For more information, see the Web Services Guide.

Documentation

The following changes to the documentation have been made in this release of Studio Server:

• Archiving files from Studio Server 10.11.1 – 10.11.3 or higher to Assets Server - new
• Upgrading an existing installation of Studio Server - updated
• Upgrading Enterprise Server to Studio Server 10.10 or higher - updated

Known issues

The following known issue exists for this release of Studio Server:

• PHP. A recent PHP security fix (#79699) has impacted the communication between Studio Server and the client applications, preventing the applications from logging in to Studio Server. To avoid this issue, the highest supported version of PHP is currently 7.3.22.

This will be resolved as soon as possible in the form of a quick path for Studio Server 10.11.1.

Fixed issues

The following issues have been fixed in this release of Studio Server:

EN-18224 Solr: Incorrect search result when sorting on Status.

EN-19936 When copying a Brand using a name that already exists, the Copy Issues check box is cleared.

EN-22114 Check boxes on Issue Maintenance page are incorrectly aligned.

EN-29204 Icons on the Export page are incorrectly aligned.

EN-30767 The 'Type' field for custom properties on the Metadata page is not localized.

EN-33175 Change default order of Brands from creation order to alphabetically.

EN-36454 User Maintenance: Nothing happens when creating a user with a Valid From date later than the Valid Till date.

EN-88415 Implement the CopyPublications service.

EN-90613 'Production Zone' value is set incorrectly when copying a Brand.

EN-93083 Support the 'Publication Date' field as a wildcard in the zone paths for archiving to Assets.

EN-93301 Add a check and prevent objects from changing object type.

EN-93345 InDesign Server: preview generation does not take into account that the active URL can have a query string.

EN-93346 InDesign Server: Error raised in logs file after deleting an InDesign Server instance from the 'Overview of InDesign Servers' page.

EN-93349 'Invalid property (S1020)' error is logged in server log file when restoring an archived Digital article containing an image which has been renamed after archiving.

EN-93352 When editing a placed article in Studio, warnings are logged in server log file.

EN-93356 'Invalid property (S1020)' error is logged in server log file when restoring an archived layout containing a placed image.

EN-93357 Copy/Create user: Password settings in configserver.php file are not respected.

EN-93365 Breadcrumb on License Status page changes when removing tickets to log-off users

EN-93368 Incorrect thumbnail shown for an image in the History panel of Studio.

EN-93370 Studio: After changing a file to a different type, restoring it to its original type and refreshing the search results page, type of format file was changed to is shown.

EN-93372 Incorrect breadcrumb when trying to copy a Brand using a name of a Brand that already exists.

EN-93375 Objects routed to Route-to groups are missing in search results.

EN-93383 Studio Publication Overview shows short user name instead of full user name for the 'Modified by' field.

EN-93396 Archiving to Assets Server: date wildcards are not properly resolved.

EN-93420 The timestamp in the Studio Server log files should be in the local time instead of in GMT.

EN-93431 Studio: Package for a published Digital article contains a maximum of 50 images.

EN-93440 Health Check: Fatal error when connection to LDAP system fails.

EN-93447 When copying a Brand, the 'Archive Zone' settings are incorrectly set.

EN-93448 When copying a Brand, the 'Default Status Restored Digital Article' and 'Default Status Restored Image' values are incorrectly set.

EN-93470 Opening a layout with placed articles and images results in a fatal 'Type Error'.

EN-93487 No warning is shown when placing an article component more than once.

EN-93549 Studio requests for number of CheckedOut/LockedBy items results into huge load on the database.

EN-93497 Article preview is showing the previous content instead of the latest.

Installation

Choose one of the following installation paths:

• Installing Studio Server on a system on which it is not yet installed
• Upgrading an existing installation of Studio Server
• Upgrading from Enterprise Server

Studio Server 10.11.0

Studio Server version 10.11.0 build 318

Release date: 23 July 2020

Downloads

New features

Changes

Documentation

Known issues

Fixed issues

Installation

Downloads

The download files for this version of Studio Server can be found in the Release announcement.

New features

The following feature has been introduced in this release of Studio Server:

• Maintenance pages now contain breadcrumb navigation. To make navigating the Maintenance pages easier, and to better visualize where in the structure the user is currently working, breadcrumb navigation has been added to all Maintenance pages.

Changes

The following sections list the changes that have been made in this release of Studio Server.

• Compatibility Matrix. Compared to Studio Server 10.10, various changes have been made to the compatibility between Studio Server and other systems as shown in the following table.

• Upgrading. Various changes have been made to Studio Server 10.11.0 which affects upgrading from previous versions. This includes:
• The upgrade path
• Features that are no longer supported
• Changes to Named Queries, PHP classes, PHP functions, database items, and more

For details, see Upgrading Enterprise Server to Studio Server 10.10 or higher.

• Assets Server integration. To following changes have been made to the functionality of archiving files to Assets Server:

• The configuration of the 'Archive Zone' and 'Archive after (days)' options can now be set for each archive schema separately. In previous versions, when both 'Issue based' and 'Continuous' archive schemas were selected, the 'Archive Zone' and 'Archive after (days)' options applied to both these schemas. Now, the 'Archive Zone' and 'Archive after (days)' options can be defined separately for each schema.

• New and changed configuration options. In the config_elvis.php file, one configuration option has changed and three new options have been added to give more control over the default values of the two properties:

• New default values. The default value for the 'Archive after (days)' option has been changed from zero (0) to the following values:

• Continues archive schema: 30
• Issue Based schema: 7

• Health Check test. When running the 'WoodWing Assets Content Source' test on the Health Check page, any of the options mentioned above are automatically checked. When no values have been set for a Brand, they automatically get the default value assigned.

When options have been repaired, an orange 'UPDATE' icon is shown together with a list of affected Brands. Each Brand can be clicked to navigate to its Brand Maintenance page for manual examination.

• InDesign Server integration. The following changes have been made:

• Logging is now off by default and can be enabled for debugging. In previous versions, logging by InDesign Server Jobs to various devices was enabled by default and could not be disabled. This could potentially negatively affect the performance of the production environment.

Now, logging is off by default and can be enabled for debugging purposes when needed. This is done through the following option in the configserver.php file:

INDESIGNSERV_LOGTODEVICES

For details, see Controlling InDesign Server Job logging in Studio Server.

• Scripts are no longer uploaded to InDesign Server during production. In previous versions, InDesign Server Jobs always uploaded their script to InDesign Server just before it was executed. This is now no longer done during production hours. Instead, scripts are uploaded during installation time and cached on the InDesign Server host machine.

Scripts are taken by the Health Check page from the StudioServer/server/utils/idsscripts folder and distributed to all InDesign Server machines (connected to Studio Server) in the following folder:

• MacOS: ~/Library/Preferences/Adobe InDesign Server/Version x.y/
  
  en_US/configuration_<port number>/Scripts/WwEnterpriseUtils
• Windows: %USERHOME%\AppData\Roaming\Adobe\InDesign Server\Version x.y\
  
  en_US\configuration_<port number>\Scripts\WwEnterpriseUtils

Where:

• Version x.y is the InDesign Server Version. For example: 'Version 15.0'.
• configuration_<port number> is the port on which InDesign Server is started. For example: 'configuration_18387'.

• No need anymore for a shared or mounted WebEdit folder with InDesign Server. In previous versions, the path to the WEBEDITDIR folder needed to be defined in the WEBEDITDIRIDSERV option. This option has now been dropped and a mount from either the Studio Server machines and/or from the InDesign Server machines is no longer needed.

Studio Server still needs access to the WebEdit folder that is shared between the application servers. However, Studio Server now creates a WebEdit folder for each InDesign Server machine automatically (without the need for configuration). This folder is shared between the InDesign Server instances running on that machine only. Files that needs to be shared will be transferred over HTTP automatically.

This folder is created in the following location:

• MacOS: ~/Library/Application Support/WwIdsWorkSpace
• Windows: %USERDATA%/WwIdsWorkSpace (by default, C:\Documents and Settings\username\Application Data\WwIdsWorkSpace)

• The generateOutputPages function can no longer be used. Integrations may have used this function provided by the BizWebEditWorkspace class. However, the parameters for this function have been heavily changed due to the changes mentioned above. More importantly, the function is no longer static or public and can therefore no longer be called.

Note: As this is a breaking change, integrators should look for an alternative solution for integrations using this function.

• Drop in preview performance. Due to the changes mentioned above, the performance of generating previews has dropped with an average of about 12%. (The actual figure depends on many factors, such as the size of the layout and article, and the number of images used.)

• Support for the use of certificate files via WWSettings.xml dropped. This SSL feature of Studio for InDesign Server can no longer be used for the preview feature of the InDesign Server integration. This is because the generated previews are now directly uploaded to Studio Server by the InDesign Server preview script.

Note: Specifying certificate files is still supported by Studio for InDesign Server. SSL connections for the preview feature can also still be set up. For the latter, the certificates registered at operating system level are used.

• Periodic clean-up of the WebEdit folders should be planned. When installing a new InDesign Server host (or upgrading an existing InDesign Server host) to connect to Studio Server, the WebEdit folders should be cleaned periodically.

These folders are created by the InDesign Server preview script (provided by Studio Server) for each preview session.

When an InDesign Server host is busy, the WebEdit folder is created by another InDesign Server host.

To make maximum use of the InDesign Server capacity (and to not have the process delayed because of auto-cleaning operations) it is the responsibility of the system operator to periodically remove the WebEdit folders.

The more users are served, the more often this should happen. However, doing this too often can lead to inefficiencies. A good starting point is to clean the folder every 15 minutes and to remove all WebEdit folders in the InDesign Server Workspace folder that are older than one hour.

For Windows Server, two example scripts are provided: a clean-up script that does the actual cleaning and an installation script that makes it periodically run with help of the Windows Task Scheduler. The scripts can be found in the StudioServer/sdk/ids folder.

Further instructions can be found in the headers of the scripts.

Note: The scripts provided are a guideline for setting up the automated cleaning. Usage of it is at your own risk; support for these scripts is not provided by WoodWing.

The Workspace folder can be found in the following locations:

• Windows: %USERDATA%\WwIdsWorkSpace
• MacOS: ~/Library/Application Support/WwIdsWorkSpace

• Publication Channels. The following has been changed:

• The behavior of a Publication Channel of type 'Web' is now the same as for type 'Print'. When a Dossier was created in previous versions, the Issue that was assigned to any objects within the Dossier depended on the Issue that the Dossier was assigned to: an Issue belonging to a Publication Channel of type 'Print' or of type 'Web'.

Example: When an article was created in a Dossier assigned to an Issue of a Publication Channel of type 'Print', the article was also assigned to the Print Issue. However, when an article was created in a Dossier assigned to an Issue of a Publication Channel of type 'Web', the article was not assigned to the Web Issue.

In Studio Server 10.11.0, an object that is created within a Dossier assigned to an Issue of a Publication Channel of type 'Web' is now also assigned to that Web Issue.

Note: When searching for files by filtering on a Web issue, all the child objects are now returned instead of only the Dossiers. (Applies to objects created in Studio Server 10.11.0 or higher only; objects created in previous versions will still not appear in the search results.

• Third-party libraries. The following has been changed:

• The Zend Framework has been replaced by Laminas. The Zend Framework and all its sub-projects has been transitioned to an open source project hosted at the Linux Foundation. As a result, the following changes have been made:

• The Zend Framework in the StudioServer/server/vendor folder has been replaced by Laminas.
• Zend Framework usages by Studio Server have been replaced with Laminas.

• Web service performance. As the footprint of Studio Server has been reduced, the web services show an improved performance.

This has been tested by running the ServerStudio/server/wwtest/speedtest.php module using its default options but with the 'Number of runs' option set to 5.

The test was run using the following configuration:

• Application Server running on Apache 2.4 + PHP 7.3 + ImageMagick + ExifTool + CentOS 7 instance in AWS (m5.large).
• Database running on MySQL 8.0 + CentOS 7 instance in AWS (m5.large).
• Server logging and profiling disabled.
• 3rd-party integrations disabled (InDesign Server, Elvis, RabbitMQ, Solr, and so on).
• Enterprise Server 10.8 and Studio Server 10.11 installed side-by-side (on the same instances).

• The database was set up with the standard WW News Brand configuration.

• One test run was made for SOAP and one for JSON-RPC.

Note: The InDesign/InCopy plug-ins for Studio are using SOAP and the Studio web application is using JSON-RPC.

The calculated Average outcomes are compared between Enterprise Server 10.8 and Studio Server 10.11 installations:

• SOAP performance improved by 16%.
• JSON-RPC performance improved by 29%.

• SpeedTest tool. Various improvements were made to the ServerStudio/server/wwtest/speedtest.php module:

• The Version option has been removed as it lists very old server versions that are no longer relevant.

• A new option named Protocols has been added. It makes it possible to run the tests over SOAP or JSON-RPC.

Note: The InDesign/InCopy plug-ins for Studio are using SOAP and the Studio web application is using JSON-RPC.

• The Average calculation has been improved. Outcomes of the lowest performance (the highest value) are now ignored and are shown in strikethrough text.

• A Best calculation is now also performed. It shows the fastest execution of the runs.

• The Summary report now shows totals calculated for each test run (shown when performing more than 1 test run).

• Health Check page. The following changes have been made:

• The 'InDesign Server / CS editor' test has been renamed to 'InDesign Server'. The 'CS editor' part was included because the test was originally used for the previews of the Content Station editor.

However, only the configured InDesign Server instances were tested. Because these are used for more purposes nowadays such as the InDesign Server Automation feature, naming the test 'InDesign Server' better reflects its purpose.

• The WSDL Cache is now automatically repaired. In previous versions, when the WSDL Cache was outdated, the WSDL Cache entry showed a WARNING icon and provided a link to clear the cache.

Now, an UPDATED icon is shown and the cache is automatically cleared when it is outdated. When the cache is cleared or up-to-date, an OK icon is shown.

• LOGFILE_FORMAT. The LOGFILE_FORMAT option in the configserver.php file now also makes it possible to output in JSON format.

The output contains fields respecting the Elastic Common Schema, designed for centralized logging. It can be set up with the help of third-party tools such as Filebeat for reading logs and saving them in ElasticSearch.

Documentation

The following changes to the documentation have been made in this release of Studio Server:

• Compatibility of Studio Server 10.11 - new
• Controlling InDesign Server Job logging in Studio Server - new
• Using SSL to secure the connection between Studio Server and Studio for InDesign and InCopy - updated
• Archiving Digital articles to Assets Server - updated
• Archiving InDesign layouts to Assets Server - updated
• Upgrading Enterprise Server to Studio Server 10.10 or higher - updated
• Studio Server full installation - updated
• Logging server activity in Studio Server 10.13 or lower - updated

Note: Some screenshots in the product documentation may still show Enterprise Server. This will be updated over the coming weeks.

Known issues

No known issues exist for this release of Studio Server.

Fixed issues

The following issues have been fixed in this release of Studio Server:

EN-4766 Maintenance pages: '© WoodWing Software' should link to woodwing.com.

EN-10819 Incorrect spelling of metadata for PHP Preview and Meta Data server plug-in.

EN-17988 Default value of custom property is not set when the default is zero (0).

EN-89640 Support CloudFront (allow empty INETROOT).

EN-90609 Replace the WebEdit folder by another mechanism to exchange files between Content Station and InDesign Server.

EN-91845 Maintenance pages: Performance issues for the Service Logs page.

EN-92155 Maintenance pages: Make version info of InDesign Server human readable on the Health Check page.

EN-92633 Error S1029 shown when changing the Issue of a Dossier when some of its files have been moved to the Trash Can.

EN-92690 Planning interface: Issues can be created with the same name as an existing Issue.

EN-92817 When deleting Routing Rules in a copied Brand, the Routing Rule in the source Brand are also deleted.

EN-92820 Assets Server integration: Mismatch in file names between Studio Server and Assets Server when adding a file which already exists in Assets Server.

EN-92885 Studio: Metadata is not inherited when creating a Print variant of a Digital article.

EN-92920 Studio: When creating a Digital article together with a Dossier, the selected Issue is not assigned to the article.

EN-93061 MadeToPrint: Health Check test incorrectly reports an error for the Axaio configuration in Studio Server.

EN-93069 MadeToPrint: Creation of a MadeToPrint Job fails for a layout when the layout does not have an Edition assigned.

EN-93073 MadeToPrint: Health Check test does not show an error when the database tables are not yet initialized for the MadeToPrint plug-in.

EN-93107 Planning interface and Studio do not block duplicate layout names in the same Issue.

EN-93111 Assets Server integration: Separate the 'Archive after (days)' archive option for print and digital.

EN-93112 Assets Server integration: Separate the 'Archive Zone' option for print and digital.

EN-93130 Maintenance pages: Add the option to navigate by breadcrumbs.

EN-93142 MySQL: dbmodeldiff.php does not work for MySQL 8 nor for database models of server plug-ins.

EN-93229 Security: The ID parameter of hpusers.php is vulnerable to cross-site scripting.

EN-93233 Studio: When creating a Print variant of a Digital article, the Route To field is not filled.

EN-93278 Maintenance pages: After creating a new Named Query and refreshing the Overview of Named Queries page, the Named Queries page appears again.

Installation

Choose one of the following installation paths:

• Installing Studio Server on a system on which it is not yet installed
• Upgrading an existing installation of Studio Server
• Upgrading from Enterprise Server

Studio Server 10.10.0 build 321 Quick Patch

Studio Server version 10.10.0 build 321

Release date: 21 October 2020

Downloads

Fixed issues

Installation

Downloads

The download files for this version of Studio Server can be found in the Release announcement.

Fixed issues

The following issue has been fixed in this release of Studio Server:

EN-93538 Requests by Studio during log on results in a large database load and performance issues.

Additional info: When a user logs in to Studio, a request is sent to Studio Server for the number of items that are checked out by that user, as well as a request for the number of items in the inbox of the user. When the user has access to many Brands and objects, this can result in a large load on the database. When many such users log on at the same time, the stability of the system can be affected.

Installation

Choose one of the following installation paths:

• Installing Studio Server on a system on which it is not yet installed
• Upgrading an existing installation of Studio Server
• Upgrading from Enterprise Server

Studio Server 10.10.0

Studio Server 10.10.0 build 311

Studio Solr Integration 10.10.0 build 311

Studio Proxy for SC Integration 1.2.0 build 10

Studio CopyWithPlacements Integration 10.10.0 build 311

Release date: 19 May 2020

Downloads

New features

Changes

Documentation

Known issues

Fixed issues

Installation

Downloads

The download files for this version of Studio Server can be found in the Release announcement.

New features

No features have been added in this release of Studio Server.

Changes

Studio Server 10.10 is based on Enterprise Server 10.9 and is technically the same. Apart from re-branding it by changing logos and product name references at various places, no additional changes have been made.

Note: References to Enterprise, Smart Connection, and Content Station are still present in configuration options, folder names, and so on. These will be updated in a future release.

Documentation

Documentation for Studio Server is available on Help Center:

• Installing, configuring, and using Studio Server
• Compatibility Matrix

Note: Some screenshots in the product documentation may still show Enterprise Server. This will be updated over the coming weeks.

Known issues

No known issues exist for this release of Studio Server.

Fixed issues

No issues have been fixed in this release of Studio Server.

Installation

Choose one of the following installation paths:

• Installing Studio Server on a system on which it is not yet installed
• Upgrading an existing installation of Studio Server
• Upgrading from Enterprise Server

Versions 10.0–10.9

Release Notes for versions 10.0 to 10.9 are part of the Enterprise Server documentation.