Release Notes for Studio Server 10

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-14549 'Uncaught throwable TypeError' while updating a Print article created from a Digital article.

Installation

Choose one of the following installation paths:

Studio Server 10.46.0

Studio Server version 10.46.0 build 492

Release date: 14 November 2024

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 password validation for custom plug-ins has been removed. In the past, the Studio Server password validation support could be overruled by custom plug-ins. As of Studio Server version 10.43, this support has been marked as deprecated and, even if configured, this configuration does not overrule the Studio Server password validation.

Today, the Studio Server password validation covers all scenarios, including disabling validation. All of this is done without the use of custom plug-ins.

Studio Server 10.43.0 implemented a change by disabling the default WoodWing password to enhance our overall security measures. As part of this initiative, server passwords are now visible during database installation for standard administrative access.

However, we are also reviewing the handling of custom plug ins, which previously had the ability to bypass the Studio Server password validation. To ensure the continued security and integrity of WoodWing Studio Server, we are limiting the plug-ins capability to bypass the validation of passwords.

As a result, the related connector 'NameValidation_EnterpriseConnector' has been updated and the method 'validatePassword' has been marked as deprecated.

The password validation can now not be overruled anymore by custom plug-ins.

Customers who do not want to make use of the new configuration can add the configuration used in the previous Studio Server versions to the config_overrule.php file (see the instructions for upgrading to 10.43.0 and higher).

For help looking into your plug-ins, please reach out to your preferred partner or WoodWing account manager.

Further information about WoodWing integrations can be found on our WoodWing Integration marketplace.

The rules for deleting files after archiving to Assets Server in Print schema have been adjusted. When archiving print content from Studio Server versions 10.45 or lower, some scenarios exist in which published and unpublished content remains in the system, even though the option to delete files after archiving is selected.

These files that were not deleted were either still in use (for example because they are still placed on another layout or are part of another Dossier), or they were meant to be archived and cleaned up by using the Dossier schema.

In some practices though, the Dossier schema is quite often not enabled, resulting in many files that are already archived but never deleted in the workflow.

Cleaning up the system from these files that were intentionally not archived and not deleted is time consuming, for example because it first needs to be determined for each individual file if it is not used elsewhere.

Studio Server version 10.46.0 therefore introduces new business rules to reduce the number of images, Print articles, or Dossiers that are left behind after archiving (in other words: more images, Print articles, and Dossiers are now deleted).

Note: These rules only apply to the following configuration:

Archive schema - Print
The 'Delete files' option is enabled

For a full overview of these rules, see Archiving files from Studio Server 10.13.1 or higher to Assets Server.

Code has been removed and marked as deprecated. Global functions, class methods, classes, and modules in the code are regularly marked as deprecated. Customizations and integrations that make use of these functions should be updated accordingly.

The following modules have been deprecated in this release of Studio Server:

Deprecated (old)	Replacement (new)
NameValidation_EnterpriseConnector::validatePassword() method	Not available. Callers should no longer use it.

The following modules have been removed in this release of Studio Server:

Deprecated (old)	Replacement (new)	Deprecated since
BizWorkflow::validateWorkflowData method	BizWorkflow::validateWorkflowMetadata() method	10.33.0
WW_Utils_TransferClient:setCurlOptionsForSsl method	Not available. Callers should no longer use it.	10.33.0

For a full overview, see Code that has been deprecated or removed in Studio Server.

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 - updated
Code that has been deprecated or removed in Studio Server - updated
Compatibility of Studio Server 10.46 - new

Known issues

No known issues exist in this release of Studio Server.

Fixed issues

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

WSS-14230 Random layouts are ignored by InDesign Server and are not running through PDF automation.

WSS-14447 Preview and PDF for layout disappear after status is changed.

WSS-14469 Layout creation via planning tools / Dataplan sometimes leads to CopyFile error, and layout is not created.

WSS-14478 dbupgrade script error for Studio Server 10.43 and 10.44.

WSS-14479 After changing the 'Password Settings' option in the configuration file and logging in with the 'Full name' of the user, no 'Password expired' page appears.

WSS-14487 When adding a custom property of the same type and name in two different Brands, the property does not appear in the Dialog Setup for the second Brand.

Installation

Choose one of the following installation paths:

Studio Server 10.45.0

Studio Server version 10.45.0 build 487

Release date: 17 October 2024

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 compatibility of RabbitMQ has changed. Support for RabbitMQ version 3.13 has been added, support for RabbitMQ 3.11 has been dropped. The full compatibility of Studio Server 10.45 with RabbitMQ is as follows:

RabbitMQ 3.13	Recommended version.
RabbitMQ 3.12

Documentation

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

Compatibility of Studio Server 10.45 - new

Known issues

No known issues exist in this release of Studio Server.

Fixed issues

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

WSS-14203 TypeError messages appear when changing the status in multiple objects when the MadeToPrint plug-in is enabled.

WSS-14357 Add support for RabbitMQ 3.13 and drop support for RabbitMQ 3.11.

WSS-14364 Studio Server 10.42 without RabbitMQ does not let the Job Processor start.

WSS-14407 Database installation for Studio causes the 'woodwing' user password to generate a second time.

Installation

Choose one of the following installation paths:

Studio Server 10.44.0

Studio Server version 10.44.0 build 484

Release date: 19 September 2024

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 process of updating or deleting a custom property has been improved to prevent database conflicts and data corruption. When a custom property is updated or deleted, the server may need some time to fully update the database. This is especially true for large databases. When an update or delete action is being sent while another update or delete action is already in progress (for example because the same user is clicking Update or Delete multiple times, or multiple users are trying to update or delete custom properties at the same time), database conflicts or data corruption could occur.

To improve this process, actions are blocked while a process is in progress and users are given feedback about this. The following table shows the possible scenarios, the actions that take place, and the feedback that is given:

Scenario

Actions

The action is started while no other update or delete process is already running.

The action is processed by the server.

The page is grayed-out to prevent that the same action is sent multiple times.

A message is shown:

The action is being processed. Keep this page open to prevent data corruption.

A spinning icon is shown.

The action is started while another update or delete process is already running.

The action is not processed by the server.

A message is shown:

The database is currently busy and cannot process this action. Try again later.

Code has been removed and marked as deprecated. Global functions, class methods, classes, and modules in the code are regularly marked as deprecated. Customizations and integrations that make use of these functions should be updated accordingly.

The following modules have been deprecated in this release of Studio Server:

Deprecated (old)	Replacement (new)
BizCustomField::insertFieldAtModel() method	Not available. Callers should no longer use it.
BizInDesignServerJobs::updateObjectVersionByJobId() method	Not available. Callers should no longer use it.
BizProperty::collectCustomPropertyNamesFromCorePlugins() method	Not available. Callers should no longer use it.
BizProperty::convertCustomPropertyTypeToDB() method	WW_DbClasses_Adm_CustomProperty::mapPropertyTypeToDbType() method
DBCustomField::insertFieldAtModel() method	Not available. Callers should no longer use it.

The following modules have been removed in this release of Studio Server:

Deprecated (old)	Replacement (new)	Deprecated since
BizServerJob::formatTimeInSecondsWithMilliSeconds	DateTimeFunctions::formatUtcTimeWithMicroSeconds	10.31.0

For a full overview, see Code that has been deprecated or removed in Studio Server.

Documentation

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

Known issues

No known issues exist in this release of Studio Server.

Fixed issues

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

WSS-12962 Make adding and removing custom properties more robust.

WSS-14380 Admin apps: When the focus is not on the Submit button, pressing Enter leads to form submission.

Installation

Choose one of the following installation paths:

Studio Server 10.43.0

Studio Server version 10.43.0 build 480

Release date: 22 August 2024

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:

Password security has been improved by implementing the following changes:

Passwords to authenticate via LDAP are no longer stored in Studio Server. In previous versions, the password of the LDAP system is synchronized with Studio Server. Storing this password is now not done anymore because it is superfluous and it should only be stored in LDAP. Also, the configuration of passwords in Studio Server has become more restrictive (see below) and therefore will probably not match any current passwords in LDAP anymore.

When upgrading from a previous installation of Studio Server in which LDAP is integrated, it is recommended to let the LDAP users change their password so that it does not correspond with the stored password in Studio Server. Passwords previously synchronized to Studio Server remain in the server but will be ignored.

The configuration of passwords has become more strict by increasing the number of minimum required characters. In the Studio Server configuration, the required number of minimum characters has been increased:

	Version 10.43.0 and higher	Earlier versions
Minimum characters	8	1
Special characters	1	0
Characters in upper case	1	0
Characters in lower case	1	0

This configuration can be found in the configserver.php file:

define('PASSWORD_MIN_CHAR', 8);
define('PASSWORD_MIN_SPECIAL', 1);
define('PASSWORD_MIN_UPPER', 1);
define('PASSWORD_MIN_LOWER', 1)

When upgrading from an earlier version of Studio Server, take note of the following:

When a custom configuration has been added to the config_overrule.php file and these settings need to be kept, no action is required: the currently used passwords are in line with the configuration.

When the option ‘User Cannot Change Password’ is not enabled on the User Maintenance page for users and the default password configuration is not overruled, users will be prompted to update their password after the upgrade of Studio Server. This is because their password is not in line anymore with the new configuration.

When the option ‘User Cannot Change Password’ is enabled on the User Maintenance page for users and the default password configuration is not overruled, users will not be able to log in and are advised to contact their system administrator. To prevent this, the configuration used in the previous Studio Server version can be added to the config_overrule.php file so that the passwords are again in line with the configuration.

When you do not want to make use of the new configuration, the configuration used in the previous Studio Server version can be added to the config_overrule.php file.

The fixed password ‘ww’ for the ‘woodwing’ user is now replaced by a more secure, randomly generated password. After first installation of Studio Server, the system administrator could log in to the server by using password ‘ww’ for the user ‘woodwing’. These credentials are also documented in the installation instructions and in other articles and therefore publicly available. The installation steps include instructions to replace this default password by a more secure password, but when that is forgotten, the system becomes vulnerable.

To improve this, a randomly generated password for logging in to the system for the first time is now generated as part of the installation of the Studio Server database. During this process, the password is displayed and should at that time be copied. The password can then later be used for logging in to the system for the first time using user 'woodwing'.

The password is generated based on the password configuration in Studio Server (which itself has become more strict, see above).

For new installations, it is advised to set the password configuration before the database is installed so that it is in line with your company's security rules. The installation instructions have been updated with this step.

Code has been marked as deprecated. Global functions, class methods, classes, and modules in the code are regularly marked as deprecated. Customizations and integrations that make use of these functions should be updated accordingly.

In addition, all services defined in the /Enterprise/server/interfaces/AppSession.wsdl have been marked as deprecated. These services are no longer used and maintained.

The following modules have been deprecated in this release of Studio Server:

Deprecated (old)	Replacement (new)
AppServiceDispatcher class	Not available. Callers should no longer use it.
AppServiceDispatcher::__construct() method	Not available. Callers should no longer use it.
AppServiceDispatcher::handleJson() method	Not available. Callers should no longer use it.
AppServiceDispatcher::handleSoap() method	Not available. Callers should no longer use it.
'appservices.php' module	Not available. Callers should no longer use it.
AppSession class	Not available. Callers should no longer use it.
AppSession::GetObjectIcons() method	Not available. Callers should no longer use it.
AppSession::GetPubChannelIcons() method	Not available. Callers should no longer use it.
AppSession::InstantiateWidget() method	Not available. Callers should no longer use it.
AppSession::LogOff() method	Not available. Callers should no longer use it.
AppSession::LogOn() method	Not available. Callers should no longer use it.
AppSession::SendDiagnostics() method	Not available. Callers should no longer use it.
AppSessionTestApp class	Not available. Callers should no longer use it.
AppSessionTestApp::__construct() method	Not available. Callers should no longer use it.
AppSessionTestApp::testGetObjectIcons() method	Not available. Callers should no longer use it.
AppSessionTestApp::testGetPubChannelIcons() method	Not available. Callers should no longer use it.
AppSessionTestApp::testLogOff() method	Not available. Callers should no longer use it.
AppSessionTestApp::testLogOn() method	Not available. Callers should no longer use it.
AppSessionTestSoapProxy class	Not available. Callers should no longer use it.
AppSessionTestSoapProxy::__construct() method	Not available. Callers should no longer use it.
AppSessionTestSoapProxy::call() method	Not available. Callers should no longer use it.
BizDiagnostics class	Not available. Callers should no longer use it.
BizDiagnostics::handle() method	Not available. Callers should no longer use it.
BizResources::getObjectIcons() method	Not available. Callers should no longer use it.
BizResources::getPubChannelIcons() method	Not available. Callers should no longer use it.
BizUser::validatePassword() method	WW_BizClasses_PasswordRulesValidator::validate() method
DBConfig::getContactInfo() method	Not available. Callers should no longer use it.
Diagnostics class	Not available. Callers should no longer use it.
Diagnostics::execute() method	Not available. Callers should no longer use it.
GetObjectIcons class	Not available. Callers should no longer use it.
GetObjectIcons::execute() method	Not available. Callers should no longer use it.
GetPubChannelIcons class	Not available. Callers should no longer use it.
GetPubChannelIcons::execute() method	Not available. Callers should no longer use it.
SendDiagnostics class	Not available. Callers should no longer use it.
SendDiagnostics::execute() method	Not available. Callers should no longer use it.
'server/wwtest/appsessionservicetest.php' module	Not available. Callers should no longer use it.
WW_BizClasses_Facades_User::validatePassword() method	WW_BizClasses_PasswordRulesValidator::validate() method
WW_SOAP_AppClient class	Not available. Callers should no longer use it.
WW_SOAP_AppClient::__construct() method	Not available. Callers should no longer use it.
WW_SOAP_AppServer class	Not available. Callers should no longer use it.
WW_SOAP_AppServer::__construct() method	Not available. Callers should no longer use it.
WW_SOAP_AppServer::wsdlRequest() method	Not available. Callers should no longer use it.

