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
Did you know you can tell Selenium IDE to execute certain commands only if a specific element exists on the page? The if element exists trick makes your web app testing scripts far more interesting. Here is a quick example using Selenium IDE 3 — the “new” Selenium IDE.
Log out a standard user
In this use case a WordPress multisite standard user is logged in. We can only execute our commands if we are a super admin. When trying to open a URL that is only available to the super admin an error page shows up. Thankfully this page also comes with an easily identifiable body ID set to error-page.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.