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 ...
That seems like the template you are using to publish such page is not using the DD4T Template Building Blocks or the format it uses to generate the output is incorrect. Double check the TBBs within the page template for such page, chances are you are publishing JSON and DD4T MVC app is expecting XML or you are not even publishing JSON/XML (due to the ...
Rolling upgrades are only supported and tested from the previous point release. In this case it means that a rolling upgrade from 9.0 > 9.1 is supported and everything else isn’t.
So, in total, supported:
8.5 -> 9.0
From 8.5 to 9.1 you'll have to be creative and press on with the upgrade. The most viable route might be a staged upgrade ...
I had the same thing a while ago. It was caused by the command line argument '/closed' which I had added to the ilmerge call. This is described in the documentation (https://github.com/dotnet/ILMerge/blob/master/ilmerge-manual.md#26-closed).
In the documentation, they warn you that it's not an easy topic (but that is life). The way I understand it, in '...
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:
After some debugging, we finally found that the database server was provisioned in a different datacenter, causing some latency.
Since the discovery service is making a lot of database calls for one request (especially if you have a lot of publication mappings/websites), this latency (even very small latency) adds up and causes a long wait time.
Moving the ...
Watch this space Mr Williams. I checked this very question out at he Benelux user group and the answer was that it would ‘PROBABLY’ work for 8.5 to 9.1.
I expressed my concern should it be minor versions for the simple fact that most clients (and of course I’m excluding cloud clients here) are reluctant to upgrade to the first version of a new major (and ...
Remembering the Sites 9 Technical Readiness webinar, it was said that rolling upgrades will only be possible 1 "version" at a time. They didn't specify major or minor, but it makes sense that that "limitation" will apply to both.
In other words, you won't be able to directly upgrade to 9.1 (using the rolling approach), but instead will have to do 2 rolling ...
As far as I can say - It's unsupported - It's not been tested by the Engineering team and you are taking the risk.
Why you need Tridion 2013sp1 HTTP upload in sites 9.1?
The latest version of deployer services has been changed a lot and improved, since sites 9.0 onwards introduced to support multi namespace for both SDL Tridion Sites and SDL Tridion Docs, ...
Try the following steps to troubleshoot.
Ensure ContentServiceCapability registered with the discovery (DXA model extension works without configuration it's mandatory to register the ContentServiceCapability before content service restart, either install the service with auto-register or run the discovery registration and then restart the service, otherwise ...
AFAIK - Alchemy Installer - It is currently not supported in tridion sites 9.0+.
Anwer to your question
Q: Is there any way to install the Alchemy plugin without Alchemy?
A: No, Alchemy plugins wont work without Alchemy framework.
There is a possible hacky way to install Alchemy Installer in Sites 9.0 and 9.1 by your own risk.
The current Alchemy ...
After some more research, it turns out that a previous failed install was causing this problem.
The previous install had placed some files, but most likely not everything.
We were able to fix it by first uninstalling the failed installation, and then running the unattended install again.
I faced the similar issue recently and that was because of the content import (using content importer or using import export service). You can check if there is a content porting activity that happens just before Business Process Type is set to "None". If that is the case then make sure you exclude the BPT from the export package.
This happens ...
The DXA Container Framework was more or less abandon when the region concept was introduced in Sites 9.0. If there are still are some interests I could look into reviving the framework again and adapt it the region concept + upgrade it to DXA 2.2. It could potentially serve as a gap filler until user defined regions are available in Tridion Sites.
@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.
The error shown in the logs says 'could not locate the root of the configuration'.
Could this have anything to do with this (I know it's a different version, but the issue might still apply to 9.1)
Assuming you are just referring to the Dynamic Navigation capability in DXA: I vaguely remember that there was an issue in the CIL Taxonomy API that custom Keyword metadata was not returned and therefore this wasn’t exposed in DXA’s TaxonomyNode models.
We are talking years ago when we were working on the implementation of Dynamic Navigation in DXA 1.6 (on ...
Yes, in Tridion 9.1 we can still publish items to the file system.
In the cd_storage_conf.xml where the Discovery Service is installed, add the <Storage> element to publish files to the file system inside the <Storages> element like this:
<Storage Class="com.tridion.storage.filesystem.FSDAOFactory" Id="ascx" Type="...
Yes. It's possible to Configure Add-On Service on the Content Manager side to install the SDL Tridion Sites by scripted to install silently then it is required to pass
Indeed, The documentation it was missing, I will raise this internally to update the documentation, also left the comment in the documentation section.
User Defined Regions indeed seems to be a popular feature. See also SDL Ideas (ensure to leave a vote & comment there): https://community.sdl.com/ideas/sdl-tridion-dx-ideas/i/sdl-tridion-sites-ideas/allow-editors-to-insert-regions-into-a-page
It has been high on the prioritized list of candidate features for quite a while, but unfortunately not high ...
you can try to delete all configuration without parent item, Only the DefaultEnvironment should have no parent.
Query for the same would be like this.
""delete from CONFIGURATION_VALUE where ITEM_ID in (select ID from CONFIGURATION_ITEM where ID not in (select LINKED_ITEM_ID from CONFIGURATION_ITEMS_LINKS) and ID != 'DefaultEnvironment')
delete from ...
You can refer to the following document links for the configuration.
Adding Experience Optimization to your .NET API (RESTful) Role
Configuring a .NET website for Experience Optimization
Configuring Experience Optimization behavior with the smarttarget_conf file
AFAIK - SDL Tridion Sites 9.1 - you need to manually install the .Net framework 4.8 and .NET Core Runtime 2.2 manually prior to install.
Note: These pre-requisites not comes with SDL Tridion Sites installation media.
AFAIK - still old ELC provider supported in the same way as before. I'm not sure youtube connector available based on new Tridion Integration Framework.
For your reference, @Niclas created a nice blog about Developing connectors using the new Tridion Integration Framework.
I hope it helps.
As per DXA compatibility and support documentation, I can see DXA 1.8 supported in SDL Tridion Sites 9.0 For DXA .NET with CIL hotfix 10.1.1027.
Although CIL is backward compatible - I believe it will also work in SDL Tridion Sites 9.1, not sure and not tested.
I would recommend upgrading to DXA 2.2 to get used of GraphQL for content, Starting in DXA 2.0, ...
Please go through the link which give you clear idea about it