Content Manager Explorer issues resolved in SDL Web 8.5
Issues resolved in the Content Manager Explorer user interface.
- Single sign-on servers no longer need to be configured to exclude PNG files from authentication
-
A dynamically named PNG file needed to be authenticated and could therefore not be excluded by your single sign-on server. Because the file was dynamically named, any image with a PNG extension could not be excluded. This issue was fixed; PNG files can now be excluded by your SSO server.
- URL path segment (context URL) in Site Wizard could not contain spaces and also could not contain the escape sequence %20
-
A space character in the URL path segment as entered in Site Wizard created problems. Issue was resolved.
-
Uploading a non-image to a Multimedia Component produced an error:
HTTP 404: File not found, reverting to mimetype -
If a user uploaded a binary file that was not an image (for example, a PDF file) to a Multimedia Component, Content Manager Explorer would not display the icon for the file type, and instead give an error. This issue was resolved.
- Uploading a file to a Multimedia Component failed if its Multimedia Schema has a Workflow Process associated with it
-
Trying to upload a Multimedia Component based on a workflow-enabled Multimedia Schema yielded this error:
(80040356) Unable to create a new multimedia component from uploaded data The item is in Workflow.This issue was resolved.
- Mozilla Firefox 47 did not display the BluePrint tab of a Publication correctly.
-
The tab was empty. This issue was resolved.
- User without administration-level rights and with no access to a Publication could not add an item to a Bundle
-
A user with the rights described who tried to add an item to Bundle by opening a Component, selecting the Bundles tab and selecting Add to a Bundle, would see the following error:
(80040356) Unable to retrieve a list for item Object reference not set to an instance of an object.This issue was resolved.
- Administrator-level users could not see items checked out by other users
-
An architectural change caused this problem, which was resolved.