Skip to main content

Release Notes for Studio Server 10.13

  • Updated

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

Note: Release Notes of other versions of Studio Server 10 can be found in the Release Notes section.

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

Filter by version:

Studio Server 10.13.1

Studio Server version 10.13.1 build 363

Release date: 8 September 2021

Downloads

New features

Changes

Documentation

Known issues

Fixed issues

Installation

Downloads

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

New features

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

Changes

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

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

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

  1. Delete files. When selected, the archived files are deleted from Studio Server. Note that files are purged; they cannot be found in the Trash Can and cannot be restored.
  2. Send files to next Status. When selected, the layout, Digital article, or Dossier is sent to the next Workflow Status. (Only applicable when the Delete files option is not selected, else it has no effect.)
  • It is now possible to send files to the next Workflow Status. When a layout, Digital article, or Dossier is kept in Studio Server after archiving, it is sent to the next Workflow Status.
  • It is now possible to automate tasks on files in Studio Server after archiving. Combining the two options above, files can be kept in Studio Server and sent to the next Status. This makes it possible for integrators to automate tasks on these files such as modifying them in a way which results in versions that are not suited for archiving, converting print layouts to digital articles, and so on.
  • The period at which the archiving should start can now be defined in hours instead of days for better control of the archiving process. For this, the option 'Archive after (days)' has been renamed to 'Archive after (hours)'.
  • The option 'Archive after (hours)' now also applies when Trigger 'Status Based' is chosen. This makes it possible for this method of archiving to keep the files in the system for a short while to perform specific actions on them and to prevent that they are archived instantly.
  • The archiving process can now be started before the trigger is reached by setting a negative value in hours.
  • When archiving layouts, Collections are now created to represent the Dossier structure. Layouts are typically part of multiple Dossiers: one for each Story consisting of the layout, an article that is placed on the layout, some images that are placed on the layout, and additional reference files. To represent this structure in the archive, Collections are now created in the archive folder: one for each Dossier that contains the layout as well as the article and any other files that are placed on the layout.
  • Compatibility with Elvis Server increased to version 6.44 or higher. Because of the added functionality of creating Collections when archiving layouts, the compatibility with Elvis Server has been increased to version 6.44 or higher.

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

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

Documentation

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

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

Studio Server 10.13.0 build 352 Quick Patch

Studio Server version 10.13.0 build 352

Release date: 21 July 2021

Downloads

Fixed issues

Installation

Downloads

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

Fixed issues

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

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

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

Installation

Studio Server 10.13.0

Studio Server version 10.13.0 build 351

Release date: 3 June 2021

Downloads

New features

Changes

Documentation

Known issues

Fixed issues

Installation

Downloads

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

New features

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

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

Examples:

  • When an article reaches the Ready status, a ZIP file of the content of the entire Dossier of the article is made, uploaded to an S3 bucket and the URL for downloading the file is made available by adding it to a row in a Google Sheet.
  • Same as the previous example, but now done when a layout reaches the Ready status to make all of its pages in PDF format available for download.

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

Background information

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

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

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

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

What is implemented?

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

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

More information

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

Changes

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

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

Dropped:

  • Support for Adobe CC 2017.
Solr

Added:

  • Support for Solr 8.8.

Dropped:

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

The integration was offered through the following web service interfaces:

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

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

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

The following Web Services have been removed:

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

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

The following files have been removed:

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

The following Studio business connector has been removed:

  • DataSource_EnterpriseConnector

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

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

The following web service connectors have been removed:

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

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

Examples:

Ads*_EnterpriseConnector: 

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

Dat*_EnterpriseConnector: 

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

The following database tables have been removed:

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

The following Maintenance page has been removed:

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

It involves the following method:

\AxaioMadeToPrintDispatcher_EnterpriseConnector::queueLayoutObjectFilterEditions()

Its signature has been changed from:

queueLayoutObjectFilterEditions( array $layEditions ....

to:

queueLayoutObjectFilterEditions( array &$layEditions ....

Documentation

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

Known issues

No known issues exist for this release of Studio Server.

Fixed issues

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

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

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

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

EN-92781 AutomatedPrintWorkflow script folder contains a __MACOSX folder.

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

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

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

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

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

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

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

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

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

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

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

EN-93655 Security: SQL Injection in User Inbox.

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

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

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

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

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

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

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

EN-93891 Add support for Status based archiving.

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

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

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

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

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

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

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

Installation

Related articles

Comments

Do you have corrections or additional information about this article? Leave a comment!

Do you have a question about what is described in this article? Please contact support here.


0 comments

Please sign in to leave a comment.