New answers tagged

0

I did investigate and found that it was still possible to manage dxa.properties in the /config folder of the content service for on-premise setup. In case if you are using cloud and docker container setup, then it's possible to pass as environment variables for containers. Interestingly also found that this config was embedded into this udp-content-dxa-...


1

Now Publishing is working. Root cause is, In the Tridion Site 9.1 installation media for the Deployer role there are now 9 deployer folders. The previous Deployer and Deployer-combined folders are now used to run with the add-ons framework. Pipelines are not enabled by default which causes the error. The quickinstall script or the documentation steps for a ...


1

The response from Tridion Support confirmed that this is not supported for database publishing: documentation for the root element and path attribute says they're used for the filesystem storage provider. So unfortunately it looks like this isn't possible without additional customization work. https://docs.rws.com/816112/100911/sdl-tridion-sites-9-5-main-...


0

Mark, not sure if you considered using custom Template Building Blocks. Although not a quick solution, in the custom TBB, we should be able to update the root path just for PDFs by calling the Engine.AddBinary() method and specifying the path (Structure Group) where you'd like the PDFs to be published. So, something like this in the TBB should deploy only ...


1

Failure to prepare for deployment often indicates a false Content Deployer configuration or problems with customizations. If your publishing fails in the'Preparing for deployment' phase, try the following: Is your Content Deployer configuration (deployer-conf.xml) correct? Are you using a custom Module and/or Processor in your Content Deployer? The code for ...


Top 50 recent answers are included