Hot answers tagged

7

The recommended way to achieve such dynamic, query-based page assembly in DXA is by creating a custom Controller. Unfortunately, DXA doesn't support custom Region Controllers yet, but you can create a custom Entity Controller (your own Controller class derived from EntityController). So, you would have to model the entire dynamic list of Entities (DCPs) as ...


7

No you don't have to use the Media Manager ECL Stub Schema provided as part of the DXA Media Manager Module, as long as you ensure that the Schema title is exactly the same (it's the default title for MM ECL Stub Schemas, assuming that the ID of your ECL Mount Point for Media Manager is mm). As of DXA 1.5, there are a few additional metadata fields defined ...


6

You need to create multiple properties corresponding the allowed Schema. The Semantic Property for all allowed schemas should be same. It should look something like this. [SemanticProperty("Schema_Field")] public List<SchemaModelA> A{ get; set; } [SemanticProperty("Schema_Field")] public List<SchemaModelB> B{ get; set; } [SemanticProperty("...


6

I think the problem is in the field name; the implicit mapping assumes that when a List-type property name is plural (e.g. buttons), the associated field name in CM is singular (e.g. button). It seems that in your case the CM field name is also plural and that is why you need an explicit mapping.


6

You are requesting http://10.9.5.175:8080 You have your BaseUrls set as http://localhost:8080 Add a Base URL of http://10.9.5.175:8080 You can add a BaseURL with the Powershell command (assuming your Website Id is 'Website1' and you want to keep localhost) Set-TtmWebsite -BaseUrls "http://localhost:8080", "http://10.9.5.175:8080" -Id Website1 You can ...


6

Thanks to Rick's comment above we looked into our code. Somehow we pulled the wrong version of DXA (we were working on 1.1) when we added a custom area. After updating our code base to 1.5 and then adding our new Area, the issue went away. All versions of DXA are available on Github at https://github.com/sdl/dxa-web-application-dotnet


6

This is browser specific Cache issue, Add "Vary: Accept" to the response header and try to replicate your issue. I had resolved similar issue with above setting.


5

DXA supports server-side responsiveness (e.g. image resizing) and uses (by default) the SDL Context Engine to get device data needed for that purpose. On SDL Web 8, DXA uses the Context Service to get access to the SDL Context Engine by default. It is also possible to configure it to get the context claims from ADF (which is used by default on 2013SP1). In ...


5

DXA follows the behavior that SDL Web (or Tridion if you will) delivers, when using an External URL in a Multimedia Component, at Publish time, the content of the External URL is fetched and published as a binary. So while this might not be what you expected or wanted, this is considered correct behavior at this time. The idea behind this is that the ...


5

In case of 404 exception DXA indeed resolves a page error-404 and shows it. Such a case is handled by @ExceptionHandler(NotFoundException.class) annotation in PageController. I don't see any way how to override it properly. Fortunately, you have MvcData and ability to write your custom PageBuilder. Make sure that your builder is executed after default one (...


5

As Bart says, DXA in general is designed to generate HTML, but in your case particularly the use of the dxa:region tag causes issues. You could let the Page View output the content from the "Code Component" directly. For example, to get direct access to the first Entity Model in the "MainBody" Region, you can use this in your Page View: pageModel.getRegions(...


5

Please check the following Please check the folder structure of context service installed with installation media (all files and folder) and see if there is anything is missing. Also check the system memory Try to increase the stack size of context service and re-install if possible


4

Region names are normally unqualified (e.g. just "Header" instead of "Toerisme:Header"). Furthermore, for include Pages, the (unqualified) Region Name and (qualified) Region View Name is derived from the Page Title. I see you're using qualified Region names in the dxa:regiom tag and in the PT metadata. Furthermore, you're predefining the Toerisme:Header ...


4

There is only one "problem" in your implementation, which the error message is pointing out: The type must be String or a subclass of EntityModel. In your case, you are using class EntityModel itself. Admittedly, this shouldn't be an issue in your implementation, since through semantic mapping it would always resolve a subclass anyways, so the check might ...


4

Apparently the VM's time was running slow, it was 5 minutes behind, so the token was already expired.


4

You have to ensure that your embedded View Models (class Link in this case) are also registered. See http://docs.sdl.com/LiveContent/content/en-US/SDL%20DXA-v5/GUID-FEDC295C-1D87-485E-B904-AE5596A4A802


4

You are not authenticating with the correct user. The various users have different roles, which in turn authorizes them to access different endpoints (URLs). As you are authenticating as the 'registration' user, you get an error when attempting to access the specific URL mentioned in the error. If you change to authenticate with a user with the 'cd' role ...


4

After changing DXA configuration, like the HTML Design or items of it, you will always need to refresh the cache of the application, so it will load the updated configuration (from which the favicon is one). So start with calling the Admin controller refresh route (/admin/refresh) and then there might still be the issue of the browser caching the old ...


4

As Rick mentioned, you can implement support for multiple schemas in component link by creating your own abstract base class, from which your different model types will inherit. There are couple of caveats, so I am posting detailed step by step instructions here: Create Base class public abstract class BaseSchemaModelABC : EntityModel { public string ...


4

You can create separate View Model types for each Schema (ensure you have a proper semantic mappings to the Schemas on type level). If you want a property to be able to refer to multiple View Model types, just use a common base type. All your View Model types will have EntityModel as base type, so you could use that. However, it is more elegant (more ...


4

On top of what Chris mentioned, you will find a list of API changes of all previous versions in the documentation of DXA 1.5 http://docs.sdl.com/LiveContent/content/en-US/SDL%20DXA-v5/GUID-7AAF6049-CAC4-4DA5-8128-3EDD4F0C9C50 Please also note that DXA 1.2 was the first Java version, so you will find quite a lot of changes in the project layout and source ...


4

You can follow the release notes, which are included in the documentation for each version 1.3 http://docs.sdl.com/LiveContent/content/en-US/SDL%20DXA-v3/GUID-D3920FCA-F021-4CC6-8ECF-0E7B31C5AC90 1.4 http://docs.sdl.com/LiveContent/content/en-US/SDL%20DXA-v4/GUID-D3920FCA-F021-4CC6-8ECF-0E7B31C5AC90 1.5 http://docs.sdl.com/LiveContent/content/en-US/SDL%...


4

SDL DXA, out of the box, has a PageController with the following Request Mapping @RequestMapping(value = "/**", produces = {MediaType.TEXT_HTML_VALUE, MediaType.ALL_VALUE}) This is handling ALL request, regardless of extension This could be updated to look like @RequestMapping(value = { "/**/*.jsp", "/**/*.html", "/**/*.txt", "/**/*.xml" }, method = { ...


4

A pdf is also a multimedia item except it doesn't render on any page like images. If you place url of any pdf on any link or anchor tag, on link click it will automatically download that pdf file. DXA cache these files inside media folder of BinaryData folder of corresponding publication. I believe you have published pdf components at structure group path ...


4

The Page View has access to the Page Model, which contains the Region Models, which in turn contain the Entity Models. That means that a Page View has direct access to al the Entity Models on the Page. For example, to access the first Article in the "Main" Region: var article = (Article) Model.Regions["Main"].Entities[0]. Theoretically, you could render ...


4

DXA expects multimedia files published in Database. You can see this instruction at SDL Docs Url http://docs.sdl.com/LiveContent/content/en-US/SDL%20DXA-v7/GUID-6D3337B6-FC47-479A-A38B-6AF3C53B9A51. DXA caches multimedia files to the file system inside BinaryData folder. So first time your multimedia files served from Broker database otherwise from file ...


4

As per best of my knowledge, there is no configuration available in the DXA framework to configure timeout of any request. You may do it using standard http request time out setting(code may vary for .Net and Java). To handle it in your application code you can create your own controller and write code to handle(throw 502 error) it. You can do timeout ...


4

It is a known issue that when you are trying to use empty Region views, you will get an additional <html>, <head> and <body> tag generated, see https://github.com/sdl/dxa-web-application-java/issues/5 So currently that simply isn't possible, as DXA is basically designed to generate HTML. The only quick option I could think of in solving ...


4

In SDL Web 8.x, using Topology Manager, DXA will check if XPM is enabled by checking the Discovery service. So, if you have registered the microservices needed for XPM for your specific purpose or not, it will enable/disable XPM by setting Staging to true or false. In Tridion 2013 (this is what you are using), it will check the Publication Target to which ...


4

The error is not specific to DXA; it occurs in the Ambient Data Framework. Looking at the Stack Trace, it seems that there is some claim with an unexpected type (HttpResponseStream ?!) which cannot be serialized by the JSON serializer used in the ADF. Did something change recently with regard to your ADF claims? It may be best to contact SDL Support to ...


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