Hot answers tagged

7

I think the problem here is that the implicit semantic mapping "de-pluralizes" the name of a list-type property. So, a property called "items" implicitly maps to a CM field called "item". However, as visible in the schemas.json fragment you provided, your CM field is called "items" too. This means you will need an explicity semantic mapping: add a @...


7

The DXA Web App has to be configured for Category/Taxonomy-based navigation too; OOTB it uses a so-called Static Navigation Provider and for Taxonomy-based Navigation you need the Dynamic Navigation Provider. The Dynamic Navigation Provider looks for a published Taxonomy with [Navigation] in its title and if it doesn't find it, it falls back to SG-based ...


6

That EHCache uses a lot of memory makes sense, since when caching is turned on, it will use the configured amount of memory to store items. If you disable cache, be prepared to take a big performance hit. All models and items generated and fetched from the Tridion Broker database will always happen. Turning on the Tridion Object Cache will essentially move ...


4

For such URL to resolve, you have to ensure you have a Publication which maps to the Website root (you don't have to actually publish anything in that Publication, but just have a mapping in Topology Manager so a Localization can be resolved). Alternatively, you can change the redirect URL prefix in smarttarget_conf.xml so it matches the URL path of one of ...


4

Be sure to publish the 'Publish Settings' page. Then also access http://localhost:8080/admin/refresh to make sure the new internal .json files are up to date on the filesystem.


3

The DXA upgrade procedure is documented here: http://docs.sdl.com/LiveContent/content/en-US/SDL%20DXA-v7/GUID-7BBD251F-E5AB-4A40-B57A-51E3F7635C17 Admittedly, this is DXA 1.7 docs, but the procedure didn't really change in DXA 1.7; it just wasn't explicitly documented earlier.


3

Please take a look at the SDL docs for the new features Changes introduced in DXA 1.6. Looking at the core module seperation feature, there seems to be quite a bit of change in CMS side as well. Its always advisable to upgrade both CMS and webapp together. DXA CMS Import script is smart enough to identify the existing DXA versions in CMS and upgrade it. ...


3

The "Images URL" (a.k.a. "Multimedia URL") is supposed to be "under" the "Publication URL". The way you have it configured currently indeed results in images being resolved in context of the 500 Website Master Publication/Localization, because that is the only one where the Publication URL matches the URL of the images. So: you should set the "Images URL" ...


3

Although DXA supported upgrades since v1.1, the (simple) upgrade procedure was indeed not documented till DXA 1.7: http://docs.sdl.com/LiveContent/content/en-US/SDL%20DXA-v7/GUID-7BBD251F-E5AB-4A40-B57A-51E3F7635C17 DXA 1.6 introduced a better separation of Framework and Core Module and as part of that, a Framework subtree was introduced in CM. The cms-...


3

Despite your pictures, the structure of your View Models (and how they map to Components in CM) is not quite clear to me. For example: what does "Component as embedded field" mean? Do you mean you have an embedded View Model mapped to an embedded field? Regardless, it seems to me you want to get a link to Component B resolved. DXA link resolving will ...


3

After generating trace level log, I was able to identify that issue is because of the creating view model with default mapping. In Trace log it was showing error message: 05:56:16.770 [http-nio-8080-exec-2] TRACE c.s.w.c.i.mapping.SemanticMapperImpl - No match found for field: private java.util.List modelclass.items; registry semantics: [FieldSemantics(...


3

The settings are cached agressively in the DXA Web App. If you change/republish the settings, you either have to restart your DXA Web App or use the /admin/refresh URL to flush the cache. Furthermore, if you change the Images/Multimedia URL on your Publication, you will have to republish all Binaries (because their URLs change).


3

Yes, you can do that; we also do that on some of our test environments. You do have to ensure your machine has sufficient memory. Something like 16 GB.


3

Yes, but you can skip the step to install XO in your website/app; that is covered by the DXA XO Module installation. Yes.


3

DXA 1.6 provides basic support for HTML Forms. See http://docs.sdl.com/LiveContent/content/en-US/SDL%20DXA-v6/GUID-2C331449-7CF4-4031-8080-85B3F478F700 This support includes: Support for managing form text (labels, validation messages) in CM Support for doing server-side validation and View Model mapping of form fields Support for preventing CSRF attacks ...


2

I'm a bit surprised that you want to do a new DXA Installation on Production; I would expect items to be ported (using Content Porter) from a Test/Acceptance environment instead. Regardless, you can use cms-import.ps1 -importType master-only to import only the Core DXA Items into an existing Publication in your BluePrint. If you want the DXA Site Type ...


2

OK, let me walk you through the analysis of the artifacts you provided: The JSON reveals two issues: There is no XpmMetadata at all for the ST Region. That explains why Model.GetStartQueryMarkup is empty. This is unexpected, because XPM is enabled (as witnessed by XpmMetadata on some Entities furtheron). MaxItems is 0 whereas you would expect 3. The DXA ...


2

Yes! the DXA Framework is separated from basic but optional Views and View Models that were used in example implementation from DXA 1.6 onward. If you are installing it in CMS for your existing publication using the PowerShell script cms-import.ps1, then the script automatically detects the old folder structure and moves items to the new folder location for ...


2

Functionally speaking, if you say the list contains unexpected items, it sounds like you didn't properly specify the query for the list in CM. Technically speaking, the flow is as follows: You create a Component representing the dynamic list and the query to execute (currently not shown in your Question) You put it on a Page together with a CT which ...


2

Expansion of Component Links is done in DD4T TBBs (DXA 1.x) or the DXA Model Builders in DXA R2. Note that static (CM-side) expansion means that the data of the linked Component/Keyword is embedded in the data of the linking item; the linked Component/Keyword is not published as separate entity. DXA 2.0 can also do dynamic (CD-side) expansion, but I ...


1

Tracking the root of the issue is difficult but let us put out the scenarios so that you can narrow down the issue. In general, the DXA is just another web application and best practices to setup a web application on a server should still be followed. At a high level : Does the issue happen for all binaries (new vs changed vs unchanged)? The reason is ...


1

Although there are indeed a lot of moving parts to XPM, it should actually be quite simple to get it to work with DXA, because it has built-in support for XPM. As Nick mentioned, XPM is typically only enabled on “Staging” and DXA determines whether XPM should be enabled or not by checking whether the CD Environment has a Preview Service Capability (assuming ...


1

As Nick says, there could be lots of reasons why the XPM icon is not showing. If it were me, then I'd start by checking whether the Page Settings HTML comment and the XPM (a.k.a. SiteEdit) JavaScript tag appears in the source of the published page. For example: <!-- Page Settings: {"PageID":"tcm:9-259-64","PageModified":"2016-08-04T14:43:31","...


1

At the very basic surface, a Tridion system has 3 core nodes: CM, DXA Staging (Preview) web app, and DXA Live web app. XPM should be set up on the Staging web app, not the Live. So make sure you're hitting the Staging instance. If the above doesn't solve your issue, as far as what configurations you need to make, there is more than a handful of them. So it'...


1

Create a new Custom Build Manager extending default BuildManager (DD4T.Templates.Base.Builder).In this implementation, use your custom BinaryPublisher extendending default (DD4T.Templates.Base.Utils). In here, you can add or remove or override any additional methods from your base implementation as well (for your requirements) Create a new Custom ...


1

Three causes of this problem: 1. The field [Key] of keyword should be trainingeducation.specialOffer 2. Only custom metadata is available I was trying to render fields in my list view which are not available 3. In my listing model, foe example I used [SemanticProperty("s:dateCreated")], the content was not shown, but if I delete [s:] ([SemanticProperty("...


1

The cd_dynamic conf resolution happens during application start up. The CdConfigLocalizationResolver (Sdl.Web.Tridion) sorts publications by Path in descending order for / or empty. Based on this sorting logic, you may have to move the publication with an empty path to the last. Publishing will still work but DXA will not be able to resolve the images since "...


1

The DXA site navigation is documented here http://docs.sdl.com/LiveContent/content/en-US/SDL%20DXA-v6/GUID-4A757BE5-AED2-4AEE-B9A0-E2A1BEE30C49 There are two ways to implement navigation: Structure Group hierarchy (default) Taxonomy based (a Category and its Keyword hierarchy, which are published) You set the navigation type while installing the Web ...


1

The Personalization and Profiling functionality is considered legacy and is not available in the SDL Web 8 CIL API. You can use conditional Component Presentations based on Context Expressions using the DXA Context Expressions Module. You can also use Experience Optimization (a.k.a. SmartTarget) using the DXA Experience Optimization Module.


1

Looks like it was the Tomcat version that was cuasing the problem.


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