Content Delivery issues resolved in SDL Web 8.5
Issues resolved in Content Delivery.
- Taxonomy Relation Manager .NET API class was not public
-
The Content Delivery RESTful .NET API contained a class Tridion.ContentDelivery.Taxonomies.TaxonomyRelationManager, but it was not public. This made certain development tasks difficult. The issue was resolved.
-
Setting log level to
TRACEaffected return value of an API method -
Ony with the log level set to
TRACE, the DynamicMappingsRetriever.GetPublicationMapping method returnednull. This issue was resolved. - Link resolving would stop working after a certain amount of time (several weeks)
-
An application pool recycle would be required as a workaround to keep link resolving working. This issue was resolved.
- Microservices would show in Windows as started Windows services, but would not actually be running
-
This issue was resolved.
- API method did not return correct value for multivalue fields
-
The method Tridion.ContentDelivery.Meta.CustomMeta.NameValues should return a comma-separated list of values when used with multivalue fields, but instead returned only the first value. This issue was resolved.
- Content Delivery Preview caused an error in Experience Manager as part of Update Preview
-
The error displayed was
The transaction under which this method call was executing was asynchronouosly aborted. This issue was resolved. -
Content Service failed to include a property in generated metadata for
BinaryVariant -
BinaryVariantdid not include aStructureGroupIdproperty in its metadata as generated by the Content Service. This issue was resolved. - In a setup with many Toplogy Manager Web site mappings, the Discovery Service returned an error during manual registration
-
Running the Java discovery-registration.jar tool in a setup with many mappings could yield the error
failed to lazily initialize a collection of role. This issue was resolved. -
The
CacheEventclass implements theSerializableinterface, but did not declare aserialVersionUIDvalue -
This omission violated the Java specification, as found at https://docs.oracle.com/javase/7/docs/platform/serialization/spec/class.html#5023. The issue was resolved; the class now has a
serialVersionUID. -
Content Service returned a 404 error if an attribute in a
tridion:ComponentLinkelement contained a space -
The spaces were erroneously resolved to the
+character rather than to the%20escape sequence. This issue was resolved. - Publishing failed if the name of the Transport Package contained the string "66560"
-
If your publish action involved a very large number of transactions, the Transport Package name may be something like tcm_0-66560-66560 or tcm_0-366560-66560. In a package with this name, there are two substrings "66560": one is (part of) the transaction ID, the other denotes the type of the transaction item. The Content Deployer did not expect a transaction ID containing the string and as a result, publishing failed. This issue is now resolved.
- Contextual Image Delivery did not support Capability discovery or OAuth
-
The Contextual Image Delivery service currently did not support Capability discovery or OAuth security. This issue was resolved.
-
The Preview Service URI required a machine name, not the string
localhost -
If you upgraded your Preview Service Server Role from a version older than SDL Web 8, referring to the service URI using
localhostwould no longer work, and you'd need to refer instead to the machine name. This is no longer an issue.