Cómo añadir campos personalizados automáticamente al publicar una entrada en WordPress

17 comentariosDeja una respuesta

1. Syed Balkhi says

   Abr 27, 2024 en 2:24 pm

   Hey WPBeginner readers,
   Did you know you can win exciting prizes by commenting on WPBeginner?
   Every month, our top blog commenters will win HUGE rewards, including premium WordPress plugin licenses and cash prizes.
   You can get more details about the contest from here.
   Start sharing your thoughts below to stand a chance to win!

2. Sateesh Raghuwanshi says

   Ago 8, 2013 en 9:29 am

   I need to add this action for custom post type named ‘ad_system’

   Responder

3. nayan says

   Oct 30, 2011 en 12:52 am

   I want to add category Id for the post in the post_meta table. How can be the function function add_custom_field_automatically($post_ID) be twicked to accomodate that?

   Thanks

   Responder

4. chris says

   Mar 15, 2011 en 8:30 pm

   Instead of adding the custom field at the time of creating the post, how do I display a custom field by default on the admin page?

   Responder

5. puanthanh says

   Mar 1, 2011 en 3:59 pm

   it’s not adding to custom post type

   Responder

   • Editorial Staff says

     Mar 1, 2011 en 7:03 pm

     If you notice, the code above doesn’t have anything related to the custom post types. It only adds to Post and Page “content type”. So you would have to specify the hook for your custom post type.

     Responder

     Administrador

     • puanthanh says

       Mar 1, 2011 en 8:00 pm

       Thanks for the reply. Can you help me out on this code.
       add_action(‘publish_page’, ‘add_custom_field_automatically’);
       add_action(‘publish_post’, ‘add_custom_field_automatically’);
       add_action( ‘save_post’, ‘add_custom_field_automatically’ );

       function add_custom_field_automatically($post_ID) {
       global $post;
       if(!wp_is_post_revision($post_ID)) {
       global $wpdb;
       $user_id = $wpdb->get_var("SELECT post_author FROM $wpdb->posts WHERE ID = $post_ID");
       $themename = $wpdb->get_var("SELECT meta_value FROM $wpdb->usermeta WHERE meta_key = ‘themeperauthor’ AND user_id = $user_id");
       add_post_meta($post_ID, ‘themeperauthor’, $themename, true);
       }
       }
       When the user meta field is changed, I want to automatically delete the custom field value and update with the new one

       Responder

6. brian says

   Feb 14, 2011 en 7:06 pm

   I’ve been working on adding some hidden custom fields on post publish/update (by preceding the field name with “_”) but for some reason I have to update the post twice before the wp_postmeta entries are written to the database.

   I’ve tried messing with the priority and experimenting with other action hooks (draft_to_publish, edit_post, etc) but it doesn’t seem to make a difference.

   Any ideas?

   Responder

   • Editorial Staff says

     Feb 15, 2011 en 2:36 pm

     are you using Otto’s trick with the transient API?

     Responder

     Administrador

7. Boba says

   Feb 2, 2011 en 5:26 am

   Thanks for including the source link

   Responder

   • Editorial Staff says

     Feb 2, 2011 en 6:37 am

     Thanks for providing an amazing tip

     Responder

     Administrador

8. Daniel Suarez says

   Feb 1, 2011 en 10:30 am

   Thanks Otto another great tip!

   Responder

9. Piet says

   Ene 31, 2011 en 11:06 pm

   will this work too for custom post types?
   sth like add_action(‘publish_custom-post-typ-name’, ‘add_custom_field_automatically’);

   Responder

   • Otto says

     Feb 1, 2011 en 4:39 am

     Yes, it will.

     One downside to this technique that people should be aware of is that if somebody edits a published post, this hook WILL get fired again on the edit. Therefore, you need to check for the meta before adding it, or to update it, or to do whatever makes the most sense for your use-case.

     If you only want to get your code fired off on the initial publish only, then you can use the transition_post_status hook. This hook works like this:

     
add_action('transition_post_status','example',10,3);
function example($new, $old, $post) {
// $new is the new post status ('publish')
// $old is the old post status ('draft')
// $post is the complete Post Object (so use $post->ID for the ID, etc)
}


     Then, in here you can do a check for something like this:
     
if ($new == 'publish' && $old != 'publish')


     To have your code only used when the post status actually transitions to publish from whatever it was before. This hook is fired at the same time as the {$status}_{$post-type} hooks are, so the operation of them is basically the same.

     Responder

     • Piet says

       Feb 1, 2011 en 4:43 am

       Thanks Otto, will play around with that a bit!

       Responder

     • Editorial Staff says

       Feb 1, 2011 en 10:56 am

       Thanks Otto for the clarification.

       Responder

       Administrador

10. Vivek Parmar says

    Ene 31, 2011 en 12:05 pm

    thanks for this handy tip. previously while using custom fields i have to work manually. now this will do it automatically. thanks for saving precious time of me

    Responder