We have recently run into a number of customers using Store Locator Plus® that are having issues with the new REST based geocoding system. It turns out that an overwhelming percentage of people that are having issues have WordPress installed in a subdirectory. Apparently not all subdirectory installs are created equal — if it is not done properly things break.
What is a subdirectory install?
A subdirectory install is one in which WordPress is installed in a directory within the document root of a website. Sometimes this is done when WordPress is only managing one part of a website such as the newsfeed or blog. Other users use this install to separate WordPress core code from the add-on and upload code (plugins, themes, uploads) and the site configuration.
For the sake of this explanation we’ll reference the document root as being in the public_html directory and WordPress inside of a /wordpress directory within.Read More
For those that are not aware, Automattic and the entire WordPress “stack” have been moving more-and-more toward an all-inclusive SaaS model. At every turn Automattic’s Jetpack and WordPress users are pushed toward creating a WordPress.com account to manage “all WordPress affairs”. With the recent recommended to use the WordPress.com SaaS as a workaround to a partly (ok, mostly) broken video process in Jetpack, the message is clear — WordPress.com will be the hub for all things WordPress.
The problem is the user experience over at WordPress.com needs some work. In many ways it is cleaner and simpler than the somewhat outdated WordPress admin panel many are used to. It also lacks many of the details that have been honed over the past decade to make daily work in WordPress easier.Read More
The problems with uploading Jetpack videos in WordPress 5 is just one example of many as to why I continue to recommend not upgrading to WordPress 5 at this time. It is clear that Matt and the folks at Automattic rushed WordPress 5 to market too quickly. Many seasoned WordPress developers including the folks at Yoast — asked Matt to wait.
The ONLY reason they pushed WordPress 5 out to the public was to show it off at WordCamp US 2018 — the big annual event that runs the first week of December.
I get it — who doesn’t like all the “oooh’s and aaah’s” when up on stage a big event. It is a big adrenaline boost.
But it is a bad business decisions that impacts millions of customers, business partners, and vendors.Read More
If you are uploading Jetpack videos on WordPress 5 you are going to need to go through some specific steps to get that to work. The built-in Video Block of WordPress 5 will not work.
If you have not upgraded to WordPress 5 yet, don’t. Wait for WordPress 5.1. WordPress 5.0, 5.0.1, and 5.0.2 still have a myriad of high-importance bugs like disabling CSV imports and exports for many plugins.Read More
In what has become a nearly annual tradition, WordPress has released yet another update that broke thousands of plugins across the Internet. As usual, they claim this is in the best interest of security. Thus the breaking change was done with ZERO notification to developers. It was also forced onto most sites as a “security patch release” which will update any site that does not forcibly stop automatic updates.
Communication From WordPress Core Is Horrid
While I don’t have an issue with breaking changes for true security issues, what IS a problem is pushing out a change with almost ZERO testing to millions of websites with ZERO communication. They gave absolutely no warning to thousands of sites that this “update version” was coming and that it would knowingly break things. They did not communicate to site owners so they could block updates. They did not communicate to plugin or theme developers so they could come up with new releases.