Hot answers tagged

6

AFAIK, ThreadAbortExceptions are quite common in ASP.NET. For example, if you terminate the HTTP processing pipeline using Response.End() (something that for example the StaticContentModule does in places), this results in the processing thread being aborted. Processing threads may also be aborted because of (idle) timeouts. So, in general, I wouldn't worry ...


6

You need to create multiple properties corresponding the allowed Schema. The Semantic Property for all allowed schemas should be same. It should look something like this. [SemanticProperty("Schema_Field")] public List<SchemaModelA> A{ get; set; } [SemanticProperty("Schema_Field")] public List<SchemaModelB> B{ get; set; } [SemanticProperty("...


6

In Visual Studio (project properties-->Web tab) you can configure the port used for IIS Express so it uses the same one each time, and depending on how your localizations are managed either add this port (and domain) in cd_dynamic_conf.xml or the topology manager to make sure that DXA understands which publication(s) this maps to.


6

Thanks to Rick's comment above we looked into our code. Somehow we pulled the wrong version of DXA (we were working on 1.1) when we added a custom area. After updating our code base to 1.5 and then adding our new Area, the issue went away. All versions of DXA are available on Github at https://github.com/sdl/dxa-web-application-dotnet


5

I guess you didn't add all the sources in that case, when looking at the VS project file (https://github.com/sdl/dxa-web-application-dotnet/blob/release/1.7/Sdl.Web.Common/Sdl.Web.Common.csproj) you see a reference to: <Compile Include="..\CommonAssemblyInfo.cs" /> Indicating that CommonAssemblyInfo.cs is located outside of the Sdl.Web.Common folder. ...


5

As Rick mentioned, you can implement support for multiple schemas in component link by creating your own abstract base class, from which your different model types will inherit. There are couple of caveats, so I am posting detailed step by step instructions here: Create Base class public abstract class BaseSchemaModelABC : EntityModel { public string ...


5

You can create separate View Model types for each Schema (ensure you have a proper semantic mappings to the Schemas on type level). If you want a property to be able to refer to multiple View Model types, just use a common base type. All your View Model types will have EntityModel as base type, so you could use that. However, it is more elegant (more ...


4

In DXA 2.0, using the new R2 Data Model and Model Service, link resolving is done in the Model Service. The Model Service uses the following class for this purpose: https://github.com/sdl/dxa-web-application-java/blob/master/dxa-framework/dxa-common/src/main/java/com/sdl/webapp/tridion/linking/AbstractLinkResolver.java Note that removal of file extension ...


4

The Page Controller is resolved through MVC Routing rather than through DXA View Model Registration. In order to use a custom Page Controller, you should change the "Tridion Page Route" in RegisterRoutes in Global.asax.cs. https://github.com/sdl/dxa-web-application-dotnet/blob/master/Site/Global.asax.cs Don't specify the third parameter in ...


4

After changing DXA configuration, like the HTML Design or items of it, you will always need to refresh the cache of the application, so it will load the updated configuration (from which the favicon is one). So start with calling the Admin controller refresh route (/admin/refresh) and then there might still be the issue of the browser caching the old ...


4

Offically, DXA v1.6 is the last version that will be supported and fully tested against SDL Tridion 2013 SP1. Bart covers this in detail in his Out with the old, in with the new post on the community site. In this post Bart outlines three options: Upgrade to SDL Web 8 Continue to use the fully supported and tested DXA 1.6 version with Tridion 2013 SP1 ...


4

The “default module” is a logical Module/Area name, not a class name. It is the name which is returned by your Module’s Area registration code (AreaName property). For example: https://github.com/sdl/dxa-modules/blob/master/webapp-net/Core/CoreAreaRegistration.cs


4

Finally, Found the culprit by doing the detailed TRACE logs analysis and fixed. It's because of below two items are not published from CMS. Sitemap [Navigation] - Categories and Keywords Generate Data Presentation - Dynamic Component Presentation (DCP)


3

It's not necessary to add the sources to your project, but you could use the *.pdb files. To get these pdb files, compile dxa from the sources in Github, and retrieve the pdb files from your bin folder. Then, in your actual web application, you can specify a new folder containing your pdb files for the dxa sources in the debug options (for a full ...


3

You need to change the Region metadata on your Component Templates to use your module region view. By default they are empty, which means they access the Core module Main region. After updating you will need to republish the pages which use these templates.


2

I haven't tried it yet for aspx code behind but you should be able to use WebRequestContext.Localization.GetConfigValue("YourConfig"). Please update here if you face any error in using that?


2

After a lot of digging, I made the following changes to the request object in ModelServiceCleint.cs Lines 162 and 163 were added. This time the request didn't timeout and I got the response back. Obviously, this is not a solution, but just isolating the root cause. There must be a performance issue on the DXA service side.


2

The issue was with some piece of DXA 1.8 code here if (localization.LastRefresh.CompareTo(lastPublishedDate) < 0) { //File has been modified since last application start but we don't care Log.Debug( "Binary with URL '{0}' is modified, but only since last application restart, ...


2

Unlike Structure Groups, Categories and Keywords don't have a URL of themselves. In order to simulate a Navigation Model built from Structure Groups, the following algorithm is used: If the Taxonomy Node (Keyword) has classified Pages and one of those Pages is an Index Page (i.e. has a URL ending with /index), the Taxonomy Node gets the URL of the Structure ...


2

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.


2

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


1

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


1

Your log file reveals that there is an HTTP Request directly to the Entity Action of your custom Entity Controller. That is not the way that Entity Controllers are normally used and no CM Model Mapping will occur in that manner. Entity Controllers are normally invoked as part of the Page rendering flow. You can let your custom Entity Controller inherit from ...


1

Do you actually observe caching issues, or are you just worried by these DEBUG messages? These messages are logged at line #215 here: https://github.com/sdl/dxa-web-application-dotnet/blob/release/1.5/Sdl.Web.Tridion/Mapping/DefaultProvider.cs As you can see, the caching happens in HttpContext.Items, so this is a very short-lived (request lifetime) cache ...


1

You might be running into similar issues as in this SO question, https://stackoverflow.com/questions/29005159/post-encodeuricomponent-query-string-internal-server-error-500


1

It also required to configure meta data of component templates and page template to use custom controllers. Also with the change of controller names you require to change the path of corresponding views. We can relate this with OTBut of the box DXA demo site, Component View's folder name is Entity as component templates are configured to work with ...


1

The DXA way of doing such thing is using Strongly Typed View Models and Semantic Mapping. Using a smart combination of these two, you might not need additional logic at all. In case you still need Schema-specific custom logic, you can test the type of the View Model (which maps to a CM Schema). The given code fragment is too small/isolated to give an ...


1

Note: For poor people like me. Setting can be found in "{model-service-path}/config/dxa.properties" dxa.web.link-resolver.remove-extension=false


1

I have seen a similar issue however for that case, the issue was resolved after replacing offending Media Manager images with older images, and then updating/republishing components with the most recent linked images.


1

The fact that EntityError.cshtml is not in Views\Shared OOTB can be considered a defect (quirk at least). Can you create an issue (and possibly also a Pull Request) on GitHub for that? Regarding putting those Views in your own Module/Area: what would be the reason to do that? What if you use multiple Modules which have those Views defined? Note that DXA 1....


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