WordPress 5.0 will bring the world a brand new editor that is currently code-named Gutenberg. If you have been hearing the buzz around Gutenberg but have yet to try it, Frontenberg (testgutenberg.com) is the easiest way to check it out.
Frontenberg allows visitors to try Gutenberg without having to set up a separate test site of their own. It loads an instance of WordPress plus the Gutenberg plugin on the frontend so visitors don’t have to log in to play around with the new editor.
Frontenberg has a limited range of capabilities for testing purposes. Users have access to a pre-populated media library but cannot upload images to the test site. It’s also not possible to create shared blocks or save the post. Attempting to save an action will trigger an “updating failed” notice. Apart from those few limitations, Frontenberg allows users to test nearly all of Gutenberg’s features.
The tool was created by Tom Nowell, VIP Wrangler at Automattic. He launched the frontend testing instance on his own website at frontenberg.tomjn.com and the WordPress VIP team built its own version to handle more traffic. Frontenberg contains links to numerous Gutenberg resources, including vipgutenberg.com, which has some free training videos the team created for VIP clients.
Nowell has written a post called How Frontenberg Works for developers who are interested in the tech behind the tool. In it he describes the challenges he encountered in building Frontenberg and the solutions he wrote to make it work.
The “Try Gutenberg” prompt will soon be going out to millions of users in WordPress 4.9.8. Those who conservatively opt to use the Classic Editor plugin can still give Gutenberg a try using the Frontenberg tool or install it on a test site to see how interacts with themes and plugins.
The Fields API was developed to allow registering fields to different screens in the admin area through a single API. New meta boxes and fields within them could be added to posts while new sections and fields could be added to the profile screen.
The goal of the API is to integrate with all of the various admin screens including, Posts, Terms, Users, Media, and Comments and provide standardization.
It is with a heavy heart that I must pass the torch on this project. After hundreds of hours of my time, I no longer believe I can effect change within WordPress core.
The Fields API vision was too big, too much of an undertaking for any one person. I believe so deeply that WordPress needs a Fields API, but the journey to where we are at with the Fields API has been long and arduous.
The truth is, I burned out years ago while building the first and second prototypes. Not everyone agreed on how to architect the code, it went through many revisions based on core contributor feedback. I just couldn’t get enough people excited about it, I couldn’t get enough companies and people interested in supporting it.
I need to let someone else have their chance, I am dragging it down. If someone steps up to lead in the future, then I would be happy to assist where I am able to. But I am unable to continue leading the Fields API proposal/project. I am sorry, please accept my apology and I hope you can forgive me for failing to take this project over the finish line. I still believe to be such a vital part of WordPress’ future success.Scott Kingsley Clark The Trials and Tribulations of Leading an Open Source Project
In the following interview, Clark explains why he feels personally responsible for the project’s lack of progress, why the API is important for WordPress’ future, and reflects on what he could have done differently.
Are you looking to pass the torch on to anyone in particular?
No, I’m not sure who would have the drive and the clout to see the project through. It’s a large scale project that should be approached with a long-term vision but in small enough increments to make it into WordPress core. It’s a lot to ask of somebody, it’s also not a priority for people right now since they are distracted by Gutenberg being released in the near future.
Why is the Fields API a vital part of WordPress’ future?
People look at WordPress today and wonder how they ever survived without the REST API. Well, at least I know I do! The same thing can be said about the Fields API even though it’s not there yet. There are so many cases where it’s frustrating to build solutions for WordPress across all of the different hooks.
For consistency, it’s the wild west out there. You get a meta box registered and you fill it with whatever you want. You need your own CSS to style the form fields and everyone has their own idea of how this interface should look. You are in charge of your own responsive layouts that are mobile-friendly, there’s just so much you have to handle on your own. You should be able to customize appearances, but every place you want to add a field or form to should really have a proper API.
Long-term, imagine registering fields to WordPress like you register post types. Imagine fields and their configurations being available to the REST API and accessible through the WordPress App or other custom apps.
The whole world opens up because you have a consistent API, the whole world make sense because you have a consistent interface for those fields across the various edit screens. Posts, terms, comments, users, media, even the Customizer would all have the same underlying API to add groups, panels, and fields to their screens.
If Gutenberg was done after the Fields API was in, migration for folks wouldn’t have been as difficult. Gutenberg could have automatically shown all of the Fields API interfaces like it does for the meta box backward compatibility. It would have looked so much nicer too.
Taking some time to reflect, what could you have done differently to get more core contributors to buy into the project and turn it into a higher priority?
I’m not sure, it’s a delicate balance of taking input and being confident in the end result. At first, the feedback was about how the API was foreign for WordPress, they asked if it could be similar in structure to other APIs such as the Customizer.
We scrapped the code and rebuilt from the ground up as a fork of the Customizer, it even supported having the Customizer utilizing the Fields API too. At the height of development, we had all areas of the Fields API implemented.
Core releases were moving pretty fast, there was a lot of code changes from WordPress release to release that we had to keep up with because we had essentially created a project that was a giant patch for WordPress.
There weren’t enough hooks in place to do what we needed to do, and many sections were not extensible because of code decisions that marked themselves as ‘final’, which means you can’t extend a specific class to customize how it works.
I wish I could have been at all the big WordCamps in the US and Europe, essentially lobbying for this feature. Gathering supporters and such, it feels like politics in a way. I hung around in Core dev meetings, trying to bring it up. I tried to legitimize the feature by having a dedicated channel in the official WordPress Slack, posting updates on https://make.wordpress.org/core/, and holding weekly meetings.
Ultimately, I prioritized my time for development over the time to gather the troops. That was the downfall, I began to burn out quickly after the first few rewrites as I had many other responsibilities elsewhere on top of Fields API.
It’s not like companies will easily want to pay you to work on a project like this indefinitely, even though both WebDevStudios and 10up gave me time to push it forward. It wasn’t a blank check, at some point I had to get back to billable work. From then on, it was all in my free time and that was difficult to manage during times of financial stress and house selling/buying.
There’s demand for a Fields API in core but not enough hands to build it. Why do you think that is?
Everyone is focused elsewhere. There’s a lot of areas of WordPress that need people’s attention. There are things like Accessibility that deserve a lot more attention than it gets. But the focus to me, seems to be on Gutenberg and REST API.
Gutenberg especially has been a huge time sink for people contributing and people implementing. It’s a really large feature. It’s definitely larger in scale than Fields API, it’s like a whole new app that lives in WordPress. Integration with it has required a lot of education and trial/error. People’s focus is where it needs to be right now. It’s just unfortunate that Gutenberg came before Fields API in terms of priority and interest level.
What advice would you give to the next Fields API project leader?
This is a big project, everyone will want to say it should be a certain way. You have to evaluate the options and put forth something bite sized for core to start with. Build upon that, but never lose sight of the long-term goal of integration across all of the WordPress screens. Even the front-end comment forms could thrive with the Fields API.
Why do you feel personally responsible for the project not being a core priority?
At one point, we had momentum. We had at least three to four people who were active. It fell apart because I ran out of time. It’s my shortsightedness, it’s my fault. I spent hundreds of hours developing the project over a couple of years. I should have left myself much more time for organizing the feature proposal text and keeping the fires burning in our contributors’ hearts.
Considering the time and effort you’ve put into the project the last few years, do you feel any sense of relief passing the torch on?
If the torch gets passed or picked up, I will feel a ton better. The main relief is that it’s officially not a weight I have to carry alone any longer. It’s okay to try and fail, it’s still sad though.
I hope that someone or some company steps up and puts time into this. They could even reignite the fire in my own heart that burned itself out. For now, I have one less major to-do item. I still have a hefty plate but it’s no longer as heavy of a burden.
While the immediate future of the project is unclear, those interested in taking it over are encouraged to read posts marked with the Fields API tag on Make.WordPress.Core to learn about its history. You can also check out the project’s Github page.
One of the things I’ve loved most about HeroPress is getting to know people far away. It’s getting harder and harder to name a country where I can’t say “Hey, I have a friend there!”. This week I’m in Australia for WordCamp Sydney, and I’m crazy excited about all the people I’m going to meet. The global unity of the WordPress community is exhilarating.
The replay essay I picked for this week is titled “A Bottomless World of Possibilities” by Jamaal Jaamac in Mogadishu, Somalia. His world is so completely different from mine that sometimes I even have a hard time asking the right questions to find out what it’s like.
Jamaal doesn’t live in a place where good work comes easy or often. It’s chiseled out of society with labor and love. There’s a stereotype that people in poor countries are lazy, but I think they have to be stronger and work harder just to make it. Jamaal is one of my heroes.
Check out his essay.
YG Biz is a modern bootstrap based theme for your business.
- Drupal 8 core
- Bootstrap v4.0.0
It is highly recommended to install the demo site and customize it to get the exact look. Here is the link for the documentation to install demo site
Demo login credentials : admin / admin@123
Thanks for checking out our theme. We can install the theme in your server for free!
Other YG themes
- YG Booster: A free bootstrap based Drupal 8 theme with modern design for products and business
- YG Newage: an app landing page theme built using bootstrap
- YG Agency: Theme perfect for portfolio and agency websites
- YG Flew: Theme perfect for business websites
Drupal theme by Young Globes
Today I pushed an update to my redirect and repointing plugin, Page Links To. Tomorrow, this plugin will have been in the WordPress.org Plugin Directory for 13 years (it was the 339th plugin in the WordPress plugin repository; there are now over 75,000!).
To celebrate its transition to a teenager, I’ve added some new features and UI enhancements.
Last month, I received survey responses from over 800 Page Links To users and learned a lot about how it’s being put to work. One of the most interesting things I found was how many people are using it for URL redirects. For example, they might have a really long URL on their own site or someone else’s site that they want to be nice. example.com/summer-sale instead of example.com/store/specials.aspx?season=summer&_utm_source=internal. But in order to create these redirects, you have to go through the cluttered and sometimes slow post creation screen. All you really need to create a redirect is a title, a destination URL, and a local short URL.
You’ll now find a menu item “Add Page Link” that will allow you to quickly add a redirected Page without having to wait for the entire WordPress post editing interface to load. It’s super fast, and it doesn’t redirect you away from the screen you’re on.
Since short URLs are better for sharing (and remembering), the UI will give you a little push to shorten the URL if the one generated from your title is too long. From there, you can Save Draft or Publish.Hey, that URL is getting a bit long Custom slug, for a better short URL
Additionally, this release includes a “link” indicator on post and page list screens, so you can easily see what items have been re-pointed with Page Links To. When hovered, the link icon will reveal the destination URL for a quick view.The “link” icon means that this item has been pointed elsewhere.
If you want to grab the “local” short URL (which will be redirected to your chosen URL when someone visits it), just click “Copy Short URL” from the actions, and it’ll be in your clipboard.Hover the “link” icon to see where it’s pointing.
That’s it for version 3.0, but I’ll have more to announce soon — stay tuned!
Making a decision that not only affects your livelihood, the livelihood of your partners and employees, and the livelihood of an entire community isn’t for the faint of heart. It certainly wasn’t a responsibility I took lightly and spent quite a bit of time wrestling with.
The fact of the matter is this: When you make a decision that affects thousands of people, you have to wrestle with it. And then wrestle with it some more.Brian Gardner
I appreciate Gardner’s down-to-earth perspective on how he reached the decision to sell.
Ryan Sullivan, founder of WP Site Care, sold his WordPress maintenance and support business to Southern Web. On his personal site, Sullivan describes what it has been like to run a business the last seven years and drifting away from the reason he created the business in the first place.
As the team grew, I slowly moved further and further away from the reason I started my business in the first place. It’s a trend that’s talked about extensively in the E-Myth.
People start a business because they love what they do, but then the growth of the business, management of people, and demands of administrivia become too much, and the person who started the business finds themselves in a totally foreign land with no roadmap for how to get back to the thing they once loved.Ryan Sullivan
Merging with Southern Web allows Sullivan to get back to what he enjoys doing most, helping people and businesses with their sites. Sullivan also shared a great piece of advice, “Ask for help before you think you need it.”
Both articles are great reads and provide insight into the tough decisions founders inevitably have to make.
Alain Schlesser hosted the first WP-CLI Hack Day last Friday and by all accounts, it was a smashing success.
The main goal was to merge 20 pull requests during the event but due to technical issues with Travis CI, only 12 were merged. Travis CI is open source software used to perform automated testing.
In addition to the 12 pull requests that were merged, 13 more were submitted. The last two hours of the event featured a video call where contributors could talk through issues or receive help on submitting pull requests.
“We peaked at 13 participants to that video chat,” Schlesser said. “It allowed for people to make a more personal connection, which added another dimension to the act of contributing.”
Despite not reaching the goal, Schlesser is pleased with how it turned out.
“The event was also an experiment, to see whether a more direct, interactive form of contribution would attract more contributors,” he said. “I think it did succeed in doing so, and I think it was a positive experience for the participants.”
Feedback from participants is positive and folks enjoyed having Schlesser available to answer questions and walk them through how to set up an environment for testing.
Though we fell a little short of that goal, it was heartening to be a part of the communal experience, learn how to write my first Behat test (something that has been on my to-do list for a long time!), and get immediate feedback on my submitted pull request. And, of course, getting that PR merged was a thrill as well, as I can now say that I’ve contributed back to the project.Jeremy Ward
You can find links to all of the merged and submitted pull requests on the WP-CLI Hack Day summary page.
WordSesh, a virtual conference dedicated to WordPress topics, is returning for a 5th edition on Wednesday, July 25, 2018. Scott Basgaard, the original organizer of the event, has passed the torch this year to Brian Richards, who has co-organized previous WordSesh events.
The online-only event will feature 12 hours of sessions on a variety of tech and business topics, including e-commerce, freelancing, and security. In the past, WordSesh has been a marathon 24-hour event, but Richards decided to pare it down to 12 hours this year in order to organize the details quickly and get the next event on the calendar as soon as possible.WordSesh Experiments with Charging Attendees for Tickets, Adds Real-Time Transcription
For the first time in WordSesh history, the event is charging attendees for tickets (rather than making it free for everyone as in years past). Richards is using the ticket money to pay speakers and have every video professionally transcribed in real-time. He has received some pushback on the decision but wants to see how things fare with this arrangement.
“I thought the community might get behind that so we can stop asking speakers to completely volunteer their time, and the transcriptions are a huge accessibility bonus for non-native English speakers as well as the hard of hearing,” Richards said. “There have been just a few people pipe up to voice their distaste that I converted a free event to a paid event, which suggests there are many others stewing about it quietly, and I’m guessing it’s because they don’t realize where the money’s going (not that it should matter in either case).”
Richards said tickets are dynamically priced to be the operational equivalent of $25 USD in every person’s home country. In India, for example, the ticket price is closer to $9 USD. He has kept quiet about the tech until now because he didn’t want people gaming the system but has since decided that it’s not a major concern.
“The site accounts for purchase power parity so that the cost is not more than a couple of billable hours (or, ideally, much less) for everyone,” Richards said. “And for people whom the cost of a ticket is still a stretch, well, that’s where the scholarships come in.”
WordSesh still has 18 donated scholarships to give away but Richards said he is struggling to find people willing to apply to watch the event for free. Prospective attendees can apply for a scholarship or nominate others to receive one.
A ticket to the event grants attendees access to the sessions, both live and after it has been recorded. Attendees will also receive virtual swag. A few samples include:
- A steep discount on WPSessions annual memberships (33%)
- Stripe is providing an exclusive link to skip the invitation process on their Atlas program and cover the cost for processing their first $5k of payments
- CorgiBytes is offering a $1k discount (~20%) on their code auditing services
Previous WordSesh events averaged 1,000 online attendees and a good portion of them showed up the same day the events aired. This year there are approximately 400 registered so far. Richards said he won’t rule out the possibility of making the event free again for the next edition.
“Asking more from sponsors could make a free event possible again without paying for everything personally (right now I’m still about $1000 in the red), but I really want to put the onus on the community at large,” Richard said. “Quality events take a lot of time and effort to accomplish, and most of that cost is on the backs of the organizers, speakers, and sponsors rather than attendees (at least in the WP community). Having been in all of those seats I’d really like to see more responsibility shift to the attendees. I would personally be happy to pay more for an event and be glad knowing that both speakers and organizers weren’t burning all this time in hopes of a return.”
Virtual events often reach far more people than an average local WordCamp, and many also inspire in-person meetups. Watch parties for WordSesh’s 5th edition are happening in cities across the globe, including Antwerp, Lagos, Minneapolis, Mumbai, and Bar Harbor (Maine).
“I’ve always enjoyed seeing people pour in to the event each year, and there was a delightful hum throughout the WordPress community every time a WordSesh took place,” Richards said.
WordSesh has been a valuable addition to the virtual event space around WordPress, and attendee numbers at the upcoming event will be important for measuring how much traction the event can retain with its conversion to a paid event. Richards says he is committed to keeping the event alive and hopes to host it two times per year, which is one of the reasons for cutting it back to 12 hours.
“I’m already excited for the next event,” Richards said. “I’m a little concerned at the moment, only because I don’t expect this one will sell enough tickets to break even, but I’m absolutely committed to hosting WordSesh again in the future. I’m more interested in hosting an incredible event and providing a ton of value to attendees than I am in breaking even this time around.”
Customise your current admin panel with this cool theme.
The popular theme color admin for Bootstrap theme with Drupal 8.
If your archives span across multiple months and years, you can configure the block to display as a drop-down menu. Otherwise, the list may be too long and look unwieldy on your site.
Video blocks now have attributes users can can configure for Autoplay, Loop, Muted, and display Playback Controls.Video Block Attributes
There are a number of enhancements in this release that you can view via the change log.
Considering Gutenberg 3.2 released earlier this month generally completed the MVP or minimum viable product feature set, users can expect more of these types of releases to tie up loose ends and prepare Gutenberg for merge into WordPress 5.0 later this year.
WordCamp Karachi is happening on August 4, 2018, and organizers are expecting more than 400 attendees. Karachi is the largest city in Pakistan with a population of more than 30 million people. Its airport connects the country to other international cities and smaller cities within Pakistan are available by rail or bus. Organizers behind the camp are overcoming a rocky history that has plagued the planning of WordPress-related events in the country for the past several years.
At the close of 2015, Pakistan was on track to host its first WordCamp in Lahore, building on momentum from the phenomenal growth of the local meetup group. Muhammad Kashif, one of the organizers, was averaging 200-500 attendees at meetups and his team’s application to host WordCamp Lahore was approved for 2016.
The meetup events, which attracted young students, developers, freelancers, and entrepreneurs, had grown so large that Kashif was having to close registration ahead of time because they were exceeding the capacity of the venue. Organizers expected 400-500 attendees at the WordCamp before it was cancelled after several delays near the end of the planning stage.
After contacting the WordPress Community team for the reason why it was cancelled, I received an official response from representative Hugh Lashbrooke:
Sometimes a WordCamp doesn’t make it all the way from pre-planning to being an actual event — occasionally due to logistical challenges, but other times because of broader concerns. In this case, once the WordCamp planning was underway, some tense dynamics arose within the local team. Everyone worked really hard to reach a positive solution, but we weren’t able to move forward with the event in the end.
Cancelling an event is never anyone’s preference, to be clear, but it is also a customary response when it’s clear that collaboration isn’t possible in the short term. Local organizers are always encouraged to reapply as soon as the barriers to collaboration have been resolved.
Lashbrooke also cited issues with the camp’s budget for the venue organizers selected. He said the situation was thoroughly investigated before the camp was cancelled and that they would never take that kind of decision lightly.
WordCamp Lahore organizers gave me a different report on what happened and were disappointed with the decision from the Community Team.
“Representatives from the Foundation cancelled the camp in the last stage based on a complaint from one person out of a community of 3,000 people,” Kashif said. “The Foundation made a direct decision of cancellation without giving me a chance for explanation as the Primary Organizer. I suggested the Foundation conduct a survey from the whole Lahore community to know the facts but they had already made the decision to cancel.”
Kashif claims there was no disagreement between the organizers, because the community member in question, Ahmad Awais, was never part of the original organizing team.
One member of the planning team agreed to speak to me anonymously about why he believes the camp was canceled. He claims that Awais fractured the team after his request to be given a prominent position in the organization was denied.
“Ahmad Awais started hijacking Kashif and his team,” he said. “He was not a lead organizer at all, but on the planning team. Instead of contributing, Ahmad wanted to speak at every meetup and didn’t spend time with organizing team. He broke the team and started pointing fingers at Kashif and the existing organizing team. He was NOT there until WC Lahore was approved. He joined the team after that.”
Multiple leaders from WordCamp Karachi’s 14-person organizing team, who wish to remain anonymous, have reported that Awais also requested to be named keynote speaker and was unhappy with the team after they told him that speaker decisions do not work like that. Several said they feared his retaliation against the camp, given they previously had no recourse with the Community Team after the experience of WordCamp Lahore getting shut down.
Awais is not attending WordCamp Karachi and has declined to answer any questions about WordCamp Lahore due to personal reasons.
Kashif received hundreds of messages from the community after the event in Lahore was cancelled. He had been working since 2013 to bring a WordCamp to the area. He said that while the Community Team was helpful with other queries he had, he was disappointed with how quickly the camp was cancelled.
“I worked tirelessly for years to get a WordCamp to Lahore and grew the community from 430 to 2600 in one year but the Foundation didn’t even give me a chance to explain before canceling WC Lahore, Kashif said. “I am a bit disheartened by that action.”
Kashif is now helping with other WordCamps, including Karachi and NYC. He is also willing to work to re-establish a WordCamp Lahore in the future.
“Like me there are lots of other WordPress enthusiasts in Pakistan who want to participate in WordCamps but not everyone can do that outside of Pakistan due to financial or visa reasons,” Kashif said. “I was accepted as a volunteer in WordCamp Europe but couldn’t join due to visa issues. I have seen so much excitement for WordCamp Karachi in the WordPress community across the whole country. Everyone is willing to help to make it a successful event so that there are more frequent WordCamps in Pakistan. The first one is so important as it will set expectations of outcomes of a WordCamp for people who are new to these events.”WordCamp Karachi Organizers Aim to Make a Positive Impact on Pakistan
WordCamp Karachi organizers are attempting to move past the Pakistani WordPress community’s checkered history of contention. They are also eager to distance themselves from the conflict that took down WordCamp Lahore.
Usman Khalid, lead organizer of the camp, said he has put in a lot of effort asking organizers and volunteers to work together, regardless of the credit they will receive, and focus on the community.
“I want to spend time on having a positive impact for this country, avoiding any kind of noise,” Khalid said. “The Pakistani WordPress community is vibrant in many ways. We have around 6,000 plus WordPressers in our community, with people who are selling their products and services worldwide.”
Khalid said there are many users in Karachi, Lahore, Islamabad, Peshawer, and Faisalabad who are doing well with WordPress but are not yet connected to the community or participating in meetups and events. People from all over Pakistan will be attending the event as their first exposure to the WordPress community. Sessions will mostly be conducted in English but a few will be mixed with Urdu, the regional language.
Khalid has experienced many growing pains in bringing the event to a community that is new to understanding how WordCamps work. In a country that is notorious for its censorship, WordPress’ mission of democratizing publishing has the potential to change many lives.
“Since this is first Wordcamp, many people even don’t know about it,” Khalid said. “Those who know want to be a speaker, or any lead role that can promote them. When we tell them it doesn’t work like this, they are mostly get annoyed.”
Tech publications around Pakistan have not been exposed to WordCamps either. Khalid said several of them have asked for money in order to cover the story of the event, unaware that the purpose of the camps and meetups is not to translate everything into business but to give back to the community.
“I am simply working to actually deliver first and prove that this community can create a positive impact,” Khalid said. “I am sure after Wordcamp Karachi, the entire community within Pakistan will flourish, regardless of what happened in Lahore.” He said he hopes the next camps will be even more interesting in the future and that WordCamp Karachi will help to create new jobs and more businesses in Pakistan.
Welcome to the Post Status Draft podcast, which you can find on iTunes, Google Play, Stitcher, and via RSS for your favorite podcatcher. Post Status Draft is hosted by Brian Krogsgard and co-host Brian Richards.
In this episode, I bring on James Laws and Kevin Stover — cofounders of Saturday Drive, the parent company of Ninja Forms — to discuss why they are entering the world of eCommerce. I found this especially interesting given the market dominance of WooCommerce for general WordPress-based eCommerce needs.
Saturday Drive purchased Exchange, the plugin initially developed by iThemes and then handed off to A.J. Morris, with the intention of making a play for the eCommerce market, much like they did successfully once already for the somewhat-saturated forms market.Episode Links
Sandhills Development makes a suite of excellent plugins to power your WordPress website. Whether you need to sell digital downloads, restrict content, create an affiliate program, or manage an events calendar, they’ve got you covered. Thanks to Sandhills for being a Post Status partner.
WordPress 4.9.8 Beta two recently shipped and although much of the focus will be on the “Try Gutenberg” call-out, there’s a patch included that addresses a memory leak that was quite a problem for some users.
The bug is actually in PHP and is related to the stream-get-wrappers function. WordPress 4.9.7 increased the number of times it calls the wp_is_stream() function generating the error more often.
Bailing if the path isn’t a stream. This isn’t perfect: it’s still possible to trigger the PHP bug, but it does significantly reduce the chances of the bug being encountered. For many WordPress sites (those that don’t have plugins that use streams), it reduces the chance to zero.
If you encountered memory exhaustion errors after installing or upgrading to WordPress 4.9.7, try WordPress 4.9.8 Beta 2 to see if it fixes the issue.
Aside from coming up with a solution, Trac ticket #44532 is a bit refreshing to see. In open source, tickets or issues can get bogged down with suggestions, hypothetical scenarios, and bike-shed commentary.
In this instance, the issue was identified and folks from the community along with core contributors worked together in a focused fashion to create a fix in time for the next point release. The ticket is a good example of what it’s like when open source is firing on all cylinders.