Below you will find pages that utilize the taxonomy term “wordpress”
In an earlier post, I described a method of including an automatically updated age in a WordPress post using a shortcode.
In this post, I’ll show you another shortcode based on PHP’s DateTime extension and the diff method that will generate a string composed of the number of years, months, and days from a specified date.
The Code To include an automatically updating string composed of the years, months, and days from a specified date in WordPress using PHP, start by adding the following code to your child theme’s functions.
There are plenty of WordPress plugins out there that will quickly and easily add social media share buttons to WordPress posts. However, that ease-of-use comes with a price: those plugins frequently include far more functionality than you need. Since they’re typically designed to handle every conceivable social media platform, they include a lot more code, images, and web fonts than you need, if all you’re doing is adding Facebook, Twitter, and LinkedIn share buttons to your posts.
Most people these days know not to click links in suspicious emails; however, what if one of your WordPress site’s harried administrators or editors receives an authentic-looking email from the developers of one of the plugins the site relies on? The email asks them to click a link to provide an application password to increase the security/features or to continue to use the plugin?
WordPress 5.6 is due for release today, and one of its new features, Application Passwords, is a cause for concern among some security experts.
I often need to put the ages of people and events in a WordPress post, and the last thing I want to do is to come back and update them each year when the age(s) will no longer be correct.
If you’re like me, since the Gutenberg editor came out with WordPress 5.0, every time you edit an old page or post and see that “Classic Block,” you have trouble resisting the temptation to click the “Convert to Blocks” link.
Maybe you just have some major edits to do on an old page, or you want to convert a post with a whole slew of individual images to a Gallery Block.
I really like WordPress’ Twenty Sixteen default theme. It’s clean, well-designed, and versatile. With a child theme based on Twenty Sixteen, customizations are easily accomplished. I’ve used it as the basis for several sites. There is one thing I like to change.
Most sites need a Search widget. The logical place to put a Search widget on a Twenty Sixteen site is at the top of the Sidebar widget position.
Note: There is a newer version of the code in this post tested with WordPress 5.2.4 and WooCommerce 3.8 in the post WooCommerce 3.8: Send a Notification Email When a Customer Changes Their Address.
I have a client who runs a subscription-based business on a WordPress site using WooCommerce. Since some of his subscriptions last a year or more, increasing the likelihood that a customer’s address might change, he wanted to be notified by email if the customer used the WooCommerce change-of-address form.
Contact Form 7 is my favorite contact form plugin for WordPress. Not only is it well-documented on the developer’s web site, but it offers a plethora of valuable features that have made it my go-to contact form. One of those features is Contact Form 7’s ability to use variables in the URL ($_GET variables) to set the default value for email form fields.
Contact Form 7’s documentation explains in detail how to set the default value of text fields to $_GET variables passed in the URL; however, as of this writing, it doesn’t tell you that you can also set the default value of a select field by passing the value of the field in the URL.
A WordPress plugin on one of my client’s sites was filling up the error log with a PHP error “undefined index” for the server variable SCRIPT_NAME. The error persisted through a number of plugin updates. I found that I could work around it by editing the plugin’s code and substituting the server variable PHP_SELF instead of SCRIPT_NAME, but it was a hassle to modify the code for the plugin every time there was an update, and I wanted to find a permanent fix.
It was not only embarassing; it was puzzling.
I was contacted by a client whose site was returning the dreaded WordPress “this is somewhat embarassing, isn’t it?” 404 not found error message whenever he tried to access some of his pages. The affected pages all included custom variables in the URL following pretty permalinks based on the post name.
The site had functioned flawlessly when we tested it, but that was back before WordPress 4.
I posted about how to automate the Diverse Solutions dsIDXPress Property Slideshow Widget yesterday. As of this writing, the Property Slideshow widget is designed to limit the listings to a city, state, and/or zip code, but it doesn’t allow the listings to be limited to a particular office. My client wanted a slideshow that included only her office’s properties.
Enter the Diverse Solutions dsIDXPress IDX Listings widget. The Listings widget does allow the listings to be limited to those of an agent or an office, but the slideshow it comes with is not automated, either, so I wrote a little script to automate it.
One of my clients is a real estate broker who uses the Diverse Solutions dsIDXPress plugin to display MLS listings on her site.
One of the things I like about Diverse Solutions’ dsIDXPress plugin is that it uses Internet Data Exchange to display the MLS data instead of using a frame like so many other MLS plugins.
Unfortunately, at the time of this writing, the Property Slideshow Widget is not automated, and it doesn’t offer much in the way of configuration options.
One of my clients uses the plugin Woocommerce Order/Customer CSV Export to export his customers’ orders into a spreadsheet for managing a mailing list. The other day, he emailed me to tell me that instead of being prompted to download the CSV when he clicked the “Export” button, he was getting a nasty screen-full of text.
It took a while to troubleshoot, but it turned out the problem was caused by the 34,000+ records that CSV Export had inserted into the WordPress comments and commentmeta tables.
I recently built a WordPress site for an artist named Jerry Cave. One of the interesting aspects of the job was that he wanted to sell both originals and prints of his work on the site, but he expected his sales volume to be low, and didn’t want to spend the money to have me install, configure, and maintain a full-fledged e-commerce plugin like Woocommerce until he saw how many sales the site generated.
In April of this year, Yahoo changed its Domain-based Message Authentication, Reporting and Conformance (DMARC) authentication policy. Suddenly, when a user submitted an email using Contact Form 7–and some other WordPress contact form plugins’ forms–using a Yahoo email address, the messages were permanently rejected by some web hosts.
Yahoo is simply trying to reduce the amount of fraudulent emails by rejecting emails using Yahoo email addresses sent from non-Yahoo servers, but It was a really unpleasant surprise for a lot of web developers.
Many of WordPress’ default themes come with a style sheet called editor-style.css that overrides the built-in style sheet for TinyMCE, making the font a bit larger and more legible in WordPress. Unfortunately, a number of themes don’t override any of the default TinyMCE styles.
In a previous post on optimizing WordPress, I suggested configuring WordPress so that revisions are not saved, and to delete old revisions to make the wp_posts table smaller and faster to query, but I didn’t mention how to do it. That’s because there is a little more to deleting old revisions than many posts on the web, and some plugins designed to delete revisions, would have you believe.
Several months ago, in his WordPress.
I have been dealing with a WordPress site that was consuming a lot of resources on the server on which it is installed. In the course of discussing the problems I was seeing with the web host’s support team, the support representative suggested that I try W3 Total Cache instead of WP Super Cache to see if it improved the site’s loading time and reduced the resource usage for the site.
I am very impressed with WordPress, and over the past several years it has become my web platform of choice, but the fact is, more and more I find myself in the position of trying to find ways to make it more efficient. I don’t think this has anything to do with WordPress itself. Installed alone (no plugins) with a basic theme, it’s pretty efficient, but who wants to use it that way?
It’s a rare and wonderful feeling when I come across a development tool that gives me that, “Where have you been all my life?” feeling. Firebug was one. GoDaddy’s P3 (Plugin Performance Profiler) is another.
I formally used a variety of web-site performance testing sites in order to measure the loading speed of sites I developed, but often pinpointing problem WordPress plugins meant testing with the plugin deactivated, re-testing with the plugin activated, going one-by-one through a site’s plugins, or poring through the server logs to find the resource hogs.
Advanced Home Inspection’s site is another project that I developed in partnership with a designer. Its development illustrates one of the conundrums of WordPress development. What theme should be used for the new site?
There are basically four choices:
Use a default theme. Use a free WordPress.org theme. Purchase a commercial theme. Create a one-off theme from scratch. Of course, I am an advocate of always using a child theme, no matter the source of the parent theme.
Sometimes, no matter how much they try to plan ahead, a small business owner ends up in a time crunch. Whatever it is suddenly needs to get done right now. Now and then, that “whatever” ends up being their web site. Such was the case for Cari Ordway, the owner of Bead Divine, a company specializing in beaded items, classes, workshops, and retreats on beading and beaded-jewelry design.
Cari’s new web site had been in the planning stages for a while, but she found herself scheduled for a number of upcoming events within the next few weeks and wanted to make sure she had some kind of web presence in place–even a temporary one–in time for them.
The Law Offices of David Carron
Only a person who works with WordPress a lot would recognize the theme used for David Carron’s web site, and even they might have to peek at the source code to identify it.
David’s site is built using a child theme based on the default WordPress theme Twenty Twelve. The main menu has been moved, the tag line is in a new location, there is a custom logo replacing the site title, and a slider has been added to replace the default header image.
The Armarium Press
I had a lot of fun migrating The Armarium Press from its previous, conventional HTML home to a new WordPress site.
The old site was pretty much straightforward HTML, and the client wanted to incorporate a number of new features that would have to have been added piecemeal using open-source software or developed at significant cost if they had gone with a one-off approach. WordPress came to the rescue again.
The Advent Lutheran Church site was a 1and1 MyWebsite account, but it really wasn’t meeting the needs of the congregation or the parishioner who was voluntarily maintaining the site.
When they contacted me about options for adding some features to the site, I recommended a migration of the site to WordPress and the replacement of their hard-coded event calendar with a database-driven WordPress plug-in event calendar. With the addition of the event calendar, they not only had the ability to create recurring events with a single data entry, but can easily maintain a much more flexible, dynamic event-handling system.
I originally built the Classic Cougar Community as a Joomla! 1.0.x site back in 2007. When Joomla! 1.5.x debuted, the client had me migrate the site to the new version. Now, Joomla! is up to version 1.7.x, but currently there is not a simple, straight upgrade path from Joomla! 1.5.x to 1.7.x; it’s a migration.
The success he’s experienced with other WordPress sites led my client to opt for migrating the site to WordPress, a platform that in my experience is much easier–and less costly–to maintain and upgrade, rather than to migrate it to the newest version of Joomla!
The Oregon Dreamery
One of the most enjoyable parts of my job is helping small businesses build a professional-looking web presence inexpensively and efficiently from the ground up.
The Oregon Dreamery is one such project. The Dreamery did have a site, but it was a conventional HTML web site on a somewhat limited host with another domain name that was difficult for them to manage, hard to upgrade, and limited in functionality.
Mercury Cougar XR7-G Registry
Cougars are solitary animals, and don’t travel in packs, but this month, a whole pride of Cougars arrived at my door, and I learned more about classic Mercury Cougars than I ever would have believed possible. One of my best clients, a classic Cougar collector, commissioned me to migrate the classic Cougar registries from their previous web hosts to a new home. Several days after agreeing to the job, I received a set of CD-ROMs in the mail containing the HTML for the three sites.
ByLanderSea is a WordPress-based blog-style site that I “inherited.” I met Debi Lander, the author of ByLanderSea, through my work with BCT Publishing and Automotive Traveler, for whom she occasionally acts as a contributing author of travel and automotive articles.
I include it here not only because the site has some great articles, but because the site uses a custom theme for WordPress. Most of my clients don’t choose to spend much on developing a site cosmetically, and are satisfied with a few changes to one of WordPress’ default themes.
This month, I was asked to migrate an ecommerce site to a new host, a new platform, and to split the site into ecommerce and blog sections, each on a separate hosting account and domain. This time, the client chose the template for both Zen Cart (my recommendation for the ecommerce side) and WordPress (the client’s choice for the blogging platform).
The main challenge to this job was the complexity of the organization of categories and products in the ecommerce section of the site.
Lost Lake/Mt. Hood photo by Schick at Morguefile.com.