6

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 WebRequestContext.Localization.Id For more information about the localization you can ...


5

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


5

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


5

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


4

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 :)


4

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


3

Short answer: because your Include Page itself is "transformed" into a Region (along with its nested Regions and their CPs). There is no way around this.


3

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


3

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


3

Region and Entity Views primarily work on Region and Entity Models, respectively. However, both have access to the entire context Page Model through the WebRequestContext.PageModel property.


3

DXA 2.2 .NET + Core and Search Module Solution build/configuration Download the following OOTB sources and modules from GitHub: https://github.com/sdl/dxa-web-application-dotnet/tree/release/2.2 https://github.com/sdl/dxa-modules/tree/release/2.2 Extract both sources zip and Go to dxa-modules-release-2.2\webapp-net this folder and copy Core and Search ...


2

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" /> Documentation Indeed, Important to note: In the modelBuilderPipeline section, add the Dynamic Documentation model builder to the pipeline, ...


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

Settting expandLinkDepth 2->3 fixed it. \100 Master\Building Blocks\Framework\Developer\Templates\DXA.R2\Render Page Content


2

You can publish the rewrite.config to the broker and extend something like the URLRewrite.NET module to load the configuration from the database instead of the filesystem. The cool thing is that you can use it ahead of the DXA Static context module and before DXA starts processing the URLs. One thing to consider is how you are loading the config from the ...


1

We have come across a legacy solution which was maintaining URL redirects and rewrites in a component and publish that as a config file to the file system (you need to configure .config extension in the storage config to publish this to the file system). Here is an issue with this approach: The config file have it's limit (256 KB) as per Microsoft - so if ...


1

Please refer to the link from the documentation link If you still want to manage the redirection you can use the re-write module on IIS web config


1

I'll add a bit to address question 2: "What is the way to go to collect metadata at page level?" General (embedded) metadata schema is added to each page schema. Works OOTB. The metadata schema set at pages continues to work in Sites 9.5 for the classic UI, however in the (new) Experience Space UI, editors and their implementers are encouraged to ...


1

It seems that you want to implement a (multi-level) menu structure, based on the Navigation Model (navigation.json). DXA provides OOTB support for top-level navigation, context navigation (siblings of current Page) and breadcrumb navigation. These are methods of the built-in NavigationController which delegates building of the underlying View Model to the ...


1

It seems you want to map View Model property Artikel.ArticleBody (nice mix of Dutch and English, BTW) to a CM field called subsection. That is possible using a [SemanticProperty] annotation, but you currently only have one for the schema.org Vocabulary (which doesn’t define a type called “Artikel”, BTW), whereas you should use the Core Vocabulary for CM ...


1

Just add my comments. Answer to your first question: Yes SDL Tridion Sites - It's a Content Management Tool, not a CI/CD tool. Use to create the content and distribute the content in a headless way to your end-users. DXA is designed to help you more quickly create, design, and publish websites for content published from SDL Tridion Sites. As many Tridion ...


1

Simply being able to see the Business Process Type from a given publication ought not to be a problem. It's simply available from the blueprint, but you don't have to use it. You can select the Business Process Type you want to use in the publication properties. In any case, you may want to use the same Business Process Type for abc and cde. You probably ...


1

In theory, yes, you can use the Content Porter for this, as it does support mappings, but in practice, this would involve hand-crafting a mappings file, and you are already starting to see the difficulties in doing that. The approach of renaming publications has a long history. (Some of us call it "the webforms hack" because it was part of the ...


1

This issue is faced by other people including me while setting up DXA web application. Details on how to fix this issue can be found at https://github.com/sdl/dxa-web-application-dotnet/issues/33 . Please check that , I hope it would resolve the issue.


1

The DXA NuGet packages are indeed built against .NET FW 4.6.2, but you can use them in a .NET 4.7.2 (or even 4.8) Web App too. There is no need to compile the DXA Framework yourself against 4.7.2. The reason why DXA Framework typically isn’t compiled against the latest-greatest .NET Framework is that it is possible to use .NET assemblies compiled against ...


1

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


1

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. https://github.com/sdl/dxa-web-application-dotnet/pull/77


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