So via lots of head banging and experimentation I managed to get a solution to letting editors/admins review the post whilst a previous one stays live is rather convoluted but does work. The key thing I did was to create a new post status which I call awaiting. In the admin it appears as “changes … Read more
Thanks to @AhmedMahdi’s comment I figured out the following works for my situation: select * from wp_posts where post_status=”publish” order by post_modified desc; The where condition is necessary to remove all the draft or private posts that I am not concerned with.
Having 2 revisions or 100,000 will not change front end performance in a default plugin-less WordPress setup However plugin and theme authors who do not query the database correctly, could end up accidentally searching/querying revisions, which could have some performance issues Here’s a snippet on it revisions take up space in your WordPress database. Some … Read more
I’m not one-hundred percent sure, what is failing for you, but I can tell you, generally it should work. The proof is following under thirdly. Before I have some remarks for you: Firstly, my guess would be, that it indeed isn’t failing silently, but while doing an AJAX process. So make use of a tool … Read more
I’ve often thought this would make a good feature, though I’ve never seen a plugin for it. I think the term “comment” is probably throwing off your search. I wouldn’t think that this would be stored as a comment internally, but rather as metadata for the post. I did a search for plugins using the … Read more
I just wasted a lot of time figuring this out. There are number of things a user should rule out first. Deactivate any plugins and switch to a default theme like twenty-thirteen if the below items do not work. To make sure that you don’t have revisions turned off, be sure this does not exist … Read more
I have the same problem before. I put WP_POST_REVISIONS in the end of wp-config.php file and it didn’t work correctly. You should put your codes before defining ABSPATH and before this line: /* That’s all, stop editing! Happy blogging. */ it must be something like in the following: define( ‘WP_POST_REVISIONS’, 6 ); /* That’s all, … Read more
Remove the action ‘wp_save_post_revision’ from ‘pre_post_update’. It is set per default in wp-includes/default-filters.php with the default priority (10). Add your own function to this hook. You get the $post_ID as parameter, so detecting the post type is easy. In your callback copy the code from wp_save_post_revision() but use the constant WP_POST_REVISIONS for the post type … Read more
There’s a private filter you can (but shouldn’t) access: Defined in wp-includes/revision.php: /** * Filter the list of fields saved in post revisions. * * Included by default: ‘post_title’, ‘post_content’ and ‘post_excerpt’. * * Disallowed fields: ‘ID’, ‘post_name’, ‘post_parent’, ‘post_date’, * ‘post_date_gmt’, ‘post_status’, ‘post_type’, ‘comment_count’, * and ‘post_author’. * * @since 2.6.0 * @since 4.5.0 … Read more
Unfortunately, there is no standardized best practice instituted by WordPress for hooking into Backbone templates. There have been plans suggested to bring the familiar filters and actions API to Javascript in WordPress, but there is a lack of traction in this movement. Carl Danley created a library which does just that, which is helpful if … Read more