The official documentation for wp_untrash_post documents a filter for setting the status that it will use: https://developer.wordpress.org/reference/functions/wp_untrash_post/ This filter can be used to return pending instead as the status. If that’s not an option though, you could set the post status to pending after calling wp_untrash_post, it doesn’t have to happen in a single function … Read more
For this I suggest you to use given solution which ensure each post is processed individually without interrupting the batch processing, and also allowing soft deletion to work for both emptying the trash and bulk actions. You need to update the softDelete function with the given code. function softDelete( $postId ) { if ( get_post_type( … Read more
Changing Post Status from Pending to Publish twice daily
Yes, authentication is needed, because the Posts endpoint will check whether the current user has the edit_posts capability – see WP_REST_Posts_Controller::sanitize_post_statuses(). Also, a HTTP status of 401 normally indicates that authentication is required. So try again, but with an authenticated request, i.e. make sure the current user is logged-in and has the edit_posts capability.
When using get_terms with hide_empty = true, terms that only contain scheduled posts are not returned. How to override this?
How can I make a custom post status private or draft?
After thorough investigation, I identified the root cause of the issue. TL;DR: A bug in my JavaScript code was causing the post form to be submitted without the necessary publish parameter. Consequently, WordPress interpreted the request as an attempt to save a draft. I resolved the issue by updating the code to include the publish … Read more
You have to supply post_modified and post_modified_gmt to a date in the future. Otherwise the “future” date will be in the past, and the post will become published. For example: wp post update 6868 –post_status=future –post_date=”2023-08-26 15:11:29″ –post_date_gmt=”2023-08-26 22:11:29″
Yes, editPost is a wrapper around editEntityRecord which according to the core/data docs takes an options object that supports undoIgnore: options Object: Options for the edit. options.undoIgnore [boolean]: Whether to ignore the edit in undo history or not. While you could use this, generally the need to use it implies a mistake or misunderstanding somewhere, … Read more
The problematic line is the one for the transition_post_status action’s callback as the input parameter is post status (string) but not post ID (integer): https://developer.wordpress.org/reference/hooks/transition_post_status/