Your arguments for both wp_get_attachment_image_url() and wp_get_attachment_image() are in the wrong order – check the linked documentation for details. Additionally, wp_get_attachment_image_url() returns a URL – not an actual image element. Removing the width and height attributes from <img> elements is inadvisable: if the layout of the page is in any way influenced by the size … Read more
At the beginning of wp_insert_post, the function that saves/updates a post, there is a filter called wp_insert_post_empty_content. By default this filter checks whether the title, editor, and excerpt fields are all empty, in which case the save process will be halted. However, since all the fields to be saved are passed to this filter, you … Read more
The underscore prefix are private, these meta fields will be hidden and will not be shown as custom fields in the post backend screens. Those meta fields without the underscore prefix are public fields and shows up as custom fields in the post screens
As the author of WPAlchemy, I’m a bit bias, but you essentially have a good working model outlined to follow depending on what ever route you choose. However, if using WPAlchemy, you would basically do something like the following (step #2): // functions.php include_once ‘WPAlchemy/MetaBox.php’; if (is_admin()) { // a custom style sheet if you … Read more
$post in the callback function is an array, not an object. So you cannot use $post->id. Change it to $post[‘id’] and it should work: function slug_get_phone_number($post, $field_name, $request) { return get_post_meta($post[‘id’], ‘_phone’, true); } I recommend to change _phone to phone_number or something else without underscore prefix. Because _ is often used with private meta … Read more
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.
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