Skip to main content

Release Notes for Studio Server 10.14

  • Updated

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

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

Studio Server version 10.14.1 build 380

Release date: 21 April 2022

Downloads

New features

Changes

Documentation

Known issues

Fixed issues

Installation

Downloads

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

New features

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

Changes

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

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

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

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:

Known issues

No known issues exist for this release of Studio Server.

Fixed issues

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

Studio Server 10.14.0

Studio Server version 10.14.0 build 373

Release date: 13 January 2022

Downloads

New features

Changes

Documentation

Known issues

Fixed issues

Installation

Downloads

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

New features

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

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

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

  • Improvements to server logging. To improve the functionality of logging server activity, the following has been added:
  • Log files can now be output or streamed to a central location. When multiple instances of Studio Server are used, errors, warnings and information about the use of deprecated features can now be logged in a central location outside of Studio Server. This makes it easier and more efficient to detect problems from multiple servers from just one location.
  • Controlling the logging detail for an individual user via the User Maintenance page. When server logging is used for investigating technical issues that a user experiences, the level of detail to log can now be controlled via the User Maintenance page for that user. This is done by setting any of the DEBUGLEVEL options (ERROR, WARN, INFO, or DEBUG) in the new Log Level field.

This has the following advantages:

  • It prevents having to configure the log level in the configserver.php file to which few people have access.
  • The generated log files are smaller in size and contain only data based on the actions performed by the user. The data is thereby more relevant and easier to analyze.
  • New loglevel field in the smart_users table. To support the new Log Level field on the User Maintenance page, a new field named 'loglevel' has been added to the smart_users table. User logging is set to NONE by default, including when upgrading to Studio Server 10.14.0.
  • LogLevel has been added to the Admin WSDL. Integrators using the admin web services can define the log level for a user in the SmartConnectionAdmin.wsdl file. A 'LogLevel' option has been added to the 'User'. Affected web services such as Create/Modify/Get/Copy-users will now have a 'LogLevel' item: Users[]->LogLevel.
<xsd:simpleType name="LogLevel">
    <xsd:restriction base="string">
        <xsd:enumeration value="NONE"/>
        <xsd:enumeration value="ERROR"/>
        <xsd:enumeration value="WARN"/>
        <xsd:enumeration value="DEPRECATED"/>
        <xsd:enumeration value="INFO"/>
        <xsd:enumeration value="DEBUG"/>
    </xsd:restriction>
</xsd:simpleType>

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

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

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:

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

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.