Exponent's Latest News

The most robust release of the v2.2.0 code line thus far has been set free.  We've corrected many anomalies still present in the 2.1.x code line and there are quite a number of new features and enhancements from the alpha3 release.  These include better EQL file import/export which is much more flexible in backing up and restoring backups made from various versions.  Noted additions in beta 1 include;

Q: What do you get when you cross the Flowplayer module, the YouTube module, and HTML5 compatibility?  A: the new Media Player module!  We recently added a new module to the v2.2.0 pre-release code line called the Media Player module.  It is designed to display Audio (mp3) and Video (mp4, webm, ogv, flv, or f4v) files, and YouTube links in an HTML5 compliant manner (Flash player is not always required).  This is done by using the MediaElement.js library instead of Flowplayer and also using HTML5 audio/video tags.

Continuing our 2-week release cycle, we bring the next iteration on the road to a stable 2.2.0 release.  v2.2.0alpha3 not only incorporates all the 2.1.3 bug fixes, but adds several new features.  The biggest fix in alpha 3 is migration once again works (and also clears up some lingering quirks), and the newest feature is category support and some new views for the blog module, along with a second installation sample for a ready-to-run' blog site'.

The suite of exponentcms.org sites (www.exponentcms.org, docs.exponentcms.org, forums.exponentcms.org, api.exponentcms.org & testing1.exponentcms.org) have been migrated to a new server and are back up and running!  Access to those sites had been slow and intermittent (at best) for the past several months.  We apologize for the delay in solving this problem.

(updated Feb 26th) If you wondering where the next 2.2.0 release is and why it wasn't released in conjunction with the 2.1.3 release, not to worry it's still on it's way.  We wanted to get the 2.1.3 bug fix release out quickly, but want to take a bit more time getting 2.2.0alpha3 polished.  The biggest fix in alpha 3 will be that migration once again works (and also clears up some lingering quirks), and the newest feature will be categories and some new views for the blog module, along with a second installation sample for a ready-to-run' blog site'.

In an effort to squash all bugs, v2.1.3 (Placid Precedent) has been released.  This release only fixes bugs found in the previous version, since new features are now destined for the v2.2 major version update.  Specific changes include:

You can expect to see v2.1.3 released in the next few days.  We've run across a few bugs that though not fatal (cause the site to crash), they do hinder some sites.  We have already implemented these fixes in the pre-release code, but want to wait (for additional reports from v2.1.2) before finalizing it.

We've quickly pushed out another unstable release in the push toward the next major upgrade, v2.2.0.  The alpha 2 release addresses many anomalies, especially with nested containers. Furthermore it incorporates all the fixes found in the v2.1.2 release.  Though this release should be fairly stable, it will continue to be tagged as 'alpha' because we have a number a features we want to add before a stable v2.2.0 is released.

Even sweeter than Lucky Lemonade is a Special Sweetheart!  v2.1.2 fixes over a dozen issues found with the previous version, especially some bugs and usability issues in the new forms module.   Additionally, we now display file and image size in  the file manager tooltips.  There are no new features in this release.  This is expected to be the final version of the 2.0/2.1 codeline as we push into the next major upgrade v2.2.  v2.2 will be fully backwards compatible with all 2.x versions, but will deprecate all v0.9x support/compatibility, except for database migration.

You can expect to see version 2.1.2, 'Special Sweetheart' on or around Valentine's Day 2013.  Several non-fatal type issues have already been addressed which would normally result in an eventual 'patch' release.  However, since this will (likely) be the last 'old school' compatible release, it will not be left in a 'patched' (version) state.  Furthermore, there were some anomalies which cropped up within the v2.2.0alpha1 release which required us to slow down its development slightly to ensure they are fully eradicated before proceeding with an v2.2.0alpha2 release.  However, the alpha 2 release is now also planned for the same date.