List More Custom Field Names

FAQ

What is the default number of custom field names/keys that WordPress lists in the admin when writing/editing pages and posts?

WordPress only lists up to 30.

How many custom field names/keys does this plugin list in the admin when writing/editing pages and posts?

By default, this plugin lists up to 200. You can customize this value to anything equal to or above the WordPress default of 30.

How can I customize the default number of custom field name/keys listed in the admin when writing/editing pages and posts?

There are two ways you can customize this value (in both examples, change 100 to the number you’d like to use):

1. In your wp-config.php file (in the root directory of your site), add the following line of code (making sure it is after the opening <?php PHP tag (and before the closing ?> PHP tag if one is present):

   define( 'CUSTOM_FIELD_NAMES_LIMIT', 100 );
   

2. 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; } );
   

Does this affect which custom field keys are shown?

This plugin only affects how many custom field keys WordPress includes in the dropdown. WordPress will return the configured number of custom fields from the full alphabetized list of all custom field keys. WordPress excludes private custom field keys, which will continue to be hidden.

Is it possible to include all available custom field keys?

Currently with this plugin this is only possible by explicitly configuring a high enough value such that it exceeds the number of custom field keys in use.

Programmatically, the plugin’s filter could be hooked by code that determines the exact number of custom keys and then uses that value.

Can configuring a large enough number affect page loading performance when editing a post?

Yes, but it depends on the number you’ve configured and the actual number of custom field keys in use on the site. If you’re showing just a few hundred, you should be fine. (Anything more and the dropdown might become unwieldy anyhow.) Simply lower the value if you feel the page load has been slowed (and verify that the change actually sped things back up).

Why don’t I see form fields for adding/editing custom fields for a post, as mentioned by documentation for this plugin?

The block editor does not expose the “Custom Fields” meta box by default, so it may not be shown. Plugins (such as Advanced Custom Fields) may also hide the meta box for custom fields. This plugin has no effect on the presence of the “Custom Fields” input fields or their functionality.

Is this plugin tested through PHP 8.5+?

Yes.

Does this plugin have unit tests?

Yes. The tests are not packaged in the release .zip file or included in plugins.svn.wordpress.org, but can be found in the plugin’s GitHub repository.