Other deprecated functionality in Content Manager
This topic lists miscellaneous Content Manager functionality deprecated in this release of SDL Web.
- SpellChecker feature
-
As of SDL Web 8.5, the SpellChecker features, which allows you to spell-check the textual content of your content items, has been deprecated.
-
Templating method
RenderComponentField() -
As of SDL Tridion 2013 SP1, the use of the
RenderComponentField()method has been deprecated in favor of theFieldStartMarkerandFieldEndMarkertags (to delimit a field), theFieldValueStartMarkerandFieldValueEndMarkertags (to delimit a value in a field), and theGetFieldValue()method (to get a specific field value). - LDAP
-
The following LDAP functionality has changed as of SDL Tridion 2011 SP1:
- Combined LDAP and Active Directory authentication
- SDL strongly recommends against authentication through LDAP and through Active Directory using a single machine. If you currently have such a setup running, submit a support ticket to SDL Customer Support.
- LDAP version 2
- Version 2 of LDAP is now no longer supported, in favor of LDAP v3.
- Core Service API
-
Your Core Service client connects to the Core Service through a specific service contract endpoint. The .NET assembly used by your client determines the service contract endpoint:
Service contract version number Supports endpoints introduced in Introduced in 2011 SDL Tridion 2011, SDL Tridion 2011 SP1 SDL Tridion 2011 SP1 2012 SDL Tridion 2011 SP1, SDL Tridion 2013 SDL Tridion 2013 2013 SDL Tridion 2011 SP1, SDL Tridion 2013, SDL Tridion 2013 SP1 SDL Tridion 2013 SP1 201501 SDL Tridion 2011 SP1, SDL Tridion 2013, SDL Tridion 2013 SP1, SDL Web 8 SDL Web 8 201603 SDL Tridion 2011 SP1, SDL Tridion 2013 SP1, SDL Web 8, SDL Web 8.5 SDL Web 8.5 If you upgrade from SDL Tridion 2011, the new Core Service API has the following impact on existing implementations:- Because the SDL Tridion 2011 SP1 endpoints are still supported, your existing 2011 service contract calls to the Core Service still work.
- Because the SDL Tridion 2011 endpoints are no longer supported, you must update and recompile code that uses the 2010 service contract.
- Write operations in Template code
-
The TOM.NET API is still functionally a read-only interface during rendering and publishing. That is, you cannot create, update or delete Content Manager items while your Template is executing. This behavior also applies to the now deprecated TOM API, meaning that if you have Templates that use the TOM API and perform write actions, these Templates will now fail.
If you do want your old TOM templates to be able to write to the Content Manager, you can configure the Content Manager to allow writing during rendering and publishing. SDL strongly recommends against this practice as it compromises your security. You enable Templates to write to the Content Manager as by opening the Content Manager configuration file Tridion.ContentManager.config (located in the config subfolder of the Content Manager root location), and adding an attribute
allowWriteOperationsInTemplates, set totrue, to the element calledtridion.contentmanager.security. - Avoid unmanaged binaries
-
Both the deprecated TOM API and the TOM.NET API have the possibility of rendering and publishing a binary resource without specifying a related Multimedia Component (either by omitting the parameter or explicitly setting it to
Nothingornull). SDL strongly recommends against this practice.