The Release Notes for Studio Server contain information about the new features, changes, fixed issues, known issues, and upgrade instructions for each release of Studio Server.
The versions are listed by version number in descending order. Use the Navigation block to the right of the page to quickly navigate to a version.
Release Notes for:
- Studio Server 10.13
- Studio Server 10.12
- Studio Server 10.11
- Studio Server 10.10
- Versions 10.9.0 and lower
Studio Server 10.13.0
Studio Server version 10.13.0 build 351
Release date: 3 June 2021
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:
|
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:
|
| Solr |
Added:
Dropped:
|
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: Dat*_EnterpriseConnector: |
The following database tables have been removed:
- smart_datasources
- smart_dsobjupdates
- smart_dspublications
- smart_dsqueries
- smart_dsqueryfamilies
- smart_dsqueryfields
- smart_dsqueryplacements
- smart_dssettings
- smart_dsupdates
The following Maintenance page has been removed:
- Integrations > Data sources
Axaio MadeToPrint integration: manipulating Edition IDs
The signature of one of the Enterprise Connector methods of the MadeToPrint integration has been changed to make it possible for customization scripts to manipulate the Edition ID.
It involves the following method:
\AxaioMadeToPrintDispatcher_EnterpriseConnector::queueLayoutObjectFilterEditions()
Its signature has been changed from:
queueLayoutObjectFilterEditions( array $layEditions ....
to:
queueLayoutObjectFilterEditions( array &$layEditions ....
Documentation
The following changes to the documentation have been made in this release of Studio Server:
- Compatibility of Studio Server 10.13 - new
- Archiving files from Studio Server 10.13.0 or higher to Assets Server - new
- Studio Server database tables - updated
- Web Services Guide - updated
Known issues
No known issues exist for this release of Studio Server.
Fixed issues
The following issues have been fixed in this release of Studio Server:
EN-31825 Configuration: Default value for ATTACHMENTDIRECTORY for Windows is incorrect.
EN-90992 Brand Maintenance page: Blank page is shown when creating a new Brand, leaving Name field empty and clicking Update.
EN-92771 Workflow Maintenance page: Missing function parameter error when enabling 'Skip InDesign Server Automation' for articles and clicking Update.
EN-92781 AutomatedPrintWorkflow script folder contains a __MACOSX folder.
EN-93125 Health Check page: WoodWing Assets Content Source test show 'Elvis' instead of 'Assets' in error message.
EN-93161 Solr: Fall back on database search when Solr is indexing.
EN-93168 Routing e-mail template: custom date type field's are displaying as type datetime with T00:00:00.
EN-93172 InDesign Server: improve the extraction of the Adobe version of a layout.
EN-93258 ExifTool integration: Metadata extraction for EPS and AI files by ExifTool results in warning in server log.
EN-93373 Health Check page: OPCache error in server logging when user opens page (or clicks links on page).
EN-93401 The WSDLs seems no longer compatible with modern .NET clients.
EN-93537 User Maintenance page: When setting the 'Password Expiration in Days’ field, the database field ‘expirepassdate’ should also get updated/re-calculated.
EN-93585 Breadcrumbs: Enable breadcrumb navigation when new entity is added.
EN-93589 Client applications: Brands are not arranged alphabetically if no display order is defined.
EN-93599 Planning interface: Layout created via planning interface has no preview when the pages use a non-arabic numbering system.
EN-93655 Security: SQL Injection in User Inbox.
EN-93656 Security: SQL Injection via the HaveVersion ID Parameter.
EN-93699 Replace article: No error reported by InDesign Server on macOS.
EN-93702 Access Profiles: remove the 'Content Station Pro - Edition' access right.
EN-93718 Add support for archiving Adverts from Studio Server to Assets Server.
EN-93726 Control characters in the Name field of an object are replaced with a space.
EN-93815 Image frame fitting settings in the layout are overridden by Studio.
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
- Installing Studio Server on a system on which it is not yet installed. See Studio Server full installation.
- Upgrading an existing installation of Studio Server. See Upgrading an existing installation of Studio Server.
- Upgrading from Enterprise Server. See Upgrading Enterprise Server to Studio Server 10.10 or higher.
Studio Server 10.12.0
Studio Server version 10.12.0 build 333
Release date: 20 January 2021
Downloads
The download files for this version of Studio Server can be found in the Release announcement.
New features
No features have been introduced in this release of Studio Server.
Changes
The following sections list the changes that have been made in this release of Studio Server.
Compatibility Matrix
Compared to Studio Server 10.11, various changes have been made to the compatibility between Studio Server and other systems as shown in the following table.
| Technology/feature | Remarks |
|---|---|
| Adobe 2021 |
Studio Server 10.12 is compatible with InDesign 2021, InDesign Server 2021, and InCopy 2021. Note: The use of these applications requires Studio for InDesign and InCopy 2021 (version 16.0.0) which is planned to be released in Q1 2021. |
| PHP | Studio Server 10.12 requires PHP 7.4. |
| ionCube Loader | Studio Server 10.12 requires ionCube Loader 10.4.5. |
| MS SQL Server drivers | Support for SQL Driver 5.6 for PHP has been removed because this driver is not compatible with PHP 7.4. |
Support for creating catalogs in InDesign
The following DataSource Web service interface definitions have been marked as deprecated:
| Entry point | WSDL |
|---|---|
| https://localhost/StudioServer/datasourceindex.php | StudioServer/server/interfaces/PlutusDatasource.wsdl |
| https://localhost/StudioServer/datasourceadminindex.php | StudioServer/server/interfaces/PlutusAdmin.wsdl |
See also:
- The Web Services guide
- The Web Services index: Studio Server > Advanced > Web Services SDK
The following server plug-ins have been removed:
| Display name | Internal name |
|---|---|
| CSV Data Source | CSVDataSource |
| Database Data Source | DBDataSource |
| DataSource Workflow Service | DataSourceWorkflowService |
| DataSource Record Structure | DataSourceService |
Dossier template support for Content Station 9
Support for adding Dossier templates to the Home page of Content Station 9 has been removed. Support for this feature was already deprecated but has now been fully removed from the software.
The following has been removed from the Brand Maintenance page:
- The Dossier templates section.
Note: When upgrading from a version of Enterprise Server in which records for this list existed, these records will be automatically removed during the upgrade.
The following PHP classes have been removed:
- BizAdmTemplateObject
- DBAdmTemplateObject
- TemplateObjectAccess
- AddTemplateObjectsRequest
- AddTemplateObjectsResponse
- AddTemplateObjectsService
- GetTemplateObjectsRequest
- GetTemplateObjectsResponse
- GetTemplateObjectsService
- RemoveTemplateObjectsRequest
- RemoveTemplateObjectsResponse
- RemoveTemplateObjectsService
The following Named Query has been removed:
- DOSSIER_TEMPLATES_IN_APPLICATIONS. This was implemented in the Server plug-in 'Studio List Dossiers' (also known as 'Content Station List Dossiers').
The following database table has been removed:
- smart_publobjects
The following elements and services under the Admin interface (StudioServer/server/interfaces/SmartConnectionAdmin.wsdl) have been removed:
- Elements:
- TemplateObjectAccess
- ArrayOfTemplateObjectAccess
- AddTemplateObjectsRequest
- AddTemplateObjectsResponse
- GetTemplateObjectsRequest
- GetTemplateObjectsResponse
- RemoveTemplateObjectsRequest
- RemoveTemplateObjectsResponse
- Services:
- AddTemplateObjects
- GetTemplateObjects
- RemoveTemplateObjects
Publish Forms: Removal of the Publishing Services feature
Publishing Services were used in conjunction with Publish Forms in Content Station 9. Support for Publish Forms was already deprecated but its functionality (the Publishing Services) has now been fully removed.
Note that this means that these services cannot be called anymore, for example from custom integrations or plug-ins.
The following files have been removed:
- StudioServer/server/utils/PublishingProgressBar.class.php
- StudioServer/server/utils/PublishingFields.class.php
- StudioServer/server/utils/ParallelCallbackCache.class.php
- StudioServer/server/bizclasses/BizPublishing.class.php
- StudioServer/server/bizclasses/BizPubIssue.class.php
- StudioServer/server/interfaces/plugins/connectors/PubPublishing_EnterpriseConnector.class.php
- StudioServer/server/dbclasses/DBPubPublishedIssues.class.php
- StudioServer/server/dbclasses/DBPublishedObjectsHist.class.php
- StudioServer/server/dbclasses/DBPublishHistory.class.php
The following functions have been removed:
In StudioServer/server/bizclasses/facades/ServerPlugin.class.php:
- WW_BizClasses_Facades_ServerPlugin::runChannelConnector()
In StudioServer/server/bizclasses/BizServerPlugin.class.php:
- BizServerPlugin::getPluginFolderForChannelId()
- BizServerPlugin::runChannelConnector()
- BizServerPlugin::getChannelConnector()
In StudioServer/server/bizclasses/BizAdmPublication.class.php:
- BizAdmPublication::getDefaultPubChannel
The following Named Query has been removed:
- The build-in Named Query 'PublishManager'. This was used by Content Station 9 in the 'Publish Manager' tab to show an overview of the publish status of each Publish Form ('Ready To be Published', 'New', 'Updated', 'Published').
The following Studio business connector has been removed:
- PubPublishing_EnterpriseConnector
As a result, in the <pluginName>/PluginInfo.php file of a custom server plug-in, the following entry cannot be called anymore in the getConnectorInterfaces() function:
final public function getConnectorInterfaces()
{
return array( 'PubPublishing_EnterpriseConnector' );
}The following classes in StudioServer/server/smartevent.php have been removed:
- class smartevent_issuereorderpublished
- class smartevent_publishissue
- class smartevent_updateissue
- class smartevent_unpublishissue
- class smartevent_setpublishinfoforissue
- class smartevent_publishdossier
- class smartevent_updatedossier
- class smartevent_unpublishdossier
- class smartevent_setpublishinfofordossier
- class smartevent_issuereorder
The following database tables have been removed:
- smart_pubpublishedissues
- smart_publishedobjectshist
- smart_publishhistory
When upgrading from a previous version of Studio Server or Enterprise Server, these tables will be removed ('dropped') during the database upgrade.
The following database fields have been removed:
- smart_states table: 'readyforpublishing'
- smart_targets table: 'publisheddate', 'publishedmajorversion', 'publishedminorversion', 'externalid'
- smart_channels table: 'publishsystem'
When upgrading from a previous version of Studio Server or Enterprise Server, these database fields will be removed ('dropped') during the database upgrade.
The following Web Service has been removed:
- Publishing interface (StudioServer/server/interfaces/EnterprisePublishing.wsdl). This interface was mainly called by Content Station 9.
No services related to the Publishing interface can be called anymore.
The following 'actions' in the Workflow interface (StudioServer/server/interfaces/SCEnterprise.wsdl) have been removed:
In the Workflow interface as part of simple type 'Action', the following entries have been removed:
<simpleType name="Action”><enumeration value="PublishDossier"/>
<enumeration value="UpdateDossier"/>
<enumeration value="UnPublishDossier"/>
<enumeration value="SetPublishProperties"/> The following properties have been marked as discontinued:
Workflow interface (StudioServer/server/interfaces/SCEnterprise.wsdl)
- Under 'Target':
- 'PublishedDate' and 'PublishedVersion' properties (Discontinued)
- Under 'PubChannelType':
- 'sms' type (Discontinued)
Admin interface (StudioServer/server/interfaces/SmartConnectionAdmin.wsdl)
- Under 'Status':
- 'ReadyForPublishing' property (Discontinued)
- Under 'PubChannel':
- 'PublishSystem' property (Discontinued)
- Under 'PubChannelType':
- 'sms' type (Discontinued)
The Studio Server code base no longer handles these properties.
Web Services: Changes to the WflGetPagesService
The WflGetPagesService is used for retrieving page renditions (thumbnails or previews) of layouts in applications such as Journal Designer. The following changes have been made to it:
- Improved performance. To speed up the retrieval process, the following has been changed:
- A new parameter named 'HaveVersions' has been added to the WflGetPagesRequest. By setting this parameter, only page rendition attachments are returned when, after an initial request, a newer version of the page is available. Previously all page renditions were copied to the Transfer Server folder (by the server) and downloaded by the client, even though no newer version was available.
- The following functions have been removed from the DBPage class; these should no longer be called by PHP customizations:
- DBPage::listPagesByLayoutPerIssue
- DBPage::listPagesByLayoutPerIds
- The following parameters have been deprecated since Enterprise Server 8.3.3 and have now been removed from the WflGetPagesRequest; these should no longer be used by web service integrations:
- PageOrders
- PageSequences
- RequestMetaData
- RequestFiles
For information about Web Services, see The Web Services SDK of Studio Server.
Documentation
The following changes to the documentation have been made in this release of Studio Server:
- Compatibility of Studio Server 10.12 - new
- Studio Server database tables - updated
- The Web Services SDK of Studio Server - updated
- Studio Server plug-ins - updated
Known issues
No known issues exist for this release of Studio Server.
Fixed issues
The following issues have been fixed in this release of Studio Server:
EN-16009 Performance/JournalSuite: Improve performance of the planning overview in JournalDesigner.
EN-91829 Brand and Issue Maintenance pages: The field labels 'Reading Order Reversed" and 'Reading Order' are swapped.
EN-91948 User Authorization report: The tooltip for the Back button is not shown.
EN-92052 Publication Channel Maintenance page: When creating or copying a new Brand, the focus is not set to the Name field.
EN-93426 Performance: Add index to smart_objects table on 'publication and 'type'.
Installation
- Installing Studio Server on a system on which it is not yet installed. See Studio Server full installation.
- Upgrading an existing installation of Studio Server. See Upgrading an existing installation of Studio Server.
- Upgrading from Enterprise Server. See Upgrading Enterprise Server to Studio Server 10.10 or higher.
Studio Server 10.11.3
Studio Server version 10.11.3 build 338
Release date: 13 April 2021
Downloads
The download files for this version of Studio Server can be found in the Release announcement.
New features
The following has been introduced in this release of Studio Server:
- Archiving Adverts. Support for archiving Adverts from Studio Server to Assets Server has been added. They are typically archived as part of the layout on which they are placed, but unplaced Adverts can also be archived as part of the process of archiving Dossiers.
Take note of the following:
- An Advert is archived as an image, not as an Advert object. The archived image will have the original Workflow Status of the Advert object. When the image is restored, it will be assigned the default Workflow Status for images, as configured in Studio Server.
- To archive an Advert, a high-resolution version of the Advert should be available (typically in the form of a PDF file). This file should not be stored on an external drive but in the File Store folder of Studio Server.
- When an Advert is placed on a layout, it will get archived through the print based archiving schema.
- When an Advert is not placed on a layout but is part of a Dossier, it will get archived through the Dossier based archiving schema.
- When an Advert is not placed on a layout and is not part of a Dossier, it is not archived.
For more information about archiving, see Archiving files from Studio Server 10.11.1 or higher to Assets Server.
Changes
The following changes have been made in this release of Studio Server:
- Archiving: A layout that contains a planned image is considered to be incomplete and therefore not ready for archiving. When the archiving process is run, the process for that layout now fails and an error is shown to the user.
Documentation
The following changes to the documentation have been made in this release of Studio Server:
Known issues
The following known issues exist for this release of Studio Server:
EN-94077 Assets Server integration, archiving Adverts. When restoring a layout containing an Advert, the restored Advert in the form of an image is unlinked. During this process, the following message appears:
The following files could not be restored from Assets Server and were unlinked from the layout
This issue is planned to be fixed in the upcoming patch version for Adobe 2020 (Studio for InDesign and InCopy 15.2.1) and Adobe 2021 (Studio for InDesign and InCopy 16.1.0).
Fixed issues
The following issues have been fixed in this release of Studio Server:
EN-93815 Image frame fitting settings in the layout are overridden by Studio.
Installation
- Installing Studio Server on a system on which it is not yet installed. See Studio Server full installation.
- Upgrading an existing installation of Studio Server. See Upgrading an existing installation of Studio Server.
- Upgrading from Enterprise Server. See Upgrading Enterprise Server to Studio Server 10.10 or higher.
Studio Server 10.11.2
Studio Server version 10.11.2 build 335
Release date: 9 March 2021
Downloads
The download files for this version of Studio Server can be found in the Release announcement.
New features
The following has been introduced in this release of Studio Server:
- Compatibility: Support for Adobe 2021 added. Studio Server 10.11.2 is compatible with InDesign 2021, InDesign Server 2021, and InCopy 2021.
Note: The use of these applications requires Studio for InDesign and InCopy 2021 (version 16.0.0).
- Archiving based on Workflow Status: Archiving files to Assets Server can now also be done based on a dedicated Workflow Status such as 'Ready for Archiving'. Any file that is set to that status is automatically archived. This archiving method is known as 'Status based' archiving and is in addition to the already existing Continuous and Issue based archiving in which files are archived when a defined number of days has passed since a specific date.
Status based archiving is used for archiving files when they are ready to be archived and makes it possible for example to prepare periodic publications well in advance of the actual publication (such as a Christmas edition that is prepared during the summer), or tweak publications after they have been published (such as modifying layouts for XML export).
Note: Although Status based archiving is a manual way of archiving files, the actual archiving process is a scheduled process and therefore determined by how often this process is run. Technically it is therefore also time based.
To make Status Based archiving work, the following has been added:
- On the Brand Maintenance page: a Trigger named 'Status Based'. When enabling this for a Digital article, Dossier, or layout, files are archived when they are assigned to a dedicated Workflow Status.
- On the Workflow Maintenance page: an option named 'Send to Archive'. Enabling this for a Workflow Status indicates that any file that is set to that status is marked for archiving based on the Status Based archiving method.
Figure: The Send to Archive option on the Workflow Maintenance page. Here. a Workflow Status 'Ready for Archiving' has been created for which the option is enabled.
For more information, see Archiving files from Studio Server 10.11.1 or higher to Assets Server.
Changes
The following changes have been made in this release of Studio Server:
- Preview performance optimization: master spreads are deleted when previews are generated on InDesign Server. The performance of the Layout preview in the Print editor of Studio has been optimized by deleting unused master spreads from the layout when the preview is generated. We have observed that layouts that contain many master spreads with content can significantly delay the preview generation of that layout.
This change is implemented in the IDPreview.jsx script that is run by InDesign Server.
Note: The master spreads are only removed from the local copy for InDesign Server; it does not affect the layout that is saved in Studio Server.
- Archiving: When the process to see if candidate layouts are available for archiving is run, layouts that are found are now first checked to see if they are part of an InDesign Server Job. When this is the case, these layouts are then not archived and an error is raised to make the user aware of this.
- Access Rights: The Access Right 'Content Station Pro - Edition' has been removed; support for Content Station in combination with Studio Server was already dropped. The access right will be removed from the database during the upgrade.
Documentation
The following changes to the documentation have been made in this release of Studio Server:
- Compatibility of Studio Server 10.11 - updated
- Archiving files from Studio Server 10.11.1 or higher to Assets Server - updated
- Creating Workflow Statuses in Studio Server - updated
- Workflow Status settings in Studio Server - updated
Known issues
No known issues exist for this release of Studio Server.
Fixed issues
The following issues have been fixed in this release of Studio Server:
EN-31825 Configuration: Default value for ATTACHMENTDIRECTORY for Windows is incorrect.
EN-90992 Brand Maintenance page: Blank page is shown when creating a new Brand, leaving Name field empty and clicking Update.
EN-92771 Workflow Maintenance page: Missing function parameter error when enabling 'Skip InDesign Server Automation' for articles and clicking Update.
EN-92781 The AutomatedPrintWorkflow script folder contains hidden files and MACOSX internal folders/files.
EN-93168 Routing e-mail template: custom date type fields are displaying as type 'datetime' with 'T00:00:00'.
EN-93125 Health Check page: 'Elvis' is shown instead of 'Assets' in error message.
EN-93172 InDesign Server: improve the extraction of the Adobe version of a layout.
EN-93258 ExifTool integration: Metadata extraction for EPS and AI files by ExifTool results in warning in server log.
EN-93401 The WSDLs seems no longer compatible with modern .NET clients.
EN-93537 User Maintenance page: When setting the 'Password Expiration in Days’ field, the database field ‘expirepassdate’ should also get updated/re-calculated.
EN-93585 Breadcrumbs: enable breadcrumb navigation when new entity is added.
EN-93589 Client applications: Brands are not arranged alphabetically if no display order is defined.
EN-93599 Planning interface: Layout created via planning interface has no preview when the pages use non-arabic numbering system.
EN-93655 Security: SQL Injection in User Inbox.
EN-93656 Security: SQL Injection via the HaveVersion ID Parameter.
EN-93699 Replace article: no error reported by InDesign Server on macOS.
EN-93702 Access Profiles: Remove 'Content Station Pro - Edition' Access Right.
EN-93726 Control characters in the Name field of an object are replaced with a space.
EN-93858 'Not sufficient access rights' message S1077 shown when user logs in to the server using the full name.
EN-93882 Preview performance optimization: delete master spreads when generating previews on InDesign Server.
Installation
- Installing Studio Server on a system on which it is not yet installed. See Studio Server full installation.
- Upgrading an existing installation of Studio Server. See Upgrading an existing installation of Studio Server.
- Upgrading from Enterprise Server. See Upgrading Enterprise Server to Studio Server 10.10 or higher.
Studio Server 10.11.1 build 327 Quick Patch
Studio Server version 10.11.1 build 327
Release date: 2 November 2020
Downloads
The download files for this version of Studio Server can be found in the Release announcement.
Fixed issues
The following issues have been fixed in this release of Studio Server:
EN-93573 Unable to log in to Studio because of a PHP security fix.
Installation
- Installing Studio Server on a system on which it is not yet installed. See Studio Server full installation.
- Upgrading an existing installation of Studio Server. See Upgrading an existing installation of Studio Server.
- Upgrading from Enterprise Server. See Upgrading Enterprise Server to Studio Server 10.10 or higher.
Studio Server 10.11.1
Studio Server version 10.11.1 build 326
Release date: 27 October 2020
Downloads
The download files for this version of Studio Server can be found in the Release announcement.
New features
The following feature has been introduced in this release of Studio Server:
- Archiving Dossiers to Assets Server. Dossiers can now be archived to Assets Server in the following ways:
- When a layout or Digital article is archived, all files in the Dossier of which the layout or Digital article is part can now also be archived.
- Dossiers that do not contain a layout or Digital article (such as Dossiers containing reference material or a Print article) can now also be archived.
For more information, see Archiving files from Studio Server 10.11.1 or higher to Assets Server.
Changes
The following changes have been made in this release of Studio Server:
- Archiving files to Asset Server. The following changes have been made:
- Digital articles do not have to be placed in a Dossier anymore to be archived.
- Archiving layouts and Digital articles can now also be based on a custom number of days that have passed since the layout was last modified.
- When setting up the Archive Zone folder using wildcards, the year, month, and day of the publication date of the Issue can now be included in the folder name by using the following wildcard:
${publicationdate:Y-m-d}
- This wildcard is ignored when the layout, Digital article, or Dossier is not targeted for an Issue.
- When a layout, Digital article, or Dossier is targeted to more than one Issue, the name of the first Issue is taken.
For more information, see Archiving files from Studio Server 10.11.1 or higher to Assets Server.
- Integration with Assets Server: password settings validation. In previous versions, the password restrictions that were defined in the configserver.php file (such as the required number of characters) were not validated. When not making use of authentication providers such as LDAP/Active Directory, Okta or AWS Cognito, it was possible therefore to create user accounts that did not adhere to these restrictions This has now been fixed.
We advice to have all users reset their passwords for logging in to Studio Server. Note that this is only needed when all of the following is true:
- No third-party authentication providers such as LDAP/Active Directory, Okta, or AWS Cognito are used.
- The WoodWing Assets plug-in is enabled.
- Changes have been made to the default settings of the Password management configuration in the configserver.php or config_overrule.php file.
- Display order of Brands. When setting up Brands, the order in which the Brands are displayed can be defined by assigning a number to each Brand. When multiple Brands have the same number, these Brands are now sorted alphabetically. In previous versions they were sorted by creation date or sometimes randomly.
- Searching: sorting on status. When Solr was not enabled in previous versions, and the user sorted the search results on the Status column, the results were sorted by their order as set on the Workflow Status page. Now, the sorting is done alphabetically by status name.
If sorting on status order is still preferred, set the following option in the configserver.php/config_overrule.php file to 'true':
SORT_ON_STATE_ORDER'
Note: The 'SORT_ON_STATE_ORDER' setting is not new but was ignored when Solr was not enabled.
- Web Services: AdmCopyPublications service enabled. The AdmCopyPublications service which used to be commented out in the WSDL has now been enabled. For more information, see the Web Services Guide.
Documentation
The following changes to the documentation have been made in this release of Studio Server:
- Archiving files from Studio Server 10.11.1 or higher to Assets Server - new
- Upgrading an existing installation of Studio Server - updated
- Upgrading Enterprise Server to Studio Server 10.10 or higher - updated
Known issues
The following known issue exists for this release of Studio Server:
- PHP. A recent PHP security fix (#79699) has impacted the communication between Studio Server and the client applications, preventing the applications from logging in to Studio Server. To avoid this issue, the highest supported version of PHP is currently 7.3.22.
This will be resolved as soon as possible in the form of a quick path for Studio Server 10.11.1.
Fixed issues
The following issues have been fixed in this release of Studio Server:
EN-18224 Solr: Incorrect search result when sorting on Status.
EN-19936 When copying a Brand using a name that already exists, the Copy Issues check box is cleared.
EN-22114 Check boxes on Issue Maintenance page are incorrectly aligned.
EN-29204 Icons on the Export page are incorrectly aligned.
EN-30767 The 'Type' field for custom properties on the Metadata page is not localized.
EN-33175 Change default order of Brands from creation order to alphabetically.
EN-36454 User Maintenance: Nothing happens when creating a user with a Valid From date later than the Valid Till date.
EN-88415 Implement the CopyPublications service.
EN-90613 'Production Zone' value is set incorrectly when copying a Brand.
EN-93083 Support the 'Publication Date' field as a wildcard in the zone paths for archiving to Assets.
EN-93301 Add a check and prevent objects from changing object type.
EN-93345 InDesign Server: preview generation does not take into account that the active URL can have a query string.
EN-93346 InDesign Server: Error raised in logs file after deleting an InDesign Server instance from the 'Overview of InDesign Servers' page.
EN-93349 'Invalid property (S1020)' error is logged in server log file when restoring an archived Digital article containing an image which has been renamed after archiving.
EN-93352 When editing a placed article in Studio, warnings are logged in server log file.
EN-93356 'Invalid property (S1020)' error is logged in server log file when restoring an archived layout containing a placed image.
EN-93357 Copy/Create user: Password settings in configserver.php file are not respected.
EN-93365 Breadcrumb on License Status page changes when removing tickets to log-off users
EN-93368 Incorrect thumbnail shown for an image in the History panel of Studio.
EN-93370 Studio: After changing a file to a different type, restoring it to its original type and refreshing the search results page, type of format file was changed to is shown.
EN-93372 Incorrect breadcrumb when trying to copy a Brand using a name of a Brand that already exists.
EN-93375 Objects routed to Route-to groups are missing in search results.
EN-93383 Studio Publication Overview shows short user name instead of full user name for the 'Modified by' field.
EN-93396 Archiving to Assets Server: date wildcards are not properly resolved.
EN-93420 The timestamp in the Studio Server log files should be in the local time instead of in GMT.
EN-93431 Studio: Package for a published Digital article contains a maximum of 50 images.
EN-93440 Health Check: Fatal error when connection to LDAP system fails.
EN-93447 When copying a Brand, the 'Archive Zone' settings are incorrectly set.
EN-93448 When copying a Brand, the 'Default Status Restored Digital Article' and 'Default Status Restored Image' values are incorrectly set.
EN-93470 Opening a layout with placed articles and images results in a fatal 'Type Error'.
EN-93487 No warning is shown when placing an article component more than once.
EN-93549 Studio requests for number of CheckedOut/LockedBy items results into huge load on the database.
EN-93497 Article preview is showing the previous content instead of the latest.
Installation
- Installing Studio Server on a system on which it is not yet installed. See Studio Server full installation.
- Upgrading an existing installation of Studio Server. See Upgrading an existing installation of Studio Server.
- Upgrading from Enterprise Server. See Upgrading Enterprise Server to Studio Server 10.10 or higher.
Studio Server 10.11.0
Studio Server version 10.11.0 build 318
Release date: 23 July 2020
Downloads
The download files for this version of Studio Server can be found in the Release announcement.
New features
The following feature has been introduced in this release of Studio Server:
- Maintenance pages now contain breadcrumb navigation. To make navigating the Maintenance pages easier, and to better visualize where in the structure the user is currently working, breadcrumb navigation has been added to all Maintenance pages.
|
Notes:
|
Changes
The following sections list the changes that have been made in this release of Studio Server.
Compatibility Matrix
Compared to Studio Server 10.10, various changes have been made to the compatibility between Studio Server and other systems as shown in the following table.
| Technology/feature | Remarks |
|---|---|
| Microsoft SQL |
Added:
|
| Operating systems |
Added:
Dropped:
|
| Output devices | As a result of the dropped support for publishing to Adobe DPS/AEM, the Output Devices Maintenance page is no longer available. |
| Publish Forms and Suggestion providers |
These features were part of Content Station 9 which is not supported. The following back-end functionality has been removed:
The following changes to the Maintenance pages have been made:
|
| RabbitMQ |
Added:
Dropped:
|
| Solr |
Added:
Note: Solr 7.6 has officially reached its end of life. |
| Spelling and Suggestions |
These features were part of Content Station 9 which is not supported. All related back-end functionality has been removed. On the Health Check page, the following entries have been removed from the Test Tools menu:
|
Upgrading
Various changes have been made to Studio Server 10.11.0 which affects upgrading from previous versions. This includes:
- The upgrade path
- Features that are no longer supported
- Changes to Named Queries, PHP classes, PHP functions, database items, and more
For details, see Upgrading Enterprise Server to Studio Server 10.10 or higher.
Assets Server integration
To following changes have been made to the functionality of archiving files to Assets Server:
- The configuration of the 'Archive Zone' and 'Archive after (days)' options can now be set for each archive schema separately. In previous versions, when both 'Issue based' and 'Continuous' archive schemas were selected, the 'Archive Zone' and 'Archive after (days)' options applied to both these schemas. Now, the 'Archive Zone' and 'Archive after (days)' options can be defined separately for each schema.
- New and changed configuration options. In the config_elvis.php file, one configuration option has changed and three new options have been added to give more control over the default values of the two properties:
| Option | Remarks |
|---|---|
|
DEFAULT_ELVIS_ARCHIVE_ZONE |
Changed option, can now only be used for the 'Archive Zone' option of the 'Continuous' archive schema. |
|
DEFAULT_ELVIS_ARCHIVE_AFTER_DAYS_DIGITAL |
New option, default for the 'Archive after (days)' option of the 'Continuous' archive schema. |
|
DEFAULT_ELVIS_ARCHIVE_ZONE_PRINT |
New option, default for the 'Archive Zone' option of the 'Issue Based' archive schema. |
|
DEFAULT_ELVIS_ARCHIVE_AFTER_DAYS_PRINT |
New option, default for the 'Archive after (days)' option of the 'Issue Based' archive schema. |
- New default values. The default value for the 'Archive after (days)' option has been changed from zero (0) to the following values:
- Continues archive schema: 30
- Issue Based schema: 7
- Health Check test. When running the 'WoodWing Assets Content Source' test on the Health Check page, any of the options mentioned above are automatically checked. When no values have been set for a Brand, they automatically get the default value assigned.
When options have been repaired, an orange 'UPDATE' icon is shown together with a list of affected Brands. Each Brand can be clicked to navigate to its Brand Maintenance page for manual examination.
InDesign Server integration
The following changes have been made:
- Logging is now off by default and can be enabled for debugging. In previous versions, logging by InDesign Server Jobs to various devices was enabled by default and could not be disabled. This could potentially negatively affect the performance of the production environment.
Now, logging is off by default and can be enabled for debugging purposes when needed. This is done through the following option in the configserver.php file:
INDESIGNSERV_LOGTODEVICES
For details, see Controlling InDesign Server Job logging in Studio Server.
- Scripts are no longer uploaded to InDesign Server during production. In previous versions, InDesign Server Jobs always uploaded their script to InDesign Server just before it was executed. This is now no longer done during production hours. Instead, scripts are uploaded during installation time and cached on the InDesign Server host machine.
Scripts are taken by the Health Check page from the StudioServer/server/utils/idsscripts folder and distributed to all InDesign Server machines (connected to Studio Server) in the following folder:
- MacOS: ~/Library/Preferences/Adobe InDesign Server/Version x.y/
en_US/configuration_<port number>/Scripts/WwEnterpriseUtils - Windows: %USERHOME%\AppData\Roaming\Adobe\InDesign Server\Version x.y\
en_US\configuration_<port number>\Scripts\WwEnterpriseUtils
Where:
- Version x.y is the InDesign Server Version. For example: 'Version 15.0'.
- configuration_<port number> is the port on which InDesign Server is started. For example: 'configuration_18387'.
- No need anymore for a shared or mounted WebEdit folder with InDesign Server. In previous versions, the path to the WEBEDITDIR folder needed to be defined in the WEBEDITDIRIDSERV option. This option has now been dropped and a mount from either the Studio Server machines and/or from the InDesign Server machines is no longer needed.
Studio Server still needs access to the WebEdit folder that is shared between the application servers. However, Studio Server now creates a WebEdit folder for each InDesign Server machine automatically (without the need for configuration). This folder is shared between the InDesign Server instances running on that machine only. Files that needs to be shared will be transferred over HTTP automatically.
This folder is created in the following location:
- MacOS: ~/Library/Application Support/WwIdsWorkSpace
- Windows: %USERDATA%/WwIdsWorkSpace (by default, C:\Documents and Settings\username\Application Data\WwIdsWorkSpace)
- The generateOutputPages function can no longer be used. Integrations may have used this function provided by the BizWebEditWorkspace class. However, the parameters for this function have been heavily changed due to the changes mentioned above. More importantly, the function is no longer static or public and can therefore no longer be called.
Note: As this is a breaking change, integrators should look for an alternative solution for integrations using this function.
- Drop in preview performance. Due to the changes mentioned above, the performance of generating previews has dropped with an average of about 12%. (The actual figure depends on many factors, such as the size of the layout and article, and the number of images used.)
- Support for the use of certificate files via WWSettings.xml dropped. This SSL feature of Studio for InDesign Server can no longer be used for the preview feature of the InDesign Server integration. This is because the generated previews are now directly uploaded to Studio Server by the InDesign Server preview script.
Note: Specifying certificate files is still supported by Studio for InDesign Server. SSL connections for the preview feature can also still be set up. For the latter, the certificates registered at operating system level are used.
- Periodic clean-up of the WebEdit folders should be planned. When installing a new InDesign Server host (or upgrading an existing InDesign Server host) to connect to Studio Server, the WebEdit folders should be cleaned periodically.
These folders are created by the InDesign Server preview script (provided by Studio Server) for each preview session.
When an InDesign Server host is busy, the WebEdit folder is created by another InDesign Server host.
To make maximum use of the InDesign Server capacity (and to not have the process delayed because of auto-cleaning operations) it is the responsibility of the system operator to periodically remove the WebEdit folders.
The more users are served, the more often this should happen. However, doing this too often can lead to inefficiencies. A good starting point is to clean the folder every 15 minutes and to remove all WebEdit folders in the InDesign Server Workspace folder that are older than one hour.
For Windows Server, two example scripts are provided: a clean-up script that does the actual cleaning and an installation script that makes it periodically run with help of the Windows Task Scheduler. The scripts can be found in the StudioServer/sdk/ids folder.
Further instructions can be found in the headers of the scripts.
Note: The scripts provided are a guideline for setting up the automated cleaning. Usage of it is at your own risk; support for these scripts is not provided by WoodWing.
The Workspace folder can be found in the following locations:
- Windows: %USERDATA%\WwIdsWorkSpace
- MacOS: ~/Library/Application Support/WwIdsWorkSpace
Publication Channels
- The behavior of a Publication Channel of type 'Web' is now the same as for type 'Print'. When a Dossier was created in previous versions, the Issue that was assigned to any objects within the Dossier depended on the Issue that the Dossier was assigned to: an Issue belonging to a Publication Channel of type 'Print' or of type 'Web'.
Example: When an article was created in a Dossier assigned to an Issue of a Publication Channel of type 'Print', the article was also assigned to the Print Issue. However, when an article was created in a Dossier assigned to an Issue of a Publication Channel of type 'Web', the article was not assigned to the Web Issue.
In Studio Server 10.11.0, an object that is created within a Dossier assigned to an Issue of a Publication Channel of type 'Web' is now also assigned to that Web Issue.
Note: When searching for files by filtering on a Web issue, all the child objects are now returned instead of only the Dossiers. (Applies to objects created in Studio Server 10.11.0 or higher only; objects created in previous versions will still not appear in the search results.
Third-party libraries
- The Zend Framework has been replaced by Laminas. The Zend Framework and all its sub-projects has been transitioned to an open source project hosted at the Linux Foundation. As a result, the following changes have been made:
- The Zend Framework in the StudioServer/server/vendor folder has been replaced by Laminas.
- Zend Framework usages by Studio Server have been replaced with Laminas.
|
Notes:
|
Web service performance
As the footprint of Studio Server has been reduced, the web services show an improved performance.
This has been tested by running the ServerStudio/server/wwtest/speedtest.php module using its default options but with the 'Number of runs' option set to 5.
The test was run using the following configuration:
- Application Server running on Apache 2.4 + PHP 7.3 + ImageMagick + ExifTool + CentOS 7 instance in AWS (m5.large).
- Database running on MySQL 8.0 + CentOS 7 instance in AWS (m5.large).
- Server logging and profiling disabled.
- 3rd-party integrations disabled (InDesign Server, Elvis, RabbitMQ, Solr, and so on).
- Enterprise Server 10.8 and Studio Server 10.11 installed side-by-side (on the same instances).
- The database was set up with the standard WW News Brand configuration.
- One test run was made for SOAP and one for JSON-RPC.
Note: The InDesign/InCopy plug-ins for Studio are using SOAP and the Studio web application is using JSON-RPC.
The calculated Average outcomes are compared between Enterprise Server 10.8 and Studio Server 10.11 installations:
- SOAP performance improved by 16%.
- JSON-RPC performance improved by 29%.
|
Disclaimer:
|
SpeedTest tool
Various improvements were made to the ServerStudio/server/wwtest/speedtest.php module:
- The Version option has been removed as it lists very old server versions that are no longer relevant.
- A new option named Protocols has been added. It makes it possible to run the tests over SOAP or JSON-RPC.
Note: The InDesign/InCopy plug-ins for Studio are using SOAP and the Studio web application is using JSON-RPC.
- The Average calculation has been improved. Outcomes of the lowest performance (the highest value) are now ignored and are shown in strikethrough text.
|
Example: When the outcome is as follows:
The value of 11.2 is ignored and shown in strikethrough text. |
- A Best calculation is now also performed. It shows the fastest execution of the runs.
- The Summary report now shows totals calculated for each test run (shown when performing more than 1 test run).
Health Check page
- The 'InDesign Server / CS editor' test has been renamed to 'InDesign Server'. The 'CS editor' part was included because the test was originally used for the previews of the Content Station editor.
However, only the configured InDesign Server instances were tested. Because these are used for more purposes nowadays such as the InDesign Server Automation feature, naming the test 'InDesign Server' better reflects its purpose.
- The WSDL Cache is now automatically repaired. In previous versions, when the WSDL Cache was outdated, the WSDL Cache entry showed a WARNING icon and provided a link to clear the cache.
Now, an UPDATED icon is shown and the cache is automatically cleared when it is outdated. When the cache is cleared or up-to-date, an OK icon is shown.
LOGFILE_FORMAT
The LOGFILE_FORMAT option in the configserver.php file now also makes it possible to output in JSON format.
The output contains fields respecting the Elastic Common Schema, designed for centralized logging. It can be set up with the help of third-party tools such as Filebeat for reading logs and saving them in ElasticSearch.
Documentation
The following changes to the documentation have been made in this release of Studio Server:
- Compatibility of Studio Server 10.11 - new
- Controlling InDesign Server Job logging in Studio Server - new
- Using SSL to secure the connection between Studio Server and Studio for InDesign and InCopy - updated
- Archiving Digital articles to Assets Server - updated
- Archiving InDesign layouts to Assets Server - updated
- Upgrading Enterprise Server to Studio Server 10.10 or higher - updated
- Studio Server full installation - updated
- Logging Studio Server activity - updated
Note: Some screenshots in the product documentation may still show Enterprise Server. This will be updated over the coming weeks.
Known issues
No known issues exist for this release of Studio Server.
Fixed issues
The following issues have been fixed in this release of Studio Server:
EN-4766 Maintenance pages: '© WoodWing Software' should link to woodwing.com.
EN-10819 Incorrect spelling of metadata for PHP Preview and Meta Data server plug-in.
EN-17988 Default value of custom property is not set when the default is zero (0).
EN-89640 Support CloudFront (allow empty INETROOT).
EN-90609 Replace the WebEdit folder by another mechanism to exchange files between Content Station and InDesign Server.
EN-91845 Maintenance pages: Performance issues for the Service Logs page.
EN-92155 Maintenance pages: Make version info of InDesign Server human readable on the Health Check page.
EN-92633 Error S1029 shown when changing the Issue of a Dossier when some of its files have been moved to the Trash Can.
EN-92690 Planning interface: Issues can be created with the same name as an existing Issue.
EN-92817 When deleting Routing Rules in a copied Brand, the Routing Rule in the source Brand are also deleted.
EN-92820 Assets Server integration: Mismatch in file names between Studio Server and Assets Server when adding a file which already exists in Assets Server.
EN-92885 Studio: Metadata is not inherited when creating a Print variant of a Digital article.
EN-92920 Studio: When creating a Digital article together with a Dossier, the selected Issue is not assigned to the article.
EN-93061 MadeToPrint: Health Check test incorrectly reports an error for the Axaio configuration in Studio Server.
EN-93069 MadeToPrint: Creation of a MadeToPrint Job fails for a layout when the layout does not have an Edition assigned.
EN-93073 MadeToPrint: Health Check test does not show an error when the database tables are not yet initialized for the MadeToPrint plug-in.
EN-93107 Planning interface and Studio do not block duplicate layout names in the same Issue.
EN-93111 Assets Server integration: Separate the 'Archive after (days)' archive option for print and digital.
EN-93112 Assets Server integration: Separate the 'Archive Zone' option for print and digital.
EN-93130 Maintenance pages: Add the option to navigate by breadcrumbs.
EN-93142 MySQL: dbmodeldiff.php does not work for MySQL 8 nor for database models of server plug-ins.
EN-93229 Security: The ID parameter of hpusers.php is vulnerable to cross-site scripting.
EN-93233 Studio: When creating a Print variant of a Digital article, the Route To field is not filled.
EN-93278 Maintenance pages: After creating a new Named Query and refreshing the Overview of Named Queries page, the Named Queries page appears again.
Installation
- Full installation. For information about installing Studio Server on a system on which Studio Server is not yet installed, see Studio Server full installation.
- Upgrading. For information about upgrading, see Upgrading Enterprise Server to Studio Server 10.10 or higher.
Studio Server 10.10.0 build 321 Quick Patch
Studio Server version 10.10.0 build 321
Release date: 21 October 2020
Downloads
The download files for this version of Studio Server can be found in the Release announcement.
Fixed issues
The following issue has been fixed in this release of Studio Server:
EN-93538 Requests by Studio during log on results in a large database load and performance issues.
Additional info: When a user logs in to Studio, a request is sent to Studio Server for the number of items that are checked out by that user, as well as a request for the number of items in the inbox of the user. When the user has access to many Brands and objects, this can result in a large load on the database. When many such users log on at the same time, the stability of the system can be affected.
Installation
- Installing Studio Server on a system on which it is not yet installed. See Studio Server full installation.
- Upgrading an existing installation of Studio Server. See Upgrading an existing installation of Studio Server.
- Upgrading from Enterprise Server. See Upgrading Enterprise Server to Studio Server 10.10 or higher.
Studio Server 10.10.0
Studio Server 10.10.0 build 311
Studio Solr Integration 10.10.0 build 311
Studio Proxy for SC Integration 1.2.0 build 10
Studio CopyWithPlacements Integration 10.10.0 build 311
Release date: 19 May 2020
Downloads
The download files for this version of Studio Server can be found in the Release announcement.
New features
No features have been added in this release of Studio Server.
Changes
Studio Server 10.10 is based on Enterprise Server 10.9 and is technically the same. Apart from re-branding it by changing logos and product name references at various places, no additional changes have been made.
Note: References to Enterprise, Smart Connection, and Content Station are still present in configuration options, folder names, and so on. These will be updated in a future release.
Documentation
Documentation for Studio Server is available on Help Center:
Note: Some screenshots in the product documentation may still show Enterprise Server. This will be updated over the coming weeks.
Known issues
No known issues exist for this release of Studio Server.
Fixed issues
No issues have been fixed in this release of Studio Server.
Installation
- Full installation. For information about installing Studio Server on a system on which Studio Server is not yet installed, see Studio Server full installation.
- Upgrading. For information about upgrading Enterprise Server to Studio Server, see Upgrading Enterprise Server to Studio Server 10.10 or higher.
Versions 10.9.0 and lower
For versions 10.9.0 and lower, see the Release Notes for Enterprise Server 10.
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.