Hot answers tagged

7

The first issue clearly states that the custom models and views have not been registered with DXA. You'd have to create a class that extends AbstractModuleInitializer and register all views and custom entity models. For your setup you should have something like this: @Component @Configuration @ComponentScan("com.sdl.dxa") public class ...


6

You don't need any separate configuration for that. In DXA there is a container called Localization to store the requested Publication information. You can retrieve the publication id from that localization. Use the below line to get the publication id from your code WebRequestContext.Localization.Id For more information about the localization you can ...


5

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 losing the CPs. In Sites 9.1, this was improved upon by expanding on the synchronization methods to cover those scenarios. Additionally, the CME ...


5

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 DXA website is started, it downloads (caches) said jsons into the Binary Data folder. See also DXA Json files | Who is what Now the issue might be ...


5

No, not really, but besides modifying the package that you already did or tried, you can do second sort of hack. You can export from 100 Example Master then temporarily rename it to maybe 100 Example Master TEMP then you do import (it will import publication as 100 Example Master and you rename it to 100 Master). And finally, you revert the name for the ...


5

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 achieve the same thing by adding non-nested fields into the Region Schema (representing the Page Schema). Both options comes in Razor view back as dictionary e.a. @...


5

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


5

We reviewed the customer setup and we saw following error - Unable to get response from OData service: Bad Request. on the content service We reviewed the configuration and we found the discovery service and token service endpoint was not https. after we changed the protocol from http to https the issue was fixed. I would like to share so this will help ...


4

After some further debugging we found that few DCPs stored in broker database has no content(Empty value) and leads to the know issue with DXA 2.2 here https://gateway.sdl.com/apex/communityknowledge?articleName=000011590.


4

As the json file is updated I assume you did a publish of the 'Publish Settings' Page. Afterwards, you need to call the Admin Refresh endpoint /admin/refresh so that the website loads the new value. You do that by loading the {WebsiteBaseUrl}/admin/refresh url in your browser, where WebsiteBaseUrl is the url of your website.


4

I see quite a bit of confusion around the difference between PageModel.Meta and custom Page Models w.r.t. mapping Page Metadata. Indeed, PageModel.Meta can be used as “poor man’s semantic mapping”, but it is originally intended to be used to generate HTML meta tags in the rendered output. By default, it contains some metadata for Facebook (OpenGraph) and ...


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 ...


4

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 virtual so you can override it. Truth be told, it would be better to have direct control over just the location :)


3

AFAIK - In the DXA Java 2.2.5, A few dependency jars are missing in Maven, and also XpmRegionConfigImpl class has an initialization error for XpmRegionImpl It was missed in the maven version. Try following steps to get prepared to use the DXA Java 2.2.5 Ensure Java and maven installed as prerequisites as per SDL docs supported versions Run the below command ...


3

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 resolveLink() method expects the ID of the Component it's supposed to resolve. In your code, you are giving it the Publication ID. One other thing which should be ...


3

DXA 2.2 .NET + Core and Search Module Solution build/configuration Download the following OOTB sources and modules from GitHub: https://github.com/sdl/dxa-web-application-dotnet/tree/release/2.2 https://github.com/sdl/dxa-modules/tree/release/2.2 Extract both sources zip and Go to dxa-modules-release-2.2\webapp-net this folder and copy Core and Search ...


3

Taking your questions one by one: DXA web application cannot publish to filesystem. Is that right? In general, the pages served by a DXA application are not "published to the file system", however binary assets can be published to Tridion Content Delivery, and are then available via the services. This is how your configuration settings are managed, ...


3

Indeed, In DXA 2.2.8 and 2.2.9, some of the jars are not pushed to maven, It does not have a real fix just a refactoring and conflicts. You can go for DXA 2.2.5, I have answered the steps to prepare DXA 2.2.5 version from Maven, I have tested that version with 9.5 OOTB it's working fine as expected. I have raised this to the engineering team to fix the ...


3

Region and Entity Views primarily work on Region and Entity Models, respectively. However, both have access to the entire context Page Model through the WebRequestContext.PageModel property.


3

I have used Tridion to publish CSS and JavaScript many times in the past. Please keep in mind that every implementation is different. What I've done may not work with what you've done. Code Component + Page template The most common approach is a "Code Component" which is a Tridion schema with a single plain-text field that's set to 20 - 30 rows. ...


3

Frankly, I don’t fully understand all of your questions nor requirements, but let me clarify some things: Semantic mapping does not presume any field names; field names are either derived from the View Model property names or explicitly specified in [SemanticProperty] annotations. So, your statement “other XML names than internalLink doesn’t work” is ...


3

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.


3

@Rick gives the context on why Experience Manager has the context setting. I'll add a little more at the end of this answer. Except for shared items that are owned in the same "context" Publication setting, the "regular" BluePrinting rules do apply for localized items. So though the setting mentions XPM will read from the configured ...


3

It turns out that CMS side of DXA 2.2 for SDL Web 8.5 has a bug (or incompatibility with Java DXA 2.2 side) which is causing values of Schemas to be generated as a List<RichTextData> instead of List<String> in the ExtensionData of the JSON page model. As in our case, InheritMetadataPageModelBuilderi is using the method GetTypedArrayOfValues which ...


2

AFAIK - It's a known issue. Please refer to the below link for more information. I vaguely remember I think it was fixed in one of the versions. https://gateway.sdl.com/apex/communityknowledge?articleName=Adding-a-new-region-should-not-affect-other-existing-region-contents-in-that-page https://docs.sdl.com/792149/750845/sdl-tridion-sites-9/known-issues-in-...


2

It does look like you reached the configured expansion depth. If you debug the template in Template Builder (with Debug logging enabled), you will get more insight in why Entity Models are not expanded. Note that there is a third place where link expansion depth can be configured: in the “Generate Data Presentation” TBB. Furthermore, your implementation may ...


2

If you map a Component Link field to a property of type string, the semantic mapping will use the resolved link URL which is injected in the DXA R2 Data Model by the DXA Model Service/Extension. Unfortunately, this part of link resolving is not customizable. However, if you map a Component Link field to an Entity Model, you will have access to the underlying ...


2

Publishing binaries to a Structure Group rather than the standard Multimedia location is supported in Tridion Sites since ages, but not in DXA (OOTB). Unfortunately, that is still the case for DXA 2.2. Upgrading to DXA 2.2 can be done according to the documentation: https://docs.sdl.com/784837/756547/sdl-digital-experience-accelerator-2-2/upgrading-----------...


2

Settting expandLinkDepth 2->3 fixed it. \100 Master\Building Blocks\Framework\Developer\Templates\DXA.R2\Render Page Content


2

Your data looks a lot like DXA R2 JSON, so I assume you’re using DXA (TBBs at least)? It also looks like the Categories are marked as publishable, in which case the TBBs will only include the Keyword IDs; the DXA Model Extension should take care of dynamically retrieving and expanding the Keyword Data.


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