Our no-risk upgrade sale was so popular, now that 3.1 has launched with a bevy of great add-ons, we’re bringing it back! That means that ExpressionEngine 3 upgrades are
$149 , and upgrading additional sites for your v2 license are $99 each.
How is it no-risk? When you upgrade to v3, you still have access to the latest release of v2, so you can take your time migrating while benefitting from today’s savings. New purchases of version 3 include similar access.
The sale is active today
Only two days after 3.1.0 was released, we’re releasing 3.1.1. We found a few bugs that we couldn’t let stand and squashed them as fast as possible. It’s releases like this that make us really thankful for 3.0’s much-improved updater.
In particular, there were a few PHP errors thrown when creating template groups when saving templates as files, when sometimes submitting a contact form, and when some add-ons would save particular models. With these bugs, you can expect our test coverage to
I’m happy to announce that the ExpressionEngine Wiki module is now compatible with ExpressionEngine version 3 and is available for download on Github.
As we mentioned a few weeks back, our main focus of ExpressionEngine 3.1.0 was on third-party developers. With 3.1.0, we’ve added hooks to enable even more awesome add-ons, which are now available.
Our community of developers have created feature-rich solutions for ExpressionEngine 3 that include:
- event handling
- asset management
- backup solutions
- real estate / MLS
- and more!
ExpressionEngine 3.1.0 has been released and it’s full of great new features, performance improvements, and over 35 bug fixes. Here are the high notes:
- Template Partials and Template Variables can now be saved as files, just like your templates. Just check “Save Templates as Files” and you’re all set.
- As of 3.1.0 we now support PHP 7.0 and MySQL 5.7. Feel free to upgrade to the latest and greatest version of PHP and reap the rewards!
- Edit Categories on the Publish page to your heart’s
We’ve been working with third-party developers in our Developer Preview Program for the upcoming version 3.1.0, and we wanted to share some details with you ahead of its release. Our main goal for 3.1.0 is to add hooks that replace some old ones from v2. Third parties need these hooks for some of the great add-ons you’ve been waiting for v3 compatibility. So when we release 3.1.0, you can expect to see many of your favorite add-ons released around the same time.
But we didn’t want third
The ExpressionEngine user guide is now at a new home. There you can find documentation for all major versions of ExpressionEngine, including legacy and retired versions.
If you target the specific versions in your links, they will remain good regardless of future releases. So your links to
https://docs.expressionengine.com/v3/ currently redirect to
latest/, but will continue to point to v3 docs even after we release 4.0 (which would itself become
The move returns the focus on
Ho ho ho! I got so many letters from you asking for a maintenance release of ExpressionEngine 2.10 and since you’ve been good little boys and girls I asked the fine folks at EllisLab to make your Christmas wish come true! I’m told this maintenance release fixes a number of bugs, changes the password maximum length to 72 characters, improves New Relic transaction reporting, and added a notification to the File fieldtype when its file does not exist. There is a full changelog available.
We wanted to get out one more release before the holidays, so here’s a small release with 16 bug fixes and 8 other additions. In particular, relationships had quite a few fixes logged and should behave itself after searching.
We have a few small additions this time around as well. As fans of Markdown we’re happy that comments can now use any formatter you have installed, including ExpressionEngine’s native Markdown formatter.
We’ve also changed how we’re reporting New Relic transactions.
ExpressionEngine 3.0.5 is now available for download. We fixed 24 bugs in this release with a continued focus on files. Using two file fields in one publish page should work as you’d expect. File fields with restricted directories now retain that restriction as expected while browsing and modifying the limit and view. The uninstallable File module is now installed.
Developers will be interested to know that the
cp_css_end hook has been fixed so it will be used and no longer cause PHP errors.