An easy way to add custom fields to your object types (post, pages, custom post types, users)
|Author:||Mohammad Jangda, Joachim Kudish & Colin Vernon (profile at wordpress.org)|
|WordPress version required:||3.3|
|WordPress version tested:||3.4.1|
|Added to WordPress repository:||18-10-2010|
Warning! This plugin has not been updated in over 2 years. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress.
|Total downloads:||13 638|
Click to start download
An easy way to add custom fields to your object types (post, pages, custom post types, users) & to generate option pages.
The goal of this plugin is to help you rapidly build familiar, intuitive interfaces for your users in a very WordPress-native way.
The custom field panel is nice, but not quite the easiest thing for users to work with. Adding your own metaboxes and fields involves a lot of time and repetitive code that could be better used elsewhere.
This plugin handles all that heavy-lifting for you behind-the-scenes, so that you can focus on more on building out and connecting your data rather than all the minor details. This single piece of code
x_add_metadata_field( 'my-field-name', 'post' ); generates a metabox with a text field inside it, with the necessary hooks to save the entered values.
The API is similar to that used for registering custom post types and taxonomies so it should be familiar territory.
NOTE: The plugin now requires WordPress 3.3+ (chiefly for the wysiwyg & datepicker fields)
See "Other Notes" section for usage information
Write easy, intuitive and WordPress-like code to add new fields.
Custom Metadata Manager supports many field types with an easy way to render your own.
Adding custom columns is also easy. You can go with a default display, or specify your own output callback
Why a code-based approach instead of a UI?
This is also a developer feature, aimed towards site builders. And real developers don’t need UIs 😉
(But really, though, the main benefit of this fact comes into play when you’re working with multiple environments, i.e. development/local, qa/staging, production. This approach makes it easy to replicate UIs and features without having to worry about database synchronization and other crazy things.)
Why isn’t the function just `add_metadata_field`? Do you really need the stupid `x_`?
We’re being good and “namespacing” our public functions. You should too.
- fix a bug where non-image file upload path doesn’t get inserted into the input when clicking Insert into Post from the media manager
- add ‘editor’ and ‘richtext’ as synonyms of ‘wysiwyg’ field type
- added the ability to have readonly fields with the new
- note: the plugin now requires WordPress 3.3+ (chiefly for the wysiwyg & datepicker fields)
- update/clean-up the examples file
- properly enqueue admin css for WP 3.3+
- added a filter for the CUSTOM_METADATA_MANAGER_URL constant
- fix fields not appearing when editing users in WP 3.3+ (props @FolioVision)
- now passing the
- use the new
wp_editor()function (since WP 3.3+) instead of
- wysiwyg fields are no longer cloneable (may be revisited in a future version)
- note: metaboxes that have a wysiwyg field will break when moved, this is not a bug per-se (may be revisited in a future version)
- password fields are now cloneable
- added filters for most of the plugin’s internal variables
- now using WordPress’ built-in jQuery UI for the datepicker field
- updated the screenshots
- updated the instructions in readme.txt
- pass additional params for
- fix bugs with datepicker
- remove all whitespace
- fix some bugs with the tinymce field
- fix display_callback for fields
- removed php opening shorttags
<?in favor of regular
<?phptags, which caused parse errors on some servers
- better tiny mce implementation and added html/visual switch
- small css fixes and added inline documentation
- moved DEFINEs in to admin_init() so that they can be filtered more easily
- Bug fix with group context on add meta box
- Remove few lines of old code left-over from 0.4
- Making the changes from 0.4 public
- Removed ability to generate option pages; after further consideration this is out of scope for this project
- Removed attachment_list field, useless
- Dates now save as unix timestamp
- Taxonomy fields now save as both a custom field and as their proper taxonomy (will consider adding the ability to enable/disable this in a future version)
- Multiplied fields no longer save as a serialized array, instead they save as multiple metadata with the same key (metadata api supports multiples!) – remember to set the last param to false to get multiple values.
- NOTE: currently multiplied fields will display out of order after saving, however this should not affect anything else other than the admin, should be fixed soon
- Other small improvements
- Enhanced the code which generates the different field types
- Added new types: password, upload, wysiwyg, datepicker, taxonomy_select, taxonomy_radio, attachment_list
- Added field multiplication ability
- Metadata is now deleted if a value is empty
- Can now also generate option pages which use a metabox interface
- Can now limit or exclude fields or groups from specific ids
- Added updated screenshots and new code samples!
- Bug fix: the custom display examples weren’t working well
- Bug fix: fields not showing on “Add New” page. Thanks Jan Fabry!
- Bug fix: fields not showing on “My Profile” page. Thanks Mike Tew!
- Added a textarea field type
- Added support for comments (you can now specify comments as an object type)
- Added basic styling for fields so that they look nice
- Initial release