I’ve finally got the latest version of my Developer’s Custom Fields plugin released. It’s bumped up to 0.8 because there’s a number of new features as well as improvements and fixes.
- Support for WordPress 3.5 media handling. The upcoming release of WordPress has revamped media handling. Now attachments make use of the standard post editing screen. This means that instead of using a separate method for adding custom fields to attachment edit screens, we can use the same metabox interface as everything else. An ideal instance of the handiness of this plugin – in theory, you don’t have to do a thing. Your current attachment custom fields definitions registered using
slt_cf_register_boxshould “just work” :-) Obviously, let me know if they don’t. A bonus with this 3.5 feature is that I’ve been able to easily add support for all field types for attachments (except
datetimefield types. Thanks to Saurabh Shukla for this one. The field types use the jQuery Timepicker addon.
Please adjust your code as necessary if the following changes affect you:
datepicker_css_urlsetting, to account for additional UI elements, is now
- The defaults for the
css_urlsettings have been moved inside the
slt_cf_initfunction. If these values are being changed by the
slt_cf_settingfunction, this must be hooked to
initwith a priority of 11 or above to ensure they aren’t re-set to the defaults. These defaults have been moved inside because they use the
plugins_urlcore function. Now they are exposed to any filters that other plugins might attach to the
For more details, see: