9

Yes, there is. In the cd_link_conf.xml of the (Session-enabled) Content Service there is a OverrideDiscoveryService attribute. If you set that to true, the Content Service will switch back to old-style link resolving using the mappings defined in cd_link_conf.xml and if you don't define any mappings in there, you will get relative URLs. Unfortunately, the ...


4

You have a few options here that I can see, and probably a few more that I won't mention. (1) Application server URL rewrites (such as the IIS URL rewrite Pankaj mentioned). It's pretty powerful and will let you write all sorts of rules for this sort of thing. (2) Write your own resolver tag. You can read a bit more of the specifics here (written by Will ...


3

Did you have a look at the DXA Search Module? This Module provides SI4T-based Search functionality to a DXA-based Web Application. It comes with support for Solr and AWS CloudSearch OOTB, but allows adding other Search Providers. As a matter of fact, an ElasticSearch integration has also been created: https://velmuruganarjunan.wordpress.com/2018/09/10/tds-...


3

If the hyperlink is removed in the rendered output, that implies that the link could not be resolved using the CD Linking APIs. See https://github.com/sdl/dxa-web-application-dotnet/blob/master/Sdl.Web.Tridion/Mapping/DefaultRichTextProcessor.cs Unfortunately, there is no logging for this situation in DXA (yet), but the fact that the HTML anchor tag is ...


3

If all is well, Component Links within rich text are stored in CM as XLinks. That is: as an xlink:href attribute (instead of just href, which is normally used in XHTML). The DXA model mapping code automatically detects such XLinks and will resolve them to a Page URL (using CD Linking APIs), turning the XLink into a regular HTML hyperlink. See: https://...


3

In addition to Rick's correct answer... You can indeed use the OverrideDiscoveryService to get relative URLs. The default cd_link_conf.xml in the content, session and preview micro services contains the following comment which I found confusing. OverrideDiscoveryService - specifies whether OData discovery endpoint configuration should be overridden ...


3

You can specify additional inline elements (such as abbr) to accept in your rich text fields in the following configuration file on the Content Manager server: %TRIDION_HOME%\WebUI\Core\Controls\FormatArea\TcmXhtml\TcmXHTML.config For example:


2

I distinctly remember seeing this question before and the answer was that you would have to debug your custom deployer as this information is NOT stored by the regular Tridion deployer! I would first check to ensure that you are not overwriting the output of your custom deployer with output generated by a standard Tridion deployer (either due to ...


2

I'm not familiar with the details of the format that Tridion stores component link info on the file system, but if the configurations are the same on both, the working machine and the broken one, and yet the outputs formats are different, it could be an issue with the lib versions. Is it possible one of the machines is running an older version of some ...


2

To resolve your Tridion Component Links on the CM side you're on the right track: use the IdentifiableObject.GetUsingItems(UsingItemsFilter) method on the Component that you're linking to. You'll then need to: For the Pages returned, figure out which page to link to. If you want to mimic the Dynamic Linking algorithm then you'll need to do proximity logic ...


2

I guess I was too fast in posting the question but I was able to answer my own question. For those, who find them in the same situation, just read through this post carefully and implement a .net assembly. That will fix work for custom html tags as well. The solution is to create a .Net Assembly Which searches for such CSS background image patterns and ...


1

Link resolving using proximity logic was indeed implemented in DXA 2.2. In particular: it was implemented in the DXA 2.2 Model Service and the DXA Model Extension for the GraphQL Content Service. If you’re using the 9.0 GraphQL Content Service, you have to ensure you deploy the DXA Model Extension which ships with the DXA 2.2 distribution. If you’re using ...


1

In a TBB you can read component links as <a tridion:href="@@Component.Fields.xmlnameofComponentLinkField@@" target="_blank" title="This is my Component Link"> This is my Component Link </a> please go through this link once


Only top voted, non community-wiki answers of a minimum length are eligible