Allows for more existing custom field names to be listed in the dropdown selection field when writing a post.
By default, WordPress only allows 30 custom field names/keys to be listed in the dropdown selection ‘Name’ field when writing a post or page. If you, or the plugins you use, make use of a lot of custom field key names, you may surpass the default limit resulting in some custom field keys not being listed. This may force post authors to manually type in custom field key names if they aren’t listed, which increases the chances for naming errors (typos, or not using the precise key name that is needed). This may also cause some authors concern wondering where previously used custom field keys have gone since they aren’t listed.
This plugin increases the limit to 200 custom field key names.
There is no settings page to customize the default value. If you’d like to list some number of custom field key names other than 200 (say, for example, 100), you can do so in either of two ways:
Note: This plugin has no effect for users who make use of the block editor (aka Gutenberg) introduced in WordPress v5.0 because that editor does not directly expose custom fields in the interface.
Links: Plugin Homepage | Plugin Directory Page | GitHub | Author Homepage
list-more-custom-field-names.zip
inside the plugins directory for your site (typically wp-content/plugins/
)WordPress only lists up to 30.
By default, this plugin lists up to 200. You can customize this value.
There are two ways you can customize this value (in both examples, change 100 to the number you’d like to use):
In your wp-config.php file (in the root directory of your blog), add the following line of code (making sure it is within the opening <?php
and closing ?>
PHP tags):
define( 'CUSTOM_FIELD_NAMES_LIMIT', 100 );
Somewhere — ideally in a mu-plugin or site-specific plugin, or less ideally your active theme’s functions.php file — hook the ‘c2c_list_more_custom_field_names’ filter and return the number you’d like:
add_filter( 'c2c_list_more_custom_field_names', function ( $limit ) { return 100; } );
This plugin has no effect for users who make use of the block editor (aka Gutenberg) introduced in WordPress v5.0 because that editor does not directly expose custom fields in the interface. The plugin is still beneficial for users making use of the classic editor.
Yes.
.gitignore
filecomposer.json
for PHPUnit Polyfill dependencycreate_function()
(as was done in filter example in v1.3.3)phpunit/
into tests/
phpunit/bin
into tests/
Full changelog is available in CHANGELOG.md.