The answer is yes, DXA does have plans to move to .NET Core, in line with the plans for SDL Web to move its APIs to .NET Core. These plans actually date back to February 2016 back when .NET Core 1.0 wasn't even released yet.
It seemed at that time we needed to wait for the CIL to be changed to be .NET Core compatible first, and then following that have DD4T ...
There is a component which is linked to in the HTML design component called build-files. It points to the Modules/Core/Admin/Build Files component. This component's zip file contains a gruntfile that defines exactly what grunt does on the presentation server. Specifically the gruntfile by default contains instructions to remove almost everything from the ...
The page model is available in an entity view though the WebRequestContext.
It is considered bad practice though to use page data in your entity view. It is code smell, sounds like the content model is not ideal.
The page metadata fields are available as well in PageModel.Meta.
If there is no XPM markup at all, it is very likely that the example website is thinking that you are not on a Staging website. When publishing the Settings, there is a flag published, so the Website can distinguish when it is running on staging and generate the XPM markup.
To generate this flag the TBB's rely on the publication target name. This means that ...
It turns out this is all to do with encoding.
In each microservice bin/start.sh script replace the JVM_OPTIONS with this:
JVM_OPTIONS="-Xrs -Xms256m -Xmx512m -Dorg.apache.tomcat.util.buf.UDecoder.ALLOW_ENCODED_SLASH=true -Dorg.apache.catalina.connector.CoyoteAdapter.ALLOW_BACKSLASH=true"
Restart Tomcat, the DXA site works and we are all happy again :)
SDL Tridion Docs (formerly Knowledge Center) has done something similar by adding a REST endpoint to DXA 1.8 to ...
I've seen an implementation DXA was set up to just be a JSON API. Vue.js was used as the templating framework.
XPM was dealt with by using .NET Core to render VueJS server-side (So XPM was accessing fully-rendered pages).
Webpack was used to bundle and transpile all the Vue.js code and helpers. The downside to this is that all of the state existed server-...
Interesting one - somehow the Sdl.Web.DD4T.Mapping.DD4TModelBuilder.GetCompLink(s) methods got removed, probably by some over-zealous code analysis which detected unused methods (as the only way they are called is by reflection). As the example models shipped with TRI do not use this (they always use String or Link types for linked content) it was never ...
I would start by asking what the benefit is of this technology change? Is it just that the client has a preference for these technologies? In which case I would use the same response as if a client asked me if they could create their Tridion driven website using PHP: You could, but is it worth the effort? And more importantly have you carefully considered ...
With the help of Harald, I figured out the issue.
So when your DXA Web Application starts and the first Web Request is made, DXA creates a Directory called "BinaryData" in the root of you application to hold the binaries used on the page.
So to create it, your Website Application Pool's Identity User Account (in my case Network Service) must have write ...
There are various optimization and checks you can do for performance in DXA
Enable DD4T caching.
<add key="CacheSettings_CallBackInterval" value="30" />
<add key="DD4T.CacheSettings.Page" value="3600" />
<add key="DD4T.CacheSettings.Component" value="3600" />
Outputcaching as you mentioned.
Make sure your binaries css, images, and js are ...
The recommended way to achieve such dynamic, query-based page assembly in DXA is by creating a custom Controller.
Unfortunately, DXA doesn't support custom Region Controllers yet, but you can create a custom Entity Controller (your own Controller class derived from EntityController).
So, you would have to model the entire dynamic list of Entities (DCPs) as ...
You can turn it back on in your Spring dispatcher servlet XML:
<!-- DD4T Provider beans -->
<bean id="binaryProvider" class="org.dd4t.providers.impl.BrokerBinaryProvider">
<property name="contentIsCompressed" value="true"/>
<property name="cacheProvider" ref="cacheProvider" />
Indeed! documentation is bit unclear, an example command not work for windows, I did manage to install successfully, I have sent the message to fix the documentation, I will leave the comment in the documentation.
Try the following steps to fix the installation of DXA Model Extension:
Create the extensions folder in content service root.
Copy the ...
Yes there will be a Java version of STRI, we actually have written all (or maybe I should be safe and say most) of the code already.
But there are a few things holding us back from releasing it to the community at this point. It is not waiting for DD4T 2.0 to be released, but we will try to include DD4T 2.0 if that comes out before we can release.
As soon ...
In the offical documentation under known issues (login not required anymore ;o), it states the following:
Problem: Import fails with following error when importing on a system with ECL installed: Error: Tridion.ContentManager.FilterException: The Filter condition 'ForRepository' is invalid. The item tcm:0-3-1 does not exist.
Solution: Disable the ECL event ...
It seems your problem is related to package size since I see errors in your logs corresponding to that. We faced a similar issue with the package size. To fix that you need to set the below attributes in your deployer web.config under HTTPUPLOAD:
Under system.web section add the below:
<httpRuntime maxRequestLength="Sizeyouwantinbytes" />
I like Harald's blog post (referred to by Nuno above). But note that the DXA import PowerShell script also supports importing into existing Publications (see the script's parameters).
Get-Help .\import.ps1 -detailed
For starters on Web 8, the XPM button is on the top right, and the CME URL in your pages is coming from a configuration file, which is generated when you publish the Publish Settings Page in the _System Structure Group.
When you are using Web 8 Topology Manager (the default setup), this URL will be read from what is in your Topology Manager under Content ...
With "the DXA 1.7 Nuget package" I'm guessing you mean "SDL Digital eXperience Accelerator Framework for SDL Web 8", which when you inspect the contents of the package, does contain the SDL.Web.Tridion.dll in its lib\net452 directory.
The reason it is not referenced from a Web project, is because of clarity on dependencies. a Web project (see https://github....
Some time ago, we also worked on a DXA implementation where we customized the link resolver (I think we were using DXA 1.5 or 1.6, but the approach should be similar).
The Spring framework should normally scan any of your packages for implementations, annotated by @Component. By adding @Primary, you're able to make your implementation take precedence over ...
Lets start with a few (short) answers:
Q: is splitting the DXA Master publication supported
A: in short: no. slightly longer: depending on what you expect under supported, but as you already mentioned, if you split it up by doing partial imports, future upgrade import scripts won't know where your items are and might import them in the wrong location.
Indeed!, you missed to Installing the DXA Model Extension in content service.
Try the following steps to fix:
Create the extensions folder in content service root.
Copy the \dxa\cis\dxa-model-service-extension\udp-content-dxa-extension-assembly-11.0.0-1047-core.zip file to extensions folder
UnInstall the Tridion SessionContent Service
Re-install the ...
There's no 'out of the box' way to make the Key field of a Keyword mandatory, unfortunately.
I recommend that you do this using the Tridion Events System.
It should be quite simple to write the code that intercepts the save action (as it's initiated) and prevents the successful saving of the Keyword unless the Key field is populated.
You'll probably want ...
It's not possible to use the exact same url for two mapped publications. This way, DXA would never know which publication to use to read content from.
You can point two publications to one dxa web app, but then you need to either use a different base url (eg http://english.mysite.com and http://french.mysite.com - if you want to localize by language, or ...
After examination of the code I found that the regions.json file is published as a binary when the _System\Publish Settings page is published.
The Publish Mappings TBB is used to create the regions configuration based on iterating over Component Template, where regions are automatically created based to the region name between [square-brackets] in the ...
looks like a problem with bin/config/cd_dynamic_conf.xml in your web application. Double check that the Publication element has the correct Id in here matching that of your 400 Example Site publication. If this is OK then its probably due to the configuration not being successfully published, perhaps due to the previous issue you had with Publish Settings ...