WordPress 5.9 Beta 3 is now available for testing!
This software version is still under development. Please do not run this software on a production site; install it on a test site, where you can try out the newest features and get a feel for how they will work on your site.
You can test the WordPress 5.9 Beta 3 in three ways:
Option 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).
Option 2: Direct download the beta version.
Option 3: If you use WP-CLI to upgrade from Beta 1 or Beta 2 to Beta 3 on a case-insensitive filesystem, please use the following command sequence:
Command One:
wp core update --version=5.9-beta2Command Two:
wp core update --version=5.9-beta3 --forceThe current target for the final release of 5.9 is January 25, 2022, which gets closer every minute. Your help testing this beta is vital: the more testing that happens, the more stable the release, and the better the experience for users and developers—and the entire WordPress community.
Since Beta 2, 14 bugs have been fixed. Here are a few of the changes you will find in Beta 3:
Do some testing!
Testing for bugs is vital for polishing the release in the beta stage and a great way to contribute.
If you think you’ve found a bug, please post to the Alpha/Beta area in the support forums. If you’re comfortable writing a reproducible bug report, file one on WordPress Trac. That’s also where you can find a list of known bugs.
For even more ways to test, you can also refer to this official Full Site Editing post from @annezazu.
In the coming weeks, follow the Make WordPress Core blog for 5.9-related developer notes that cover these items in detail. So far, contributors have fixed 316 tickets in WordPress 5.9, including 100 new features and enhancements. More bug fixes are on the way with your help through testing.
Props to @psykro, @estelaris, @hellofromtonya, @marybaum, @webcommsat, @cbringmann, @costdev, and @audrasjb for contributions to this post.
Filed under #release, #5.9, #beta
Latest PECL Releases:
Requires Oracle Client libraries from 11.2 or later.
Added oci8.prefetch_lob_size directive and oci_set_prefetch_lob() function to improve LOB query performance.
Each year, the web is full of new ideas, tools, and trends. But for WordPress, 2021 may be looked upon as one of great foundational shifts. Changes that, while still in their early stages, promise to have a lasting impact on how we work with the content management system (CMS).
That applies not only to the core software but to its massive community and ecosystem as well. There were moments when it felt nearly impossible to keep up with the flurry of movement and acquisitions in this space. For a time, WordPress was akin to an open-source Wall Street.
Now that we’ve reached the end of the year, let’s take a look at the biggest developments as they relate to WordPress.
The Gutenberg block editor was moved into WordPress core way back in 2018 (has it really been that long?), but 2021 saw the feature go beyond pages and posts.
The venerable WordPress Widgets screen’s familiar drag-and-drop UI saw wholesale changes this year. As of WordPress 5.8, Widgets are now block-based.
The transition to blocks is more than just cosmetic. It also means that virtually any block can now be placed within a sidebar. This greatly expands the content options available to site owners.
The standard core widgets that come with WordPress were refreshed, while some new additions have also been integrated. Older widgets still work and are available through a Legacy Widgets block.
However, this change may cause issues for some sites that rely on legacy widgets. Thankfully, the Classic Widgets plugin can restore things to their previous state.
It’s a big transition. One that has me thinking about the future of this longtime staple of WordPress.
Full Site Editing (FSE) was perhaps the most buzzed-about WordPress feature of the year. It offers the ability to design and edit every aspect of a theme – right from within the block editor.
The potential impact is hard to ignore. WordPress themes are going to look a lot different in terms of how they’re structured. And, with more power in the hands of users, it will be interesting to see how the theme market shifts to take advantage.
FSE could also change the design process itself. Since so much can be achieved via the browser, where does that leave traditional wireframing tools? Some designers may decide to skip them altogether.
As exciting (or terrifying) as this all sounds, FSE is not yet a part of WordPress core. It’s scheduled for full release in WordPress 5.9, which has been pushed back to January 2022.
Here’s a look at what you can expect from WordPress 5.9 when it comes to Full Site Editing.
The other major storyline involves the business side of the WordPress ecosystem. 2021 saw dozens of plugins, agencies, and hosting providers changing hands. Among close observers, heads were spinning at the sheer number of transactions taking place.
There are several theories as to why there were so many acquisitions. The pandemic, a maturing market, along with the growing complexity of WordPress were among the most common. Some combination of all three seems like a safe bet.
What does it all mean? In the short term, there are user concerns over what will happen to the software and services they rely on. It also means some well-respected members of the community have decided to move on. People such as Elliot Condon (of Advanced Custom Fields) and Pippin Williamson (of Sandhills Development) are two prime examples.
Looking out further, many of these acquisitions have been made by a handful of companies. This consolidation of assets could impact competition. How difficult will it be for a solo entrepreneur or small agency to enter the market? What (if any) influence will these large companies have on WordPress core? Will the acquired products themselves suffer or flourish?
Only time will tell. But it will be interesting to see if this trend continues in 2022.
Early in 2021, WordPress surpassed 40% market share. And it continues to grow at a healthy clip. As of this writing, it has a nearly 40-point lead over the second-most-popular CMS (Shopify).
I put together a few thoughts on the milestone back in February. But it is worth revisiting as we look back on the year.
These usage numbers, along with the aforementioned acquisitions, show that WordPress is a space people want to be a part of. That’s a testament to its relative stability, dedicated community, and continued flexibility.
However, it’s that last piece that concerns me the most. To remain a top choice for developers, WordPress should keep providing multiple paths to build a website. That includes the ability to opt-out of features such as Gutenberg and Full Site Editing.
The idea that a web designer can build in a way that suits the needs of their clients is still attractive. And while I find blocks exciting, I also understand that not everyone is on board.
Having alternative methods to accomplish your goals is what has always set WordPress apart. Hopefully, that will remain the case over the long term.
Odds are that at least one of the developments above impacted you in 2021. Whether it was wrangling that new widget UI or seeing your favorite plugin change hands, it was an eventful year for the WordPress community.
But the immediate impact will likely pale when compared to how these shifts will affect the future. The way we create content in WordPress has already changed. Next comes the way we go about building websites.
The future of the various product and service acquisitions will also be felt for years to come. Some will inevitably turn out better than others. Here’s hoping it brings energy and innovation, with minimal disruption.
Buckle up, WordPress fans – what we saw this year is just the beginning of something much bigger.
The post The 2021 WordPress Year in Review appeared first on Speckyboy Design Magazine.
PHP 8.1 is out and the hip new feature for non-blocking and asynchronous programming in PHP are fibers. In this post we're going to explore them and see how we at ReactPHP will start with them at the edge.
The concept behind WordPress Multisite is simple: it gives you the ability to run multiple websites – all from a single installation of the popular content management system (CMS). Whether your “network” consists of two sites or two thousand, everything is administered in a centralized location.
It’s a powerful tool for large, multi-faceted organizations and those who want to build online communities. Everyone from universities and governments to niche bloggers can benefit.
At its core, a Multisite network is still WordPress. Each site features the same familiar styles and settings you’re accustomed to. A network settings area adds a way to create new sites and tweak specific settings that have a broader impact.
But running a stable and secure WordPress Multisite network is a whole different animal. There are plenty of unique considerations that depend upon your specific needs. Items such as user permissions and plugin and theme choices need to be thought about ahead of time. In addition, it’s important to determine whether Multisite is even the right choice for your project.
Today, we’ll share some tips for ensuring that your Multisite network is the best it can be.
The thought of being able to run multiple websites under a single WordPress installation can get your creative juices flowing. It might lead you to conjure up all sorts of potential use cases. However, there are some situations when utilizing Multisite isn’t the best option.
Freelancers, for example, may think about hosting all of their clients under a single network. Imagine the ability to hop from site to site and perform updates with ease. Sounds pretty tempting, right?
This is not a recommended use for WordPress Multisite. Why? If something goes wrong, it has the potential to negatively impact every single site in the network. Since all sites share a database, a crash or bad case of malware could be particularly disastrous. Not to mention the possibility of server downtime.
WordPress Multisite generally makes sense when the network of sites has something in common. Think of a retailer with multiple locations or a sports league where every team needs their own website.
There should be some solid logic as to why these sites are being combined into one installation. Short of that, it might be best to avoid using Multisite altogether.
The common thread between websites goes beyond organizational. While each site can run its own unique theme and choose from an installed pool of plugins, there could be some concern about what can or should be allowed.
Ideally, each website will have similar requirements when it comes to both looks and functionality. This makes it easier to install only the items that will be utilized throughout the network.
Of course, there may be times when a particular network site needs a theme or plugin that won’t be used by the others. An online store that requires a shopping cart is a prime example.
That’s OK, as the network’s Super Admin can limit the availability of those items to just the site that needs them. This lessens the possibility of a theme or plugin being misused or taking up precious server resources.
This doesn’t mean you should go wild with plugins, however. It’s still important to choose carefully. Installing a plugin with security flaws or lots of bugs can bring about network-wide problems.
Speaking of which, WordPress Multisite includes the ability to network activate plugins. Any plugin with this designation will automatically run on every website within the network. Therefore, you’ll want to reserve this for items that you know you’ll need on each site.
As with any website, themes and plugins can affect your network’s security and performance. Determining what gets installed and who has access to it should be at the top of your to-do list.
Just like a traditional WordPress website, Multisite networks support various user roles and capabilities. Likewise, you can also create custom roles if need be. This empowers Super Admins with fine-grain control over every site and the network as a whole.
But for large organizations with a lot of sites, managing users can be tricky. This is particularly so when a user needs access to multiple websites.
By default, all registered users are assigned to the lowest user level (subscriber). That won’t allow for any meaningful access in the back end.
Thus, there may be a temptation to assign them to the Super Admin role for the sake of convenience. That allows a user to access everything. It’s not the most solid policy in terms of security, though.
The more secure option is to assign users only to the sites they’ll need access to. This can be done by first creating the user account via the Network Admin Users Screen. From there, visit My Sites > Network Admin > Sites and assign each user to the appropriate sites via the Edit Site link.
If a user only needs access to a single site, it’s easiest to visit the site’s dashboard and navigate to Users > Add New.
As always, carefully consider which user role each person should have. Think about the permissions they’ll need to do their job and assign them to the appropriate level.
Multisite networks, particularly large ones, can eat up a lot of server resources. They can push storage capacity, memory, bandwidth, and processing power to their limits.
That’s why web hosting is one of the most important components of a healthy WordPress Multisite network. Without the right configuration, your sites can take a massive hit in terms of performance and reliability.
Choosing a web hosting package can be challenging. Even if your initial choice appears to have enough resources, future growth also has to be considered. You don’t want to find out that you’ve outgrown your hosting a few months down the road.
Cost is also a major factor – but you tend to get what you pay for. Sure, some managed WordPress hosts charge a premium for Multisite installs. However, you may have access to a larger pool of resources.
Traditional shared hosting typically allows WordPress Multisite installations. That may work well enough in some instances. But don’t expect great performance for large, heavily-trafficked networks.
The bottom line is to know what you’re getting into before you sign up for hosting. Make sure that you’ll have the horsepower you need both now and in the future.
There are plenty of similarities between administering a standard WordPress website and a Multisite network. But this special configuration does come with its own set of challenges.
First, the web hosting requirements are generally greater. Multiple sites mean a bigger database and more strain on server resources.
In addition, it can be difficult to keep track of plugins, themes, and users. Maintaining great performance and top-notch security requires constant vigilance. Administrators must take care to cut down on overhead and ensure that users have only the permissions they need.
That being said, the potential for a Multisite network is awesome. The added convenience and interoperability allow both developers and organizations to achieve some incredible things.
The post Tips for Running a WordPress Multisite Network appeared first on Speckyboy Design Magazine.
Latest PEAR Releases: