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