I love WordPress, and I use it for most of my clients' sites. Between its built-in features, rich plugin ecosystem and endless learning resources/d...
For further actions, you may consider blocking this person and/or reporting abuse
Hi Tyler,
Always good to see some OOP in WP. Looks similar to a project I was developing a month ago, called Modern WordPress Website (github.com/Luc45/ModernWordPressWe...). I follow PSR-2.
Best,
Lucas
Interesting! I'll have to check Modern WordPress Website out, it looks pretty spiffy!
the link died unfortunately
Nice article. WordPress may not have a lot of modern php, but that doesn't mean my/our code cant. I may take some of your ideas and apply them to my own OOP functions.php boilerplate: github.com/vanaf1979/functionsphp Thanks.
I'm glad you potentially found some of these ideas helpful! I've been building out this class since I wrote this article. At some point I want to turn it into a Composer package so I can share easily among my themes and potentially with anyone else who is interested in it.
I really liked this post and played around with changing my construction process around it. Ultimately I didn't want to invest the time to properly figure out how to tackle filters or large $arg functions (I'm sure it's possible), but holy hell this option is elegant as hell declaring wp_ajax_ handlers. Just throw the name of the handler function in and you're set:
private function __construct()
{
$this->addAjaxHandler('feature_post' )
->addAjaxHandler('unfeature_post');
}
private function addAjaxHandler( $function_name ){
\add_action( 'wp_ajax_' . $function_name, function() use( $function_name){
self::$function_name();
} );
return $this;
}
I'm glad you got some value out of the post! I hadn't even considered using this for ajax, but I'll have to try it out at some point.
Yeah it works in this case since wp_ajax follows a standard naming convention with your function and PHP will natively try to execute a variable as a function if you put the () parens after, so declaring the function name pulls double duty here.
I have created a simple theme generator years ago, its purpose was mostly to prefix some functions and create all the standard files. I gave it to one of my newly hired colleagues once and as he was finishing his first project, translations were not working exactly because of this. It was fun looking for misspelling.
That's the worst! To some extent these kinds of mistakes are unavoidable, and probably a good a good argument for test driven development. I've got methods wrapping this functionality in this theme class because I'm using the same hooks over and over, but in most cases this approach is less than practical because of the sheer volume of hooks available.
Building a theme generator like the one you built sounds super cool. That's something I should definitely focus on learning soon.
Hey, thanks for your post !
I've been using it in a little library i'm currently building, it's time to treat wordpress as an object !
I hope it doesn't bother you 😇
gitlab.com/tgeorgel/object-press
I'm glad you found it useful. If you wanted to link to this article in your readme in would be appreciated but it isn't required. Best of luck with your library!
Of course, will do ;)
I am in the process of actually creating something very similar . what for wordpress is imperative is the possibility to dequeue or remove actions in a child theme. So each "add" method should have a mirroring "disable" or "remove" method.
You might be interested in Sage from roots.io - it’s a starter theme that makes WordPress MVC and uses Laravels blade engine
I'm a fan of Sage! I'm launching a site that I built with Sage next month, and I especially love having Blade in WordPress.
It's great for big data-heavy sites, though I tend to avoid it for smaller sites because it ends up feeling like too much tool for the job. Its folder structure can overwhelm me, and I sometimes feel like using PHP namespaces with WordPress feels like a "square block in a round hole" kind of thing.
The Blade templating though; I'll definitely be using Sage again in the future for that alone!
Yes - I’ve made similar observations - the templating is gold, and if you hook it up to advanced custom fields life gets so much easier!
Awesome!
Thanks Gabriel, I'm glad you liked it!
Nice article. I will apply some in my projects 😉
I'm glad you like it! I hope it's helpful in your projects.
Thanks Tyler for the post and for sharing classy gist!
Thanks for reading! I hope you got some value out of it.
Wonderful article. But my question is do we really need OOP for WordPress?
Nope, you definitely don't need to use an object-oriented programming approach for WordPress, though there are a few exceptions like the WP_Query object. I use this approach because it solved a pain point I was having with the functions file, but I only reach for OOP when it solves a problem that I'm having.
If the code looks like the spaghetti in the cover photo, I would want to fix it :)