Search Results

In normal cases (and in the example website), the Publish Settings in DXA will result in a [ModuleName].schemas.json and [ModuleName].templates.json inside of "/system/config/" folder, but this only h …

You don't need to follow the reference implementation, it's just an example website, though it has some good examples and scenarios which can be recycled. DXA is MVC in essence, so every design princi …

To get the add, remove, reorder functionality for multivalue properties, you must use the DxaPropertyMarkup method with an index. For multivalue "embedded properties", this should wrap all individual …

You need to use the InheritMetadataPageModelBuilder in your Model Builder Pipeline. In your case, the pipeline is a parameter of the Render Page Content TBB. See here

A bit simplified, but, when you publish the Publish Settings Page, it goes through all your active "Module Configuration" Components and creates a binary for them which end up in the broker. Once the …

Caching in DXA works great for simple use cases but can quickly get very complicated if you have exotic scenarios. I myself have spent a lot of time getting familiar with how it works in detail and tr …

Unfortunately this is the "normal" behavior in Sites 9. Changing the Page Schema or Region Schemas and opening already existing pages in the CME results in "regenerating" the Regions, which means losi …

OOTB you can't. Inside the app you will just have the viewmodel as an object with no reference to the Schema. From the websites perspective it (the schema) is totally irrelevant, it's a CM concept. Yo …

I can only give you the answer in .NET (because I haven't worked with DXA Java still), but I'm certain that the same or a very similar approach should be used. The bigger mistake is that the resolveLi …

You are correct in those two approaches, but there is something worth mentioning. For the 'Use this Page Schema as Metadata Schema' approach you don't have to use an Embeddable Schema, you could achie …

Why do you think the application will break with size increase of the config file? I'd seen huuuuge files and the module continued working with no issues at all. As for the urls and rules, personally …

Short answer: because your Include Page itself is "transformed" into a Region (along with its nested Regions and their CPs). There is no way around this.

The location is hardcoded within DXA's source code. Take a look at the PageController's NotFound method. string notFoundPageUrl = WebRequestContext.Localization.Path + "/error-404"; The method is vir …

IIRC start the names of the items (Pages and SGs) with an underscore _. Then do the required actions to regenerate the sitemap. The DXA templating code is available on GitHub so feel free to look thro …

The official documentation explains the link resolving algorithm quite detaily, however our testing showed that the proximity resolving doesn’t work like described. Instead, we see the resolving start …