Hot answers tagged

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


6

Comparing the platforms features by features will not truly help to assess which platform is best suited for your company's project. What is more important is to list all your key requirements, KPIs, current challenges with Tridion and with your specific implementation of it, your corporate roadmap with detailed criteria and priorities or weighting system ...


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

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

Support for Scalable Vector Graphics was introduced in Tridion Sites 9.1: https://docs.sdl.com/816112/750876/sdl-tridion-sites-9-5/content-manager-explorer-and-experience-manager-functionality-introduced-in-------------sdl-tridion-sites-9-1


5

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


4

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


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


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


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

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


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

SAML implementation limitations SAML 2.0 only works with the browser-based clients, Content Manager Explorer and Experience Manager. It does not work with the desktop clients, Template Builder and Content Porter, nor with APIs. Such clients require another way of authentication (LDAP). It's mandatory to Configure Directory Service for search and add users ...


3

we don't have this out of the box , if you need to apply the extension you can download from this link


3

Well, from their official FAQ page, it requires DD4T. So you need to setup DD4T properly, and then build Dyndle on top of that. I might be mistaken, but Q will give you a definite answer.


2

The reason you get this error is because the page metadata schema in your Tridion 2011 SP2 was modified at some point in time after it was created. If you check the history on that metadata, you'd find the 'creator' metadata field removed at some point in time and 'metadata_title' added later. To fix this, you can use the CoreService API which has a ...


2

EmbeddedSchemaField.Values is a collection of ItemFields objects (one for each value). If you have an optional embedded field, it will initially not have any values, so indeed EmbeddedSchemaField.Values.Count = 0 You can add values to the collection, though: Schema embeddedSchema = ((EmbeddedSchemaFieldDefinition)embeddedField.Definition).EmbeddedSchema; ...


2

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


2

refer this link [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft.NETFramework\v4.0.30319]”SchUseStrongCrypto”=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft.NETFramework\v4.0.30319]”SchUseStrongCrypto”=dword:00000001 Hope it helps!


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

It looks like your region schema is having metadata which is why you are seeing it when you are adding a component to the region or during page creation. Can you open your region schema and refractor the metadata? Additionally, there is a hotfix from SDL for items having special characters in metadata that might be worth applying in your environment as well. ...


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

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

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

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

In general, there are 5 levels in the DXA example BluePrint: 000 Empty. The BluePrint root, Not really empty (it contains CM default items), but doesn’t contain anything DXA-specific and is merely there to facilitate future BluePrint changes. 100 Master. This contains the DXA Schemas, TBBs and settings (Components). In general, no “real” content. 110 Site ...


1

Where is BinaryData..\ used for (images, pages, content) ? The BinaryData folder structure is a FileSystem cache for so-called Static Content Items. That is: binaries, assets and configuration files (stored as Binary in the database). This file system cache results in much better performance and less load on the CD database. What load can we expect on ...


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