Known issues in Content Delivery

The following list describes issues that are known to exist in Content Delivery.

Dynamic Linking
  • Link attributes such as titles and target, specified in a Component Link field in Content Manager Explorer, do not end up in the dynamic link on the published Web page.
User-Generated Content (UGC)
UGC requires you to set up two separate Content Delivery Web services, one for visitors and one for moderators. However, at the time of release, the Claim Processor called PostAllowedByOwnerClaimProcessor, intended for moderators, did not function properly. A hotfix for this issue is forthcoming. Contact SDL Custom Support for details.
Dynamic Content Delivery
The following call:
Server.CreateObject("cd_wai.ComponentPresentationAssembler")

may produce the following error:

Server object error: 'ASP 0178 : 80070005'
Server.CreateObject Access Error
The call to Server.CreateObject failed while checking permissions. Access is denied to this object.
To resolve this problem, follow the instructions in the following Microsoft Knowledge Base Article: http://support.microsoft.com/kb/278013/
Publishing fails if the name of the Transport Package contains the string "66560"

If your publish action involves 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 does not expect a transaction ID containing the string and as a result, publishing fails.

If this problem occurs, you can work around it by republishing the content that failed to publish separately. It will get a different transaction ID and publish successfully.