Exponent's Latest News

This version is considered a major upgrade and as always we recommend testing prior to updating a production site (see below)!  This stable release has many new features and addresses several issues in previous versions.  We've already posted several news and blog articles discussing these new features.

(Updated 11 Apr 2014) It's been a while since the last update to Exponent...which was the plan.  Several users were having to spend an inordinate amount of time continually updating their sites to the latest version, so we've slowed down our version updates from monthly to between quarterly and semi-annually (every 3 to 6 months).  Hopefully, the 2014 Wish List article whetted your appetite for what will actually hit the streets later this spring.  Because we'll be implementing MANY new features, we've also decided to bump minor versions. Here's some of the things you can look forward to in v2.3.0.

We've experienced a LOT of forum spamming lately, so much so that we changed some things which inadvertently disallowed new user registrations...then when fixing that issue and requiring admin approval prior to account activation, we were overwhelmed with new account registrations.  Luckily, all those 'tests' prevented most if not all spam from posting to the forum.  However our old forum software (PhpBB3) simply doesn't seem to have the tools to combat this form of attack.  Therefore we've moved to using Vanilla Forums software.  

The fourth patch to address issues in v2.2.3 (stable),  v2.2.3 patch #1, v2.2.3 patch #2, and v2.2.3 patch #3, has been released.  This patch can be applied to any site already running v2.2.3, v2.2.3patch1, v2.2.3patch2 or v2.2.3patch3.  The code is already fixed in the 'master' git repo and the patch file can be downloaded from sourceforge.net here.  In addition to the fixes found in patches #1, #2, and #3, this patch fixes these issues:

(Repackaged early Dec 9, 2013 to fix some errors) This is the third patch to address additional issues in v2.2.3 (stable),  v2.2.3 patch #1 and v2.2.3 patch #2, which we've fixed.  This patch can be applied to any site already running v2.2.3, v2.2.3patch1 or v2.2.3patch2.  The code is already fixed in the 'master' git repo and the patch file can be downloaded from sourceforge.net here.  In addition to the fixes found in patches #1 and #2, this patch fixes these issues:

(Updated Dec 26th) As we prepare to enter 2014, Exponent CMS is growing stronger than ever.  2013 has seen the code migrating past the old 1.0 underpinnings and also added many new features!  So what will 2014 hold in store for this mighty CMS?

This is the second patch to address some problems in v2.2.3 (stable) and v2.2.3 patch #1, which we've fixed.  This patch can be applied to any site already running v2.2.3 or v2.2.3patch1.  The code is already fixed in the 'master' git repo and the patch file can be downloaded from sourceforge.net here.  In addition to the fixes found in patch #1, this patch fixes these issues:

This is the first patch to address some anomalies in v2.2.3 (stable), which are now fixed.  This patch can be applied to any site already running v2.2.3.  The code is already fixed in the 'master' git repo and the patch file can be downloaded from sourceforge.net here.  The patch fixes these issues:

This version implements several minor changes, so we recommend testing prior to updating a production site (see below)!  This most recent stable release has changes which include a new role for the 'create' permission and global group permissions (see article) and it also (finally) deprecates several obsolete features (see article).  Furthermore, it adds several new features and addresses several issues (see article) in previous versions.

This is the second patch to address a bug in v2.2.2 (stable), which is now fixed.  This patch can be applied to any site already running v2.2.2 or v2.2.2patch1.  It includes all the fixes found in v2.2.2patch1  The code is already fixed in the 'master' git repo and the patch file can be downloaded from sourceforge.net here.  The patch fixes this bug: