Since the release of the WordPress Theme Customizer, my team and I have been more and more interested in using it as a way for users to make changes to the appearance of their theme without the use of the dashboard. As powerful as the dashboard is, the “Appearance” section creates a disconnect between what […]
I’m currently working on a lengthy set of articles that are intended to provide an in-depth look at the WordPress Theme Customizer. Yes, there has been a lot of material already written on this subject. Some of the best articles are: Otto’s guide to the WordPress Theme Customizer The comprehensive Codex article on the Theme Customization […]
It’s no secret that one of the things that I love most about the most recent versions of WordPress is the Theme Customizer (which is soon to be called the Customizer). I’ve talked about it in a number of different articles, some of which include: A Guide To The WordPress Theme Customizer Modular Procedural Programming […]
When The Customizer (once called The Theme Customizer) became part of WordPress, we saw a resurgence in the Theme Modification API.
At one point in WordPress history, the `get_theme_mod` and `set_theme_mod` was how we handled theme modifications (hence the function names). Then, we began to use the options table as a way to manage the various settings for our plugins.
And then we began to use the options table as an easy to way to store settings for our themes. It was like we moved the Theme Modification API to the backseat and pushed forward with options.
Should we have done that (or does it even matter)? And what’s the difference in these APIs, anyway? Why do we still have both of them, which is best to use and when?
When it comes to working with the WordPress Theme Customizer, one of the options that you’re likely to see in other themes (or that you’re likely to introduce in your own themes) is an option that is responsible for toggling the visibility of an element. For example, if a text box is empty, you may […]