We have enjoyed automatic updates for minor versions of core WordPress since version 3.7. However, until recently, it has felt like progress on auto-updating everything had stalled. From mobile phones to smart TVs, the average end-user is accustomed to their software simply staying updated. In 2020, it is time WordPress continues pushing forward, particularly when staying updated is one component of maintaining a secure website.
There are two separate changes centered on automatic updates in the pipeline.
The first, which is set to ship in WordPress 5.5, is automatic updates for plugins and themes. The feature plugin has been in development for several months and should be stable enough to launch with the next version of WordPress.
Plugin and theme developers will need to adopt a development strategy that aligns more with the WordPress philosophy of maintaining backward compatibility, at least to the point where an automatic update does not break a user’s site. This change is a welcome one because it will lead to a more secure web. However, it will be interesting to see how this plays out in the months to come. I am certain there will be a road bump or two that the developer community will need to overcome.
Automatic updates of core WordPress is slated to officially land in version 5.6. It should be an opt-in feature when it rolls out. The feature plugin should also be ready by the time WordPress 5.5 lands.
Original excerpts: WordPress Tavern – Justin Tadlock
Notes from a reader:
In the same paragraph, I read two contrasting sentences:
“For example, most users should have no need to adjust the line-height for their text.”
“At a certain point, it is better to learn CSS.”
How can the proposal of learning a code language, even if its basics, through CSS, be better as an solution for the casual users, rather than allowing them to simply choose a value in a checkbox?! By redirecting their actions to a specific field, requiring them to translate their thoughts into code, instead, at this age of even quantum technology, this argument is just an arbitrary decision for how to deal with their wishes. It is really not the only way for us to better serve the community.
Decades in programming have already taught developers how to organize complex code, and UX designers study decades to serve us very well to simplify these scenarios – where our arbitrary opinions clashes, there are methods out there with solutions for both of us.
Imagine if tax payers needed to learn code in order to answer urgent requests instead of on their mother lamguages? It could be better for those managing the requests? Okay, but better for everyone? No… out of scope.
“We certainly cannot expose every possibility via an option.”
It is true that we cannot expose every possibility via an option.
But it is false that we …Certainly… need that.