For a full overview, see Code that has been deprecated or removed in Studio Server.

Documentation

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

Compatibility of Studio Server 10.43 - new
Studio Server full installation - updated
Upgrading an existing installation of Studio Server - updated
Changing the default WoodWing credentials in Studio Server - updated
Managing passwords in Studio Server - updated
Code that has been deprecated or removed in Studio Server - updated

Known issues

No known issues exist in this release of Studio Server.

Fixed issues

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

WSS-14204 Pentest Cross-site-scripting.

Installation

Choose one of the following installation paths:

Studio Server 10.42.0

Studio Server version 10.42.0 build 476

Release date: 25 July 2024

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:

A recurrent server job named RepairRabbitMQVirtualHost has been introduced to automatically manage the creation of RabbitMQ virtual hosts. In scenarios in which RabbitMQ connections are lost, the RabbitMQ virtual host can now automatically be restored by the use of the newly introduced RepairRabbitMQVirtualHost Server Job.

To make use of this server job, activate and configure it, and set up a recurring job for it. See Working with Studio Server Jobs in Studio Server.

Documentation

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

Compatibility of Studio Server 10.42 - new
Upgrading an existing installation of Studio Server - updated
Working with Studio Server Jobs in Studio Server - updated

Known issues

No known issues exist in this release of Studio Server.

Fixed issues

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

WSS-14241 The ionCube loaders contain a deprecated piece of code.

Installation

Choose one of the following installation paths:

Studio Server 10.41.0

Studio Server version 10.41.0 build 470

Release date: 27 June 2024

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:

When archiving files to Assets Server, files that are still checked out and would thereby cause the archiving process to fail, can now automatically be unlocked. When files stored in Studio Server are archived to Assets Server and any of the files is still checked out, the default behavior is that the archiving process fails. It could be namely that any changes to these files that are not yet saved need to be checked in first. In practice though, users often leave files checked out unintentionally and no unsaved changes exist.

Because keeping track of failed archiving processes, finding out why they failed, and re-archiving them can be a time consuming process, a new option has been added to automatically unlock any checked out files during the archiving process so that the process can continue. This should help in reducing the number of failed archiving processes because of files still being in a checked-out state.

This option is named 'Force abort check out after (interval)' and is part of the archiving options on the Brand Maintenance page. The option can be set to a predefined time period ranging from 1 hour to 3 weeks.

Note: The default value is 'Disabled'. This reflects the behavior in previous versions of Studio Server.

When a time period is defined, the behavior is as follows:

If the checked out date for all files falls outside the defined time period, the checked out files are unlocked via an abort check out action (note that any unsaved changes are then lost). This makes the files available for archiving and ensures that the archiving process does not fail for this reason.
If the date at which at least one checked out file falls within the defined time period, the archiving process fails.

Examples:

The Force abort check out after option is set to 1 week.
A layout is archived while one of the placed files was checked out 3 days prior and is not yet checked in.
Because the 3 days do not fall outside the set time period of 1 week, the archiving process fails.

The Force abort check out after option is set to 1 week.
A layout is archived while one of the placed files was checked out 2 weeks prior and is not yet checked in. All other files are checked in.
Because the 2 weeks fall outside the set time period of 1 week, the check out of the file is aborted and the archiving process continues.

The time period set for the Force abort check out after option of the candidate file (a layout, Digital article, or Dossier) is leading and overrules any time period set for any related files.

Example:

A layout belonging to Brand A is archived. The Force abort check out after option for Brand A is set to 1 week.

An image belonging to Brand B is placed on the layout. The Force abort check out after option for Brand B is set to 1 day.

When the layout is archived, the time period of 1 week is taken into account; the time period of 1 day is ignored.

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

Changes

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

The definition of the smart_objectlocks table in the database has changed: one column has been removed and one column has been added. As a result of adding the 'Force abort check out after (interval)' option (see above), the following changes to the smart_objectlocks table in the database have been made:
The existing column named ‘timestamp’ has been removed. This column was of type ‘timestamp’ which, in case of MSSQL, did not store the date and time information in an appropriate format for tracking when an object was locked.
A new column named ‘since’ has been added. This column stores the date and time information in the ISO8601 format (Y-m-dTH:i:s) and is therefore suitable for tracking when an object was locked.

Users who are upgrading from a previous version of Studio Server will be prompted to run the database upgrade script as part of the Health Check test during the upgrade process.

Code that was marked as deprecated has been removed. Global functions, class methods, classes, and modules in the code are regularly marked as deprecated. Customizations and integrations that make use of these functions should be updated accordingly. Code that was marked as deprecated in Studio Server 10.28 has now been removed.

For a full overview, see Code that has been deprecated or removed in Studio Server.

Documentation

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

Compatibility of Studio Server 10.41 - new
Code that has been deprecated or removed in Studio Server - updated
Archiving files from Studio Server 10.13.1 or higher to Assets Server - updated

Known issues

No known issues exist in this release of Studio Server.

Fixed issues

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

WSS-14193 GetPublications requests fail with an S1000 error due to a negative SortOrder for one or more of the Brands.

WSS-14214 Typo in sample code $cfgFieldHandlers['C_DATETEST"'] in the config_elvis.php file.

WSS-14219 Inconsistent translation for the term 'credit' in German.

WSS-14232 Error 'array_keys(): Argument #1 ($array) must be of type array, bool given' appears when accessing the DB admin page when upgrading to Studio Server 10.38.

Installation

Choose one of the following installation paths:

Studio Server 10.40.0

Studio Server version 10.40.0 build 462

Release date: 30 May 2024

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 PHP 8.2 has been added, support for PHP 7.4 has been dropped. The following changes to the support for PHP have been made:
Support for PHP 8.2 has been added (required patch level: PHP 8.2.14 or higher).
Support for PHP 8.1 has been kept, but requires an upgrade of ionCube loader.
Support for PHP 7.4 has been dropped.

Integrators providing their own custom server plug-ins should strive to make them compatible with PHP 8.2 (and preferably keep them backwards compatible with PHP 8.1).

Changes have been made to the compatibility with Adobe and ionCube. The following changes to the compatibility of Studio Server with other systems have been made:

Adobe

Support for Adobe CC 2019 has been dropped.

ionCube

Support for ionCube Loader 12.0.4 has been dropped.
Support for ionCube Loader 13.0.2 has been added.

The above applies to both PHP 8.1 and 8.2. In other words, even for PHP 8.1 an upgrade of ionCube Loader is required.

The Brand field in the dialog box for creating a Print variant from a Digital article in Studio is now disabled by Studio Server. To enforce that changing the Brand when creating a Print variant from a Digital article in Studio is not supported, Studio Server now disables the Brand field in the dialog box for creating a Print variant in Studio 11.168 or higher. When a combination of Studio Server 10.40.0 and Studio 11.168 (or higher) is not used, users are able to change the Brand but the action will fail with an unclear 'Missing function parameter (S1000)' message.

A new element named 'Context' has been added to the GetDialog2 in the WSDL for providing context about the action that is sent to the server. When a dialog box needs to be created in a client application, the application sends a getDialog2 request to Studio Server which then responds with a getDialog2Response containing the relevant information.

This element can be utilized for any purpose, simply by populating it with any relevant data associated with the getDialog2 service.

In the following section of code, the newly added element is highlighted.

<element name="GetDialog2"> 
  <complexType>
       <sequence>
              <element name="Ticket"  type="xsd:string"/>                         <!-- Ticket retrieved through LogOn. Mandatory. -->
              <element name="Action"  type="tns:Action"     nillable="true"/>     <!-- Workflow Action type. -->
              <element name="Context" type="xsd:string"    nillable="true" minOccurs="0" maxOccurs="1"/>  <!-- v10.40 Can be used to provide relevant information based on the dialog circumstances. -->
              <element name="MetaData" type="tns:ArrayOfMetaDataValue"  nillable="true"/> <!-- v8.0: MetaData value allows client app to round trip the data.-->
              <element name="Targets"  type="tns:ArrayOfTarget" nillable="true"/> <!-- v8.0: Object's targets. Data contained in Targets allow client app to round trip the data. -->
       </sequence>
  </complexType>
</element>

For more information about the WSDL, navigate to Advanced > Web Services SDK in Studio Server.

The 'RequestModes' parameter of the GetUsersRequest is not used anymore and has been marked as deprecated. The 'GetUsersRequest' parameter is used by client applications for retrieving registered users from the server, including user group information. This parameter is not used anymore and is therefore marked as deprecated.

Code has been removed and marked as deprecated. Global functions, class methods, classes, and modules in the code are regularly marked as deprecated. Customizations and integrations that make use of these functions should be updated accordingly.

The following modules have been deprecated in this release of Studio Server:

Deprecated (old)	Replacement (new)
BizFileStoreXmpFileInfo::getInDesignDocumentVersion() method	BizFileStoreXmpFileInfo::getLayoutInternalVersion() method
WflGetDialogService class	Not available. Callers should no longer use it.
WflGetDialogService::execute() method	\WflGetDialog2Service::execute() method
WflGetDialogService::runCallback() method	Not available. Callers should no longer use it.

The following functions that were deprecated in previous versions have been removed in this release of Studio Server:

Deprecated (old)	Replacement (new)	Deprecated since version
BizMetaDataPreview::generatePreviewLater() method	BizMetaDataPreview::generatePreviewNow() method	10.27.0
BizMetaDataPreview::getBufferAsFile() method	Not available. Callers should no longer use it.	10.27.0
BizMetaDataPreview::getJobConfig() method	Not available. Callers should no longer use it.	10.27.0
BizMetaDataPreview::runJob() method	Not available. Callers should no longer use it.	10.27.0
MimeTypeHandler::getExtensionMap() method	WW_Utils_MimeTypeHandler::getExtensionMap() method	10.28.0
MimeTypeHandler::mimeType2FileExt() method	WW_Utils_MimeTypeHandler::mimeType2FileExt() method	10.28.0
MimeTypeHandler::fileExt2MimeType() method	WW_Utils_MimeTypeHandler::fileExt2MimeType() method	10.28.0
MimeTypeHandler::filePath2MimeType() method	WW_Utils_MimeTypeHandler::filePath2MimeType() method	10.28.0
MimeTypeHandler::native2DBname() method	WW_Utils_MimeTypeHandler::native2DBname() method	10.28.0
MimeTypeHandler::filename2ObjType() method	WW_Utils_MimeTypeHandler::filename2ObjType() method	10.28.0
MimeTypeHandler::mime2ObjType() method	WW_Utils_MimeTypeHandler::mime2ObjType() method	10.28.0
MimeTypeHandler::isInCopy() method	WW_Utils_MimeTypeHandler::isInCopy() method	10.28.0
MimeTypeHandler::isJPEG() method	WW_Utils_MimeTypeHandler::isJPEG() method	10.28.0
MimeTypeHandler::repairMimetype() method	WW_Utils_MimeTypeHandler::repairMimetype() method	10.28.0
WW_Utils_MimeTypeHandler::mime2ObjType() method	WW_Utils_MimeTypeHandler::filename2ObjType() method	10.27.0
WW_Utils_ShellScript class	Not available. Callers should no longer use it.	10.27.0
WW_Utils_ShellScript::buildCmd() method	Not available. Callers should no longer use it.	10.27.0
WW_Utils_ShellScript::init() method	Not available. Callers should no longer use it.	10.27.0
WW_Utils_ShellScript::shell_exec() method	Not available. Callers should no longer use it.	10.27.0
WW_Utils_ShellTransferClient class	Not available. Callers should no longer use it.	10.27.0
WW_Utils_ShellTransferClient::__construct() method	Not available. Callers should no longer use it.	10.27.0
WW_Utils_ShellTransferClient::cleanupFile() method	Not available. Callers should no longer use it.	10.27.0
WW_Utils_ShellTransferClient::downloadContentInParallel() method	Not available. Callers should no longer use it.	10.27.0
WW_Utils_ShellTransferClient::downloadFile() method	Not available. Callers should no longer use it.	10.27.0
WW_Utils_ShellTransferClient::uploadFile() method	Not available. Callers should no longer use it.	10.27.0

