Steve Taylor photo

Developer’s Custom Fields 0.8

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.

Please let me know if you encounter any issues with this release. If you’re sure there’s a bug, raise an issue on GitHub. If you’re not sure what the problem is, contact me.

New features

  • 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_box should “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 file!).
  • New time and datetime field types. Thanks to Saurabh Shukla for this one. The field types use the jQuery Timepicker addon.
  • New slt_cf_default_value filter.

Important changes

Please adjust your code as necessary if the following changes affect you:

  • The datepicker_css_url setting, to account for additional UI elements, is now ui_css_url.
  • The defaults for the ui_css_url and css_url settings have been moved inside the slt_cf_init function. If these values are being changed by the slt_cf_setting function, this must be hooked to init with 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_url core function. Now they are exposed to any filters that other plugins might attach to the plugins_url core filter.

For more details, see: