Working with the command line can be intimidating if you’re used to a nice graphical user interface (GUI), but it’s worth getting familiar with. There’s a lot of mundane tasks in web development can be automated with good set of scripts and shortcuts.
It’s also often much faster and simpler to accomplish a task with the command line, and in this respect WordPress is no exception. WP-CLI makes it possible for you to get your WordPress related tasks done with the help of a set of commands.
You might have a natural question in your mind: if the WordPress admin interface is so gorgeous and user-friendly, why would someone like to use the command line interface? There are two key reasons:
People find keyboard faster than the mouse: Instead of using mouse, a power user always prefer to use keyboard shortcut to accomplish a task. In general, using keyboard shortcuts is 3 times faster than clicking a mouse.
Automation:To make several commands execute automatically, you just need to put them into a single text file. Automation saves a lot of your precious time.
So in this guide, I’m going to give you a taste of WP-CLI: a command line interface for administering WordPress sites. Continue reading →
I’ve been working on a new theme that allows users to select certain pages in the customizer, and then display those pages out on a “showcase” template. I think this is pretty useful functionality and wanted to share how I implemented it.
Add Settings, Controls and Sanitization
First, we’ll need to the page select boxes to the customizer. In the code below, I add a new customizer section called “Showcase”. Then, I loop through the add_setting / add_control functionality in order to display four distinct page select boxes.
I’ve also created a function called “prefix_get_pages_array” which returns an array of all the pages to be used both by the controls and the sanitization function. You’ll notice it sorts the pages alphabetically, and indents sub-pages slightly with an em dash when output in the select box. Continue reading →
It’s surprisingly difficult to disable comments globally in WordPress.
Comments can be turned off for new posts in “Settings > Discussion” screen. However, all previously published posts would still retain their comment settings and need to be disabled individually under the “Discussion” metabox on the post edit screen (which can be very time consuming).
Disable Comments with One Click
The easiest way to turn off comments globally is actually with a plugin called “Disable Comments”, which is a free download from wordpress.org.
After enabling the plugin, you can choose to disable comments everywhere or only for specific post types. If you want the changes to be permanent, choose the “persistent mode” option before saving.
If you have chosen to make the changes permanent, the plugin can be deleted after you save the settings.
If a site was abandoned for a while or suddenly got hit by a lot of comment spam, you might want to delete all the pending comments or spam comments. For both of those scenarios, you can use a plugin called Delete Comments By Status.
Delete Comments By Status also allows you to delete “trash” comments and “approved” comments in bulk.
After enabling the plugin, go to “Settings > Delete Comments”.
One neat “feature” introduced in WordPress 4.1 was the removal of the background and header admin screens in favor of the customizer (see ticket). Now if you click to customize one of those items, it links directly to the customizer and opens the appropriate panel.
If your plugin or theme adds customizer options, you can also link to those. Just use:
If an excerpt is explicitly defined, it will be displayed (including HTML).
If an excerpt isn’t defined, the post content will be used, but stripped of HTML and truncated to 55 words by default. An indication that is has been truncated also displays “[…]”.
If a post consists entirely of a YouTube embed, a gallery, a single image, or a Tweet embed, “the_excerpt” will strip all that out- and thus nothing will be displayed. This makes for a very weird looking archive page if the_except is used.
The alternative is to use the_content. This allows the full content to show. But the content can also be truncated on archives by using more tag.
This is what I’ve been using in most of my new themes as it is the most flexible. Continue reading →
2015 will be a transformative year for language support in WordPress. The majority of new WordPress installs are now in languages other than English. New APIs are in the works for wordpress.org which should make translation easier, and new features in WordPress core will add better support for those languages. But what I’m really excited for is the eco-system in those other languages to grow.
Matt Mullenweg alluded to this at WordCamp Europe, “Personally, I am far and away most excited about the internationalization improvements, because the fact that WordPress has that many users at all in these other languages where there’s not very much documentation, no plugins, very few themes, it’s kind of amazing.”
Which brings me to a new project I’ve been working on with a partner based in France… Continue reading →
I released a new version of the Cascade theme with DevPress a few weeks ago, and I thought it would be worth writing about the process.
I learn a few new lessons with every new theme I build. This one was especially interesting because I was able to study the existing codebase, analyze all the choices that had been made by the previous author, and also learn a few new good tricks. Continue reading →