I am oversimplifying... but here's what applies to Tridion.
Basic Tridion (since 1999) is a decoupled CMS (Content Management and Website/Delivery are separate applications that can run completely isolated from each other)
Headless CMS is one where the Delivery of content for a website is done over webservices and there is no "CMS logic" inside ...
WebRequestContext.Localization is indeed the context Localization/Publication per definition.
However, you can obtain other Localizations using SiteConfiguration.LocalizationResolver.GetLocalization(); it takes the Localization ID (i.e. the first number from the TCM URI) as input.
You can then pass in the obtained Localization object to the GetEntityModel ...
DXA is built on top of DD4T, so the underlying APIs are the same. We should be able to use the standard Content Delivery API to get DCPs. Using the ComponentPresentationAssembler class and passing the publication ID in the constructor, we should be able to get DCPs based on publications. Something like this should work:
@RickPannekoek: thank you very much for pointing out the problem area.
indeed deserialize is happening and post that order of list was correct. but post that json has been stored in cache for better performance. that is where the list is getting sorted.
as an workaround as of now we have commented the code so-that json has not stored in cache.
You already found yourself that use of “scale” is hard-coded in ContextualMediaHelper. But you can also see that it is a property, which is set with a hard-coded value in the constructor.
So, a custom MediaHelper can be very minimal: create a subclass of ContextualMediaHelper which only has a constructor which sets the ImageResizeUrlFormat to the desired ...
Version.json value managed in the CMS in the "HTML Design Configuration" component in this path 100 Master\Building Blocks\Settings\Core\Site Manager
And this component is used in Publish HTML Design page and got published to DXD using this TBB Publish HTML Design.
please note that when not publishing the HTML design you can provide the ...
I would recommend to align Schema namespace URIs across DTAP environments, regardless of DXA.
For DXA, it will only be required to do so if you are using retrofit mode for semantic mapping, because that uses the CM Schema's namespace URI as semantic Vocabulary ID (whereas regular mode uses a single "Core Vocabulary" for all CM Schemas).