Discussion Forum

timbuckingham

Administrator

From: Baltimore, MD

Registered: April 2, 2012

Posts: 978

BigTree 4.0RC2 Backwards Compatibility Notes

BigTree 4.0RC2 introduces some issues regarding a few specific behaviors and custom PHP modules in the admin. First, the bigger issue of custom PHP modules in the admin:

BigTree's admin now has a more thorough default.php layout from which it draws most of the admin. This includes related modules, H1s, breadcrumbs, and navigation. You no longer need to draw these elements yourself so if you were previously drawing them you will need to modify your module to no longer do so (or use your own custom layout file that replicates the old behavior, just don't replace default.php or the rest of the admin will no longer draw it). In addition, the "form_container" class has been renamed "container" to more accurately describe its functionality. You will want to update any custom pages that use that class.

Miscellaneous Changes

• BigTree now defaults to use MySQLi PHP extension instead of the deprecated MySQL extension. In relation to this, anywhere you were previously using mysql_real_escape_string you may want to switch to using the new shorthand sqlescape function which will use whichever extension is available.

• sqlfetch() no longer throws an Exception if debug is turned off.

• Tagging is now associated by table instead of by module. BigTree's update scripts should update this automatically from older versions but if you were using custom functions related to bigtree_tags_rel you may need to update them.

• Many to Many field type's list parser function now parses both the list of available items as well as the list of currently tagged items. The list of available items is given true as its second parameter when parsing. The list of current items receives false as its second parameter when parsing.

• Including custom CSS and JavaScript in the admin is now done through $bigtree["css"] and $bigtree["js"] instead of $css and $js.

• More semantic paging for BigTreeModule::getPage and other page-related functions: The first page is now page 1 instead of page 0.