How to create a WordPress plugin for another wordpress plugin?

3 comments

1. I think best way to do this is via actions and filters, like we extend WordPress core itself.

   Other options is like @helgatheviking pointed, if plugin is class you can extend it.

   Unfortunately not all plugin developers provide useful filters and actions with their code, most often plugin isn’t written in OOP manner. Only way to save your modifications on plugin update, is to create copy of original plugin, change plugin name. I usually prefix original name e.g. Mamaduka Twitter Connect, but with this solution you’ll need to manually update original plugin’s code.

   If you think that plugin needs more filters/action, you can contact the author and ask him to include those hooks into the core.

   Log in to Reply

2. One simple way would be to define custom hooks within your plugin that you can hook onto. The in-built hooks system allows for you to create your own hooks and then bind onto them like normal WordPress hooks. The WordPress Codex has great examples and explanations of the do_action function and how you can use it to create custom hooks. A seriously overlooked feature in WordPress by plugin and theme developers.

   I am a firm believer that the hooks system is all you need to develop plugins that can be extended by other plugins, but as I said seriously overlooked by 90% of all WordPress developers.

   See below for an example (taken from the WordPress Codex link provided):

   <?php 
   # ======= Somewhere in a (mu-)plugin, theme or the core ======= #
   
   /**
    * You can have as many arguments as you want,
    * but your callback function and the add_action call need to agree in number of arguments.
    * Note: `add_action` above has 2 and 'i_am_hook' accepts 2. 
    * You will find action hooks like these in a lot of themes & plugins and in many place @core
    * @see: http://codex.wordpress.org/Plugin_API/Action_Reference
    */
   
   // Define the arguments for the action hook
   $a = array(
        'eye patch' => 'yes'
       ,'parrot' => true
       ,'wooden leg' => (int) 1
   );
   $b = 'And hook said: "I ate ice cream with peter pan."'; 
   
   // Defines the action hook named 'i_am_hook'
   do_action( 'i_am_hook', $a, $b );
   
   # ======= inside for eg. your functions.php file ======= #
   
   /**
    * Define callback function
    * Inside this function you can do whatever you can imagine
    * with the variables that are loaded in the do_action() call above.
    */
   function who_is_hook( $a, $b )
   {
       echo '<code>';
           print_r( $a ); // `print_r` the array data inside the 1st argument
       echo '</code>';
   
       echo '<br />'.$b; // echo linebreak and value of 2nd argument
   } 
   // then add it to the action hook, matching the defined number (2) of arguments in do_action
   // see [http://codex.wordpress.org/Function_Reference/add_action] in the Codex 
   
   // add_action( $tag, $function_to_add, $priority, $accepted_args );
   add_action( 'i_am_hook', 'who_is_hook', 10, 2 );  
   
   # ======= output that you see in the browser ======= #
   
   Array ( 
       ['eye patch'] => 'yes'
       ['parrot'] => true
       ['wooden leg'] => 1
   ) 
   And hook said: "I ate ice cream with peter pan."
   

   Log in to Reply

3. FWIW, you can increase the plugin version number so that it doesn’t auto update. while its not the best solution, it’ll solve the immediate problem. You could also change the naming and filenames so that they aren’t the “same” plugin anymore.

   Log in to Reply