7

manifest.json file allows multiple extensions, so you could add resolvers for both Component and Page as separate entries. For example: manifest.json file with multiple extentions: "extensions": [ { "type": "CMResolver", "name": "AssetUnpublish", "...


5

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 ...


5

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 ...


4

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 9.0->9.1 9.1->9.5 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 ...


4

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 '...


3

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: ComponentPresentationAssembler ...


3

%TRIDION_HOME%bin\client Default location for %TRIDION_HOME$ is C:\Program Files (x86)\SDL\Tridion Sites\ But if you are using Tridion Sites 9.1 you should use latest V3 dll (in same folder)


3

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 ...


3

To answer my own question; SDL delivered a hotfix and it resolved the issue.


3

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 ...


3

Yes, it is possible, but only for CM side extensions. For CD, it's either the old way OR the add-on mechanism.


3

This is known issue. Please ask support for hotfix ECL_9.1.0.17684


3

As you can see @Nuno shared the official release notes of sdl documentation for good source. In High level listed out main functional and technical features of sites 9.0 and 9.1 Functional features Pre-defined Regions support Usability improvements for Component Presentations Blended marketing and product information from SDL Tridion Docs Image editing ...


2

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 ...


2

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 ...


2

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, ...


2

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.


2

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) https://gateway.sdl.com/CommunityKnowledge?articleName=000005260


2

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.


2

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 ...


2

@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.


2

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 ...


2

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 ...


2

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.


2

You can refer to ECL API reference for more details.Not sure if you can do this using core service.


2

It does look like you reached the configured expansion depth. If you debug the template in Template Builder (with Debug logging enabled), you will get more insight in why Entity Models are not expanded. Note that there is a third place where link expansion depth can be configured: in the “Generate Data Presentation” TBB. Furthermore, your implementation may ...


2

Please refer to this link for more details on how to Scheduling a periodic cleanup of the State Store database


2

As Alvin correctly points out, there is not currently a componentPresentation root query that takes a page parameter. The nearest would be the items query, which when returning pages, can include the componentPresentations contained within that page, and they will have the associated page context in those results. E.g. { items(filter: {itemTypes: [PAGE], ...


2

As suggested, Support ticket is indeed required to correct this feature/issue. A possible workaround could be to resolve component links yourself in your application code. This can done as Alvin mentioned, using separate GraphQL queries (instead of relying on DXA Model Extension/Service). This would roughly translate to following steps for a DXA-based ...


2

AFAIK - This error most likely still your certificate is not correctly exported and imported to configured your SSL Keystore file in microservice. Try this below PowerShell script to export the CA certificate and generate the Keystore file using the key tool. $thumbprintNumber="2F4463A65623BAA4E5CE83EB0B91F800B0CEF327" $certficateFilePath = "D:...


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