CMS Made Simple Forums

It appears to be a smarty issue with the actual name of the block plugin. renaming the block plugin to something that does not start with zz2 works just fine. What name are you using? When I change it to "abcqrs" I still get the same behavior as long as the block actually exists: it works...

Thanks so much. I'll watch this thread for developments.

Obviously it's a powerful and useful feature. Being smarty-based and especially the versatility of smarty's open-close tagging paradigm were decisive in persuading me to migrate my project to CMSMS.

You pasted directly to a content page or you put it in the layout template used by that page? I only have trouble putting it in the layout template.

I'll also try upgrading 1.11.10 to 1.11.11 as there seems to be a diff download for that.

Running version 1.11.10, I have (among others) a trivially defined block tag that works as expected when inserted into a content page. When I try to put the simplest possible invocation of it into a layout template, the editor reports a compile error ending with "unexpected closing tag." I...

Thanks for getting back, but the metadata in question isn't always known at edit time, and in any case the tag implementing this needs to be more plug-and-play in the content block than that. I've proceeded with two tags in the template, each inspecting a session variable for run-time additions to s...

I'm looking for the canonical way to take advantage of the content block being processed ahead of the head block to let a UDT or other tag in the content block append additional styles or scripts to a page's head block at runtime. My fallback method would be to have one or more placeholder tags temp...