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 ...
You don't need any separate configuration for that. In DXA there is a container called Localization to store the requested Publication information.
You can retrieve the publication id from that localization.
Use the below line to get the publication id from your code
For more information about the localization you can ...
By default, only MM Component links (incl. ECL Item links) in img elements in Rich Text Fields are processed by DXA.
However, as of DXA 2.2, this is configurable. See section “Embedding” in the What’s New for DXA 2.2
Note that the “Resolve ECL Items V2” TBB should not be used in DXA TBBs; DXA has built-in support for ECL.
No, not really, but besides modifying the package that you already did or tried, you can do second sort of hack. You can export from 100 Example Master then temporarily rename it to maybe 100 Example Master TEMP then you do import (it will import publication as 100 Example Master and you rename it to 100 Master). And finally, you revert the name for the ...
A bit simplified, but, when you publish the Publish Settings Page, it goes through all your active "Module Configuration" Components and creates a binary for them which end up in the broker. Once the DXA website is started, it downloads (caches) said jsons into the Binary Data folder. See also DXA Json files | Who is what
Now the issue might be ...
Unfortunately this is the "normal" behavior in Sites 9. Changing the Page Schema or Region Schemas and opening already existing pages in the CME results in "regenerating" the Regions, which means losing the CPs.
In Sites 9.1, this was improved upon by expanding on the synchronization methods to cover those scenarios. Additionally, the CME ...
You are correct in those two approaches, but there is something worth mentioning. For the 'Use this Page Schema as Metadata Schema' approach you don't have to use an Embeddable Schema, you could achieve the same thing by adding non-nested fields into the Region Schema (representing the Page Schema).
Both options comes in Razor view back as dictionary e.a. @...
We reviewed the customer setup and we saw following error - Unable to get response from OData service: Bad Request. on the content service
We reviewed the configuration and we found the discovery service and token service endpoint was not https. after we changed the protocol from http to https the issue was fixed.
I would like to share so this will help ...
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/$...
Answer to your questioon - Yes it's supported in sites 9.5, I did a test with sites 9.5 OOTB DXA 2.2 .NET and DXA 2.2.5 Java both working fine in sites 9.5.
DXA 2.2 in sites 9.0+ not required modelservice you can use DXA model extention.
In your case I would expect you need to upload this DXA Model extention in add-on service or load this extention in ...
I see quite a bit of confusion around the difference between PageModel.Meta and custom Page Models w.r.t. mapping Page Metadata.
Indeed, PageModel.Meta can be used as “poor man’s semantic mapping”, but it is originally intended to be used to generate HTML meta tags in the rendered output.
By default, it contains some metadata for Facebook (OpenGraph) and ...
Publication Key is a part of Publication metadata, it has no direct relation with the publishing content, so republishing of content wouldn't be required. For a DXA application, you probably need to republish Publish Settings page only.
AFIK it (changing) has no impact on import/export either.
However, do make sure to update any mappings in Topology Manager ...
The location is hardcoded within DXA's source code. Take a look at the PageController's NotFound method.
string notFoundPageUrl = WebRequestContext.Localization.Path + "/error-404";
The method is virtual so you can override it. Truth be told, it would be better to have direct control over just the location :)
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]:
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 ...
In general, CD Linking generates absolute URLs if you define Publication mappings in cd_link_conf.xml.
If you prefer server-relative URLs (which is often the case), you should not define any Publication elements in cd_link_conf.xml (Maybe it also works if you do define Publication elements, but no Host elements; never tried that).
I can only give you the answer in .NET (because I haven't worked with DXA Java still), but I'm certain that the same or a very similar approach should be used.
The bigger mistake is that the resolveLink() method expects the ID of the Component it's supposed to resolve. In your code, you are giving it the Publication ID.
One other thing which should be ...
DXA 2.2 .NET + Core and Search Module Solution build/configuration
Download the following OOTB sources and modules from GitHub:
Extract both sources zip and Go to dxa-modules-release-2.2\webapp-net this folder and copy Core and Search ...
Taking your questions one by one:
DXA web application cannot publish to filesystem. Is that right?
In general, the pages served by a DXA application are not "published to the file system", however binary assets can be published to Tridion Content Delivery, and are then available via the services. This is how your configuration settings are managed, ...
Please keep in mind that every implementation is different. What I've done may not work with what you've done.
Code Component + Page template
The most common approach is a "Code Component" which is a Tridion schema with a single plain-text field that's set to 20 - 30 rows. ...
Frankly, I don’t fully understand all of your questions nor requirements, but let me clarify some things:
Semantic mapping does not presume any field names; field names are either derived from the View Model property names or explicitly specified in [SemanticProperty] annotations. So, your statement “other XML names than internalLink doesn’t work” is ...
It turns out that CMS side of DXA 2.2 for SDL Web 8.5 has a bug (or incompatibility with Java DXA 2.2 side) which is causing values of Schemas to be generated as a List<RichTextData> instead of List<String> in the ExtensionData of the JSON page model.
As in our case, InheritMetadataPageModelBuilderi is using the method GetTypedArrayOfValues which ...
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 ...