Abandoned plugins should be avoided if at all possible – therefore:
If you use or plan to use posts as an event calendar, then I can recommend to display the posts thru the plugin “Content Views”. I have realized that I can filter posts also by status and so you don’t need a plugin like “No future posts”. I think this was not an option years back, but now it is (also in the free version which I use).
You can take a look here to see how it can work:
https://www.detfynskekammerkor.dk/wp/en/calendar-front-page/
Hello,
is it possible to exclude a specific custom post type, maybe directly in php code ?
thanks
It’s been over 2 years since this plugin has been updated.
Wordfence reports it *as* abandoned… Is it?
If it is abandoned, does anyone recommend a replacement?
]]>Is it possible to exclude some pages to show future posts, or set future posts only for a specific page type (archive for example) or a specific page?
]]>Hi,
The fix for the deprecated get_all_category_ids, proposed by @witters below, unfortunately throws a fatal error in some situations.
This is because get_terms returns an array of full term objects, but the function wp_update_term_count only needs (can only accept) the term_ids.
Proposed fix: (changes from line 118-125 in no-future-posts.php)
/**
* update post counts in categories
*/
static function update_count()
{
// $terms = get_all_category_ids(); // deprecated
$terms = get_terms( array(
'taxonomy' => 'category'
) );
if( $terms ) {
// build array of just the IDs for wp_update_term_count
$term_ids = array();
foreach( $terms as $term ){
$term_ids[] = $term->term_taxonomy_id;
}
wp_update_term_count($term_ids, 'category');
}
}Line 112 of no-future-posts.php uses get_all_category_ids() but this is deprecated from WP 4.0.0. (Turn on WP_DEBUG to see).
Use get_terms() instead
]]>I’ve got a funny bug keeping my subscriptions from auto firing. I wonder if this plugin, WHICH I LOVE, might be setting the renewal dates in the future as present and effecting them from auto-renewing.
]]>Hi,
Thanks for plugin.
There is a bug, if you are using WMPL plugin.
On list category you will see only category from current active language.
After update other language checkbox selection will drop.
The Plugin needs an update because it uses the get_all_category_ids function
Notice: get_all_category_ids ist seit Version 4.0 veraltet! Benutze stattdessen get_terms(). in /www/htdocs/****/wp-includes/functions.php on line 3573Hi, is this plugin still being maintend?
Since a few days, when we update a future post (event), we get a fatal error or white page and the new event(post) goes into scheduled status.
So it’s not showing up directly on the blog loop as usual.
Any help will be very much appreciated.
Thanks
]]>Following errors are occurring ONLY when creating a NEW POST
Warning: Missing argument 2 for wpdb::prepare(), called in /home/xxx/public_html/wp-content/plugins/no-future-posts/no-future-posts.php on line 74 and defined in /home/xxx/public_html/wp-includes/wp-db.php on line 992
Warning: Missing argument 2 for wpdb::prepare(), called in /home/xxx/public_html/wp-content/plugins/no-future-posts/no-future-posts.php on line 81 and defined in /home/xxx/public_html/wp-includes/wp-db.php on line 992
]]>Upgraded WP and all plugins to the latest. Getting this after when editing a post, in the header:
Warning: Missing argument 2 for wpdb::prepare(), called in /[…]/wp-content/plugins/no-future-posts/no-future-posts.php on line 74 and defined in /[…]/public_html/wp-includes/wp-db.php on line 990
Warning: Missing argument 2 for wpdb::prepare(), called in /[…]/wp-content/plugins/no-future-posts/no-future-posts.php on line 81 and defined in /[…]/public_html/wp-includes/wp-db.php on line 990
When publishing, a blank page with this shows:
Warning: Missing argument 2 for wpdb::prepare(), called in /[…]/wp-content/plugins/no-future-posts/no-future-posts.php on line 74 and defined in /[…]/wp-includes/wp-db.php on line 990
Warning: Missing argument 2 for wpdb::prepare(), called in /[…]/wp-content/plugins/no-future-posts/no-future-posts.php on line 81 and defined in /home3/escaso/public_html/wp-includes/wp-db.php on line 990
Warning: Missing argument 2 for wpdb::prepare(), called in /[…]/wp-content/plugins/no-future-posts/no-future-posts.php on line 74 and defined in /[…]/wp-includes/wp-db.php on line 990
Warning: Missing argument 2 for wpdb::prepare(), called in /[…]/wp-content/plugins/no-future-posts/no-future-posts.php on line 81 and defined in /[…]/wp-includes/wp-db.php on line 990
Warning: Cannot modify header information – headers already sent by (output started at /[…]/wp-includes/wp-db.php:990) in /[…]/wp-includes/pluggable.php on line 876
https://www.ads-software.com/extend/plugins/no-future-posts/
]]>This plugin did exactly what I wanted, until I updated to WP3.5.
The plugin gives the following errors:
Warning: Missing argument 2 for wpdb::prepare(), called in .../wp-content/plugins/no-future-posts/no-future-posts.php on line 74 and defined in .../wp-includes/wp-db.php on line 990
Warning: Missing argument 2 for wpdb::prepare(), called in .../wp-content/plugins/no-future-posts/no-future-posts.php on line 81 and defined in .../wp-includes/wp-db.php on line 990
Warning: Missing argument 2 for wpdb::prepare(), called in .../wp-content/plugins/no-future-posts/no-future-posts.php on line 74 and defined in .../wp-includes/wp-db.php on line 990
Warning: Missing argument 2 for wpdb::prepare(), called in .../wp-content/plugins/no-future-posts/no-future-posts.php on line 81 and defined in .../wp-includes/wp-db.php on line 990
Warning: Cannot modify header information - headers already sent by (output started at .../wp-includes/wp-db.php:990) in .../wp-includes/pluggable.php on line 876Can you please fix it for WP3.5?
https://www.ads-software.com/extend/plugins/no-future-posts/
]]>Your plugin works great however; It needs to sort posts by ascending order instead of descending. Any way to do this?
https://www.ads-software.com/extend/plugins/no-future-posts/
]]>