February 28, 201412 yr For all you EE developers ExpressionEngine 2.8 has been released and includes lots of lovely new features. Here's some of the highlights: 1. Template layouts You no longer have to embed common page parts separetely like header, footer, asides (or use Snippets). Template layouts work like embeds but work for a whole page. Typical layout template: <html> <head> <title>{layout:title}</title> </head> <body> {layout:contents} </body> </html> Of course you can create as many layouts as you need, and calling the layout into a template is one simple tag syntax: {layout="site/wrapper"} You can also use layout:set tags to override default layout parameters and value: {layout:set name="title" value="News | {title}"} And of course you can still use regular embedded templates and Snippets anywhere. 2. Template routes You can now specify custom URL paths for any template group. Previously you were tied to something like /staff/entry/name but now you can create variations such as /staff/first-name/last-name and /staff/managers/position/name, you can of course create as many you need for different content and page types. Template routes can use Regex style formatting (eg to allow min/max characters, numeric only, only list certain characters such as + and =). 3. Improved caching New caching drivers have been added that support Memcached or Redis, if you run a high traffic site this can improve page load times by up to 200%. 4. Relative dates You can now display relative dates, like "9 days ago" without a plugin - hurrah! Supports both past and future dates, and there are loads of tag parameters to customise the date output. And of course there are numerous other tweaks such as new parameters for related entries, improved pagination formatting, CP enhancements plus of course a few bug fixes.
March 7, 201412 yr I've followed EE's release cycle for the past two years. We actually stopped using it for a lot of projects about a year ago, in favor of Craft and Statamic. Despite the lack of Craft plugins at the moment, we have found that we don't actually need many, if any at all.
March 7, 201412 yr Author Indeed Craft is a good bit of kit, though I've yet to use on a live site. Statamic as well, got a site lined up for it. Like Craft, EE doesn't usually require many addons if you know how to use it properly. I have seen EE sites that have had 20-30 addons installed when they could have used out of the box functionality for 90% of it.
March 9, 201412 yr I've loved EE in the past (current site uses it). But it really needs to fix some stuff. It needs to have the ability to take out the index in the URL by default. Why this is still present in codeignighter stuff is beyond me, but I know of no one that likes it. Its a pain to take out of every EE project I did. They should automate it. The next is the bad process to switch servers. It is such a pain in the tail having to manually switch all the URLs to a set folders and such. I also wish they would make it file based instead of everything on the db. It makes it impossible to version control it, and let's forget multiple people working on the same project. I haven't touched EE seriously in a while so maybe these have been fixed, but in any case I'm sick of dealing with the same headaches that other managers have already gotten by.
March 9, 201412 yr Author I've loved EE in the past (current site uses it). But it really needs to fix some stuff. It needs to have the ability to take out the index in the URL by default. Why this is still present in codeignighter stuff is beyond me, but I know of no one that likes it. Its a pain to take out of every EE project I did. They should automate it. There is default .htaccess code to remove index.php provided in the docs if you need it. The reason it's not there by default is that .htaccess isn't supported on all servers, I come across many servers which don't, especially those behind firewalls running intranets and so on. The next is the bad process to switch servers. It is such a pain in the tail having to manually switch all the URLs to a set folders and such. I've never had a problem, Deeploy Helper is a useful addon, lets you change all paths in one go. You can always use custom config settings for paths/url's as well which instantly update sitewide. I also wish they would make it file based instead of everything on the db. It makes it impossible to version control it, and let's forget multiple people working on the same project. You can save templates, snippets and global variables as files then sync with Git or whatever for version control. I haven't touched EE seriously in a while so maybe these have been fixed, but in any case I'm sick of dealing with the same headaches that other managers have already gotten by.
March 9, 201412 yr There is default .htaccess code to remove index.php provided in the docs if you need it. The reason it's not there by default is that .htaccess isn't supported on all servers, I come across many servers which don't, especially those behind firewalls running intranets and so on. About time. Goodness. I've never had a problem, Deeploy Helper is a useful addon, lets you change all paths in one go. You can always use custom config settings for paths/url's as well which instantly update sitewide. They should simply the process and I shouldnt have to buy a $15 plugin to do this. You can save templates, snippets and global variables as files then sync with Git or whatever for version control. But the last time I tried to do that, they didn't sync with what was in the DB. Or am I wrong about that. Everything that makes sense in other CMS's seems to be a pain in EE. Just one of the reasons why im dropping it in favor of something like Statamic (haven't tried it, but we'll see)
March 9, 201412 yr Author About time. Goodness. Lol... it's been in the docs for a couple of years now... it's really only a generic one but helps peeps copy n paste They should simply the process and I shouldnt have to buy a $15 plugin to do this. It used to be free, but I don't blame the developer for earning a few pennies from it... But the last time I tried to do that, they didn't sync with what was in the DB. Or am I wrong about that. Everything that makes sense in other CMS's seems to be a pain in EE. Just one of the reasons why im dropping it in favor of something like Statamic (haven't tried it, but we'll see) They should sync automatically after you have pushed updates to the site, when EE sees a newer timestamp on the static file it automatically updates. Statamic is really good, blindingly fast because it runs on static files, no DB, plus you can configure custom fields for as many content types as you want. Template tags are similar to EE, This example gets 10 entries from the blog folder, plus entries from the news folder + any subfolders... <ul> {{ entries:listing folder="blog|news*" limit="10" }} <li> <a href="{{ url }}">{{ title }} by {{ author }}</a> </li> {{ /entries:listing }} </ul>
March 10, 201412 yr Indeed Craft is a good bit of kit, though I've yet to use on a live site. Statamic as well, got a site lined up for it. Like Craft, EE doesn't usually require many addons if you know how to use it properly. I have seen EE sites that have had 20-30 addons installed when they could have used out of the box functionality for 90% of it. Of course, I see the same on Wordpress sites (usually a lot worse on WP though). At least they have upped the field types to include a grid and relationship field. Although I still prefer the P&T versions, the fact there's more than one option now is good. Craft solves a lot of the problems we had with EE. Things like one-click updating, live preview, the ability to trial packages (plugins will also have this in the future). Not to mention how instantly flexible it is with custom fields, entry types, Matrix and relationship fields. I just prefer it. I think the competition from Craft helped EllisLab improve it's product. It seems like they are really trying to solve a lot of the issues people have had over the years, with more features being built into each major release, and not just a tonne of bug fixes.
March 10, 201412 yr Author Of course, I see the same on Wordpress sites (usually a lot worse on WP though). That's WP's inherent weakness, you often need plugins to do even basic content management. At least they have upped the field types to include a grid and relationship field. Although I still prefer the P&T versions, the fact there's more than one option now is good. Yes, a long time coming, as you say Brandon Kelly seems to have woken EL up a bit! I actually prefer working with the native Grid and Relationships field, less addons to manage and they have virtually the same functionality bar a few obscure parameters and variables. Craft solves a lot of the problems we had with EE. Things like one-click updating, live preview, the ability to trial packages (plugins will also have this in the future). Not to mention how instantly flexible it is with custom fields, entry types, Matrix and relationship fields. I just prefer it. Yes EL have lagged a bit with the updating routine but saying that I've never had and problems with traditional upgrades, bar the odd addon having a fit (easily rectified). I can think of only one time when an upgrade went skewy and that was as a result of the sql server going down at the same time. I think the competition from Craft helped EllisLab improve it's product. It seems like they are really trying to solve a lot of the issues people have had over the years, with more features being built into each major release, and not just a tonne of bug fixes. Agreed. I think EL have now got their skates on and I think they will be playing catch up with Craft in the next few releases
March 11, 201412 yr Lol... it's been in the docs for a couple of years now... it's really only a generic one but helps peeps copy n paste Yeah, but it's not dynamic. I bought a plugin (dont like to buy stuff like that) that made it dynamic. Unfortually, like a lot of plugins Ive noticed, the developer hasn't kept up development. It used to be free, but I don't blame the developer for earning a few pennies from it... Nor do I, but seeing how the CMS is so expensive, I would expect some functioanlity that is at least on par with free CMS's. In this respect EE fails. They should sync automatically after you have pushed updates to the site, when EE sees a newer timestamp on the static file it automatically updates. Makes me wonder why they don't do this by default in the first place... like Pyro. Not sure I see a benifit from it all being in the DB other than to be a pain in the neck.
March 11, 201412 yr Author "expensive" is very subjective! I find a lot of clients are reassured that EE is a commercial product and find it really easy to use (when compared to other CMS's). Swings and roundabouts!
Create an account or sign in to comment