I like Harald's blog post (referred to by Nuno above). But note that the DXA import PowerShell script also supports importing into existing Publications (see the script's parameters).
Get-Help .\import.ps1 -detailed
Indeed, DXA model mapping doesn't support Page Links just like CM itself doesn't support that.
What you are suggesting (putting a Page TCM URI in a text field) is a bad idea in general; it is not a managed link and will give problems when you delete the referenced Page or when you port the item to another environment.
Content Manager (and DXA) assumes you ...
here's what docs say-
-The default Context Engine Cartridge installed as part of SDL Digital Experience Accelerator is used to detect device/browser screen features and capabilities.
-This information is used to manipulate page layout and image resizing and drive a reponsive design.
-This functionality is free to use without an SDL Mobile license, ...
I am assuming you have understanding of basic flow of DD4T based content model where Component Template is directly connected with component view and Page Template is directly connected with Page view in your MVC based application.
DXA 1.2 come up with a ready-made website solution in Java. If you setup the DXA website code and debug the whole application ...
Starting from version 1.2, the SDL Digital Experience Accelerator (DXA) provides support for Java, which unfortunately because of time contrainst did not come with Java modules yet (so indeed the modules are currently only available for DXA .NET).
https://github.com/sdl/dxa-modules/tree/master/webapp-java simply contains placeholders for the modules which ...
Your question is:
Is there some setting that we am missing which would overcome the above scenario?
The answer to that simply is:
Yes you missed setting up Session Preview, i.e. you deliberately disabled it for whatever reason. Without a working Session Preview, you will not see the up to date content on a Page after its content has been changed, ...
You're probably using Tomcat 7, which by default doesn't allow Java 1.7-specific stuff like diamond syntax.
It can be configured to allow it, though: http://censore.blogspot.nl/2015/04/how-to-set-tomcat-7-source-level-to.html
Fixed the above said null pointer issue by doing null check on Accept header. Changes needs to be done in DefaultDataFormatter's getHtmlAcceptScore() and BaseFormatter's getValidTypes(List<String> allowedTypes) operations.
Now Varnish cache is able to probe the application successfully. We do not need to change @RequestMapping or in Varnish cache now.
Your question is of very low quality, but I'll attempt an answer anyways.
First thing I think you should keep in mind is the way DXA is setup. DXA is an MVC application that uses view models, so we are not talking about Component anymore that you want to retrieve in your views. If you have set your Component Template to be a dynamic one, then from there on ...
Just checked the \400 Example Site\Building Blocks\Content\_Cloneable Content content, actually Article Component attached on the Page type is created itself in 400 Example Site. so you will get your new page's component created in 400 only.
if you create this component in master, you will get desired results.
It indeed seems that Page.LastPublishedDate is never set by DD4T Templates. DXA (currently) also has no OOTB model mapping for this property.
However, it is quite easy to obtain the last publish date using the CD API. Something like:
PageMetaFactory pageMetaFactory = new PageMetaFactory(Convert.ToInt32(localization.LocalizationId));
IPageMeta pageMeta = ...
As I commented on your original question already, I don't think an upgrade to a DXA 1.x version will solve the issue you are dealing with, since there haven't been that much changes in the DD4T template version we are using there, and the issue you see is something which originates from there.
Having said that, I should probably also mention that we are ...
In DXA 1.2, the OOTB Page Types and Content Types are defined in the 400 Example Site. XPM doesn't allow you to create the Pages/Components higher in the BluePrint than where the Page/Component Types are defined.
In DXA 1.3, the Page/Content Types are defined higher up in the BluePrint (in a new Site Type Publication), which makes them re-usable and also ...
For changing the cache settings, you need to look into the ehcache.xml of your web application. If you have Tridion object cache being turned on, you will have to look into the settings in your cd_storage.xml.
DXA 1.2 Java does not set cache headers as well for some browsers. See open issue HERE. It was resolved with 1.3 release.
Bart's comment was correct. I had named my schema field incorrectly. Quoting the manual:
When attempting to populate a property of type List, remove any
trailing s's from the property name. For example, the Paragraphs
property is mapped to Schema field paragraph.
So I modified my schema to rename the field to service, changed the model to remove the ...
Answer to the second Question (in Update 2; note that this is getting messy): no, it is not required to specify explicit semantic mappings on the CM-side (nor on the CD-side, BTW). There will always be an implicit mapping to semantic type [Schema Root Element Name] in the Core vocabulary.
Likewise, on the CD-side (i.e. on your View Model Types), there is ...
The first error in the error message (Unable to map field 'article' to property of type 'WFA.Web.Site.Models._Article') is something I'll come back on later, let's first discuss the second error (Unable to map field 'article_text' to property of type 'System.String'):
It mentions it is unable to map your RTF field to a string, which is correct since in DXA ...
Let's focus on the root cause of this error: "Cannot create an (instance of an) abstract class".
In the stack trace you can see that the exception occurs in DefaultRichTextProcessor line 116, where it calls Activator.CreateInstance. Let's check the source code: https://github.com/sdl/dxa-web-application-dotnet/blob/release/1.2/Sdl.Web.Tridion/Mapping/...
One idea would be to implement a 'soft' notification system where somebody could get notified if a Global Component is modified and also published in any site. (ie. it's ready for prime time). The publisher role would get a link to the staging item and component, and also their local page (with the outdated component). Maybe there is also a link in the ...
In general, if you need custom logic for how Page Models are constructed, I would recommend using a custom Page Controller (can be a subclass of Sdl.Web.Mvc.Controllers.PageController which overrides the Page method).
Creating a custom Content Provider requires you to use a non-public extension point which may change considerably between releases (as a ...
I have made a small fix to make .mp4 works as a partial content. In DXA Sdl.Web.Mvc.Statics.StaticContentModule.BeginRequest method, I have added the below couple of lines to make it work. after HttpResponse response = context.Response;
Note: I have made this ...
DXA decomposes TCM URIs; the ID of Entity Models correspond to the item reference ID of the TCM URI of the Component. In case of a DCP, the Entity Model ID is a combination of Component and Template ID.
Furthermore, you will find TCM URIs in the XpmMetadata but that is intended for (guess what?) XPM and not included on a Live environment.
Here’s an example ...
DXA JAVA depends on the CID and CWD. The dxa-parent pom, dxa-tridion-provider pom and DXA Tridion provider spring context in dxa-framework\dxa-tridion-provider\src\main\resources\META-INF\spring-context.xml have a dependency on the following libs.
By removing those dependencies (remove a line from the spring ...
I'm not sure if I fully get the question, but from what I understand it sounds like you have created two regions, where you only need a single one.
If you want to have the following content in a region:
Then I would create a LHS region allowing both the ArticleContent and the ...
You must check following:
In binarydata folder on your application, do you see your Schema details in schemas.json file. Binarydata folder is created at run time on root directory of your web application.
And your entity in Java project is annotated with Schema RootElement name, apart from properties mapping.
I have found the solution for the issue, Implemented in the generic way so that it would cater for all the scenarios and below is the code fix required. In the PageBuilderImpl.java is the class and the methodName processMetadataField(final Field field)
final String fieldName = field.getName();
FieldType fieldType = field.getFieldType();
406 happens when the server cannot respond with the accept-header specified in the request, so this definitely is a configuration issue.
As mentioned in the documentation (http://docs.sdl.com/LiveContent/content/en-US/SDL%20Web-v1/GUID-6A8C7A13-A652-4134-B93E-9AFED1A7DC22) you should set the Content Delivery Endpoint URL to the URL of the Experience Manager ...