This is a much safer query to use and will remove related entries from the postmeta and term_relationship, unlike deathlocks query in his answer. Change the {id} to the id of each blog posts table. You can combine this query to run all the post tables at once, but try this on one table first. … Read more
A short primer on WordPress development that might help or might confuse you: The main thing to keep in mind: it’s all just PHP. And also: don’t edit the core files of WordPress, because you will get in trouble when you update to a newer version later. The only code you should edit is that … Read more
Found a workaround below. I guess it has to do with a bug in the WordPress core. This will list ALL users in posts, so be cautious. // Filter to fix the Post Author Dropdown function author_override( $output ) { global $post, $user_ID; // return if this isn’t the theme author override dropdown if (!preg_match(‘/post_author_override/’, … Read more
Digging myself deeper in documentation, I got the following result. There is a way to group your custom blocks around a given category in Gutenberg, and therefore we have the method block_categories_all. So with a filter, you can extend the default categories with custom ones. Here is my example: add_filter( ‘block_categories_all’, function( $categories, $post ) … Read more
There is no query that will be 100% certain to delete everything unused and not delete those things because any theme or plugin can add options to the wp_options table. Still, with a little effort you can get a pretty good idea of what’s not in use and then manually decide which of those things … Read more
@s_ha_dum suggests that Post meta will be deleted automatically. Therefore because his reputation suggests he knows what he is talking about, this solution only handles Post attachments. I’d suggest checking out the docs for the before_delete_post() hook, as it’s quite handy to be able to check out what Post Type is being deleted, etc. add_action(‘before_delete_post’, … Read more
Your above function tests whether a page is a child page of some other page, not whether it has children. You can test for children of the current page like so: function has_children() { global $post; $children = get_pages( array( ‘child_of’ => $post->ID ) ); if( count( $children ) == 0 ) { return false; … Read more
In any foreach loop, the last value of the array being looped over remains after the end of the foreach loop. That is why one should actually always unset that value after the foreach loop is done. wp_list_pluck() is also just a basic foreach loop if $index_key is not passed. Also, as with any foreach … Read more
When submitting a plugin, the slug becomes the sanitized plugin name, as submitted. The “Name” of the plugin can change after this, but the slug remains the same forever more. When WordPress needs to check for a plugin update, it gets all the header information of the plugin and the directory name that the plugin … Read more
Using a class for encapsulation is a very common approach by a number of developers for plugins. I do this, and I do find it cleaner. But for plugins. Themes are more procedural by nature. We don’t do it for default WordPress themes because it raises the barrier to entry. The functions are quite simple. … Read more