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
Yes you can do that… define( ‘DISALLOW_FILE_MODS’, true ); Put this snippet in your wp-config.php file and you will able to disable core and plugin updates.
Never rely on core strings for translation, they may change or get a context parameter any time. Once that happens your users get a partially translated interface, and your translators have no way to fix that. Also keep in mind the same string is not necessary translated everywhere with the same word. Even without a … Read more
Do not just upgrade immediately. Take the time you need for an informed decision. And make a backup, of course. 🙂 Read the changelog for the new version. Example for 3.4.1. The blog announcements and the Codex pages are not complete. Test the upgrade with an exact copy of your production site, including plugins and … Read more
This should work: add_action( ‘woocommerce_init’, ‘remove_wcpgsk_email_order_table’ ); function remove_wcpgsk_email_order_table() { global $wcpgsk; remove_action( ‘woocommerce_email_after_order_table’, array( $wcpgsk, ‘wcpgsk_email_after_order_table’ ) ); }
the Best way to do this is have your X plugin made with its own hooks for actions and filters so new plugins (in your case Y) could interact with plugin X’s functions and data. Defining your own hooks is fairly easy and simple. Action Hook from the codex: Actions are the hooks that the … Read more
$pageID = get_option(‘page_on_front’); should get you the Page ID of the page set at ‘Front Page’ in WordPress options.
If you can stick to overriding just functions that are located in wp-includes/pluggable.php then you should be able to avoid any kind of plugin conflicts … unless you are using plugins that are overriding the same pluggable functions. Just make sure that your functions are declared before pluggables is loaded. Plugins are loaded before the … Read more
is_plugin_active() is rather fragile: it will break when either the plugin author renames the main file or when the user renames the plugin’s directory or main file. It’s better to check if a certain public function exists. To avoid having to make that check each time you need some of the plugin’s functionality, you could … Read more
That’s the total number of downloads. It includes direct downloads in the Repository and installs/updates done in the dashboard. Quotes from Otto comments in this 2010 article about the stats charts in every plugin’s page. […] the download count includes direct downloads as well […] There is no “raw count” anywhere on that version number … Read more