New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| ↑ | Allows for more existing custom field names to be listed in the dropdown selection field when writing a post. | You have to log in to add a translation. | Details |
Original untranslated
Allows for more existing custom field names to be listed in the dropdown selection field when writing a post.
You have to log in to edit this translation. |
|||
| ↑ | List More Custom Field Names | You have to log in to add a translation. | Details |
Original untranslated |
|||
| Yes. The tests are not packaged in the release .zip file or included in plugins.svn.wordpress.org, but can be found in the <a href="https://github.com/coffee2code/list-more-custom-field-names/">plugin's GitHub repository</a>. | You have to log in to add a translation. | Details | |
Original untranslated
Yes. The tests are not packaged in the release .zip file or included in plugins.svn.wordpress.org, but can be found in the <a href="https://github.com/coffee2code/list-more-custom-field-names/">plugin's GitHub repository</a>.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| 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. | You have to log in to add a translation. | Details | |
Original untranslated
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.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Why don't I see form fields for adding/editing custom fields for a post, as mentioned by documentation for this plugin? | You have to log in to add a translation. | Details | |
Original untranslated
Why don't I see form fields for adding/editing custom fields for a post, as mentioned by documentation for this plugin?
CommentFound in faq header. You have to log in to edit this translation. |
|||
| <em>Note:</em> 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. | You have to log in to add a translation. | Details | |
Original untranslated
<em>Note:</em> 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.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| Links: <a href="https://coffee2code.com/wp-plugins/list-more-custom-field-names/">Plugin Homepage</a> | <a href="https://wordpress.org/plugins/list-more-custom-field-names/">Plugin Directory Page</a> | <a href="https://github.com/coffee2code/list-more-custom-field-names/">GitHub</a> | <a href="https://coffee2code.com">Author Homepage</a> | You have to log in to add a translation. | Details | |
Original untranslated
Links: <a href="https://coffee2code.com/wp-plugins/list-more-custom-field-names/">Plugin Homepage</a> | <a href="https://wordpress.org/plugins/list-more-custom-field-names/">Plugin Directory Page</a> | <a href="https://github.com/coffee2code/list-more-custom-field-names/">GitHub</a> | <a href="https://coffee2code.com">Author Homepage</a>
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| 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: | You have to log in to add a translation. | Details | |
Original untranslated
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:
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Install via the built-in WordPress plugin installer. Or download and unzip <code>list-more-custom-field-names.zip</code> inside the plugins directory for your site (typically <code>wp-content/plugins/</code>) | You have to log in to add a translation. | Details | |
Original untranslated
Install via the built-in WordPress plugin installer. Or download and unzip <code>list-more-custom-field-names.zip</code> inside the plugins directory for your site (typically <code>wp-content/plugins/</code>)
CommentFound in installation list item. You have to log in to edit this translation. |
|||
| 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: | You have to log in to add a translation. | Details | |
Original untranslated
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:
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| This plugin increases the limit to 200 custom field key names. | You have to log in to add a translation. | Details | |
Original untranslated
This plugin increases the limit to 200 custom field key names.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| 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; } ); | You have to log in to add a translation. | Details | |
Original untranslated
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; } );
CommentFound in description list item. You have to log in to edit this translation. |
|||
| (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 ); | You have to log in to add a translation. | Details | |
Original untranslated
(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 );
CommentFound in installation list item. You have to log in to edit this translation. |
|||
| By editing your wp-config.php file and at the end adding a line such as:↵ define( 'CUSTOM_FIELD_NAMES_LIMIT', 100 );↵ <em>-or-</em> | You have to log in to add a translation. | Details | |
Original untranslated
By editing your wp-config.php file and at the end adding a line such as:↵
define( 'CUSTOM_FIELD_NAMES_LIMIT', 100 );↵
<em>-or-</em>
CommentFound in description list item. You have to log in to edit this translation. |
|||
| 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 <code><?php</code> and closing <code>?></code> PHP tags): | You have to log in to add a translation. | Details | |
Original untranslated
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 <code><?php</code> and closing <code>?></code> PHP tags):
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
Export as
Comment
Short description.