WordPress has two similar translation functions __() and _x(). The function _x() does the same thing as the function __() except the _x() function allows you to define a context for the translation (with the $context parameter). This is helpful when you have a string that could be two different words. For example there are two words that are spelled “tear” each with a separate meaning (and separate pronunciation). By including the context you could use both of these words and have them correctly translated based on their $context value.
By default all of the WordPress database tables will start with the prefix “wp_” (e.g. wp_users, wp_posts, etc.). Because this is the default value, you’ll often hear the tables referred to (and written about) using the “wp_” prefix. Let’s look at how and why this prefix is modified.
A list of the database tables (and the columns in those tables) used by a default WordPress installation. This is the companion blog post to my talk, “Introduction to the WordPress Database”.
In the WordPress database table “wp_term_taxonomy”, each row almost always has the same value for the two columns ‘term_taxonomy_id’ and ‘term_id’. What is the difference between these two columns?
While working on another post, I had some very large tables and I wanted to use Bootstrap Responsive Tables by adding the .table-responsive class but only in the situation where the table is too wide. This is the code I used.
In one of the slack channels I follow, the question came up on how to set WordPress posts older than a certain date to “draft” status using with WP CLI. I was surprised by how difficult I found this task and wanted to document my solution.
Recently I was working on a site using Advanced Custom Fields (ACF) and the field input boxes had stopped working. In the browser console, I saw the error “ACF Uncaught TypeError: Cannot read property ‘id’ of undefined”.
The WordPress plugin repository at wordpress.org/plugins is a great resource. I often use WP CLI to install plugins on my WordPress site from there, however, sometimes I want to install other plugins with WP CLI.
When creating new posts for a video demonstration, I wanted to display a consistent date. While my first thought was to reset my system clock, this snippet overrides the date when the post is first created, which worked for me.