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
Step 1 – Make sure things are formatted correctly WordPress itself depends on the headers at the top of your main plugin file. In many cases, if your plugin is “My Cool Plugin” this file is my-cool-plugin.php in the main directory of your folder. Make sure the top part of the file follows this format: … Read more
Use the filter update_option_{$option}. It runs after a successful saving. $option is the name of your option, and you get the old and the new value as parameters. From wp-includes/option.php: do_action( “update_option_{$option}”, $oldvalue, $_newvalue ); Use it like this for an option wpse_themesettings: add_action( ‘update_option_wpse_themesettings’, ‘wpse_check_settings’, 10, 2 ); function wpse_check_settings( $old_value, $new_value ) { … Read more
From what I understand Starkers 3.0 fits the bill. Do you want something this naked, or less?
add_action(‘admin_menu’, ‘my_remove_sub_menus’); function my_remove_sub_menus() { remove_submenu_page(‘edit.php’, ‘edit-tags.php?taxonomy=category’); remove_submenu_page(‘edit.php’, ‘edit-tags.php?taxonomy=post_tag’); }
Insert this into your wp-config.php // Enable WP_DEBUG mode define(‘WP_DEBUG’, true); // Enable Debug logging to the /wp-content/debug.log file define(‘WP_DEBUG_LOG’, true); // Disable display of errors and warnings define(‘WP_DEBUG_DISPLAY’, false); @ini_set(‘display_errors’,0); Before /* That’s all, stop editing! Happy blogging. */
As @tom-j-nowell said in comment to OP, multisite can make this easier. Performance and security are not really a problem for multisite (at least, not more than they are for regular installations), but I do agree that multisite can sometimes be a problem, because a lot of plugins (either custom or 3rd party) may not … Read more
Looking through some resources, I found this track ticket which discusses the same topic. It seems the following will stop it, add it to your wp-config.php: define(‘CORE_UPGRADE_SKIP_NEW_BUNDLED’, true);
It took me way too long to find this but all you have to do is set SCRIPT_DEBUG to true. Simply add this line to wp-config.php: define(‘SCRIPT_DEBUG’, true);
In general: Yes, wait for a dedicated hook to start your own code. Never just throw an object instance into the global namespace. But init is rarely necessary. You hook in as late as possible. If your first code runs on wp_head do not use an earlier hook. You can even cascade hooks: add_action( ‘wp_head’, … Read more