To answer this, I have gone and done some tests on this, and the results was actually mind blowing. Here is my test To this yourself, set yourself up with a test page. Just simply copy page.php, rename it and delete the loop. Now just create a new page in the back end. Before you … Read more
The action hook save_post is called on save, but i don’t know if you can add metadata at this time. But it should be possible to create/update your meta data after the post was saved with the action hook updated_post_meta. EDIT To pre-select some meta fields (custom fields) on the post creation screen, you have … Read more
There are no convenient hooks to add something to that box. You could do one of two things. 1. Add a new Meta Box You do this by hooking into the add_meta_boxes action and calling add_meta_box. You can specify a callback function in your call to add_meta_box. That callback will take care of echoing out … Read more
Pages do have Custom Fields enabled by default on WordPress. If you’re not seeing them on the “New/Edit Page” page, then check the “Screen Options” pull down tab on the upper right corner of your Dashboard. See if “custom fields” is checked.
You can stop the post from saving all together with minor JQuery hacks and validate the fields before saving on the client side or server side with ajax: first we add our JavaScript to capture the submit/publish event and use it to submit our own ajax function before the actual submit: add_action(‘wp_print_scripts’,’my_publish_admin_hook’); function my_publish_admin_hook(){ if … Read more
I don’t think it’s the WordPress 4.8.1 release doing that: but, do you have Advanced Custom Fields Installed? If you do, their release 5.6.0 hides the default WordPress custom fields meta box by default. remove_wp_meta_box We added in a new setting in v5.5.13 allowing the default WP custom field metabox to be removed. Although simple, … Read more
Thanks for your code. I’ve investigated this issue further (this is not an integer formatting problem). The only solution I came up with for number fields is to monkey patch more WP JS. Here is entire code with modifications which supports any input type: add_action(‘print_media_templates’, function(){ ?> <script type=”text/html” id=”tmpl-custom-gallery-setting”> <h3>Custom Settings</h3> <label class=”setting”> <span><?php … Read more
From the looks of things, your safest bet and easiest route would be to fork the More Fields plugin specifically for your use. The two biggest features I can see your fork needing are a field “factory” and a drag-and-drop interface. Multiple Fields My suggestion would be to look at the WordPress Widget class and … Read more
Solution from a cross post over at StackExchange from @birgire: The problem is that you run the clientarea_default_order callback too late. To fix that you only have to change the priority from the default one that’s 10: add_action( ‘pre_get_posts’,’clientarea_default_order’); to the priority of 9: add_action( ‘pre_get_posts’,’clientarea_default_order’, 9 ); But you don’t actually need two pre_get_posts … Read more
Both usermeta.meta_value and postmeta.meta_value are stored as LONGTEXT. Here’s how the MySQL docs describe the size of a LONGTEXT data type: “A TEXT column with a maximum length of 4,294,967,295 or 4GB (232 – 1) characters. The effective maximum length is less if the value contains multi-byte characters. The effective maximum length of LONGTEXT columns … Read more