Adding function to hooks is runtime operation, it is not persistent. Whatever hook operation you run in Ajax actions – they are performed in separate WP instance and expire as soon as Ajax response is returned. They have no influence on currently loaded page. You probably need to hook your functionality to save_post as usual … Read more
just check inside the action ^^ add_action( ‘vc_before_init’, ‘vc_master_home_slider’ ); function vc_master_home_slider(){ if(is_plugin_active(‘some-plugin.php’){ //Do stuff. } }
Use the hooks added_term_relationship and deleted_term_relationships. These only fire when the relationship changes, as opposed to set_object_terms which always fires: function wpse_181090_object_terms_updated( $object_id ) { static $did = array(); // This function might fire multiple times for the same object, ensure it only runs once if ( ! isset( $did[ $object_id ] ) ) { … Read more
No, deactivated_plugin won’t fire during a plugin’s uninstallation process. But there are indeed two hooks that fire when a plugin is uninstalled: pre_uninstall_plugin, which is called right before a plugin is uninstalled. It acts globally, targeting any plugin. uninstall_{$file}, which fires after a specific plugin is uninstalled. Its scope it’s limited to a unique plugin … Read more
The answer when the question is about hooks is always either: timing, priority, or both. Consider the following code: add_action( ‘shutdown’, ‘wpse_258451_shutdown’ ); function wpse_258451_shutdown() { add_action( ‘init’, ‘wpse_258451_init’ ); } function wpse_258451_init() { wp_die( ‘I will never be called.’ ); } It should be obvious that the function wpse_258451_init() will never be called. This … Read more
The plugin probably (or: hopefully) used the $wpdb object, an instance of the wpdb-class, to add the custom table. If so (and only if so), then its author probably also uses $wpdb->insert() to add rows/ entries to the table. Taking a look at wpdb::insert(), and looking at its source, you will find out that this … Read more
All you need to do is to modify your method of restricting users. add_action( ‘admin_init’, function() { if ( (defined(‘DOING_AJAX’) && DOING_AJAX) || ( strpos($_SERVER[‘SCRIPT_NAME’], ‘admin-post.php’) ) ) { return; } if ( !current_user_can(‘manage_options’) ) { wp_redirect( home_url(‘/meu-perfil’) ); exit(); } }
You alluded to this in your comments, one way is to provide an API key for your plugin, that way your clients are actually paying for support and updates and not code, it’s really one of the only decent ways to go about this. For example if their API key is not valid or expires … Read more
Best Hook for that would be wp_insert_post_data function wpse44358_filter_handler( $data , $postarr ){ //do your stuff //if ($data[‘post_author’] == … return data; // make sure you return something } add_filter( ‘wp_insert_post_data’ , ‘wpse44358_filter_handler’ , ’99’, 2 );
You cannot check if an action will be called before that happens. Even if there were already callbacks attached to the action there would be no guarantee the matching do_action() will be used. In your case, test with is_plugin_active(): if ( is_plugin_active( ‘wordpress-seo/wp-seo.php’ ) ) { // do something } As @Barry Carlyon mentions in … Read more