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.
Should you update to WordPress 5? This is a question that has been asked thousands of times in the past week. I have been asked at least a dozen times and every time my answer is the same. NO.
Unless WordPress automatically updates your site and it is more difficult to restore the prior 4.X release , then WAIT.
While the WordPress 5.0 editor, the most obvious updated to WordPress in the 5 release, is definitely a step in the right direction it is not a compelling reason to upgrade. Not too mention it is different. That means the content writing process you’ve gotten used to, including all the quirks inherent in WordPress, is going to have to be re-learned.
Vue is running on several projects to create a better admin user experience. Vuetify is layered on top and baked into WordPress themes and plugins.
You will need to add a little custom CSS to stop WordPress from stomping on the UX. You’ll also add a small localize script to seed Vue with relevant data from WordPress. A little REST applet to serve Vue requests and you get a fast good looking responsive app with far less effort than custom code, WordPress skeleton apps, React, or Angular.
Vue + Vuetify is my new go-to tool for plugins and themes. I am happier with my choice knowing that was created and is supported by small independent developers.
As PHP continues its march into the future with improved support for objects, better memory management, and notable performance boosts WordPress seems to be dead-set in sticking to the “must support old technology no matter how bad it is”. As of this writing, on the verge of the much-anticipated WordPress 5.0 release with the almost-modern reactive components interface — the past continues to hamper the technology by insisting on clinging to PHP 5.2 as the baseline version that plugins and themes should support.
PHP 5.2 Is Dead
Not recently dead. Long deceased. PHP 5.2 support officially ended OVER SEVEN YEARS AGO in January of 2011. That is about 3,000 years ago in human-time.