Comment ajouter des champs personnalisés automatiquement lors de la publication d’un article dans WordPress

17 commentairesLaisser une réponse

1. Syed Balkhi says

   Avr 27, 2024 à 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

   Août 8, 2013 à 9:29 am

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

   Répondre

3. nayan says

   Oct 30, 2011 à 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

   Répondre

4. chris says

   Mar 15, 2011 à 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?

   Répondre

5. puanthanh says

   Mar 1, 2011 à 3:59 pm

   it’s not adding to custom post type

   Répondre

   • Editorial Staff says

     Mar 1, 2011 à 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.

     Répondre

     Administrateur

     • puanthanh says

       Mar 1, 2011 à 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

       Répondre

6. brian says

   Fév 14, 2011 à 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?

   Répondre

   • Editorial Staff says

     Fév 15, 2011 à 2:36 pm

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

     Répondre

     Administrateur

7. Boba says

   Fév 2, 2011 à 5:26 am

   Thanks for including the source link

   Répondre

   • Editorial Staff says

     Fév 2, 2011 à 6:37 am

     Thanks for providing an amazing tip

     Répondre

     Administrateur

8. Daniel Suarez says

   Fév 1, 2011 à 10:30 am

   Thanks Otto another great tip!

   Répondre

9. Piet says

   Jan 31, 2011 à 11:06 pm

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

   Répondre

   • Otto says

     Fév 1, 2011 à 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.

     Répondre

     • Piet says

       Fév 1, 2011 à 4:43 am

       Thanks Otto, will play around with that a bit!

       Répondre

     • Editorial Staff says

       Fév 1, 2011 à 10:56 am

       Thanks Otto for the clarification.

       Répondre

       Administrateur

10. Vivek Parmar says

    Jan 31, 2011 à 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

    Répondre