In this article, we take a deeper look into ExpressionEngine's Preload Replace tag and explore different ways you can use it throughout your templates.
ExpressionEngine is great in many ways - security, robust features and flexibility are just to name a few. However, with great freedom comes the need to know how to keep it running quick and efficient.
Social media APIs offer up JSON counts for a URL, but how do you parse and display them? To do it the right way, there's more to it than you might think - but it's really not too difficult.
In this article we take a look at the ExpressionEngine $config variable and explore quick and easy ways to override troublesome configuration errors saved to the database.
Sometimes, a grid-like field is exactly what you need for the job at hand. This is exactly what we needed for a recent client's ExpressionEngine build – only we didn’t want to take the time to create a full-blown Freeform Pro integrated field type – so we improvised, or freestyled a little bit.
Of the many things I love about ExpressionEngine, native events management is not one of them. What do you do if you need a location or other basic event field displayed in your calendar?
Two of my favorite aspects of using ExpressionEngine are Matrix and Safecracker. In terms of making life easier, they're amazing. Here’s a creative way edit Matrix data on the front-end, with more flexibility.
When it comes to development, the old saying about another person's trash just doesn't apply. Let's clean up our ExpressionEngine projects for ourselves and for all the lovely developers who may end up working on it someday too.
The #eecms hashtag is on fire, blog posts are out and people are adding Scotch to their coffee. On Sunday, November 25th, a bunch of changes at EllisLab happened, and it riled up the ExpressionEngine community. Amid the numerous outspoken rants, few quiet praises and several rabid tweets is a story of big and small changes. In case you missed it, here’s a summary of the big news.
The ExpressionEngine community got together to commit to a Q&A board on Stack Exchange. And honestly we weren't sure how to feel. Sure, Stack Exchange is a great tool. But why pay for support from EllisLab? Is it worth it to split the EE community? We've collected our thoughts on the matter. But we want to hear from YOU.