Blog Sections Open
Rendering Two JotX Blocks Without Output Conflicts
JotX behaves well in isolation, but pages that need more than one comment block can run into placeholder and output conflicts. That was the practical issue behind this topic. Typical Pattern [[JotX? &docids=`1,3` &placeh
JotX behaves well in isolation, but pages that need more than one comment block can run into placeholder and output conflicts. That was the practical issue behind this topic.
Typical Pattern
[[JotX? &docids=`1,3` &placeholders=`1` &output=`0`]]
[!JotX? &pagination=`10` &docids=`1,3` &placeholders=`1` &output=`0`!]
Why It Gets Messy
- shared placeholders are reused unintentionally
- cached and uncached blocks mix on the same page
- template expectations differ between the two blocks
If a page really needs two comment-related outputs, treat them as separate rendering contexts. Once their placeholders and output modes are isolated, the setup becomes much easier to reason about.
Understanding Checkbox TV Value Formats in Evolution CMS
A quick guide to how checkbox TVs store values and why frontend output often looks odd until the stored format is understood.
Building Resource Links Correctly in EvoGallery Templates
How to render gallery items so they link back to the correct resource instead of only exposing the raw image path.