View All›More from June, 2014
10Jun | 2014
There are many great reasons to use ExpressionEngine (EE) as your Content Management System (CMS) of choice: security, flexibility and ease are just a few.
One of the aspects I like best is the security of the template parser.
I have yet to personally see an EE site that has been compromised - the core and templates are locked down and that gives us and our clients peace of mind that their sites and content are safe. It’s important to know how EE works at the template parser level to make sure you know how to keep your EE site running quickly and securely.
One of the most important things to understand about performance and the template parser is that EE will parse everything in a template before running conditional logic. Unlike writing in a raw scripting language, everything in a conditional statement is run whether the conditional passes as true or not.
Parse first, ask questions later
If you have multiple channel entries tags, for whatever reason, in one template separated by conditional logic to show per a given scenario, it will parse all tags and make all database queries before deciding which content to display. So if you wanted to use segment_2 (equals null or not) for determining whether it’s a detail view or landing view in one template, it would run both instances of the EE tags and greatly slow your load times.
Read the rest of this article on theMetaQ.com.