0

We have this problem with Component Templates with output format: REL and published as Dynamic Component

When we do a content update on the Component, and publish it, the changes don't show up in the Page, so we restart the app pool and after that, the updates are getting reflected

Do I need to do any setting in any of the config file.

Can anyone let me know reason behind this?

Thanks In Advance.

  • Did any of the answers help you? In any case, please leave some feedback so that others who have the same/similar issue can benefit from this question. If you have, provide some additional information based on the suggested answers. – Atila Sos Feb 12 '18 at 17:40
  • Hi @AtilaSos, I wasn't able to read the answers until now, for sure I will my feedback on each answer. So sorry for the delay. Thank you !! – Carolina Feb 27 '18 at 19:48
2

Does this happen for all items or just Component Templates with REL?

Nonetheless, it sounds to me that the cache invalidation is not set up properly or is not working. Tridion has a mechanism (Cache Channel Service) to invalidate the cached items when an item is republished or unpublished. By recycling the app pool, you effectively clear the cache so the new versions of items are retrieved.

More information here for troubleshooting your scenario.

  • it is happening for all items "Published as Dynamic component", after reading tridion documentation, I've updated cache to true (it was set to false), but we are still facing same problem, Content is not updated until we recycle app pool. Thanks – Carolina Feb 27 '18 at 19:53
0

Check that the language of your Publishing Target is not set to 'none'. The 'none' setting will force the publisher to embed the DCPs in the Page, and prevent them from being dynamically included.

  • Hi, we have this into tcdl-conf.xml : <Properties> <Property Name="tcdl.page.target.language" Value="dotnet"/></Properties> – Carolina Feb 27 '18 at 19:54
0

Not sure if this is related, but on our end we had c# razors being used in component templates and we use to publish the same through Tridion. The issue we had was the way .Net framework works, wherein it used to download the razors for compilation and keeps it in a temp folder after compilation so that they can be used for future. The folder location is

"%WINDOWS\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\"

So, anytime we published the CT and observed changes weren't reflecting, we had to empty the folder and then it will work. Please note that you need to clear the files under the .net framework version which you are using which in the above example is v4.0.30319

Qualifier, I will like to attach to this is that only when we changed the razors, it used to happen. Not with updating components which were using this component template.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.