New answers tagged

4

You can add role on your configuration into your patch config. For example I created a patch config for setting up site definition for prod environment. <site name="website1" env:require="PROD" role:require="ContentDelivery" patch:before="site[@name='website']" hostName="test.com" targetHostName="...


0

If you need Unicorn to publish to two different databases then yes, adding it to the list of TargetDatabases is the way to go. As with anything Sitecore, I would not recommend modifying the configuration file directly, rather to patch the value in. Also be mindful that a few compatibility issues snuck in on recent Sitecore releases, so you should aim to get ...


0

I fixed it. I was referring to Helix's Unicorn project. https://github.com/Sitecore/Helix.Examples/tree/master/examples/helix-basic-unicorn It seems that the problem was the following. In Foundation.Serialization.Base.config <dataProviderConfiguration set:enableTransparentSync="$(env:UNICORN_ENABLE_TRANSPARENT_SYNC)" /> I deleted here. Or, ...


Top 50 recent answers are included