rename your existing publications,
perform the install and then
bearing in mind you will need to account for Blueprinting, you can integrate the contents of organizational items as best suits your needs.
I just got reminded I had some problems with this a while back, have a glance here too: TRI Import.ps1 fails for websites-only
Also, Bart had ...
The cms-import.ps1 script has parameters for dealing with this problem. There's a very good reason why a script is provided to deal with the import rather than a compiled programme: you can read the script yourself. So for example at line 81, you can see how they use the parameters to create a base webdav URL.
$WebDavUrl = "/webdav/$masterPublication/$...
InputSortParam inputSortParam = new InputSortParam();
this fixed the problem. based on error i figured out both fields order and sortBy on are required InputSortParam.
The DXA 2.2 Dynamic Documentation Module (for .NET and Java) will be released later (expected soon).
Try enabling these following properties in dxa.properties file
#adf.context.provider - Activates ADF instead of Context Service for context claims.
ADF is needed for XPM Session Preview, Experience Optimization and Context Expressions. Values: [true, false]:
I do not think you can upgrade directly from Tridion 2013 SP1 to Site 9.1, the documentation states the following;
"If you perform a non-rolling upgrade, you can upgrade to the current
version of SDL Tridion Sites (formerly called SDL Web or SDL Tridion)
from the following versions: SDL Tridion Sites 9 SDL Web 8.5
What I have done in the past was to ...
Standard DXA TBBs do publish binaries (you can check in Template Builder, in the CME preview or by intercepting a Transport Package).
However, DXA assumes that your Deployer is configured to deploy binaries to the CD Content Store (aka Broker Database). If you say you don’t see anything in the DB, I guess that is your problem.
Try following to troubleshooting.
First, check that your website domain URL mapping URLs exist in the discovery database or not? by using postman http://localhost:8082/discovery.svc/PublicationMappings, in case if you looking for how to access postman to explore SDL microservices
Could be Discovery Service out-of-sync with Topology Manager then you can ...
It was config issue from my side I did placed the the DD Module builder pipeline in the last.
<add type="Sdl.Web.Modules.DynamicDocumentation.Mapping.ModelBuilder, Sdl.Web.Modules.DynamicDocumentation" />
Important to note:
In the modelBuilderPipeline section, add the Dynamic Documentation model builder to the pipeline, ...
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)
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 ...
I think you’re suffering from this Known Issue: https://docs.sdl.com/LiveContent/content/en-US/SDL%20DXA-v12/GUID-069E6E6E-7296-4E79-BF75-E3729BC915C8
See also https://docs.sdl.com/LiveContent/content/en-US/SDL%20DXA-v12/GUID-E709D04C-36D8-4666-A9D6-A1759C162FF3
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 ...
The DXA Framework itself doesn't use these configuration files, but Module implementation may.
For example, the Core Module's ContentList View Model uses it to map a Schema name to ID (used to do a Broker Query). See https://github.com/sdl/dxa-modules/blob/master/webapp-net/Core/Models/Entity/ContentList.cs
In general, DXA expects that on CM side, all ...
The difference between DXA 2.2 and 2.0 on CM side is mainly in the TBBs and associated parameter schemas (and the resolver).
So, your idea to just upload the DXA 2.2 TBBs would get you quite far. But, in general, DXA CM-side is more than only the TBBs, of course. To be on the safe side, it’s best to import/upgrade all items from the framework-only package.
You can find the Spring MVC version in the (parent) POM of the DXA Web application.
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 ...
Link resolving using proximity logic was indeed implemented in DXA 2.2.
In particular: it was implemented in the DXA 2.2 Model Service and the DXA Model Extension for the GraphQL Content Service.
If you’re using the 9.0 GraphQL Content Service, you have to ensure you deploy the DXA Model Extension which ships with the DXA 2.2 distribution.
If you’re using ...
I was getting issues because i was not using dynamic documentation module here,
And this is Tridion docs implementation so after addition ofdynamic documentation moduler and update of few references to dynamic documentation module classes now I am able to get the pagemodel object.
After investigating I found out udp-discovery-client-lightweight:11.1.0-1063 api is trying to find default ehcache file with name : ehcache-default.xml.
In order to fix exception on console, i have renamed dxa-ehcache.xml to ehcache-default.xml
and on dxa.properties also updated the reference for key dxa.caching.configuration
from dxa-ehcache.xml to ...
I was able to fix this problem by updating jackson apis to version 2.10.0, previously it was refering to version 2.8.10
jacksonversion = '2.10.0'
When I resolved another issue this problem was resolved as well.
It seams my images was published all the time in original format. But when I saw that the image variants was missing in the website I thought the renditions should be created by TBBs at publishing time. Now I believe they are generated at runtime. For some reason they couldn't be generated due ...
It seems that the DXA 2.2 resolver is built against SDL Tridion Sites 9.0 API, so it can’t be loaded on a SDL Web 8.5 system.
Frankly, I’m flabbergasted, because I’m quite sure that DXA 2.2 has been tested against SDL Web 8.5.
This should be reported as a DXA 2.2 defect.
It should be possible to work around this issue by putting assembly binding redirects ...
You could indeed use -importType master-only, but this is intended for importing DXA Core Items (excl. the Example Site) into an existing BluePrint (or upgrading).
If you want to import the entire DXA BluePrint (incl. example Publications) into a system which happens to already have Publications with same names, but you don’t want to import into that ...
The solution I mentioned in the question seems to be the answer. I have created a pull request in order to introduce the fix and potentially get hotfix out of it.