New answers tagged

1

The fact that the hyperlink is removed altogether indicates that the DXA Model Service/Extension did process/resolve the link, but link resolution didn’t provide results (i.e. the linked Component is not found on any published Page). In that case, the hyperlink is suppressed. So, all seems fine except that the link doesn’t resolve whereas you do expect it ...


1

Let me clarify, For the broker query nothing to do with model service, broker query will always go to content service only, one thing I will mention for performance always recommend to pass the SetResultFilter Limit the number of results, it will add in your query something like select top 50 based on your SearchCap value. Example: // Limit the amount of ...


4

Publication Key is a part of Publication metadata, it has no direct relation with the publishing content, so republishing of content wouldn't be required. For a DXA application, you probably need to republish Publish Settings page only. AFIK it (changing) has no impact on import/export either. However, do make sure to update any mappings in Topology Manager ...


2

As suggested, Support ticket is indeed required to correct this feature/issue. A possible workaround could be to resolve component links yourself in your application code. This can done as Alvin mentioned, using separate GraphQL queries (instead of relying on DXA Model Extension/Service). This would roughly translate to following steps for a DXA-based ...


1

As mentioned, do follow up with Support. For a little more context here is the GraphQL requests to render links documentation that describes how you can also use the contextData argument to control how links resolve. If you're managing or resolving the links yourself (e.g. in DXA or other application), the GraphQL requests to resolve links documentation ...


2

As Alvin correctly points out, there is not currently a componentPresentation root query that takes a page parameter. The nearest would be the items query, which when returning pages, can include the componentPresentations contained within that page, and they will have the associated page context in those results. E.g. { items(filter: {itemTypes: [PAGE], ...


1

We have come across a legacy solution which was maintaining URL redirects and rewrites in a component and publish that as a config file to the file system (you need to configure .config extension in the storage config to publish this to the file system). Here is an issue with this approach: The config file have it's limit (256 KB) as per Microsoft - so if ...


2

You can publish the rewrite.config to the broker and extend something like the URLRewrite.NET module to load the configuration from the database instead of the filesystem. The cool thing is that you can use it ahead of the DXA Static context module and before DXA starts processing the URLs. One thing to consider is how you are loading the config from the ...


5

Indeed, DXA Model Extension is currently not Open Source. That may well change in the future, though.


Top 50 recent answers are included