!is_admin()), or anywhere in the Admin Area EXCEPT the dashboard (e.g., via
get_current_screen()). It's just basic human decency.
I've been working on updating my collection of WordPress plugins for the imminent Gutenberg update. So far it has not required much time to learn, and the API is straightforward. It will however take significantly longer to integrate Gutenberg support into 20+ plugins. To help keep things organized, I will be posting tips and snippets here at DigWP.com. Blocks are the foundation of all things Gutenberg, so this first post is all about block recipes. Some of these code snippets are far less useful than others, hopefully they will be useful to others.
Technically, there is nothing special about showing code on a WordPress site. You just wrap code in
<pre></pre> (and probably
, for semantics and font control) tags, something like this:
WordPress ships with its own version of the jQuery library (for longevity's sake, as I write this WordPress is at version 3.2.1).
I posted a little tip on CSS-Tricks the other day about how you can load only parts of other pages on a site via Ajax, and how to do that without needing additional HTML wrapping elements to keep it clean. A common criticism of this is that the Ajax request still loads the entire page, using all that bandwidth, it's just that it only places onto the page the part you specify via CSS selector.
Sometimes it's hard to have discussions like this without looking at specific use case, but I see where they are coming from. Loading content you aren't going to use is a waste of bandwidth. It does make progressive Ajax enhancements a lot easier though. And in fact, that's how our All AJAX theme works.
Have you ever seen WordPress archives where you select something (usually a month/year) from a dropdown and it takes you to a page where you can view that? It's fairly common. WordPress almost has built in functionality for it, since you can specifically tell the
wp_get_archives() function that you want the values to be returned as
The goal here is to make a list of posts in the sidebar that show a number of recent posts. There will be a button you can click which will replaces those links to recent posts with older posts, AJAX style. You can keep clicking the button and keep getting older and older posts. On this site, we currently show 5 recent posts. So this little section shows the 5 posts after that, then clicking the button once will show 5 more older than that, and so on. This quick post outlines six steps to make it happen.
I was talking with Darren Hoyt recently about building a better interactive button1. The goal of the button was to provide three states: regular, hover, and active (pressed). That is standard of any good button, but we were going to integrate some fading effects into it to really making the button satisfying to interact with. Here is a demo, and in this tutorial we'll show you how to integrate it into WordPress.
On blogs that like to share snippets of code like this one, it is common to use the
<pre></pre> tag to wrap the code so that the spacing/indenting is maintained and long lines do not wrap. While this is desirable behavior, it can be undesirable to have those un-wrapped lines break out of their containers awkwardly and overlap other content.
I previously posted on how to include jQuery in your WordPress theme the Right Way. That is, to use the
wp_register_script function to register the script first. It's literally a one-liner in your header.php or functions.php file, but by default, it loads the internal version of jQuery that ships with WordPress.
If you want, you can just download jQuery, put it on your server and link to it from your
header.php file in the
<head></head> section. But that can cause you grief. For one thing, some plugins use the jQuery library, and they are going to load it as well. This can cause problems. How was your plugin to know you already had it loaded?