The problem I've had, was that over the years I have always believed module call tags could be placed either in the content or the template. A lot of modules only function or function better when placed in the content.
This meant that I mixed a module call like this {FormBuilder form='contact'} with text (an address perhaps) in the content editor.
Based on this I've had clients call and tell me they accidentally deleted the "thing with the squiggly brackets". Not a huge problem, but not the slick user experience I try to create for my clients.
Here's my (very late) revelation:
I had overlooked using a second content tag. I put this at the top of my template.
Code: Select all
{content assign="ModuleTag" block="tag_content_block" label="Tag Content Block" wysiwyg="false" oneline="true" tab="options"}
That's where I dump the module call tag {FormBuilder form='contact'}.
I then put this {$ModuleTag} in the template body above or below the {content} tag depending on what my client needs to edit.
So far no problems with this, but if anyone can see why this would be a bad idea please let me know.
Simon66