There are two common solutions to access classes in a plugin from inside a theme: 1. Use an autoloader in the plugin (preferred). You tell the autoloader how to relate a class name to a PHP file name that contains the class. Then, when you access a class that is not yet known to PHP, … Read more
WordPress itself is not very object oriented – it has objects (like WP_User, for example), but most interactions with the core API take place through plain function calls. It also depends widely on global state, though it does a good job of managing this through the abstractions of actions and filters. In my experience there … Read more
Give it a try like so: File: oowp/bootstrap.php <?php /* Plugin name: OOWP */ require_once( ‘autoload.php’ ); use oowp\objects\Custom_Objects; new Custom_Objects;
The reason that the plugin activation hook wasn’t working in the code provided in the question is that on plugin activation the plugins_loaded hook is never run. Since the register_activation_hook hook was hooked from plugins_loaded it was never run on activation. And since it’s never fired ever again, this way of hooking results in register_activation_hook … Read more
I’m not entirely sure what you want to do exactly. But basically you just create one instance and then add functions like public static function FunctionName() to be used anywhere you want after the plugin got activated. To fire your hooks simply use the public function __construct(). Taking the Sample Plugin from below, the FooBar … Read more
AFAIK $query->get for main query works only with public query vars, i.e. vars that can be triggered via url, but nothing prevents to directly access directly to tax_query property of query, but notice that it is an object, instance of WP_Tax_Query and the current queried taxonomy arguments are in the queries property of that object. … Read more
An alternative way is to use static class methods in plugins, and optionally write functions as alias: in Plugin: class Pluginslug_Foo { static $foo = ‘Bar!’; public static function bar() { return self::$foo; } } if ( ! function_exists( ‘pluginslug_bar’ ) ) { function pluginslug_bar() { echo Pluginslug_Foo::bar(); } } in Theme: if ( function_exists( … Read more
Technically, it is possible. But I would use a slightly different approach. If your second plugin is loaded first you get an error. If you want to replace the class in another plugin, it is hard to do this. So hook into plugins_loaded with a specific priority to create the object and use the object … Read more
You can simply put your init code within the constructor of the class. For example: class myWidget extends WP_Widget{ function myWidget(){ // Init code here } function widget( $args, $instance ) { // The widget code wp_enqueue_script(…); wp_enqueue_style(…); } // Over methods… } register_widget(‘myWidget’); My preference is to actually put the enqueue calls within the … Read more
The errors I’ve spotted in your code: One was pointed by @helgatheviking in a comment: the Ajax callback has to be a public method, not private. Not sure how are you initializing this class, but wp_enqueue_script&_style (in singular) has to be encapsulated inside a wp_enqueue_scripts hook (WP_DEBUG dumps a notice). You can drop the & … Read more