I just tested this and it works. <?php function toCall(){ global $wpdb; $togos = $wpdb->get_results(“SELECT * FROM $wpdb->postmeta WHERE meta_key=’_nelioefi_url'”); return $togos; } foreach (toCall() as $go) { global $wpdb; $wpdb->update( $wpdb->postmeta, array( ‘meta_key’ => ‘external_thumbnail’, // string // ‘column2’ => ‘value2’ // integer (number) ), array( ‘meta_id’ => $go->meta_id ) ); }; ?> You … Read more
Put simply, you don’t, and you shouldn’t The Problems Race Conditions Make the Data Super Unreliable Updating post meta, options, terms, etc is not an atomic operation. You need to fetch the view count, add 1 to it, then send it back to the database. During that process, another page load is occuring which does … Read more
You have created a custom field by altering the post table in the database. Custom fields in WordPress API are considered meta fields; such fields are stored in wp_postmeta table and that is the table used by functions like add_post_meta() and the rest of the functions and methods related with post custom/meta fields. You can … Read more
You need to use {old_status}to{new_status} hook. And use draft and publish statuses. This hook will only be executed when your post will change status from draft to publish. function wpse_288250_send_email( $post ) { $post_id = $post->ID; if( wp_is_post_revision( $post_id ) ) { return; } $post_url = get_permalink( $post_id ); $subject=”Your post is published!”; $message = … Read more
home.php is the file in the WordPress template hierarchy which is used for the posts page. However, after looking at the Twentyseventeen theme code on GitHub, there is no home.php file provided which means the index.php will be used instead. Within index.php Twentyseventeen then uses get_template_part to seperate reusable sections of code. The most general … Read more
Neither option are the correct option for your use case Your question is barking up the wrong tree, because you neglected to mention that you intend to search for these posts based on the values the meta holds. If you’re displaying a post, you can use either method, though the first is cleaner/simpler to handle … Read more
The documentation for this is contradictory, but I believe wp_sitemeta is meant to only store information for sites in the wp_sites table, which only stores the main site in a network. It would make more sense to store each site’s template_color in their individual wp_[BLOGID]_options tables. However, keeping the data as-is, you may be able … Read more
Pages are posts, you just need to change the post_type to page: $args_automobile_just_launched_bike = array( ‘posts_per_page’ => 3, ‘post_type’ => ‘page’, ‘order’ => ‘DESC’, ‘meta_query’ => array( array( ‘key’ => ‘wpcf-new-launch-bikes’, ‘value’ => ‘1’, ), ), );
the_field() function shows the value and it doesn’t get/return anything. Like the_title() and other template tags starting with the_. It means that: This line prints the value and $hero variable is empty. $hero = the_field(‘hero_title’); This line prints only <h1> tags. echo ‘<h1>’.$hero.'</h1>’; What you want is: echo ‘<h1>’ . get_field(‘hero_title’) . ‘</h1>’;
Maybe with SQL, but I wouldnt suggest it, so you have two options: Query a full list, and then check your condition on each post retrieved. or Save the product of those three fields in another meta field, which can then be queried. EDIT: For the second method, it really depends on the context. if … Read more