Documentation

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

Compatibility of Studio Server 10.40 - new
Creating a print variant of a Digital article in Studio - updated
Code that has been deprecated or removed in Studio Server - updated
Upgrading an existing installation of Studio Server - updated

Known issues

No known issues exist in this release of Studio Server.

Fixed issues

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

WSS-12682 InDesign Server Automation robustness: clean up files before logout in case checkIn and abortCheckOut both fail.

WSS-14025 'Missing function parameter (S1000)' error is shown when changing the Brand while creating a Print variant via the context menu.

WSS-14074 Inconsistent time format for server jobs.

WSS-14171 Studio Server Jobs are not handling dates correctly.

Installation

Choose one of the following installation paths:

Studio Server 10.39.0

Studio Server version 10.39.0 build 460

Release date: 2 May 2024

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 process of determining in which InDesign Server version a layout needs to be opened has been improved by storing the version in a new table named ‘smart_layoutversions’ for quick reference. In environments in which multiple versions of InDesign Server are used and it is not known in which of the versions a layout needs to be opened (for example for generating a layout preview), previous versions of Studio Server had to always download the layout so that the version of InDesign in which the layout was created could be extracted from the XMP data.

To improve this time consuming process, the version of InDesign (together with the object ID of the layout) is now stored in the smart_layoutversions table after the initial download. The next time the layout needs to be processed, the table is now referenced for the version of InDesign Server in which it needs to be opened instead of downloading the file to obtain that information.

Note: When upgrading from an earlier version of Studio Server, this table is left empty. It will be populated over time when layouts are processed by InDesign Server. During the upgrade process, the Health Check test will prompt you to update the database with the new table.

A change has been made to the properties that are inherited when creating a file based on a template. When an article, Dossier, or layout is instantiated from a template in Studio or in Studio for InDesign and InCopy, it inherits some of the properties of the template. A change has been made to which properties are inherited compared to previous versions of Studio Server: some properties have been dropped and some properties have been added.

Dropped	Added
Description	Urgency
DescriptionAuthor	RouteTo

For a full overview, see Properties that are inherited when creating a file from a template in Studio or in Studio for InDesign and InCopy.

Code has been marked as deprecated. Global functions, class methods, classes, and modules in the code are regularly marked as deprecated. Customizations and integrations that make use of these functions should be updated accordingly.

The following modules have been deprecated in Studio Server 10.39.0:

Deprecated (old)	Replacement (new)
cookieMonster() function	Not available. Callers should no longer use it.

For a full overview, see Code that has been deprecated or removed in Studio Server.

Documentation

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

Known issues

No known issues exist in this release of Studio Server.

Fixed issues

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

WSS-13357 Dossier template values are not carried over when creating a new Dossier in Studio.

WSS-14100 A warning is raised when deleting an Access Profile from the Overview of Access Profiles page.

WSS-14113 No Error or Warning is raised when a user tries to delete a Category that has checked-out objects.

WSS-14136 Uploaded webp images do not get a width and height.

WSS-14148 Critical vulnerability – Execute code on server.

Installation

Choose one of the following installation paths:

Studio Server 10.38.1 build 458 Quick Patch

Studio Server version 10.38.1 build 458

Release date: 9 April 2024

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-14148 Prevent vulnerability issues when converting a data representation into a PHP data structure.

Installation

Choose one of the following installation paths:

Studio Server 10.38.0

Studio Server version 10.38.0 build 456

Release date: 4 April 2024

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:

Files in .xml format are now treated as objects of type 'Article', thereby making sure that uploading them does not fail. When uploading a file in .xml format (for example by using Studio), the file is now treated as an article. In previous versions, no object type was assigned to files in this format and the upload would fail with an unclear message in Studio: 'Some files could not be added. Please try again. Invalid status (S1017)'. To make the upload work, the object type had to be manually configured in Studio Server. This configuration is now included by default.

The configuration was changed in the EXTENSIONMAP section of the configserver.php file, where 'Article' has been added as the object type for .xml files.

