News items tagged with "bugs"

The first patch to address issues in v2.3.0 (stable) has been released.  This patch can be applied to any site already running v2.3.0.  The code is already fixed in the 'master' git repo and the patch file can be downloaded from sourceforge.net here.  This patch updates a few 3rd party libraries and fixes these issues:

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:

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 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:

This is the first patch to address a couple bugs and other issues in v2.2.2 (stable), which are now fixed.  This patch can be applied to any site already running v2.2.2.  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 bugs:

This is a fifth patch to address a couple big bugs and several other issues in v2.2.0 (stable), which are now fixed.  This patch can be applied to any site already running v2.2.0, v2.2.0patch1, v2.2.0patch2,  v2.2.0patch3, or v2.2.0patch4.  The code is already fixed in the 'master' git repo and the patch file can be downloaded from sourceforge.net.  The patch fixes these bugs:

This is a fourth patch to address a couple big bugs and several other issues in v2.2.0 (stable), which are now fixed.  This patch can be applied to any site already running v2.2.0, v2.2.0patch1, v2.2.0patch2 or v2.2.0patch3.  The code is already fixed in the 'master' git repo and the patch file can be downloaded from sourceforge.net.  The patch fixes these bugs:

We knew it would eventually occur, but the API to work with Twitter v1 has been blacked out in favor of v1.1.  You've probably already seen this warning message on your site, esp. if you have ever set up a Twitter module.  There is a forthcoming fix (v2.2.0patch4) due later this week which will attempt to fix this, but in the past had caused page breaks when Twitter was bogged down.  Here are some work-arounds in the mean time: