1

I have a DXA 2.1 application that uses elastic search module. The module stores the tcm id of an image and an internal link to a component on another page.

Using this page, Handling an image in a Multimedia Component

I used all three methods described there but my images are not being rendered as expected. given a tcm id, how can I resolve to images and internal component links?

Improve this question
3
  • What is the “Elastic Search Module” you are referring to, exactly?
    – Rick Pannekoek
    Jun 28, 2019 at 7:21
  • The documentation topic you refer to is about old-style (CM-side) templating. DXA uses a Dynamic Delivery architecture, where CM-side templates render raw data (JSON) and the “real templating” (rendering) is done on Delivery side (in your MVC Web Application).
    – Rick Pannekoek
    Jun 28, 2019 at 7:24
  • @RickPannekoek the elastic search module I'm referring to is si4t search module using elastic search. Elastic search stores the tcm id of images and links currently but when I perform a search I need to be able to resolve those links and display the content appropriately. Is there a way to use the tcm id to be able to display images and link resolve components?
    – Michael Poblacion
    Jun 28, 2019 at 12:57

1 Answer 1

Reset to default
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-event-presentation-si4t-based-elasticsearch-integration-for-sdl-tridion-web-8-with-dxa-2-0/

Or is that maybe what you are referring to?

Do I understand correctly that your problem lies in embedded images and Component Links in the search results? So, you want to post-process the Search results to resolve Component Links?

In general, the DXA Framework provides a Link Resolver for the purpose of resolving Component Links (to either a published page containing the Component or the published binary data of a MM Component).

Improve this answer
1
  • Thank you! The link resolver reference you shared solved my issue. I am indeed using the DXA Search module with a custom elastic search extension.
    – Michael Poblacion
    Jun 28, 2019 at 16:26

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.