define('EXTENSIONMAP', serialize(array(
...
     '.xml' => array( XMLTYPE, 'Article'),
...

When upgrading from a previous version and this change has already been made in the config_overrule.php file, no steps are needed as the mapping in this file takes precedence over the configserver.php file. The configuration can optionally be removed from the config_overrule.php file now that it is set by default in the configserver.php file.

The error message that is shown when a file with an unsupported extension is uploaded has been improved. In previous versions, when a file with an unsupported extension was uploaded in Studio, the upload would fail and an unclear message was shown:

Some files could not be added. Please try again. Invalid status (S1017).

To better inform the user about what is going on, the following message is now displayed:

The file type could not be detected because the extension is unknown. (S1079)

Information or guidance about the usage of MySQL databases in cloud environments is no longer provided. Starting from Studio Server version 10.38.0, WoodWing will no longer provide guidance or information regarding the usage of MySQL in an (AWS) cloud environment. This decision is motivated by our desire to streamline communication and ensure clarity for our users.

While previous compatibility guides indicated support for various MySQL flavors in an (AWS) cloud setup, our actual testing and support are focused on a single configuration of MySQL, which may evolve over time. Therefore, to avoid confusion, we have opted to specify only the exact versions of MySQL that we actively support, rather than attempting to enumerate the specific database flavors in AWS that are compatible. This approach aligns with how we handle compatibility statements for Studio Server with Microsoft SQL.

The current list of MySQL versions that are compatible with Studio Server 10.38.0 therefore now looks as follows:

MySQL 8.0	Recommended version.
MySQL 5.7

For more information about the compatibility of Studio Server with other systems, see the Compatibility of Studio Server 10.38.

Documentation

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

Compatibility of Studio Server 10.38 - new
Upgrading an existing installation of Studio Server - updated

Known issues

No known issues exist in this release of Studio Server.

Fixed issues

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

WSS-10631 File with an .xml extension cannot be uploaded into a Dossier in Studio and an unclear message is shown.

WSS-13281 Studio: Adding a file in an unsupported file format from Assets results in an object without a type.

WSS-13479 Frame Fitting Options on a graphic frame are defaulted to Fill Frame Proportionally after placing a Digital article in Studio.

WSS-13782 Block the injection of SQL code.

WSS-14060 Make the preview generation of the Studio Print editor more reliable by updating the app.doScript call.

WSS-14066 The licensing serial prefix is sometimes missing on the licensing activation page despite having products already activated.

WSS-14080 When deleting a Category which is assigned to offline objects, a 'Missing function parameters' error is raised.

WSS-14082 After deleting a Brand using the 'Delete Selected' option on the Brands page, warnings are generated.

Installation

Choose one of the following installation paths:

Studio Server 10.37.1 build 454 Quick Patch

Studio Server version 10.37.1.0 build 454

Release date: 20 March 2024

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-14120 The value of a boolean-type custom property is not interpreted correctly and not stored correctly in the database.

Note: Studio Server 10.37.0 introduced a change in the behavior of custom properties of type boolean in which the boolean value was handled too strictly. As a result, when a non-boolean value was sent, the value was interpreted incorrectly (for example: "false" (a string) became true in Studio Server).

With this fix, a boolean custom property now accepts the following values:

"true" (case insensitive)
"false" (case insensitive)
1
"1"
0
"0"

Installation

Choose one of the following installation paths:

Studio Server 10.37.0

Studio Server version 10.37.0 build 449

Release date: 7 March 2024

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:

Code has been removed or marked as deprecated. Global functions, class methods, classes, and modules in the code are regularly marked as deprecated and eventually removed from the code. Customizations and integrations that make use of these functions should be updated accordingly.

The following modules have been deprecated in Studio Server 10.37.0:

Deprecated (old)	Replacement (new)
WW_Utils_ZipUtility::extractArchive() method	Not available. Callers should no longer use it.
WW_Utils_ZipUtility_CommandLine::extractArchive() method	Not available. Callers should no longer use it.
WW_Utils_ZipUtility_ZipArchive::extractArchive() method	Not available. Callers should no longer use it.

The following functions that were deprecated in previous versions have been removed in Studio Server 10.37.0:

Deprecated (old)	Replacement (new)	Deprecated since version
WW_DbDrivers_DriverBase::autoincrement() method	Not available. Callers should no longer use it.	10.11.0

For a full overview, see Code that has been deprecated or removed in Studio Server.

Documentation

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

Compatibility of Studio Server 10.37 - new
Code that has been deprecated or removed in Studio Server - updated

Known issues

No known issues exist in this release of Studio Server.

Fixed issues

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

WSS-12709 The value of a custom property synchronized to Assets shows correctly in the Properties panel but not in a List view column.

WSS-13781 Block the file inclusion and arbitrary file write via an archive extraction.

WSS-14011 Hide the Delete button on the User Groups Maintenance page when the group is not created yet.

WSS-14030 Archive jobs fail if there is a candidate placed on a layout where this layout has a null value for the C_ELVIS_ARCHIVESTATUS field in the database.

Installation

Choose one of the following installation paths:

Studio Server 10.36.3 build 455 Quick Patch

Studio Server version 10.36.3.0 build 455

Release date: 20 March 2024

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-14120 The value of a boolean-type custom property is not interpreted correctly and not stored correctly in the database.

Note: Studio Server 10.36.0 introduced a change in the behavior of custom properties of type boolean in which the boolean value was handled too strictly. As a result, when a non-boolean value was sent, the value was interpreted incorrectly (for example: "false" (a string) became true in Studio Server).

With this fix, a boolean custom property now accepts the following values:

"true" (case insensitive)
"false" (case insensitive)
1
"1"
0
"0"

Installation

Choose one of the following installation paths:

Studio Server 10.36.0

Studio Server version 10.36.0 build 447

Release date: 7 February 2024

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 3rd-party software. Various changes have been made to the compatibility between Studio Server and other systems.

RabbitMQ:
Added support for RabbitMQ 3.12 (recommended version).
Dropped support for RabbitMQ 3.9 (is out of support per 31 July 2023).

Solr:
Added support for Solr 9.4 (recommended version)
Dropped support for Solr 8.11 (will soon be end of life)

Adobe 2024. Studio Server 10.36 is compatible with Studio for InDesign and InCopy 2024.

Code has been removed or marked as deprecated. Global functions, class methods, classes, and modules in the code are regularly marked as deprecated and eventually removed from the code. Customizations and integrations that make use of these functions should be updated accordingly.

The following modules have been deprecated in Studio Server 10.36.0:

Deprecated (old)	Replacement (new)
BizTransferServer::copyFromFileTransferServer() method	Not available. Callers should no longer use it.
FileStorage::getSize() method	Not available. Callers should no longer use it.
FileStorage::getSoap() method	Not available. Callers should no longer use it.
FileStorage::listFilenames() method	Not available. Callers should no longer use it.

The following functions that were deprecated in previous versions have been removed in Studio Server 10.36.0:

Deprecated (old)	Replacement (new)	Deprecated since version
BizPublication::getCategoryInfos function	WW_BizClasses_Wfl_Publication::getCategoryInfos function	10.23.0

For a full overview, see Code that has been deprecated or removed in Studio Server.

The Axaio MadeToPrint parameter '$layEdition' within the 'outputProcessingFilesBegin' method can now be updated from within the method. The method AxaioMadeToPrintDispatcher_EnterpriseConnector::
outputProcessingFilesBegin has changed its signature from:

public function outputProcessingFilesBegin(string $layoutId, string $layStatusId, array &$fullRow, ?Edition $layEdition, string $publId, bool &$break): void

to:

public function outputProcessingFilesBegin(string $layoutId, string $layStatusId, array &$fullRow, ?Edition &$layEdition, string $publId, bool &$break): void

The $layEdition parameter is now passed by reference which makes it possible to update this variable within the method.

This change affects all customers who are implementing this method on any existing customization. Customers who are upgrading from a previous version of Studio Server should therefore check if the layEdition variable is modified within the same method. If that is the case, this change could create breaking customizations: if the $layEdition is changed within this function, the behavior can change from the caller perspective.

Documentation

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

Compatibility of Studio Server 10.36 - new
Code that has been deprecated or removed in Studio Server - updated
Upgrading an existing installation of Studio Server - updated

Known issues

No known issues exist in this release of Studio Server.

Fixed issues

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

WSS-13533 Web service validation errors are logged when placing an image on a Master page in InDesign.

WSS-13722 Small adaptations to the Axaio MadeToPrint Dispatcher plug-in.

WSS-13780 Block cross-site Scripting (XSS) attacks.

WSS-13819 Improve API to prevent command injection.

WSS-13878 Add support for RabbitMQ 3.12 and drop support for RabbitMQ 3.9.

WSS-13880 Add support for Solr 9.4 and drop support for Solr 8.11.

Installation

Choose one of the following installation paths:

Studio Server 10.35.0

Studio Server version 10.35.0 build 445

Release date: 18 January 2024

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:

Serial numbers on License Maintenance pages are no longer shown in readable form. For security reasons, serial numbers are no longer displayed in readable form on the License Maintenance pages, but are either obfuscated or fields in which they were automatically added are now left empty.

This affects the following pages:

On the License Status page, the last 10 characters are replaced by asterisks (***** *****).

On the License Registration page, the serial number is no longer automatically filled in when activating a license. In a note below the field, the start of the serial number is now shown in readable form while the last 10 characters are replaced by asterisks (***** *****). The correct serial number now has to be entered manually.

Note: As a result of this change, the administrator needs to keep record of the serial numbers; copying and pasting them from the License Status page is no longer possible.

On the License Unregister page, the license number can no longer be looked up by using the Inspect option of the web browser. A Serial Number field is now shown, which is empty and editable. Below the field, a note is shown in which the start of the serial number is given in readable form while the last 10 characters are replaced by asterisks (***** *****). The correct serial number now has to be entered manually. When the field is left empty or when an incorrect serial number is entered, clicking the Next button will result in the unregistration process failing with an error.

Note: As a result of this change, the administrator needs to keep record of the serial numbers; copying and pasting them from the License Status page is no longer possible.

InDesign Server Jobs with status 'Incompatible' are no longer re-planned to prevent other jobs from getting stuck. In previous versions of Studio Server, when InDesign Server Jobs could not be processed because no InDesign Server of the correct version was activated or configured, the jobs were set to status ‘Incompatible’. They were then set to status ‘Replanned’ when the InDesign Server Dispatcher process came to an end and were processed when a new InDesign Server Dispatcher process started and a matching InDesign Server was available.

However, this process kept repeating itself when no matching InDesign Server became available, thereby wasting a lot of the InDesign Server Dispatcher process time and resulting in other jobs getting stuck because they were not picked up.

In Studio Server 10.35.0 and higher therefore, the status of InDesign Server Jobs with status 'Incompatible' are no longer set to 'Replanned' but left on the 'Incompatible' status.

Once a matching InDesign Server is configured, these jobs can be manually restarted on the InDesign Server Jobs page by clicking their cog wheel icon.

Code has been removed or marked as deprecated. Global functions, class methods, classes, and modules in the code are regularly marked as deprecated and eventually removed from the code. Customizations and integrations that make use of these functions should be updated accordingly.

The following modules have been deprecated in Studio Server 10.35.0:

Deprecated (old)	Replacement (new)
HtmlTextImport class	Not available. Callers should no longer use it.
HtmlTextImport::__construct() method	Not available. Callers should no longer use it.
HtmlTextImport::getOpenHyperlinkInSameWindow() method	Not available. Callers should no longer use it.
HtmlTextImport::setOpenHyperlinkInSameWindow() method	Not available. Callers should no longer use it.
ICDBHyperlink class	Not available. Callers should no longer use it.
ICDBHyperlink::__construct() method	Not available. Callers should no longer use it.
ICDBHyperlink::createEndPI() method	Not available. Callers should no longer use it.
ICDBHyperlink::createHyperlink4Href() method	Not available. Callers should no longer use it.
ICDBHyperlink::createHyperlinkXHTML() method	Not available. Callers should no longer use it.
ICDBHyperlink::createStartPI() method	Not available. Callers should no longer use it.
ICDBHyperlink::findHyperlink4Href() method	Not available. Callers should no longer use it.
ICDBHyperlink::findHyperlink4ResId() method	Not available. Callers should no longer use it.
ICDBHyperlink::getEndRC() method	Not available. Callers should no longer use it.
ICDBHyperlink::getStartRC() method	Not available. Callers should no longer use it.
ICDBToken class	Not available. Callers should no longer use it.
ICDBToken::__construct() method	Not available. Callers should no longer use it.
ICDBToken::toString() method	Not available. Callers should no longer use it.
InCopyHyperlinkStack class	Not available. Callers should no longer use it.
InCopyHyperlinkStack::addLink() method	Not available. Callers should no longer use it.
InCopyHyperlinkStack::getCurrentLink() method	Not available. Callers should no longer use it.
InCopyHyperlinkStack::removeLink() method	Not available. Callers should no longer use it.
InCopyTextExport class	Not available. Callers should no longer use it.
InCopyTextExport::exportBuf() method	Not available. Callers should no longer use it.
InCopyTextExport::exportFile() method	Not available. Callers should no longer use it.
InCopyTextExport::pushTsxrAttrs() method	Not available. Callers should no longer use it.
InCopyTextImport class	Not available. Callers should no longer use it.
InCopyTextImport::__construct() method	Not available. Callers should no longer use it.
InCopyTextImport::enableInlineImageProcessing() method	Not available. Callers should no longer use it.
InCopyTextImport::getInlineImages() method	Not available. Callers should no longer use it.
InCopyTextImport::importBuf() method	Not available. Callers should no longer use it.
InCopyTextImport::importFile() method	Not available. Callers should no longer use it.
InCopyTextImport::importTemplate() method	Not available. Callers should no longer use it.
InCopyUser class	Not available. Callers should no longer use it.
InCopyUser::__construct() method	Not available. Callers should no longer use it.
InCopyUtils::cmyk2rgb() method	Not available. Callers should no longer use it.
InCopyUtils::createNewResourceId() method	Not available. Callers should no longer use it.
InCopyUtils::freeFontSizeHTML2IC() method	Not available. Callers should no longer use it.
InCopyUtils::freeFontSizeIC2HTML() method	Not available. Callers should no longer use it.
InCopyUtils::getColorRGB() method	Not available. Callers should no longer use it.
InCopyUtils::getDefaultCharStyle() method	Not available. Callers should no longer use it.
InCopyUtils::getDefaultParaStyle() method	Not available. Callers should no longer use it.
InCopyUtils::hex2rgb() method	Not available. Callers should no longer use it.
InCopyUtils::lab2rgb() method	Not available. Callers should no longer use it.
InCopyUtils::rgb2hex() method	Not available. Callers should no longer use it.
PlainTextExport class	Not available. Callers should no longer use it.
PlainTextExport::exportBuf() method	Not available. Callers should no longer use it.
PlainTextExport::exportFile() method	Not available. Callers should no longer use it.
PlainTextImport class	Not available. Callers should no longer use it.
PlainTextImport::enableInlineImageProcessing() method	Not available. Callers should no longer use it.
PlainTextImport::getInlineImages() method	Not available. Callers should no longer use it.
PlainTextImport::importBuf() method	Not available. Callers should no longer use it.
PlainTextImport::importFile() method	Not available. Callers should no longer use it.
StoryResourceDef class	Not available. Callers should no longer use it.
StoryResourceDef::__construct() method	Not available. Callers should no longer use it.
StoryResourceDef::setData() method	Not available. Callers should no longer use it.
TextConverter class	Not available. Callers should no longer use it.
TextConverter::createTextExporter() method	Not available. Callers should no longer use it.
TextConverter::createTextImporter() method	Not available. Callers should no longer use it.
TextConverter::export() method	Not available. Callers should no longer use it.
TextConverter::import() method	Not available. Callers should no longer use it.
TextExport class	Not available. Callers should no longer use it.
TextImport class	Not available. Callers should no longer use it.
WW_TextConverters_Wcml2Xhtml class	Not available. Callers should no longer use it.
WW_TextConverters_Wcml2Xhtml::convert() method	Not available. Callers should no longer use it.
WW_TextConverters_Wcml2Xhtml::cssEncode() method	Not available. Callers should no longer use it.
WW_TextConverters_Wcml2Xhtml::enableInlineImageProcessing() method	Not available. Callers should no longer use it.
WW_TextConverters_Wcml2Xhtml::getDocDomVersion() method	Not available. Callers should no longer use it.
WW_TextConverters_Wcml2Xhtml::getDocType() method	Not available. Callers should no longer use it.
WW_TextConverters_Wcml2Xhtml::getInlineImages() method	Not available. Callers should no longer use it.
WW_TextConverters_Wcml2Xhtml::getOutputAsDOM() method	Not available. Callers should no longer use it.
WW_TextConverters_Wcml2Xhtml::getOutputAsString() method	Not available. Callers should no longer use it.
WW_TextConverters_Wcml2Xhtml::getStories() method	Not available. Callers should no longer use it.
WW_TextConverters_Wcml2Xhtml::getStylesCSS() method	Not available. Callers should no longer use it.
WW_TextConverters_Wcml2Xhtml::importBuf() method	Not available. Callers should no longer use it.
WW_TextConverters_Wcml2Xhtml::importFile() method	Not available. Callers should no longer use it.
WW_TextConverters_Wcml2Xhtml::setCustomCSS() method	Not available. Callers should no longer use it.

The following functions that were deprecated in previous versions have been removed in Studio Server 10.35.0:

Deprecated (old)	Replacement (new)	Deprecated since version
BizPublication::getPublicationInfo method	WW_BizClasses_Wfl_Publication::getPublicationInfosByRequestInfo method	10.22.0
BizPublication::getPublicationInfos method	WW_BizClasses_Wfl_Publication::getPublicationInfosByRequestInfo method	10.22.0
BizPublication::getPublicationInfosByRequestInfo method	WW_BizClasses_Wfl_Publication::getPublicationInfosByRequestInfo method	10.22.0
BizPublication::getPublications method	WW_BizClasses_Wfl_Publication::getPublicationInfosByRequestInfo method	10.22.0
PubMgr::getEditions method	BizPublication::getEditions method	10.22.0
PubMgr::getIssues method	BizPublication::getIssues method	10.22.0
PubMgr::getPublications method	WW_BizClasses_Wfl_Publication::getPublicationInfosByRequestInfo method	10.22.0
PubMgr::getSections method	BizPublication::getSections method	10.22.0
PubMgr::getStates method	BizWorkflow::getStates method	10.22.0

For a full overview, see Code that has been deprecated or removed in Studio Server.

Documentation

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

Compatibility of Studio Server 10.35 - new
Code that has been deprecated or removed in Studio Server - updated
Managing licenses in Studio Server - updated
The License Status page in Studio Server - updated

Known issues

No known issues exist in this release of Studio Server.

Fixed issues

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

WSS-13754 InDesign Server Automation Jobs get stuck as Planned when old layouts are in the queue.

WSS-13779 Block SQL Injection.

WSS-13809 Localization: Text in French contain escape characters.

WSS-13907 Uploading badly encoded text file raises an 'Uncaught throwable ParseError'.

WSS-13928 The first defined Workflow status of the object type is used when CreateObjectsRequest is sent in without a workflow status.

WSS-13933 The Delete Selection button is not working when language is set to Italian.

WSS-13935 Archive processing job reattempts to get the semaphore to frequently, resulting in many repetative errors in the log file.

WSS-13951 Timestamp of the log is not always correct when the log entries are first dumped into memory.

Installation

Choose one of the following installation paths:

Studio Server 10.34.0

Studio Server version 10.34.0 build 442

Release date: 14 December 2023

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:

Code has been removed or marked as deprecated. Global functions, class methods, classes, and modules in the code are regularly marked as deprecated and eventually removed from the code. Customizations and integrations that make use of these functions should be updated accordingly.

The following modules have been deprecated in Studio Server 10.34.0:

Deprecated (old)	Replacement (new)
'server/apps/reportdeadlines.php' module	Not available. Callers should no longer use it.
'server/apps/sendmsg.php' module	Not available. Callers should no longer use it.
'server/apps/unlock.php' module	Not available. Callers should no longer use it.
'server/apps/video.php' module	Not available. Callers should no longer use it.
'soapattachment.php' module	Not available. Callers should no longer use it.

The following functions that were deprecated in previous versions have been removed in Studio Server 10.34.0:

Deprecated (old)	Replacement (new)	Deprecated since version
BizWorkflow::validateMultipleTargets() method	BizWorkflow::validateTargetsForCreateOperation() method	10.21.0
BizWorkflow::validateMultipleTargets() method	BizWorkflow::validateTargetsForUpdateOperation() method	10.21.0

For a full overview, see Code that has been deprecated or removed in Studio Server.

The coding style for PHP modules has been changed into PSR-12. This style is automatically applied to the entire code base of Studio Server using the PHP CS Fixer tool. The tool itself is shipped with Studio Server from now onwards and can be found in the server/vendor/bin folder.

For consistency and readability reasons you may want to apply the PSR-12 code style to your custom server plug-ins as well. For details, see Managing Server plug-ins in Studio Server.

The .csv file format is now supported by default. The .csv format has been added to the configserver.php file > EXTENSIONMAP list and is therefore now supported by default by Studio Server.

Documentation

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

Compatibility of Studio Server 10.34 - new
Code that has been deprecated or removed in Studio Server - updated
Upgrading an existing installation of Studio Server - updated
Managing Server plug-ins in Studio Server - updated
File formats supported by Studio Server - updated

Known issues

No known issues exist in this release of Studio Server.

Fixed issues

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

WSS-12980 The smart_config table can be overloaded with records when 'enterprise_system_id' or 'local_cache_buckets' contain duplicates.

Installation

Choose one of the following installation paths:

Studio Server 10.33.0

Studio Server version 10.33.0 build 440

Release date: 16 November 2023

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:

Code has been removed or marked as deprecated. Global functions, class methods, and classes in the code are regularly marked as deprecated and eventually removed from the code. Customizations and integrations that make use of these functions should be updated accordingly.

The following functions have been deprecated in Studio Server 10.33.0:

Deprecated (old)	Replacement (new)
BizWorkflow::validateWorkflowData() method	BizWorkflow::validateWorkflowMetadata() method
WW_Utils_TransferClient::setCurlOptionsForSsl() method	Not available. Callers should no longer use it.

The following functions that were deprecated in previous versions have been removed in Studio Server 10.33.0:

Deprecated (old)	Replacement (new)	Deprecated since version
DBUserSetting::purgeSettings() method	DBUserSetting::deleteAllSettingsByUserShortName() method	10.20.0
WW_DbClasses_Wfl_Query_QueryObjectComposer::filterOnAuthorizationAndBrandsId() method	WW_DbClasses_Wfl_Query_QueryObjectComposer::addFilterOnUserRights() method	10.20.0

For a full overview, see Code that has been deprecated or removed in Studio Server.

Documentation

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

Code that has been deprecated or removed in Studio Server - updated
Upgrading an existing installation of Studio Server - updated
Studio Server full installation - updated
Compatibility of Studio Server 10.33 - new

Known issues

No known issues exist in this release of Studio Server.

Fixed issues

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

WSS-13649 Studio Server processes unsupported field values when sent via API.

WSS-13744 Studio Server 10.28 and 10.29 return 'Uncaught throwable ‘TypeError' when changing the Description field of an image using the SetObjectProperties SDK call.

WSS-13776 Block access to arbitrary server files.

WSS-13868 Invalid 'Login' link in the e-mail for certain configurations.

Installation

Choose one of the following installation paths:

Studio Server 10.32.0

Studio Server version 10.32.0 build 430

Release date: 19 October 2023

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:

Deprecated code has been removed. Global functions, class methods, and classes in the code are regularly marked as deprecated and eventually removed from the code. Customizations and integrations that make use of these functions should be updated accordingly.

The following functions that were deprecated in previous versions have been removed in Studio Server 10.32.0:

Deprecated (old)	Replacement (new)	Deprecated since version
BizObject::isAlternateLayout() method	Not available. Callers should no longer use it.	10.19.0
BizRelation::getDeletedPlacedRelations() method	BizRelation::getPlacedRelationsToDelete() method	10.19.0

For a full overview, see Code that has been deprecated or removed in Studio Server.

Documentation

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

Code that has been deprecated or removed in Studio Server - updated
Compatibility of Studio Server 10.32 - new

Known issues

No known issues exist in this release of Studio Server.

Fixed issues

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

WSS-13770 The call to run the InDesignServerjob 'main' script occasionally causes fatal transaction level issues in InDesign and InDesign Server.

WSS-13786 DeleteAdverts returns message related to 'createAdvert' when the service request is incomplete.

Installation

Choose one of the following installation paths:

Studio Server 10.31.0

Studio Server version 10.31.0 build 429

Release date: 21 September 2023

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:

Compatibility with Red Hat Linux. The following changes have been made to the compatibility between Studio Server and Red Hat Linux:
Support for RHEL 9 has been added and marked as the recommended version.

Notes:

Support for the Apache module mod_php has been dropped from RHEL 9.
Apache in combination with PHP-FPM can be used instead.

Support for RHEL 7 has been dropped.

Code has been removed or marked as deprecated. Global functions, class methods, and classes in the code are regularly marked as deprecated and eventually removed from the code. Customizations and integrations that make use of these functions should be updated accordingly.

The following functions have been marked as deprecated in Studio Server 10.31.0:

Deprecated (old)	Replacement (new)
BizServerJob::formatTimeInSecondsWithMilliSeconds() method	DateTimeFunctions::formatUtcTimeWithMicroSeconds() method

The following functions that were deprecated in previous versions have been removed in Studio Server 10.31.0:

Deprecated (old)	Replacement (new)	Deprecated since version
authorizationmodule::getRightsCached() method	Not available. Callers should no longer use it.	10.18.0
DBPlacements::getPlacementsOfArticlesPlacedOnLayout() method	Not available. Callers should no longer use it.	10.18.0
DBPlacements::getPlacementsWithPageOrientation() method	Not available. Callers should no longer use it.	10.18.0
WW_BizClasses_Wfl_Publication::getAuthorizedStates() method	WW_BizClasses_Wfl_Publication::getAuthorizedStatesByBrandsId() method	10.18.0
WW_BizClasses_Wfl_Publication::getSectionInfos() method	WW_BizClasses_Wfl_Publication::getCategoryInfos() method	10.18.0
WW_BizClasses_Wfl_Publication::getStateInfos() method	WW_BizClasses_Wfl_Publication::getStateInfosForBrandsId() method	10.18.0

For a full overview, see Code that has been deprecated or removed in Studio Server.

Documentation

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

Compatibility of Studio Server 10.31 - new
Compatibility of Linux with WoodWing applications - updated
Code that has been deprecated or removed in Studio Server - updated

Known issues

No known issues exist in this release of Studio Server.

Fixed issues

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

WSS-13240 Users are able to place images in the Print editor of Studio on layers that are locked in InDesign.

WSS-13687 When archiving images that are used in multiple Issues, Dossiers, or layouts, the ELVIS_ARCHIVESTATUS field is not populated.

WSS-13704 Server jobs are queued for 2 hours before being processed.

WSS-13746 The Routing section on the Brand maintenance page is not sorted correctly.

WSS-13794 When exporting an image, no versions are shown under 'Show Image Versions', and an uncaught throwable 'TypeError' is raised in the log files.

Installation

Choose one of the following installation paths:

Studio Server 10.30.0

Studio Server version 10.30.0 build 427

Release date: 24 August 2023

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:

A change to the database has been made. In preparation of upcoming functionality, a change to the database has been made. When upgrading from a previous version and running the Health Check test, you will therefore be prompted to have the database updated.

Various default configuration values for communicating with Studio have changed. When using Studio Server in combination with Studio, configuration steps are required to make both applications work seamlessly together. The default values of various options have changed, as shown below.

Note: When the old values are used in a current production system and need to be maintained, these values can be defined in the config_overrule.php file as part of the upgrade steps of Studio Server.

In the configserver.php file of Studio Server:

Option: MESSAGE_QUEUE_CACERT_FILE
Description: cURL certificate file for the secure RabbitMQ connections over SSL listed in the MESSAGE_QUEUE_CONNECTIONS option.
Old default value: BASEDIR.'/config/encryptkeys/rabbitmq/cacert.pem'.
New default value: '' (empty string).
Reason: Security improvement.

Option: EVENT_BUS_CACERT_FILE
Description: cURL certificate file for the secure RabbitMQ connections over SSL listed in the EVENT_BUS_CONNECTIONS option.
Old default value: BASEDIR.'/config/encryptkeys/rabbitmq/cacert.pem'.
New default value: '' (empty string).
Reason: Security improvement.

Option: EXIFTOOL_APP_PATH
Description: Full path to the folder of the ExifTool application.
Old default value:
Windows OS: 'C:/Program Files/ExifTool'.
Linux: '/usr/local/bin'.
New default value: '/usr/bin'.
Reason: This is the default path for Linux installations. Studio Server does not check the operating system, and the default value is always the same.

Option: IMAGE_MAGICK_APP_PATH
Description: Full path to the folder of the ImageMagick application.
Old default value: '' (empty string).
New default value: '/usr/bin'.
Reason: This is the default path for Linux installations.

Option: GHOST_SCRIPT_APP_PATH
Description: Full path to the folder of the GhostScript application.
Old default value: '' (empty string).
New default value: '/usr/bin'.
Reason: This is the default path for Linux installations.

Option: EXPIREDEFAULT
Description: Generic logon expiration time.
Old default value: 1 day.
New default value: 8 hours.
Reason: Security improvement.

In the config.php file of Studio:

Option: CS_URL
Description: Defines the URL through which Studio Server redirects a user to WoodWing Studio.
Old default value: SERVERURL_ROOT.INETROOT.'/contentstation/'.
New default value: SERVERURL_ROOT.'/app/'.
Reason: Content Station is not used anymore. Instead, a more generic URL is used for connecting to Studio.

Documentation

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

Compatibility of Studio Server 10.30 - new
Upgrading an existing installation of Studio Server - updated
Integrating RabbitMQ in Studio Server - updated

Known issues

No known issues exist in this release of Studio Server.

Fixed issues

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

WSS-12354 InDesign Server jobs are marked as Incompatible when all InDesign Servers are busy.

Installation

Choose one of the following installation paths:

Studio Server 10.29.0

Studio Server version 10.29.0 build 424

Release date: 27 July 2023

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: Re-archived Digital articles are now always 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.

In Studio Server 10.23.0, this functionality was changed so that the re-archived article is always stored in its own folder.

If this behavior was not desired, an option was made available in Studio Server 10.23.0 to continue using the old behavior. This was done by adding the following option to the SERVERFEATURES section of the configserver.php file:

ArchiveDigitalArticlesInOriginalLocation

As mentioned in the Release Notes of Studio Server 10.23.0, the old behavior was scheduled to be phased out. This has now been done; the option to revert back to the old behavior has been removed. As a result, re-archived Digital articles are now always archived in their own folder.

If the option is still configured, the WoodWing Assets Content Source test on the Health Check page will notify you of this.

Documentation

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

Compatibility of Studio Server 10.29 - new

Known issues

No known issues exist in this release of Studio Server.

Fixed issues

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

WSS-13378 When exporting PDF files from the Export page, nothing happens.

WSS-13606 Solr shows 100% even when not all objects are indexed.

WSS-13622 'Uncaught throwable 'TypeError'' message when uploading files in Studio.

Installation

Choose one of the following installation paths:

Studio Server 10.28.0

Studio Server version 10.28.0 build 423

Release date: 29 June 2023

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:

Performing searches for 'last week' and 'next week' using QueryObjects has changed; searching for 'this week' has been added. Users of Studio and Studio for InDesign and InCopy can quickly perform a search in Studio Server to locate particular files. One type of search that can be done is using a date range that spans last week or next week. The QueryObjects request for these ranges has changed while it is now also possible to search for 'this week'.

The following changes have been made based on QueryObjects requests using the 'starts' operator:

Request

Range

Change

-P7D

Last week.

Deprecated.

Use -P1W instead.

P7D

Next week.

Deprecated.

Use P1W instead.

P0W

This week.

New.

For more information about these changes, see Object Searching in the Studio Server Web Services Guide.

Code has been marked as deprecated or removed. Global functions, class methods, and classes in the code are regularly marked as deprecated and eventually removed from the code. Customizations and integrations that make use of these functions should be updated accordingly.

The following functions have been marked as deprecated in Studio Server 10.28.0:

Deprecated (old)	Replacement (new)
BizInDesignServer::nextIDSWithUnknownVersion() method	Not available. Callers should no longer use it.
DBInDesignServer::nextIDSWithUnknownVersion() method	Not available. Callers should no longer use it.
DateTimeFunctions::calculateDateTime() method	Not available. Callers should no longer use it.
DateTimeFunctions::getDaysToNextFirstDay() method	Not available. Callers should no longer use it.
DateTimeFunctions::getDaysToPrevFirstDay() method	Not available. Callers should no longer use it.
Flags class	Not available. Callers should no longer use it.
Flags::__construct() method	Not available. Callers should no longer use it.
Flags::addBits() method	Not available. Callers should no longer use it.
Flags::addFlags() method	Not available. Callers should no longer use it.
Flags::bits2flags() method	Not available. Callers should no longer use it.
Flags::clear() method	Not available. Callers should no longer use it.
Flags::flags2bits() method	Not available. Callers should no longer use it.
Flags::getBits() method	Not available. Callers should no longer use it.
Flags::getFlags() method	Not available. Callers should no longer use it.
Flags::hasBit() method	Not available. Callers should no longer use it.
Flags::hasFlag() method	Not available. Callers should no longer use it.
Flags::listAllNames() method	Not available. Callers should no longer use it.
Flags::removeBits() method	Not available. Callers should no longer use it.
Flags::removeFlags() method	Not available. Callers should no longer use it.
Flags::setBits() method	Not available. Callers should no longer use it.
Flags::setFlag() method	Not available. Callers should no longer use it.
FolderUtils class	Not available. Callers should no longer use it.
FolderUtils::cleanDirRecursive() method	WW_Utils_FolderUtils::cleanDirRecursive() method
FolderUtils::copyDirectoryRecursively() method	WW_Utils_FolderUtils::copyDirectoryRecursively() method
FolderUtils::encodePath() method	WW_Utils_FolderUtils::encodePath() method
FolderUtils::ensureDirExists() method	WW_Utils_FolderUtils::ensureDirExists() method
FolderUtils::extractParentFolder() method	WW_Utils_FolderUtils::extractParentFolder() method
FolderUtils::getFilesInFolderRecursive() method	WW_Utils_FolderUtils::getFilesInFolderRecursive() method
FolderUtils::getFilesPathInFolder() method	WW_Utils_FolderUtils::getFilesPathInFolder() method
FolderUtils::getLibraryFolders() method	WW_Utils_FolderUtils::getLibraryFolders() method
FolderUtils::getReflectionPath() method	WW_Utils_FolderUtils::getReflectionPath() method
FolderUtils::isDirWritable() method	WW_Utils_FolderUtils::isDirWritable() method
FolderUtils::isEmptyDirectory() method	WW_Utils_FolderUtils::isEmptyDirectory() method
FolderUtils::isLocalRootFolder() method	WW_Utils_FolderUtils::isLocalRootFolder() method
FolderUtils::mkFullDir() method	WW_Utils_FolderUtils::mkFullDir() method
FolderUtils::replaceDangerousChars() method	WW_Utils_FolderUtils::replaceDangerousChars() method
FolderUtils::scanDirForFiles() method	WW_Utils_FolderUtils::scanDirForFiles() method
HtmlDateTimeField class	Not available. Callers should no longer use it.
HtmlDateTimeField::__construct() method	WW_Utils_HtmlClasses_HtmlDateTimeField::__construct() method
HtmlDateTimeField::drawBody() method	WW_Utils_HtmlClasses_HtmlDateTimeField::drawBody() method
HtmlDateTimeField::drawHeader() method	WW_Utils_HtmlClasses_HtmlDateTimeField::drawHeader() method
HtmlDateTimeField::getDisplayValue() method	WW_Utils_HtmlClasses_HtmlDateTimeField::getDisplayValue() method
HtmlDateTimeField::requestInput() method	WW_Utils_HtmlClasses_HtmlDateTimeField::requestInput() method
HtmlDateTimeField::requestValue() method	WW_Utils_HtmlClasses_HtmlDateTimeField::requestValue() method
HtmlDateTimeField::setValue() method	WW_Utils_HtmlClasses_HtmlDateTimeField::setValue() method
MimeTypeHandler class	Not available. Callers should no longer use it.
MimeTypeHandler::fileExt2MimeType() method	WW_Utils_MimeTypeHandler::fileExt2MimeType() method
MimeTypeHandler::filePath2MimeType() method	WW_Utils_MimeTypeHandler::filePath2MimeType() method
MimeTypeHandler::filename2ObjType() method	WW_Utils_MimeTypeHandler::filename2ObjType() method
MimeTypeHandler::getExtensionMap() method	WW_Utils_MimeTypeHandler::getExtensionMap() method
MimeTypeHandler::isInCopy() method	WW_Utils_MimeTypeHandler::isInCopy() method
MimeTypeHandler::isJPEG() method	WW_Utils_MimeTypeHandler::isJPEG() method
MimeTypeHandler::mime2ObjType() method	WW_Utils_MimeTypeHandler::mime2ObjType() method
MimeTypeHandler::mimeType2FileExt() method	WW_Utils_MimeTypeHandler::mimeType2FileExt() method
MimeTypeHandler::native2DBname() method	WW_Utils_MimeTypeHandler::native2DBname() method
MimeTypeHandler::repairMimetype() method	WW_Utils_MimeTypeHandler::repairMimetype() method
PhpConfigParser class	Not available. Callers should no longer use it.
PhpConfigParser::__construct() method	WW_Utils_PhpConfigParser::__construct() method
PhpConfigParser::parseDefineValues() method	WW_Utils_PhpConfigParser::parseDefineValues() method
PhpConfigParser::parseDefines() method	WW_Utils_PhpConfigParser::parseDefines() method
RemovePhpComments class	Not available. Callers should no longer use it.
RemovePhpComments::iterFile() method	Not available. Callers should no longer use it.
RemovePhpComments::iterFolder() method	Not available. Callers should no longer use it.
RemovePhpComments::removeAllComments() method	Not available. Callers should no longer use it.
RemovePhpComments::skipFile() method	Not available. Callers should no longer use it.
RemovePhpComments::skipFolder() method	Not available. Callers should no longer use it.
UtfConverter class	Not available. Callers should no longer use it.
UtfConverter::convert2UTFAdobe() method	Not available. Callers should no longer use it.
WW_Utils_ListEncoder class	Not available. Callers should no longer use it.
WW_Utils_ListEncoder::__construct() method	Not available. Callers should no longer use it.
WW_Utils_ListEncoder::decodeList() method	Not available. Callers should no longer use it.
WW_Utils_ListEncoder::encodeList() method	Not available. Callers should no longer use it.
WW_Utils_ListEncoder::encodeListItem() method	Not available. Callers should no longer use it.

The following functions that were deprecated in previous versions have been removed in Studio Server 10.28.0:

Deprecated (old)	Replacement (new)	Deprecated since version
DBUser::getRights()	-	10.15.0

For a full overview, see Code that has been deprecated or removed in Studio Server.

Documentation

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

Compatibility of Studio Server 10.28 - new
Code that has been deprecated or removed in Studio Server - updated

Known issues

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

WSS-13622 "Uncaught throwable ‘TypeError'" when uploading an image in Studio

The issue occurs in Studio when uploading an image that contains a metadata field with multiple values whereas Studio Server expects this field to have only a single value.

In such cases, the following error is shown in Studio:

Some files could not be added to the Dossier. Please try again.

file name

"Uncaught throwable ‘TypeError'"

The following is logged in the log files:

Exception Message: mb_substr(): Argument #1 ($string) must be of type string, array given
Exception File: /opt/apps/enterprisep01/server/utils/UtfString.class.php 163

Exception Stack:
- UtfString::truncateMultiByteValue (line#1611 at DBObject.class.php)
- DBObject::truncatePropertyValue (line#1552 at DBObject.class.php)
[...]

This only happens when the following conditions are happening at the same time:

Studio Server 10.23.0 or higher with PHP 8.1 is used.
ExifTool is used as a metadata extractor.
An object with a metadata field containing multiple values is added while Studio Server expects it to contain just one value (such as an Author field).

Fixed issues

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

WSS-13163 sceUsed is always set to true on archived objects even if there is no variant actually currently being used in Studio.

Note: The fix for WSS-13163 requires Assets Server 6.97 or higher.

WSS-13425 Improve API to prevent command injection.

WSS-13495 Security (third-party package): Improper header name validation in guzzlehttp/psr7 ≤1.9.1.

WSS-13507 MadeToPrint process terminated and a 'TypeError' in Studio Server when changing the status of a layout to the trigger a MadeToPrint status.

WSS-13534 Private keys that are not used anymore can be downloaded from Studio Server.

WSS-13608 Placement of a Print article on a Layout preview in Studio is blocked and the error ‘Missing function parameter (S1000)’ is raised.

Installation

Choose one of the following installation paths:

Studio Server 10.27.0

Studio Server version 10.27.0 build 421

Release date: 1 June 2023

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 images in HEIC, HEIF, and WEBP format. Support has been added for images in HEIC, HEIF and WEBP format. This has resulted in the following changes:

Generating the image previews for these new image formats is handled by ImageMagick.

Note: The ImageMagick binaries might need to be recompiled in order to have this working.

A new configuration option named IMAGEMAGICK_FORMATS has been introduced.

The file types for which ImageMagick should generate previews for can now be configured through this option in the configserver.php file.

This makes it possible to configure the system in such a way that previews are only generated for those file formats that are used within the production environment.

Commonly used image formats such as JPEG, PNG and so on are included in this option by default.

Preview generation for images in WEBP format is also enabled by default. Generation for images in HEIC and HEIF format needs to be manually enabled through configuration steps.

The ImageMagick Health Check test will validate the image format added in the IMAGEMAGICK_FORMATS option. If any of the listed image formats are not supported by ImageMagick, the test will raise an error together with instructions about how to resolve the issue.

The following requirements and limitations exist:

Placing images in HEIC or HEIF format on layouts or Print articles requires InDesign 2023 or higher, or InCopy 2023 or higher.

When using InDesign on Windows, a HEIC/HEIF codec is needed. See the Adobe documentation: Work with HEIF or HEIC files on Windows.

Placing images in HEIC or HEIF format on Digital articles requires Assets Server integration to generate a high-resolution JPEG image that can be rendered in the editor and in the published article. Without the Assets Server integration, HEIC and HEIF images are placed and published in their own format and cannot be rendered by the web browser (showing an empty image frame).

Some ImageMagick distributions do not support HEIC and HEIF image formats out of the box. In that case the HEIC module needs to be added. The Image Magick test on the Studio Server Health Check page will show an error when this is needed. See the Configuration steps explained below. This would require recompiling and reinstalling the ImageMagick binaries.

Steps for setting up image preview generation in Studio Server and higher are described in a new Help Center article.

The process of generating image previews and extracting metadata from images by the plug-ins has been simplified by specifying specific connectors for each task. In previous versions of Studio Server, the best connector (depending on which plug-ins were enabled) was picked for the preview generation and metadata extraction. Now, each image format has a dedicated connector for generating an image preview or for extracting metadata from an image.

This makes it easier to predict which task is performed by which connector, which in turn makes it easier to maintain and support those connectors. It also makes it easier to see which Server plug-in should be enabled to have a task accomplished.

Note: When Assets Server is integrated, the preview generation for all images is handled by Assets Server.

As a result of the simplification, the following Server plug-ins have been changed and renamed to better reflect their working:

Old name	New name	Change
PHP Preview and Metadata	PHP Metadata	The Preview connector has been removed.
ImageMagick Preview and Metadata	ImageMagick Preview	The Metadata connector has been removed.

The following Server plug-in is no longer shipped:

The Sips Preview plug-in.

This plug-in was provided for demo purposes only and support for it was already dropped.

Note: When upgrading from a version of Studio Server in which certain connectors were enabled or disabled for the preview generation and metadata extraction, then the following plug-ins should now be enabled to make sure that all the supported images are covered for the preview generation and metadata extraction in Studio Server 10.27.0 and higher:

PHP Metadata
ExifTool Metadata
ImageMagick Preview

The following tables show which preview connectors can handle which file formats depending on the version of Studio Server and the integrated system used.

For Studio Server 10.27 or higher:

	PHP Metadata	Sips	ImageMagick
JPEG, PNG, GIF	No	No	Yes
PDF, EPS, AI, PSD, TIFF	No	No	Yes
WEBP, HEIC, HEIF	No	No	Yes

For Studio Server 10.26 or lower:

	PHP Metadata	Sips	ImageMagick
JPEG, PNG, GIF	Yes	Yes	Yes
PDF, EPS, AI, PSD, TIFF	No	Yes	Yes
WEBP, HEIC, HEIF	No	No	No

The following tables shows which metadata connectors can handle which file formats depending on the version of Studio Server and the integrated system used.

For Studio Server 10.27 or higher:

	PHP Metadata	ExifTool	ImageMagick
JPEG, PNG, GIF	No	Yes	No
PDF, EPS, AI, PSD, TIFF	No	Yes	No
WEBP, HEIC, HEIF	No	Yes	No
InDesign, InCopy	Yes	No	No

For Studio Server 10.26 or lower:

	PHP Metadata	ExifTool	ImageMagick
JPEG, PNG, GIF	Yes	Yes	Yes
PDF, EPS, AI, PSD, TIFF	Yes	Yes	Yes
WEBP, HEIC, HEIF	No	No	No
InDesign, InCopy	Yes	No	No

The AWS SDK for PHP has been added to the release package. This results in the following:
An increase in file size of the Studio Server release package from ~19.7 MB to ~24.1 MB.
When a custom server plug-in already ships with the very same SDK, class name conflicts may occur. The SDK in the custom plug-in needs to be replaced by the one shipped with Studio Server.

Note: As with any other library shipped in the server/vendor folder, custom server plug-ins may make use of it. However, WoodWing does not provide any support on those usages. Upgrades of libraries will happen on initiative of Studio Server's needs only.

The 'datatables/datatables' javascript library has been updated. The third-party datatables/datatables javascript library package has been updated to the latest version. This package is used for generating the tables on the Maintenance pages such as the Brand Maintenance page and the User Maintenance page.

This has resulted in the following changes:

The Javascript file has been moved to a new location:
Old location: server/vendor/datatables/datatables/media/js/jquery.dataTables.js
New location: server/jquery/datatables/datatables-1.13.4.min.js

The CSS file has been moved to a new location:
Old location: server/vendor/datatables/datatables/media/css/jquery.dataTables.css
New location: config/templates/datatables.css

The datatables.js file has been moved to a new location:
Old location: server/jquery/datatables.js
New location: server/jquery/datatables/datatables.js

Note: When using this library in your integrations, update the references to this library.

Code has been marked as deprecated or removed. Global functions, class methods, and classes in the code are regularly marked as deprecated and eventually removed from the code. Customizations and integrations that make use of these functions should be updated accordingly.

The following functions have been marked as deprecated in Studio Server 10.27.0:

Deprecated (old)	Replacement (new)
BizMetaDataPreview::generatePreviewLater() method	BizMetaDataPreview::generatePreviewNow() method
BizMetaDataPreview::getBufferAsFile() method	Not available. Callers should no longer use it.
BizMetaDataPreview::getJobConfig() method	Not available. Callers should no longer use it.
BizMetaDataPreview::runJob() method	Not available. Callers should no longer use it.
WW_Utils_MimeTypeHandler::mime2ObjType() method	WW_Utils_MimeTypeHandler::filename2ObjType() method
WW_Utils_ShellScript class	Not available. Callers should no longer use it.
WW_Utils_ShellScript::buildCmd() method	Not available. Callers should no longer use it.
WW_Utils_ShellScript::init() method	Not available. Callers should no longer use it.
WW_Utils_ShellScript::shell_exec() method	Not available. Callers should no longer use it.
WW_Utils_ShellTransferClient class	Not available. Callers should no longer use it.
WW_Utils_ShellTransferClient::__construct() method	Not available. Callers should no longer use it.
WW_Utils_ShellTransferClient::cleanupFile() method	Not available. Callers should no longer use it.
WW_Utils_ShellTransferClient::downloadContentInParallel() method	Not available. Callers should no longer use it.
WW_Utils_ShellTransferClient::downloadFile() method	Not available. Callers should no longer use it.
WW_Utils_ShellTransferClient::getCommandParams() method	Not available. Callers should no longer use it.
WW_Utils_ShellTransferClient::uploadFile() method	Not available. Callers should no longer use it.

The following functions that were deprecated in previous versions have been removed in Studio Server 10.27.0:

Deprecated (old)	Replacement (new)	Deprecated since version
WW_Utils_ArrayInjector class	WW_Utils_ArrayAppender class	10.14.0
WW_Utils_ArrayInjector::insertAfterKey() method	WW_Utils_ArrayAppender::insertAfterKey() method	10.14.0
WW_Utils_ArrayInjector::insertBeforeKey() method	WW_Utils_ArrayAppender::insertBeforeKey() method	10.14.0
WW_Utils_XmlParser::getXmlParserError() method	Not available. Callers should no longer use it.	10.14.1

For a full overview, see Code that has been deprecated or removed in Studio Server.

Documentation

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

Upgrading an existing installation of Studio Server - updated
Image preview generation in Studio Server 10.27 or higher - new
Studio Server plug-ins - updated
Compatibility of Studio Server 10.27 - updated
Code that has been deprecated or removed in Studio Server - updated

Known issues

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

WSS-13608 Placement of a Print article on a Layout preview in Studio is blocked and the error ‘Missing function parameter (S1000)’ is raised. This issue was introduced in Studio Server 10.26. It will be resolved in the upcoming 10.28 release of Studio Server.

WSS-13622 "Uncaught throwable ‘TypeError'" when uploading an image in Studio

The issue occurs in Studio when uploading an image that contains a metadata field with multiple values whereas Studio Server expects this field to have only a single value.

In such cases, the following error is shown in Studio:

Some files could not be added to the Dossier. Please try again.

file name

"Uncaught throwable ‘TypeError'"

The following is logged in the log files:

Exception Message: mb_substr(): Argument #1 ($string) must be of type string, array given
Exception File: /opt/apps/enterprisep01/server/utils/UtfString.class.php 163

Exception Stack:
- UtfString::truncateMultiByteValue (line#1611 at DBObject.class.php)
- DBObject::truncatePropertyValue (line#1552 at DBObject.class.php)
[...]

This only happens when the following conditions are happening at the same time:

Studio Server 10.23.0 or higher with PHP 8.1 is used.
ExifTool is used as a metadata extractor.
An object with a metadata field containing multiple values is added while Studio Server expects it to contain just one value (such as an Author field).

Fixed issues

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

WSS-12870 Warning is generated by calling NamedQueryService when re-login by Studio client and SSO Okta is configured.

WSS-13226 InDesign Server jobs: No error logging is saved when throwing an exception error in an InDesign Server script.

WSS-13339 Add support for the HEIC, HEIF, and WEBP formats.

WSS-13392 Security: Update the vendor package phpseclib 3.0.17 to 3.0.19 to solve vulnerability.

WSS-13439 Health Check: Show version info for ImageMagick, Ghostscript, ExifTool, Solr and RabbitMQ.

WSS-13446 Blank page is shown and Uncaught 'TypeError' is logged when admin user attempts to create a Brand with a name containing only spaces.

WSS-13463 Any fatal error reported by ImageMagick is not captured in the server log.

Installation

Choose one of the following installation paths:

Studio Server 10.26.0

Studio Server version 10.26.0 build 416

Release date: 4 May 2023

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:

Global functions, class methods, and classes have been marked as deprecated. A large number of global functions, class methods, and classes have been marked as deprecated because their related feature is no longer supported. They should no longer be called by custom server plug-ins and are candidates to be removed one year after this release (which is after 12 minor releases). If a replacement is provided, call that instead.

For a full overview, see Code that has been deprecated or removed in Studio Server.

Previously deprecated functions are now logged as deprecated in the log files. When analyzing the functions that are currently marked as deprecated, we noticed that not all of these functions were logged as deprecated in the log files, and only had the @deprecated annotation set in the function document header.

As the annotations rely too much on the quality of the integrated development environment (IDE) used by the plug-in developer, these deprecated functions can be easily missed or overlooked.

The functions that did not have the logging in place yet are now corrected and are logged as a DEPRECATED item.

For a full overview, see Code that has been deprecated or removed in Studio Server.

Note: Some of the functions were already reported as deprecated in previous releases, but have now been reset to version 10.26.0 to allow sufficient time to migrate custom plug-ins that are still calling these functions.

Deprecated code has been removed. Global functions, class methods, and classes that were marked as deprecated more than a year ago have now been removed. Custom server plug-ins can no longer call these global functions, class methods, and classes. If a replacement is provided, call that instead. For a full overview of the code that is now removed, see Code that has been deprecated or removed in Studio Server.

Server plug-in read-me files named as README.md are now also detected by and shown on the Server plug-in page. A Server plug-in can contain a read-me file in the form of a markdown file with a .md extension. When such a file is placed in the base folder of the plug-in, it is detected when accessing the Server plug-ins page of Studio Server and an info icon is shown next to the plug-in on the page. Clicking the icon opens the file in the browser.

In previous versions of Studio Server, only files named as 'readme.md' (in lower case) were detected. Now, files named as 'README.md' (in upper case) are also detected.

API Request validation: The WflGetObjectsRequest API now only accepts one of the supported values defined in the WSDL; invalid values such as null can result in PHP errors. When developing integrations it is recommended to turn service validation on and to have automated integration tests in place that can be executed against a staging environment.

WoodWing Software expects that the WSDL is respected by third-party integrations, therefore WoodWing Software cannot take responsibility when an integration breaks due to a request violating the WSDL contract (now or in the future) and cannot always communicate these changes in advance.

Documentation

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

Known issues

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

WSS-13622 "Uncaught throwable ‘TypeError'" when uploading an image in Studio

The issue occurs in Studio when uploading an image that contains a metadata field with multiple values whereas Studio Server expects this field to have only a single value.

In such cases, the following error is shown in Studio:

Some files could not be added to the Dossier. Please try again.

file name

"Uncaught throwable ‘TypeError'"

The following is logged in the log files:

Exception Message: mb_substr(): Argument #1 ($string) must be of type string, array given
Exception File: /opt/apps/enterprisep01/server/utils/UtfString.class.php 163

Exception Stack:
- UtfString::truncateMultiByteValue (line#1611 at DBObject.class.php)
- DBObject::truncatePropertyValue (line#1552 at DBObject.class.php)
[...]

This only happens when the following conditions are happening at the same time:

Studio Server 10.23.0 or higher with PHP 8.1 is used.
ExifTool is used as a metadata extractor.
An object with a metadata field containing multiple values is added while Studio Server expects it to contain just one value (such as an Author field).

Fixed issues

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

WSS-4175 Brand Maintenance page: When trying to create a Brand that already exists, all options on the page become available.

WSS-5185 Unable to delete a metadata custom property with a long name.

WSS-5208 Admin user can create User Groups and InDesign Servers with spaces prefixed or postfixed.

WSS-5487 Export page: Typo in error message when clicking the Export button while no files are selected.

WSS-6216 The same user/group can be created by prefixing/postfixing spaces.

WSS-6591 Remove the 'Please try again.' message when logging in to the Maintenance pages is not successful.

WSS-8523 The php.ini Health Check test suggests an incorrect php.ini location when the PHP extension is not loaded under Windows.

WSS-10013 Security: Users are unable to log in to a Brand when an Issue name or Issue description contains invalid characters.

WSS-10031 Dialog setup page: Properties are added multiple times when clicking 'Update' or 'Add Action Property' multiple times.

WSS-10084 The Server Job dispatcher crashes when trying to check a job that is running too long while the assigned InDesign Server no longer exists.

WSS-10119 SetObjectProperties moves to the next status when no status is provided.

WSS-10822 Server plug-ins page: Remove the 'Register All' button.

WSS-11273 '404 - File or directory not found' is shown when restoring a version on the Export page.

WSS-11325 An error is incorrectly logged when logging in to the Maintenance pages using an incorrect password.

WSS-11726 Log on page: 'Enterprise' is incorrectly mentioned in the error message when logging in using Single Sign-On (SSO) fails.

WSS-12243 Uploading a file named as '0.png' fails with a 'Please enter a name' error.

WSS-12508 Support 'README.md' files for displaying Server Plug-in information.

WSS-12595 Security: Remove the word 'Confidential' from WSDL files (as they can be downloaded without credentials).

WSS-12694 No files are shown in the Studio panel of Studio for InDesign and InCopy when logging in with a user name containing an apostrophe.

WSS-12703 [MYSQL] An error is logged when logging in to InDesign with a user name containing an apostrophe.

WSS-12788 Web browser console sets an error/warning on bad headers when running the Health Check page.

WSS-12985 Studio Server e-mail notification fails for recipients with Google Mail-Server.

WSS-13020 BizWorkflow.class.php: PHP warning because a key check is missing.

WSS-13021 BizRelation.class.php logs warnings that are not actionable.

WSS-13022 PreviewMetaPHP_MetaData.class.php PHP warning because a key check is missing.

WSS-13112 Deprecated calls in core code related to getCategoryInfos().

WSS-13113 Deprecated calls in core code related to getRights().

WSS-13157 When copying a layout in InDesign using the Copy To option while the 'CopyWithPlacements' plug-in is enabled, the layout is copied without its placed objects.

WSS-13187 Make the logon URL for Studio clients configurable in e-mail templates.

WSS-13280 Multi-list metadata fields do not display values containing a '/'.

WSS-13362 'Uncaught throwable 'Exception'' is shown when closing an article in Studio after adding a few components.

Installation

Choose one of the following installation paths:

Studio Server 10.25.0

Studio Server version 10.25.0 build 414

Release date: 4 April 2023

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 3rd-party software. Various changes have been made to the compatibility between Studio Server and other systems.

RabbitMQ:
Added support for RabbitMQ 3.11 (recommended version).
Dropped support for RabbitMQ 3.8.

Solr:
Added support for Solr 9.1 (recommended version)
Dropped support for Solr 8.8.

Configuration options have been added to improve security between Studio Server and web applications. To improve the security between Studio Server and applications running in a web browser such as Studio, the Studio Management Console, and the Maintenance pages of Studio Server, the default value of the COOKIES_OVER_SECURE_CONNECTIONS_ONLY option has been changed and a new option named COOKIES_SAME_SITE has been added.

These options set the 'Secure' and 'SameSite' cookie attributes respectively. Explicitly setting these attributes enforces a certain security level that is centrally controlled by the system administrator. This improves the level of control as it no longer relies on the default setting of the web browser, which may or may not set these attributes.

The COOKIES_OVER_SECURE_CONNECTIONS_ONLY option is used for secure connections (HTTPS) to inform the web browser to only send cookies over HTTPS (and not over HTTP).

To ensure that Studio Server sets the Secure cookie attribute correctly, the default value has been changed from 'false' to a dynamically determined value depending on the connection type:

'true' for secure connections (HTTPS)
'false' for unsecure connections (HTTP)

In production environments, only use secure connections (HTTPS) for which the Secure attribute will be automatically set. The latter is needed to prevent cookies from being observed by unauthorized parties due to the transmission of the cookie in clear text.

For test and demo environments, you may want to use unsecure connections (HTTP) for which the Secure attribute will automatically not be set. The latter is required for functional reasons as user authorization depends on cookies.

The COOKIES_SAME_SITE option is a new option and informs the web browser in what circumstances cookies can be sent to 3rd-party web sites.

The following values can be set:

Value	Description
Lax	Cookies are only sent when a user is explicitly navigating to a site and when the request method is safe (GET or HEAD, but not POST). This value is most recommended.
Strict	Cookies are only sent in a first-party context and are not sent along with requests initiated by third-party web sites. This value is experimental and is not supported.
None	Cookies are sent in all contexts, such as in responses to both first-party and cross-site requests. This value is not recommended and is not supported.
null	Does not set the SameSite attribute and for HTTPS connections relies on the default setting of the web browser. Most web browsers use 'Lax' as the default. This value should not be used in production environments.

By default, Studio Server sets the SameSite=Lax cookie attribute for secure connections (HTTPS). For unsecure connections (HTTP) the attribute is not set.

Note: Stand-alone applications such as InDesign and InCopy do not use cookies and are not affected by this change.

Documentation

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

Compatibility of Studio Server 10.25 - new

Known issues

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

WSS-13622 "Uncaught throwable ‘TypeError'" when uploading an image in Studio

The issue occurs in Studio when uploading an image that contains a metadata field with multiple values whereas Studio Server expects this field to have only a single value.

In such cases, the following error is shown in Studio:

Some files could not be added to the Dossier. Please try again.

file name

"Uncaught throwable ‘TypeError'"

The following is logged in the log files:

Exception Message: mb_substr(): Argument #1 ($string) must be of type string, array given
Exception File: /opt/apps/enterprisep01/server/utils/UtfString.class.php 163

Exception Stack:
- UtfString::truncateMultiByteValue (line#1611 at DBObject.class.php)
- DBObject::truncatePropertyValue (line#1552 at DBObject.class.php)
[...]

This only happens when the following conditions are happening at the same time:

Studio Server 10.23.0 or higher with PHP 8.1 is used.
ExifTool is used as a metadata extractor.
An object with a metadata field containing multiple values is added while Studio Server expects it to contain just one value (such as an Author field).

Fixed issues

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

WSS-13129 Logging into InDesign after the session is expired results in a PHP notice.

WSS-13150 Replacing a Print article (WCML) with a different InDesign Article on a layout does not detach components that are not mapped.

WSS-13258 When creating a new article in a Dossier, the Dossier name is not set as the article name.

WSS-13307 Compatibility issues with Solr 8.11.2.

WSS-13334 Studio Server cannot be installed because the required IonCube loader is not available.

WSS-13340 'Allowed memory size exhausted' message appears when opening a layout in InDesign.

WSS-13353 Plugin generator: fix support for DbModel_EnterpriseConnector and CustomObjectMetaData_EnterpriseConnector.

WSS-13354 When running crontab, the Webhooks_EventBus throws an uncaught 'TypeError' exception.

Installation

Choose one of the following installation paths:

Studio Server 10.24.0

Studio Server version 10.24.0 build 413

Release date: 7 March 2023

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:

Deprecated method	New method
BizSession::formatClientVersion	BizSession::getClientApplication
BizSession::getClientName	BizSession::getClientApplication
BizSession::getClientVersion	BizSession::getClientApplication
BizSession::isAppInTicket	BizSession::getClientApplication
BizSession::isSmartMover	WW_Utils_ClientApplication::isSmartMover

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)'.

WSS-13622 "Uncaught throwable ‘TypeError'" when uploading an image in Studio

The issue occurs in Studio when uploading an image that contains a metadata field with multiple values whereas Studio Server expects this field to have only a single value.

In such cases, the following error is shown in Studio:

Some files could not be added to the Dossier. Please try again.

file name

"Uncaught throwable ‘TypeError'"

The following is logged in the log files:

Exception Message: mb_substr(): Argument #1 ($string) must be of type string, array given
Exception File: /opt/apps/enterprisep01/server/utils/UtfString.class.php 163

Exception Stack:
- UtfString::truncateMultiByteValue (line#1611 at DBObject.class.php)
- DBObject::truncatePropertyValue (line#1552 at DBObject.class.php)
[...]

This only happens when the following conditions are happening at the same time:

Studio Server 10.23.0 or higher with PHP 8.1 is used.
ExifTool is used as a metadata extractor.
An object with a metadata field containing multiple values is added while Studio Server expects it to contain just one value (such as an Author field).

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:

Studio Server 10.23.0

Studio Server version 10.23.0 build 411

Release date: 14 February 2023

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.

Technology/feature	Remarks
Adobe	Support for Studio for InDesign and InCopy 18 for Adobe 2023 has been added (this version of Studio for InDesign and InCopy is yet to be released.) Support for Smart Connection 13 for Adobe 2018 has been dropped.
ionCube	Support for ionCube Loader 12.0.4 has been added. Support for ionCube Loader 10.4.5 has been removed.
MS SQL Server drivers	References to specific versions have been replaced by generic instructions.
PHP	Support for PHP 8.1 has been added and is set as the recommended version. Although PHP 7.4 is still supported, PHP 7.4 was marked as end-of-life in November 2022. We therefore encourage customers to migrate to PHP 8.1.
Windows Server	Support for Windows Server 2022 has been added and is set as the recommended version. Support for Windows Server 2016 has been dropped.

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.

Note: If this behavior is not desired, it can be disabled by adding the following option to the SERVERFEATURES section of the configserver.php file (it is recommended to add it to the config_overrule.php file):

ArchiveDigitalArticlesInOriginalLocation

However, the old behavior is scheduled to be phased out in an upcoming version of Studio Server. Information about this is displayed when running the WoodWing Assets Content Source test on the Health Check page of Studio Server when this option is enabled. In case the old behavior is desired in the future as well, contact WoodWing Support.

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.

Old method	New method
BizPublication::getCategoryInfos	WW_BizClasses_Wfl_Publication::getCategoryInfos

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

WSS-13622 "Uncaught throwable ‘TypeError'" when uploading an image in Studio

The issue occurs in Studio when uploading an image that contains a metadata field with multiple values whereas Studio Server expects this field to have only a single value.

In such cases, the following error is shown in Studio:

Some files could not be added to the Dossier. Please try again.

file name

"Uncaught throwable ‘TypeError'"

The following is logged in the log files:

Exception Message: mb_substr(): Argument #1 ($string) must be of type string, array given
Exception File: /opt/apps/enterprisep01/server/utils/UtfString.class.php 163

Exception Stack:
- UtfString::truncateMultiByteValue (line#1611 at DBObject.class.php)
- DBObject::truncatePropertyValue (line#1552 at DBObject.class.php)
[...]

This only happens when the following conditions are happening at the same time:

Studio Server 10.23.0 or higher with PHP 8.1 is used.
ExifTool is used as a metadata extractor.
An object with a metadata field containing multiple values is added while Studio Server expects it to contain just one value (such as an Author field).

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:

Studio Server 10.22.0

Studio Server version 10.22.0 build 407

Release date: 12 January 2023

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.

Function	Remark
BizPublication::getPublications()	Call WW_BizClasses_Wfl_Publication::getPublicationInfosByRequestInfo instead.
BizPublication::getPublicationInfos()	Call WW_BizClasses_Wfl_Publication::getPublicationInfosByRequestInfo instead.
BizPublication::getPublicationInfo()	Call WW_BizClasses_Wfl_Publication::getPublicationInfosByRequestInfo instead.
BizPublication::getStateInfos()	Call WW_BizClasses_Wfl_Publication::getPublicationInfosByRequestInfo instead.

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.

Function	Remark
PubMgr::getPublications()	Call WW_BizClasses_Wfl_Publication::getPublicationInfosByRequestInfo instead.
PubMgr::getIssues()	Call BizPublication::getIssues instead.
PubMgr::getEditions()	Call BizPublication::getEditions instead.
PubMgr::getSections()	Call BizPublication::getSections instead.
PubMgr::getStates()	Call BizWorkflow::getStates instead.

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:

Studio Server 10.21.0

Studio Server version 10.21.0 build 405

Release date: 15 December 2022

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:

Studio Server 10.20.0

Studio Server version 10.20.0 build 404

Release date: 17 November 2022

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:

Method

Details

\WW_DbClasses_Wfl_Query_QueryObjectComposer::
filterOnAuthorization()

Removed.

This method was deprecated since Studio Server 10.16.0.

\WW_DbClasses_Wfl_Query_QueryObjectComposer::
filterOnAuthorizationAndBrandsId()

Deprecated.

This method will be removed in a future version.

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:

Studio Server 10.19.0 build 401 Quick Patch

Studio Server version 10.19.0 build 401

Release date: 1 November 2022

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:

Studio Server 10.19.0

Studio Server version 10.19.0 build 399

Release date: 20 October 2022

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.

Notes for upgraded systems with an Assets Server integration:

Shadow objects that were created before the upgrade to Studio Server 10.19.0 retain their current value (the page number). These shadow objects are only updated with the page order value when the layout on which they are placed is re-opened and re-saved.

Objects that were archived before the upgrade to Studio Server 10.19.0 retain their current value (the page number). Objects that are archived after the upgrade to Studio Server 10.19.0 will have the page order value 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:

Studio Server 10.18.0

Studio Server version 10.18.0 build 398

Release date: 8 September 2022

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:

Deprecated method	New method
WW_BizClasses_Wfl_Publication::getSectionInfos()	None.
WW_BizClasses_Wfl_Publication::getAuthorizedStates()	WW_BizClasses_Wfl_Publication::getAuthorizedStatesByBrandsId()
\WW_BizClasses_Wfl_Publication::getStateInfos()	WW_BizClasses_Wfl_Publication::getStateInfosForBrandsId()
\WW_BizClasses_Wfl_Publication::getCategoryInfos	WW_BizClasses_Wfl_Publication::getCategoryInfosByUserRights()
\authorizationmodule::getRightsCached()	None.

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:

Studio Server 10.17.0

Studio Server version 10.17.0 build 396

Release date: 11 August 2022

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:

Studio Server 10.16.0

Studio Server version 10.16.0 build 394

Release date: 19 July 2022

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:

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:

Studio Server 10.15.0

Studio Server version 10.15.0 build 391

Release date: 21 June 2022

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:

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.

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:

Library	Upgraded to version
jQuery	3.60
jQuery-UI	1.13.1
jsTree	3.3.12

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:

Studio Server 10.14.1

Studio Server version 10.14.1 build 380

Release date: 21 April 2022

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

Note: The page range of the Studio Server value is converted to single page numbers in Assets Server.

Example:

Studio Server: 1–5
Assets Server: 1,2,3,4,5

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.

Example:

Incorrect: { "client.ip": "123.123.123.123" }

Correct: { "client": { "ip": "123.123.123.123" } }

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.

Example:

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

Notes:

Future versions of Studio Server will only support the new/correct structure. When your system uses the old/incorrect structure, this structure will therefore need to be changed in your 3rd-party logging monitoring system at some point.

When running the Health Check PHP test, it will notify when the old structure is being used and will advise to change it to the new structure.

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:

Studio Server 10.14.0

Studio Server version 10.14.0 build 373

Release date: 13 January 2022

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.

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.

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:

Studio Server 10.13.1

Studio Server version 10.13.1 build 363

Release date: 8 September 2021

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:

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.
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:

Studio Server 10.13.0 build 352 Quick Patch

Studio Server version 10.13.0 build 352

Release date: 21 July 2021