Comments on: Safe Function Call v1.0

By: Scott

Scott — Thu, 07 Jan 2010 04:33:57 +0000

v1.1 of this plugin has been released. Please direct any questions or comments to the page announcing that release.

By: Scott

Scott — Fri, 30 May 2008 21:32:36 +0000

This functions provided by this plugin don't control if/when/how other functions are called or used. It only protects against the function not being available. For instance, if you had a plugin that provided the function todays_weather() and you activated the plugin and put that code into your sidebar, eveything would be fine. If you then deactivate the plugin, your site will throw an error because todays_weather() no longer exists. If you had wrapped that call in a Safe Function Call, you would've protected yourself from the error, i.e. . For what you're describing, you probably just want to use built-in WordPress functions to do what you want, i.e.


  if( is_page('about') ) {
    todays_weather();
  }

That code will only call todays_weather() if it is being viewed on the WP page with the name "about".

By: Steve

Steve — Fri, 30 May 2008 16:10:10 +0000

I’m trying to wrap my brain around this. Say I have a plugin I only need for a specific page templates, but prefer not to have it dump extra code in the head on all the other pages that don’t need the activated plugin. Would this be an appropriate use of Safe Function Call to pull in functions just for that template?

By: Scott Reilly: Two Weeks of WordPress Plugin Releases and Updates « Lorelle on WordPress

Mon, 07 Apr 2008 04:39:24 +0000

[...] Safe Function Call v1.0: Offers the ability to safely call functions not normally available from within a template, such as calling a function provided by a deactivated WordPress Plugin – great for intermediate to advanced WordPress users who like pushing the envelop with their WordPress blogs. [...]