Title: List More Custom Field Names Author: Scott Reilly Published: June 30, 2009 Last modified: April 17, 2025 --- Search plugins ![](https://ps.w.org/list-more-custom-field-names/assets/banner-772x250.png?rev= 824206) ![](https://ps.w.org/list-more-custom-field-names/assets/icon-128x128.png?rev=972944) # List More Custom Field Names By [Scott Reilly](https://profiles.wordpress.org/coffee2code/) [Download](https://downloads.wordpress.org/plugin/list-more-custom-field-names.1.4.1.zip) * [Details](https://mfe.wordpress.org/plugins/list-more-custom-field-names/#description) * [Reviews](https://mfe.wordpress.org/plugins/list-more-custom-field-names/#reviews) * [Installation](https://mfe.wordpress.org/plugins/list-more-custom-field-names/#installation) * [Development](https://mfe.wordpress.org/plugins/list-more-custom-field-names/#developers) [Support](https://wordpress.org/support/plugin/list-more-custom-field-names/) ## Description 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: 1. By editing your wp-config.php file and at the end adding a line such as: define(‘ CUSTOM_FIELD_NAMES_LIMIT’, 100 ); _-or-_ 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 to use: add_filter( ‘c2c_list_more_custom_field_names’, function ( $limist ) { return 100; } ); _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](https://coffee2code.com/wp-plugins/list-more-custom-field-names/) | [Plugin Directory Page](https://wordpress.org/plugins/list-more-custom-field-names/) | [GitHub](https://github.com/coffee2code/list-more-custom-field-names/) | [Author Homepage](https://coffee2code.com) ## Installation 1. Install via the built-in WordPress plugin installer. Or download and unzip `list- more-custom-field-names.zip` inside the plugins directory for your site (typically` wp-content/plugins/`) 2. Activate the plugin through the ‘Plugins’ admin menu in WordPress 3. (Optional) In wp-config.php, customize the number of custom fields you want shown. The default of 200 can be changed by adding a line like: define( ‘CUSTOM_FIELD_NAMES_LIMIT’, 100 ); ## 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. ### 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 blog), add the following line of code (making sure it is within the opening `` PHP tags): 2. ``` define( 'CUSTOM_FIELD_NAMES_LIMIT', 100 ); ``` 3. 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: 4. ``` add_filter( 'c2c_list_more_custom_field_names', function ( $limit ) { return 100; } ); ``` ### Why don’t I see form fields for adding/editing custom fields for a post, as mentioned by documentation for this plugin? 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. ### 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](https://github.com/coffee2code/list-more-custom-field-names/). ## Reviews ![](https://secure.gravatar.com/avatar/e30d59b16f2374933f06eec4afb83910c0a393d4d37812a899fd6fcbcceaf303? s=60&d=retro&r=g) ### 󠀁[Works like a charm.](https://wordpress.org/support/topic/works-like-a-charm-2387/)󠁿 [Lirkun](https://profiles.wordpress.org/lirkun/) March 12, 2025 Thank you! ![](https://secure.gravatar.com/avatar/afb75208fb1d4c5971a38c12d1ddefd05085b48b5d3c865b03fd1ae459175c14? s=60&d=retro&r=g) ### 󠀁[Easy Way to Solve a Small Problem](https://wordpress.org/support/topic/easy-way-to-solve-a-small-problem/)󠁿 [aisles](https://profiles.wordpress.org/aisles/) September 11, 2019 I hadn’t realised that there was a limit on the Custom Fields in the dropdown within the Page. This is a lovely little plugin to get around this problem. Thanks. [ Read all 4 reviews ](https://wordpress.org/support/plugin/list-more-custom-field-names/reviews/) ## Contributors & Developers “List More Custom Field Names” is open source software. The following people have contributed to this plugin. Contributors * [ Scott Reilly ](https://profiles.wordpress.org/coffee2code/) [Translate “List More Custom Field Names” into your language.](https://translate.wordpress.org/projects/wp-plugins/list-more-custom-field-names) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/list-more-custom-field-names/), check out the [SVN repository](https://plugins.svn.wordpress.org/list-more-custom-field-names/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/list-more-custom-field-names/) by [RSS](https://plugins.trac.wordpress.org/log/list-more-custom-field-names/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 1.4.1 (2025-04-17) * Change: Note compatibility through WP 6.8+ * Change: Note compatibility through PHP 8.3+ * Change: Update copyright date (2025) #### 1.4 (2024-08-20) * New: Add second argument to ‘c2c_list_more_custom_field_names’ for the preexisting limit * Change: Note compatibility through WP 6.6+ * Change: Update copyright date (2024) * Change: Reduce number of ‘Tags’ from `readme.txt` * Change: Remove development and testing-related files from release packaging * Unit tests: - Hardening: Prevent direct web access to `bootstrap.php` - Change: In bootstrap, store path to plugin directory in a constant * Change: Tweak formatting in `readme.txt` and `README.md` #### 1.3.9 (2023-06-06) * Change: Note compatibility through WP 6.3+ * Change: Update copyright date (2023) * New: Add `.gitignore` file * Unit tests: - Allow tests to run against current versions of WordPress - New: Add `composer.json` for PHPUnit Polyfill dependency - Change: Prevent PHP warnings due to missing core-related generated files _Full changelog is available in [CHANGELOG.md](https://github.com/coffee2code/list-more-custom-field-names/blob/master/CHANGELOG.md)._ ## Meta * Version **1.4.1** * Last updated **1 year ago** * Active installations **70+** * WordPress version ** 2.6 or higher ** * Tested up to **6.8.5** * Language * [English (US)](https://wordpress.org/plugins/list-more-custom-field-names/) * Tags * [admin](https://mfe.wordpress.org/plugins/tags/admin/)[custom fields](https://mfe.wordpress.org/plugins/tags/custom-fields/) [edit](https://mfe.wordpress.org/plugins/tags/edit/)[meta](https://mfe.wordpress.org/plugins/tags/meta/) [post](https://mfe.wordpress.org/plugins/tags/post/) * [Advanced View](https://mfe.wordpress.org/plugins/list-more-custom-field-names/advanced/) ## Ratings 5 out of 5 stars. * [ 4 5-star reviews ](https://wordpress.org/support/plugin/list-more-custom-field-names/reviews/?filter=5) * [ 0 4-star reviews ](https://wordpress.org/support/plugin/list-more-custom-field-names/reviews/?filter=4) * [ 0 3-star reviews ](https://wordpress.org/support/plugin/list-more-custom-field-names/reviews/?filter=3) * [ 0 2-star reviews ](https://wordpress.org/support/plugin/list-more-custom-field-names/reviews/?filter=2) * [ 0 1-star reviews ](https://wordpress.org/support/plugin/list-more-custom-field-names/reviews/?filter=1) [Your review](https://wordpress.org/support/plugin/list-more-custom-field-names/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/list-more-custom-field-names/reviews/) ## Contributors * [ Scott Reilly ](https://profiles.wordpress.org/coffee2code/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/list-more-custom-field-names/) ## Donate Would you like to support the advancement of this plugin? [ Donate to this plugin ](https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=6ARCFJ9TX3522)