It has been almost six months since our last bug-fix release (3.6.4) so the
release of 3.6.6 represents a large number of fixes and tweaks to the system.
vBulletin 3.6.6 is the minimum required version for the upcoming vBulletin
Blog and Project Tools products and includes various new hooks (including the
much-requested fetch_musername hook) and code changes to accomodate these new
systems. As a result, certain existing vBulletin features have been upgraded,
such as date entry fields in the Admin CP, which now all feature the calendar
popup date picker system designed for the project tools.
For the benefit of plugin authors, the information shown at the bottom of
all vBulletin pages in debug mode is now greatly enhanced and shows not only
all templates that have been called, but also all files that have been
included by PHP and all hooks that have been encountered together with whether
or not they executed code.
With the use of AJAX and other client-side scripting systems increasing all
from the templates as possible.
Upgrading from Previous Versions
In order to facilitate this switch and to provide a solid framework on
library (YUI) for much of our DOM, event and XML-HTTP features, and in future
versions you will see much greater use of this excellent library as we migrate
Included by default in vBulletin is the DOM/Event library
(yahoo-dom-event.js) and the XML-HTTP connection handler (connection.js).
3.6.6 is a maintenance release and we recommend that all customers upgrade to
benefit from six months of bug fixes and stability improvements. Certain input
validation errors in the Admin Control Panel have also been resolved so that
unexpected errors are not encountered.
No patch or plugin is available to bring previous versions up to 3.6.6
without a full upgrade, as the various changes to implement all the bug fixes
represent a large number of changes. To get the fixes from 3.6.6 onto your own
board you must perform a full upgrade.
Full instructions for upgrading vBulletin are available here.
For this release we have changed the format of our customary Templates Changed
Since X.Y.Z notice.
Previously the list was change-based, which often resulted in several
templates being listed multiple times, sometimes with mandatory changes and
other times not.
The 3.6.6 template change notice is template-based, so each template is
listed only once and all changes to that template will be listed under the
template name. If any of the changes to a template is mandatory, the entire
template will be listed as requiring the change.
We hope that this new system will be easier and quicker to work with for
those with modified templates.