I was surprised to see that my big client’s LIVE website was automatically updated to WP 5.0.1. It appears my client is letting SiteGround’s auto updater do this. What is your philosophy of allowing WordPress automatic updates vs. doing them manually?
I see WPBeginner describes how we can fine tune the type of auto updates by installing the Easy Updates Manager plugin:
It’s highly rated, does anyone have experience with this plugin, or recommend a different plugin, or would you rather set variables in wp-config.php to configure the auto updates?
WordPress default is to auto update WP core minor updates only. However you can control: whether to automatically update plugins, themes, WP core MAJOR updates, or disallow ALL auto updates.
More info on this topic, including pros and cons of auto updating, can be found here:
Note that the likelihood of a WordPress update breaking your website can depend on whether you’ve modified core WordPress files of your website, or whether you have a LOT of plugins which can conflict with each other.
My preference is to apply ANY update manually, at a time of my choosing, so I can backup before, apply the updates, then check the website. But that’s time consuming. Has anyone experienced a WordPress (or plugin) update that broke a website? What turned out to be the cause?
I figured how how to override an arbitrary file in a child theme. It is ALMOST as simple as placing the override file in the corresponding folder for the child theme. The step I didn’t know about, was to add a require_once() for the specific file in the child theme’s functions.php. Here is my example step by step:
My example is how to replace the font list in Customizr theme, with my own font list.
1) If I were to “hack” the parent theme to make this change, I’d change the file wp-content/themes/customizr/core/init-base.php
2) Make a copy of core/init-base.php, make your changes, and place it in the child theme’s folder: wp-content/themes/customizr-child/core/init-base.php. Note you must create a “core” folder in which to place init-base.php — you must replicate the full path of the overridden file (or whatever file you refer to in step 3).
3) Modify your child theme’s functions.php to include the overriding file, by adding the following line:
When you need to include files that reside within your child theme’s directory structure, you will use get_stylesheet_directory(). Because the parent template’s style.css is replaced by your child theme’s style.css, and your style.css resides in the root of your child theme’s subdirectory, get_stylesheet_directory() points to your child theme’s directory (not the parent theme’s directory).
Here’s an example, using require_once, that shows how you can use get_stylesheet_directory when referencing a file stored within your child theme’s directory structure.
It seems both WordPress and Joomla make the website editor go the extra mile to add a title tag to an image in a post. This is the tag that allows you to describe the significance of the image. Browsers usually display the tag’s value as a “tooltip” when the visitor hovers over the image. Not to be confused with the “alt” tag which describes how the image looks to a visually impaired person and helps Google to rank the image.
Try hovering over this image to see how your browser displays the title tag.
Both CMS’s automatically build an alt tag value when the image is first used in an article or post. Joomla hides the setting for the title tag behind an “Advanced” tab in the JCE image editor. That’s not helpful for encouraging a novice author to provide text for the title tag.
Today in WordPress I wanted to add a title tag to the image in my new post. I dutifully filled in the caption, description and alt tag values in the image editor when I uploaded my image. A title tag was automatically filled in for me. But when viewing my post in a browser window, no tooltip on hover!
So, I went to text mode in my post and added the title tag “by hand.” This time on hover I got an entire paragraph of text with embedded HTML markup. So that didn’t work. On close examination of my markup I could not see what was wrong. So I found this helpful article by WPBeginner.
It explained the purpose of alt and title tags, and even explained that the “title” setting WordPress uses when the image is first uploaded, is NOT the title tag that shows as a tooltip. The article’s directions said that, in my WordPress visual post editor, click on the image then click the edit button that appears.
Look in the “advanced” section to find a field you can fill in with the value of the title tag.
I had to hunt a while to find the “advanced” section, as it was out of view within the popup box. But finally, “success!”
I have figured out how to add the title tag in two ways now: if nothing special is going on with captions or other shortcodes, you can simply add a title attribute to the image in question in the post editor’s text mode; or you can use the image editor, scroll down to “advanced” settings and fill in the tag there.
By the way, in adding those last two images, I was reminded of how easy it is in WordPress to display a CAPTION for the image: you just fill in the caption field within the image source. In Joomla how the caption is used depends entirely on the template, and it requires tricky CSS overrides on the web developer’s part, and perhaps CSS knowledge on the editor’s part, to make it look good.
Also, I accidentally selected two images and found BOTH were inserted into my article. Does anyone have a good use for such a feature?