Here’s a simple one: How do you set up a site’s copyright notice so that it’s always up to date? With a dynamic publishing system like ExpressionEngine, it would be silly to manually update that copyright date at the start of every new year.
Before publishing content, many authors and editors like to double-check that it looks the way they expect it to look on the front-end. Live Look lets you do just that, and it’s pretty easy to set up.
Fortunately, the parameter
include_jquery can help save the day.
The Secure Mode setting in ExpressionEngine serves a very important function and is often misunderstood. Secure Mode ensures that all forms processed by ExpressionEngine came from the visitor who was given the form and not some other source that may be trying to do very bad things. If the call is not coming from the visitor it was generated for, ExpressionEngine will reject it.
At its most basic level, this feature helps prevent spam bots from bombing your site with automated data as they try to add unwelcome viagra ads to your innocent comments section. However, the really important duty of Secure Mode is stopping cross-site request forgery attacks which include not only common spammers but also malicious external attacks.
For the past two months, I have been working on a site for my daughter that will help her work through her emotions. I am loosely calling it an “app” that is built using ExpressionEngine. The basic idea of the app is to present my daughter with a series of questions that help her determine how she feels, and then present some healthy ways to cope with the emotion she chose. Before Grid, I was showing all of the healthy coping suggestions on one page and she would chose from the long list. With Grid, I am able to put several answers into just one entry, and with pagination in Grid, I can present one coping suggestion at a time which makes for a much better experience.
I worked on a project recently where I needed to offer a view all option in addition to the usual pagination links. Is that possible with ExpressionEngine? Of course! And since it provides a great example of what’s possible with embedded templates, I thought it’d be fun to show it off here.
Before you install ExpressionEngine and start tweaking preferences, it’s best to take some time to think about the content you’ll be managing with EE and plan out that content’s structure. It goes a long way in making that content valuable and reusable for years to come. (I’ve found it helps the design process immensely to know the chunks of content you’re designing for as well. Otherwise, you’re just designing your visual wish and cramming in content to fit the look.) In this overview, you’ll
Documentation First! Wait, Documentation First?
You hear it often enough - “Documentation First!”, but for an ExpressionEngine project?
As the Community continues to amaze with the quality, depth and breadth of sites developed in ExpressionEngine, the need for a centralized dev doc repo becomes more important. The nature of projects being built with EE edge ever closer to web apps, with incredible add-ons that are almost apps in their own right!
Documentation may be the least interesting part of any development project, but you and your users will benefit by having high-quality documentation available.
For my turn driving the EE blog, I thought I walk you through the creation of a new fieldtype. Before we get started, I should probably give you a heads up about the approach I’m taking. One of my professors once described an absolutely brilliant lecture he’d attended where a physicist was explaining some uber-high level ‘physicy’ stuff to an audience of laymen. He did it by starting with the simplest of analogies. Of course, the simplest of analogies was totally wrong. But once his audience grasped the logic of the simplest analogy, he would then draw a new, slightly less simple analogy. Which—was also wrong. And he kept building upon all of these simple, but wrong, analogies until the audience could grasp the basics that were NOT wrong.
Or to quote Terry Pratchett, “Actually that sentence is wrong in every particular, but it’s quite a useful lie.” (Night Watch)
So with that in mind, let’s start building our super simple fieldtype.
Writing add-ons for ExpressionEngine isn’t terribly difficult once you know what you’re doing. However, before you know what you’re doing it can be a frustrating tangle of guess and check. I vividly remember writing my first plugin, and then my first extension, trying to wrap my head around how hooks work. Then I tried my hand at writing a Multiple Site Manager compatible extension and there was more confusion there.
I want to walk you through writing a plugin, the best first step towards building ExpressionEngine add-ons. This tutorial will be a start-to-finish adventure, starting with the plugin skeleton and working our way to putting it on GitHub for everyone to download. I’ll explain my methods and my approach to building plugins, and by extension, software in general. Additionally, this particular plugin will be replacing the aging MagPie plugin, since MagPie is no longer being maintained.