[!NAME!]

Hello,
Today in modifying an Modx Evo to Revo I came across this tag. I'm newer to this CMS and while I've been able to discover most of the differences between the two CMS' tags, this one is alluding me. What was or is this tag generally used for?

That's for an uncached snippet. The snippet's output is not cached and the snippet tags are not removed from the content. So even if the page is served from the cache, that snippet will get processed on every request. This is useful for form processing snippets, such as a contact form or a login form, where the same page is reloaded when the form is submitted. If it had been cached, nothing would be done with the POST values because the snippet would have been removed. Since the snippet was uncached, it will get run again, processing the POST.

All Revo tags always begin and end with double brackets, and the ! uncached indicator can be used for all tags. [[!$uncachedChunk]] or [[!uncachedSnippet]] or [[!*uncachedTV]]. I won't go into why you might want to do that; you'll know if you ever do need to use it.

Quote from: sottwell at Mar 24, 2015, 10:20 AM

That's for an uncached snippet. The snippet's output is not cached and the snippet tags are not removed from the content. So even if the page is served from the cache, that snippet will get processed on every request. This is useful for form processing snippets, such as a contact form or a login form, where the same page is reloaded when the form is submitted. If it had been cached, nothing would be done with the POST values because the snippet would have been removed. Since the snippet was uncached, it will get run again, processing the POST.

All Revo tags always begin and end with double brackets, and the ! uncached indicator can be used for all tags. [[!$uncachedChunk]] or [[!uncachedSnippet]] or [[!*uncachedTV]]. I won't go into why you might want to do that; you'll know if you ever do need to use it.

Thanks for the information. You bring up a question I've had since starting this site-port though there towards the end. Why did the Revo switch it's tag style from Evo? For bigger sites that proves a relatively annoying update process in my mind. Was this due to cause, or was it more impromptu?

I'm not sure of the full reason. It does simplify and clarify parsing, especially of nested tags.

There are a few scripts available to automatically convert Evo tags to Revo. The Provisioner extra usually works pretty well for importing the bulk of an Evo site into a Revo installation, with relatively few follow-up changes needed, such as changing AjaxSearch, EForm, and Ditto snippets. It automatically converts all element tags.

http://modx.com/learn/modx-college/migrating-from-evo-to-revo/
http://www.toasteddigital.com/blog/modx-evolution-to-revolution-tag-converter.html

With the provisioner pls be very careful about collations and language sets. I had some trouble porting my data over, some punctuation in Chinese gave it trouble and I would lose some content. It was a pain and can be avoided. [ed. note: nuan88 last edited this post 11 years, 6 months ago.]