WordPress.org

WordPress Planet

April 03, 2018

WPTavern: WordPress 4.9.5 Squashes 25 Bugs

WordPress 4.9.5 is available for download and is a maintenance and security release. WordPress 4.9.4 and earlier versions are affected by three security issues. The following security hardening changes are in 4.9.5.

  • Localhost is no longer treated as the same host by default.
  • Safe redirects are used when redirecting the login page if SSL is forced.
  • Versions strings are correctly escaped for use in generator tags.

Twenty-five bugs are fixed in this release including, improve compatibility with PHP 7.2, previous styles on caption shortcodes are restored, and clearer error messages. To see a full list of changes along with their associated trac tickets, check out the detailed release post.

by Jeff Chandler at April 03, 2018 11:02 PM under security

Dev Blog: WordPress 4.9.5 Security and Maintenance Release

WordPress 4.9.5 is now available. This is a security and maintenance release for all versions since WordPress 3.7. We strongly encourage you to update your sites immediately.

WordPress versions 4.9.4 and earlier are affected by three security issues. As part of the core team's ongoing commitment to security hardening, the following fixes have been implemented in 4.9.5:

  1. Don't treat localhost as same host by default.
  2. Use safe redirects when redirecting the login page if SSL is forced.
  3. Make sure the version string is correctly escaped for use in generator tags.

Thank you to the reporters of these issues for practicing coordinated security disclosurexknown of the WordPress Security Team, Nitin Venkatesh (nitstorm), and Garth Mortensen of the WordPress Security Team.

Twenty-five other bugs were fixed in WordPress 4.9.5. Particularly of note were:

  • The previous styles on caption shortcodes have been restored.
  • Cropping on touch screen devices is now supported.
  • A variety of strings such as error messages have been updated for better clarity.
  • The position of an attachment placeholder during uploads has been fixed.
  • Custom nonce functionality in the REST API JavaScript client has been made consistent throughout the code base.
  • Improved compatibility with PHP 7.2.

This post has more information about all of the issues fixed in 4.9.5 if you'd like to learn more.

Download WordPress 4.9.5 or venture over to Dashboard → Updates and click "Update Now." Sites that support automatic background updates are already beginning to update automatically.

Thank you to everyone who contributed to WordPress 4.9.5:

1265578519, Aaron Jorbin, Adam Silverstein, Alain Schlesser, alexgso, Andrea Fercia, andrei0x309, antipole, Anwer AR, Birgir Erlendsson (birgire), Blair jersyer, Brooke., Chetan Prajapati, codegrau, conner_bw, David A. Kennedy, designsimply, Dion Hulse, Dominik Schilling (ocean90), ElectricFeet, ericmeyer, FPCSJames, Garrett Hyder, Gary Pendergast, Gennady Kovshenin, Henry Wright, Jb Audras, Jeffrey Paul, Jip Moors, Joe McGill, Joen Asmussen, John Blackbourn, johnpgreen, Junaid Ahmed, kristastevens, Konstantin Obenland, Laken Hafner, Lance Willett, leemon, Mel Choyce, Mike Schroder, mrmadhat, nandorsky, Nidhi Jain, Pascal Birchler, qcmiao, Rachel Baker, Rachel Peter, RavanH, Samuel Wood (Otto), Sebastien SERRE, Sergey Biryukov, Shital Marakana, Stephen Edgar, Tammie Lister, Thomas Vitale, Will Kwon, and Yahil Madakiya.

by Aaron D. Campbell at April 03, 2018 07:56 PM under 4.9

WPTavern: ‘Try Gutenberg’ Prompt Pushed Back to A Later Release

Last week, we reported that WordPress 4.9.5 would ship with a call-out prompt that asks users if they want to try the new editor experience.

Within the comments of the post, Gary Pendergast, who works for Automattic, is a WordPress core contributor, and a lead developer on the Gutenberg project, informed us that the prompt would not be in WordPress 4.9.5. Instead, it will ship in a later version once it has gone through a few more refinements.

Change of plans, this won’t be happening in the 4.9.5 release: there are still a few issues we’d like to fix up the callout happens, they won’t be done in time for the 4.9.5 release. I expect there will be a smaller 4.9.6 release that contains this callout, and any bugfixes that happen to be ready.

Gary Pendergast

Reverting the call-out has extended the conversation surrounding its implementation. Jadon N who works for InMotion hosting and is a contributor to the #hosting-community slack channel, says the hosting-community group is working on ideas to help test popular plugins for Gutenberg compatibility.

We have been working to expand our collection of data about how well plugins function with Gutenberg. To help with that effort, we would like to explore using feedback collected from WordPress users through the Try Gutenberg effort to add to the existing database on WordPress plugin compatibility if that could be worked out.

The goal of this project is to make sure everyone can use Gutenberg without having to worry about plugin incompatibilities.

Jadon N

The Gutenberg Plugin Compatibility Database project launched by Daniel Bachhuber last month attempts to determine which popular plugins are already compatible with Gutenberg by having volunteers test them in a sandboxed environment.

Out of the 4,213 plugins in the database, 84% have an unknown compatibility status. Out of 610 plugins that have been tested, 82% don't include editor functionality.

Pendergast supports the idea of hosts collecting a wide range of testing data and turning it into actionable items for the team to work on. There's also been some discussion on creating snapshots of plugin compatibility and filtering those results into Bachhuber's project.

Chris Lema, Vice President of Products at LiquidWeb, responded in the trac ticket with a suggestion that the team place as much emphasis on the Learn More and Report Issues sections as the Try Gutenberg message. He also added a prototype screenshot of what the call-out could look like.

Gutenberg Call Out Prototype by Chris Lema

"The reality is that people don't read a lot, so people may not fully grasp the 'testing' part given the proposed design," Lema said. "When there are equal weight to the design, the message also carries with it the same equality."

One of the best suggestions I've read comes from Bachhuber. He suggests displaying the prompt to a small percentage of WordPress sites to prevent thousands of users from re-reporting known issues with Gutenberg. It would also help lessen the load on the support forums.

One of my main concerns with the call-out is the lack of upfront information to the user that it is beta software and it could cause adverse affects on their site. Lema's prototype does a great job of informing the user of this possibility and a link to known issues is a great enhancement. What do you think?

by Jeff Chandler at April 03, 2018 12:13 AM under wordpress 4.9.5

Matt: Goose-down Nape

There was a beautiful poem by Kayo Chingonyi in the New York Magazine this week titled The Nod:

When we’re strangers that pass each other
in the street, it will come down to this tilt
of the head — acknowledging another
version of events set in a new-build
years from now, a mess of a place filled
with books and records, our kids thick as thieves
redefining all notions of mischief.

Perhaps our paths will cross in a city
of seven hills as the light draws your face
out from the bliss of anonymity.
Maybe you’ll be stroking the goose-down nape
of a small child with eyes the exact shade
of those I met across a room at the start
of this pain-in-the-heart, this febrile dance.

When I hear "seven hills" my mind immediately goes to Rome, then San Francisco, but Wikipedia has a helpful list of cities that claim to be built on seven hills.

A friend pointed out The Nod is a fine complement to The Invitation by Oriah Mountain Dreamer.

by Matt at April 03, 2018 12:05 AM under Poetry

April 02, 2018

Post Status: Contextualized Learning in or around WordPress — Draft podcast

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, the dynamic Brian duo discuss the highly-anticipated return of WordSesh, the different ways in which we all learn the same, and some of the problems we face in skill building. The guys also spend time finding and contacting the addressable market around WordPress, characterizing a business as WordPress-focused vs providing WordPress services in the context of a broader market, and some of the nuances of providing contextualized services (whether they be training, consulting, or otherwise).

Links

Sponsor: OptinMonster

OptinMonster allows you to convert visitors into subscribers. You can easily create & A/B test beautiful lead capture forms without a developer. Be sure to check out their new Inactivity Sensor technology.

by Katie Richards at April 02, 2018 07:31 PM under Everyone

Dev Blog: The Month in WordPress: March 2018

With a significant new milestone and some great improvements to WordPress as a platform, this month has been an important one for the project. Read on to find out more about what happened during the month of March.


WordPress Now Powers 30% of the Internet

Over the last 15 years, the popularity and usage of WordPress has been steadily growing. That growth hit a significant milestone this month when W3Techs reported that WordPress now powers over 30% of sites on the web.

The percentage is determined based on W3Techs’ review of the top 10 million sites on the web, and it’s a strong indicator of the popularity and flexibility of WordPress as a platform.

If you would like to have hand in helping to grow WordPress even further, you can get involved today.

WordPress Jargon Glossary Goes Live

The WordPress Marketing Team has been hard at work lately putting together a comprehensive glossary of WordPress jargon to help newcomers to the project become more easily acquainted with things.

The glossary is available here along with a downloadable PDF to make it simpler to reference offline.

Publishing this resource is part of an overall effort to make WordPress more easily accessible for people who are not so familiar with the project. If you would like to assist the Marketing Team with this, you can follow the team blog and join the #marketing channel in the Making WordPress Slack group.

Focusing on Privacy in WordPress

Online privacy has been in the news this month for all the wrong reasons. It has reinforced the commitment of the GDPR Compliance Team to continue working on enhancements to WordPress core that allow site owners to improve privacy standards.

The team's work, and the wider privacy project, spans four areas: Adding tools which will allow site administrators to collect the information they need about their sites, examining the plugin guidelines with privacy in mind, enhancing privacy standards in WordPress core, and creating documentation focused on best practices in online privacy.

To get involved with the project, you can view the roadmap, follow the updates, submit patches, and join the #gdpr-compliance channel in the Making WordPress Slack group. Office hours are 15:00 UTC on Wednesdays.


Further Reading:

If you have a story we should consider including in the next “Month in WordPress” post, please submit it here.

by Hugh Lashbrooke at April 02, 2018 08:00 AM under Month in WordPress

March 29, 2018

WPTavern: WPWeekly Episode 310 – Community Management, PHP, and Hello Dolly

In this episode, John James Jacoby and I discuss the news of the week including, the removal of offensive lyrics in Hello Dolly, a request for plugin developers to stop supporting legacy PHP versions, and changes coming in WordPress 4.9.5.

We also talk about community management, the difference between comments and forums, and finally, John shares his concerns on how the Gutenberg call-out prompt is being built into core.

Stories Discussed:

A Plea For Plugin Developers to Stop Supporting Legacy PHP Versions
Without Context, Some Lyrics Inside the Hello Dolly Plugin Are Degrading to Women
Why Gutenberg and Why Now?
Noteworthy Changes Coming in WordPress 4.9.5
In WordPress 4.9.5, Users Will Be Two Clicks Away From Installing and Activating Gutenberg From the Dashboard

Picks of the Week:

How to Disable Push Notification Requests in Firefox

Facebook Container Add-on for Firefox

WPWeekly Meta:

Next Episode: Wednesday, April 4th 3:00 P.M. Eastern

Subscribe to WordPress Weekly via Itunes

Subscribe to WordPress Weekly via RSS

Subscribe to WordPress Weekly via Stitcher Radio

Subscribe to WordPress Weekly via Google Play

Listen To Episode #310:

by Jeff Chandler at March 29, 2018 09:07 PM under php

WPTavern: My Gutenberg Experience Thus Far

Ive used Gutenberg for several months and during that time, there have been moments where I love it and situations where I've had to disable the plugin because of frustrating bugs.

One of the most frustrating aspects of using Gutenberg is the lack of support from the plugins I depend on.

Publish Post Preview

I use the Publish Post Preview plugin to generate a preview link for posts so that people can see what it looks like before it's published.

Publish Preview Checkbox in the Current Editor

In the current editor, the checkbox to generate a link is in the Publish meta box. In Gutenberg, that option doesn't exist. According to a recent support forum post, the author does not plan on making it Gutenberg compatible until there is a finalized API to extend the sidebar.

Telegram for WordPress

We use the Telegram for WordPress plugin to automatically send published posts to our Telegram channel. The plugin adds a meta box that has options to send the post, configure the message structure, send a file, and display the featured image.

In Gutenberg, the meta box is open by default which provides access to those options. However, when I edit a published post, there are times when the meta box is closed and clicking the arrow to expand it doesn't work. Since the Send this post to channel option is on by default, saving changes to the post will resend the post to Telegram subscribers. Something I don't want to happen for simple edits.

Edit Flow

We use Edit Flow to collaborate on posts and often use the Editorial Comments feature to provide feedback. In Gutenberg, the meta boxes for Editorial Comments and Notifications do not open when clicking the arrow. Therefor, we can't use those features.



Edit Flow Meta Boxes are Broken

After the Deadline

I'm a fan of After the Deadline which is a proofreading module in Jetpack. It checks posts for spelling, grammar, and misused words. When activated, a button is added to the visual editor to perform the checks. This button is not available in Gutenberg, so those features are not available as well.

Adding Images to Paragraphs is a Pain

Adding images to paragraphs in Gutenberg is more cumbersome than it needs to be. In the current editor, all I have to do is place the cursor where I want to insert an image, add media, choose image size, align it, and I'm done.

In Gutenberg, you need to create an image block below the paragraph block, move the image block to the paragraph block, align it, and use handlebars on the corner of the image to resize it.

I realize that there are a few workflows that I'm going to have to change because of how Gutenberg works, but this workflow doesn't make any sense to me, especially when I can't insert images without creating a new block. Thankfully, the Gutenberg team is on top of it and is working on a solution to add images within a paragraph block.

Random Blank Paragraph Blocks

I recently copied a large amount of text from a Google Doc and pasted it into Gutenberg and was surprised by how well it worked. Blocks were created in the right spots and I didn't have to edit it much.

I opened the post in the classic editor so that I could use the proofreading feature and it mangled the post. I opened the post in Gutenberg again and noticed a bunch of empty paragraph blocks created in-between paragraph blocks.

This resulted in having to spend some time deleting the empty paragraph blocks and questioning whether I should avoid transferring posts between editors in the future.

Tags Sometimes Appear Blank in the Meta Box

When adding tags to posts, sometimes the tags appear blank although they show up on the front-end. Also, deleting tags sometimes doesn't work. I click on the X and nothing happens in the back-end, but the tag will be removed from the front-end.

Blank Tags in Gutenberg

Gutenberg Has a Lot of Rough Edges

If this version of Gutenberg were merged into WordPress today, it would be a disaster. It's clear that the project has a long way to go before being considered for merge into core. Most of the issues I've outlined in this post are known and are being addressed. 

Gutenberg is supposed to make everything we do in the current editor easier and more efficient. If it doesn't, then I have to ask, what's the point?

What concerns me the most about Gutenberg is plugin support. Some of the plugins I mentioned above are active on 10K sites or less but are important to the way I craft and publish content in WordPress.

Without them, using Gutenberg is not a great experience and instead, makes me want to use the current editor where things simply work.

by Jeff Chandler at March 29, 2018 08:28 PM under user experience

March 28, 2018

HeroPress: Giving Back In Your Own Community

Pull quote: It is a good time to be part of the global WordPress community: the costs are low, the developer community is strong, and job availability is at an all time high.

I was delighted to find several years ago that there’s a thriving WordPress community in Nepal. Via Slack I got to meet Sakin Shrestha, and learned all about what their group is doing in Nepal to create jobs and keep the Nepali from having to leave the country to find work.

I recently found out that Sakin is finding a new way to give back to his community: opening a kindergarten. In order for any country to grow strong it has to have good education for its children, and Sakin is working to make that happen.

Read about how the Nepali WordPress community is working to build their own country.

Doing Our Part for the Community

The post Giving Back In Your Own Community appeared first on HeroPress.

March 28, 2018 02:21 PM under Uncategorized

March 27, 2018

WPTavern: In WordPress 4.9.5, Users Will Be Two Clicks Away From Installing and Activating Gutenberg From the Dashboard

At the end of last month, Matt Cromwell, Head of Support and Community Outreach for GiveWP and an administrator for the Advanced WordPress Facebook group, hosted a question and answer session about Gutenberg with Matt Mullenweg.

Mullenweg was asked a few times if he could provide a concrete date on when Gutenberg and WordPress 5.0 would be ready. While a date was not given, Mullenweg said, "For those who want a concrete date, we will have one or two orders of magnitude more users of Gutenberg in April."

It's now clear what he meant by that. WordPress 4.9.5, scheduled for release in April, will feature a call-out prompt that has links to information about Gutenberg and a button to quickly install the plugin if user permissions allow.

Gutenberg Call-out in WordPress 4.9.5

The core team added a Try Gutenberg prompt in October of last year but it was removed in WordPress 4.9 Beta 4. After discussing the subject with Mullenweg, it was determined that Gutenberg was not ready for large-scale testing.

The prompt in WordPress 4.9.5 changes the button text based on the following scenarios.

  • If Gutenberg is not installed, and the user can install plugins, the Install Today button is displayed.
  • If Gutenberg is installed but not activated, and the user can install plugins, the Activate Today button is displayed.
  • If Gutenberg is installed and activated, and the user can edit posts, the Try Today button is displayed.

If Gutenberg is not installed and the user can not install plugins, the button is hidden from view. If you'd like to hide the prompt from users, David Decker has created a plugin that's available on GitHub that simply hides it from view.

One of the concerns about the prompt is the lack of warning of the risks involved using beta software on a live site. Gutenberg is beta software that's still in development that could adversely affect sites. There is no warning on the call-out box and in two clicks, users can install and activate Gutenberg.

Whether it's Gutenberg or some other beta software, this general advice applies. Create a full backup of your site before installing and if possible, install it on a staging site first.

I predict that the volunteers who manage the WordPress.org support forums will have their hands full once WordPress 4.9.5 is released. The support team is preparing by brainstorming user outcomes, common questions that may be asked, and potential pitfalls users experience after installing Gutenberg.

If you'd like to give them a helping hand, check out the Support Handbook and if you have any questions, stop by the #forums channel in Slack.

The Gutenberg call-out has the potential to pave the way for large audiences to test major features in core without needing to use or install a beta branch of WordPress. However, this convenience comes with risks and while they can be reduced, WordPress needs to be up front and center to users about those risks.

by Jeff Chandler at March 27, 2018 10:55 PM under wordpress 4.9.5

March 26, 2018

WPTavern: Why Gutenberg and Why Now?

Tevya Washburn has been building websites for more than 20 years and building them on WordPress for 10. He bootstrapped his website maintenance and support company, WordXpress, that he’s worked on full-time for more than seven years.

Late last year he launched his first premium plugin, and presented at WordCamp Salt Lake City. He lives in Caldwell, ID and is the founding member of the WordPress Meetup group in Western Idaho.


It was only a few months ago that I knew almost nothing about WordPress’ new Gutenberg editor. I had a basic concept of what it was and this vague annoyance that it would mean I’d have to learn new things and probably put a lot of effort into making some sites or projects work with it.

I kept hearing all of the frustration and issues with Gutenberg itself and the lack of information on how to integrate with it. At WordXpress we recently pivoted away from designing websites. When we designed them in the past, we used premium themes. I figured Gutenberg was the theme developer’s problem.

I still had this feeling of dread though, knowing many of my favorite plugins might not add support for it. I also felt some apprehension that even if the themes we use did add support for it, they might have a lot of new bugs through the first few releases.

Then I launched my first WordPress plugin, Starfish Reviews, and suddenly they weren’t someone else’s problems anymore! Now I’d have to come up with a plan to integrate our plugin with Gutenberg. I installed the Gutenberg plugin on a test site where we were testing our plugin with the nightly releases of WordPress and started playing around with it.

I was pleasantly surprised at how intuitive and easy it was to use! Now it wasn’t (and isn’t) finished, so there were bugs and annoyances, but overall I was impressed.

Around the same time, I suggested we should have someone present on Gutenberg at our local meetup. My brief experience was more than what anyone else had, so the responsibility fell on me. Preparing for the presentation forced me to look at Gutenberg more carefully and pay more attention to the information and debate going on throughout the community.

I started reading blog posts, paying more attention in podcasts, and even looking at what was being said on Twitter. I watched the State of the Word at WordCamp US where the general tide in the feelings toward Gutenberg, seemed to turn, though many people still remain skeptical, critical, or antagonistic toward the project as a whole.

Today, I saw someone suggesting legal action if Gutenberg caused problems on their sites. That’s ridiculous on several levels, but shows that there’s still a lot of suspicion, frustration, and outright anger around Gutenberg.

A couple notes: 1. the graphs below are for illustration purposes only, they’re not meant to be accurate to any actual data. 2. If you prefer listening, you can watch my screencast version (13:12) of what follows. The message is the same, but differs in many aspects of presentation.

Finding the Why

Simon Sinek is known for his Ted talk where he explains that most people explain a new product or service by talking about ‘what’ it is and ‘how’ it works, but they rarely explain the ‘why’ behind it. The ‘why’ actually resonates with people the most. They want to understand the reason and beliefs behind it.

In my research, I couldn’t seem to find a clear answer to the most important question: “Why Gutenberg?” If I was going to present to people who knew little or nothing about it, I wanted to provide a reason why this major change was coming that might cause significant frustration, work, and pain for them.

I found a lot of ‘what’ and ‘how’ about Gutenberg. In some posts by Matt Mullenweg and Matías Ventura, I found hints about ‘why’ Gutenberg existed, but no really clear, simple explanation of why this whole project was happening. Why would Matt and others want to seemingly force this major change on us all? Why does it have to be such a radical departure from the past? Why now?

I was certain the conspiracy theorists—who seem to believe that Automattic’s sole mission is to make their lives more miserable—were wrong. But what was the purpose? Could it really just be a me too attitude that left all of these brilliant minds feeling like they had to keep up with Squarespace and Medium? That didn’t seem to fit. Especially since Gutenberg is already leagues better than Squarespace’s convoluted visual editor.

Innovative Disruption

The Innovator's Dilemma Book Cover

Taking cues from those hints and suggestions, I started thinking about the innovative disruption model. It was popularized in business circles, starting in 1997 when the book “The Innovator’s Dilemma” was published by Clayton Christensen, a Harvard professor. His book was an expansion of an earlier article in the Harvard Business Review.

At the risk of oversimplifying the model, innovative disruption is what happens when an existing company who is the top dog (either in sales or market share) gets comfortable with their position at the top along with their revenue stream and quits innovating. They make small, incremental updates to their products or services to keep customers happy, but fail to look at the future of their industry.

This makes it easier for a startup or smaller, more innovative company to bring a new product or service to market that completely disrupts the existing market because it’s better, faster, cheaper. The established company doesn’t see the disruption coming because they feel secure in their large market share and steady sales revenue. They often respond with “why would anyone want that?” when approached with the new model that is about to completely upset their business model.

Blockbuster Gets Busted

The classic example of this is Blockbuster Entertainment, Inc. They had over 9,000 stores at one time, allowing people to rent VHS tapes and later, DVDs. They had a huge portion of the market all to themselves and it seemed nobody could compete with this juggernaut.

Then along came two small startups: Netflix and Redbox. Netflix comes along and says “we’re going to stream movies over the internet. That’s the future and the way everyone will want to consume movies and TV in the future. But since the internet is too slow right now, we’ll just start by mailing DVDs to people.”

Blockbuster looked at this and said, “the internet is way too slow to stream movies. That’s ridiculous! Who wants to wait two weeks to get a movie in the mail?! Hahaha! Stupid startup, they’re wasting their money and energy.” In hindsight this seems ridiculous. At the time, most people would have agreed with Blockbuster.

As you know, people started changing the way they rented movies. Once they tried it, they were happy to pay a subscription and use a queue to get DVDs delivered in the mail. Ultimately, making the decision of what to watch ahead of time was better than wandering through a cathedral of DVDs only to find the one you wanted to watch has already been checked out.

Consumer internet bandwidth speeds quickly caught up. Netflix even invented some of the technologies that provide high quality streaming video to your home. Now, most of us can’t imagine having to go to the store to rent a physical copy of a movie. And those that can, get them from a Redbox kiosk that has a limited selection, but is much quicker and easier than a video store. Netflix now has a larger market share than Blockbuster ever did, with zero physical locations.

There are exactly nine Blockbuster stores still operating, mostly in Alaska. From 9,000 down to nine in only a few years! This is what failing to innovate does. This is how comfort and confidence in market share and sales blinds people and organizations to the coming innovations that will disrupt their market.

Literacy, Disruption, and Gutenberg

Disruptive innovation doesn’t apply just in business. I have a Bachelor’s degree in history. So one example I love to use is how literacy and education ultimately toppled monarchies and traditional power structures in favor of republics and representative democracy.

The choice of Gutenberg as the name of the new WordPress editor seems prescient in this example as well. The name was one of the clues that led me to answer the ‘why?’ question. It was Johannes Gutenberg and his movable type printing press that was the innovative disruption that changed everything!

Before that, the vast majority of people in Europe were illiterate and uneducated. The scarcity of books and written material made it impractical and prohibitively expensive for most people to learn to read. It also allowed the Church and aristocracy to control the opportunity to become literate. That meant the rich and powerful were the gatekeepers of knowledge. Most riots and uprisings to this point were about hunger.

The Gutenberg press changed all that. Suddenly books could be mass-produced faster, cheaper, better than they ever could before. Literacy caught on like a wildfire. The power structures thought they could control it and maintain the status quo. They outlawed printing without state approval and did many other things to limit the spread of ideas through printed materials.

But it was too late, the power to spread ideas that the printing press provided was much too viral. Many printing presses were operated illegally, then destroyed when they were discovered by authorities.

The tipping point had been reached though. The ability to read and spread ideas via printed documents was much more powerful than the money, soldiers, and weapons of the monarchy. Though hunger might have sparked riots and uprisings from this time on, those tiny flames were fanned into an inferno of revolution by ideas spread through printed words. Thomas Paine’s Common Sense is a great example if you want to learn more about concrete examples.

The Pain of Disrupting Yourself

I don’t have a business degree, but from my understanding, The Innovator’s Dilemma can be simplified down to this: to survive, and stay on top, a company (or software, or community) must innovate. It can not be incremental innovation. It must be innovation that disrupts the company’s core product or business model, even to the point of entirely replacing it.

Blockbuster tried some Redbox-like and Netflix-like solutions, but they were too little, too late. The only way they could have survived would have been to disrupt their own business model and service. They would have had to say, “in five years we will close all 9k stores and completely shift our business to providing video online.”

Who does that? Who thinks “we have built an empire, but we have to completely change it and replace it all over again”? That’s “The Innovator’s Dilemma” that the book’s title refers to: it’s incredibly difficult to think in those terms when you’re on the top. It’s nearly impossible to say, “we have to disrupt ourselves. We must compete with our own business and products and services.” But ultimately it’s the only way to survive.

…Or you can buy an innovative company and let them disrupt your main business. Did you know Blockbuster had the chance to buy Netflix for $50 million in 2000? It was pocket change, but they passed because it was a very small, niche business.

Had they bought Netflix and allowed it to continue innovating and disrupting their core retail rental model, Blockbuster might still be around. It wouldn’t have 9k retail stores, but it would have an even larger market share than it ever did renting DVDs.

In either case, the process is painful. That’s why it’s called disruptive. Not because it’s a walk on the beach or small speed bump, but because it takes a lot of work and forward-thinking and causes a lot of pain to create and implement.

If you are the market leader, you can’t rest on your previous success. You have to change everything once again, like you did to get to where you are now. Despite the pain of doing it, you have to invest yourself and your resources into hard work and difficult questions and challenging thinking that goes directly counter to our natural tendency as humans. If you want to stay on top, it’s the only way.

WordPress is Ripe for Disruption

WordPress has a 30% market share right now. It won’t be long before 1 out of every 3 websites is built on WordPress. No other platform is even close.

As WordPress professionals and community members, it seems like we have all the momentum and benefits of being the leader. “Surely nothing could displace WordPress!” That’s what Blockbuster said. That’s what monarchs of past ages said. The truth is simple: “yes, something could. In fact, something will, if WordPress doesn’t innovatively disrupt itself.”

Is it going to be painful? Yes. Is it going to cause a lot of work and effort on the part of the community? Yes! Absolutely. But the alternative is to learn a totally new platform in five years when WordPress dies like Blockbuster did. You think this change is going to be difficult? Try throwing out WordPress entirely and moving your website(s) to an entirely new platform. Because that’s the alternative.

Good Arguments Against Gutenberg

I see many people listing a string of bugs in the Gutenberg UI/UX and concluding that Gutenberg shouldn’t exist. I see others critiquing the underlying technologies and claiming that’s evidence that Gutenberg is entirely wrong.

I’m sorry, but those arguments are entirely invalid. They may be great arguments for how Gutenberg needs to change or improve, but they are not valid arguments against the existence of Gutenberg and its inclusion in core.

Hopefully, I’ve made it clear that WordPress is in dire need of innovation. If that’s true, then as I see it, there’s only one really great argument against Gutenberg. As one person in one of the meetups I presented at put it: “is it the right innovation?”

That's the crux of the whole thing: WordPress must innovate to survive. Matt Mullenweg and the entire Gutenberg team have looked at the past and the future and decided that a better, faster, easier user interface and experience, are the disruptive innovations that WordPress needs to survive.

You can argue that it’s not, that there’s some other innovation that will completely change WordPress and thereby save it from disruption by outside forces. And that's a totally valid argument to make. But in my opinion, you can’t argue that continued, incremental changes are enough. You can’t argue that the path we’ve been on the last five years is going to keep WordPress on top for the next five years. It simply won’t.

I Like Gutenberg, but I Love What it’s Doing

In my experience thus far, I like Gutenberg. I believe it is the right disruptive innovation WordPress needs at this time. It will make WordPress easier to use and help its underpinnings be ready for the future. Being easy to use is what got WordPress where it is today.

It’s not very easy to use any more. There are significantly easier options out there, that could disrupt WordPress and replace it. I think Gutenberg will allow WordPress to disrupt itself and keep ahead of other disruptive innovations. It will save WordPress and allow us all to keep using it and building our businesses on it for another 10 years into the future.

I like Gutenberg, but I really love what Gutenberg means, what it represents, and what it's doing. Gutenberg is bigger than just a new post editor, it shows that the leaders of the WordPress community are willing to make hard decisions and innovate even when it means disrupting their own work and previous innovations.

I have huge respect for the Gutenberg team, who have not only had to rethink everything and do all those difficult things I referred to before, but have had to do it all very publicly, while navigating a gauntlet of criticism, personal attacks, and much more.

I hope this post shows my thanks and newfound appreciation for what they’re doing and going through. Flipping the phrase from The Dark Knight, the members of the Gutenberg team are “the heroes the WordPress community needs right now, even if they’re not the ones we deserve.”

by Jeff Chandler at March 26, 2018 06:20 PM under innovation

Post Status: The Future of Content Distribution — Draft podcast

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.

This week the Brians put their brains together and discuss content distribution across various mediums and platforms as well as subscriptions for both digital and physical products. The conversation shifts between different tooling and platforms that exist for enabling content distribution as well as some of the societal shifts that have shaped how we share and consume both content and products.

This is a good episode for anyone who is developing sites and selling solutions around content distribution or subscriptions as well as anyone who is running (or looking to run) a business based around a subscriber model (paid or otherwise).

Links

Sponsor: Pagely

Pagely offers best in class managed WordPress hosting, powered by the Amazon Cloud, the Internet’s most reliable infrastructure. Post Status is proudly hosted by Pagely. Thank you to Pagely for being a Post Status partner

by Katie Richards at March 26, 2018 01:24 PM under Everyone

March 25, 2018

BuddyPress: 10 years

In 2008 (just 10 short years ago) Andy Peatling made the very first code-commit to the newly adopted BuddyPress project, joining bbPress, GlotPress, and BackPress at the time. As most of you can probably imagine, BuddyPress was a different piece of software back then, trying to solve a completely different decade’s worth of problems for a completely different version of WordPress.

BuddyPress was multisite only, meaning it did not work on the regular version of WordPress that most people were accustomed to installing. It needed to completely take over the entire website experience to work, with a specific theme for the primary part of your site, and blog themes for user profiles and everything else.

There was a lot to love about the original vision and version of BuddyPress. It was ambitious, but in a clever kind of way that made everyone tilt their heads, squint their eyes, and ponder what WordPress was capable of. BuddyPress knew exactly what it was trying to do, and owned it without apologies.

It touted itself as a “Social Network in a box” at a time when MySpace was generating 75.9 million unique visitors per month, so if you couldn’t imagine how different BuddyPress may have been before, imagine how excited everyone was at the idea of owning their own MySpace.

Since then, Andy invited BoonePaul, and me to help lead the project forward, and in-turn we’ve invited several other prolific BuddyPress contributors to help with every aspect of the project, website, design, and so on.

The BuddyPress team has grown in a few different ways. Most recently, we’ve added Renato Alves to the team to help with WP-CLI support. Renato is a long-time contributor who stepped up big-time to really own the WP-CLI implementation and finally see it through to the end.

Slava Abakumov lead the 2.8 release, and we finally met in person for the very first time just last week at WordCamp Miami. He’s another long-time contributor who has always had the best interests of the project in mind and at heart.

Laurens Offereins has been helping fix BuddyPress bugs and work on evolving features since version 2.1, and while we haven’t met in person yet, I look forward to it someday!

Stephen Edgar (who you may recognize from bbPress) also works a bit on BuddyPress, largely around tooling & meta related things, but he’s fully capable and will jump in and help anywhere he can, be it the forums or features.

Mercime would prefer I not blather on endlessly here about how important she is, or how much I appreciate her, or anything like that, so please forget I mentioned it.

Hugo Ashmore has spent the past 2 years completely rebuilding the default template pack. This is an absolutely huge undertaking, and everyone is really excited about sunsetting ye olde bp-legacy.

Tammie Lister has moved on to work on the enormously important and equally ambitious Gutenberg project. Tammie is wonderful, and doing a great job crafting what the future of democratizing publishing is.

Lastly, a few of our veteran team members took sabbaticals from contributing to BuddyPress in the past few years, which I see as an opportunity to return with fresh ideas and perspectives, or maybe moving onto new & exciting challenges. This is a good, healthy thing to do, both for oneself and the project. Space makes the heart grow fonder, and all that.


A small aside but worth saying here & now, is that leading an open-source project is everything you think it is (or maybe have read already that it is) and like a million other things that are hard to understand until you understand. The one constant (and subsequently the hardest and funnest part) is how to provide opportunities for personal growth, without prohibiting contributions, while also doing what’s best for the greater vision of the project itself, amongst a completely remote group of bespoke volunteers. I think Paul, Boone, and I do OK at this, but we are always learning and adjusting, so please reach out to us if there is anything we can do differently or better.


BuddyPress is my personal favorite piece of software. It’s my favorite community. I wake up excited every day because of what it can do and who it does it for. Put another way, I love what we make it do and who we make it for: ourselves, one another, each other, and you.

Cheers to 10 years, and here’s to another 10!

by JJJ at March 25, 2018 10:54 PM under anniversary

March 22, 2018

WPTavern: Noteworthy Changes Coming in WordPress 4.9.5

WordPress 4.9.5 Beta 1 is available for testing and brings with it 23 bug fixes and improvements. A release candidate is scheduled for release on March 20th and a final release on April 3rd. Here are some notable changes you can expect in the release.

"Cheatin’ uh?" Error Message is Replaced

The "Cheatin’ uh?" error message has existed in WordPress for years and for some, is insulting. The error doesn't explain what went wrong and accuses the user of trying to cheat the system.

Cheatin' Uh Error Message

Eric Meyer highlighted the error in his keynote at WordCamp North East Ohio in 2016, when talking about Designing for Real Life. He also contributed to the ticket with suggestions on how to improve the wording.

In WordPress 4.9.5, the error has been changed to more meaningful messages depending on the error that occurs.

Recommended PHP Version Increased to 7.2

Inside of the readme file in WordPress, the current recommended PHP version is 7.0. This version of PHP reached end of life last December. In 4.9.5, the recommend version is PHP 7.2. This is the same version that is recommended on WordPress.org.

Offensive Lyrics Removed From Hello Dolly

As we covered earlier this week, some of the lines displayed in the dashboard from the Hello Dolly plugin are inappropriate without context. In 4.9.5, the plugin will no longer display those lines.

There's a possibility that in the future, there will be a musical note icon or symbol placed next to the line to indicate it's from a song. In addition, the lyrics are more in line with Louis Armstrong's recording.

To see a full list of changes in WordPress 4.9.5, you can view a full list of closed tickets on Trac.



by Jeff Chandler at March 22, 2018 09:32 PM under hello dolly

WPTavern: WPWeekly Episode 309 – All AMPed Up

In this episode, I’m joined by Alberto Medina, Developer Advocate working with the Web Content Ecosystems Team at Google, and Weston Ruter, CTO of XWP. We have a candid conversation about Google’s AMP Project. We start by learning why the project was created, what its main goal is, and the technology behind it.

We also dive into some of the controversy surrounding the project by discussing whether or not AMP is a threat to the Open Web. Medina and Ruter provide insight into AMP’s transformation from focusing on the mobile web to providing a great user experience across the entire web. Last but not least, we learn about the relationship between Automattic, XWP, and the AMP team and how it’s helping to shape the future of the project.

Notable Links Mentioned:

AMP for WordPress Plugin
AMP for WordPress GitHub Repository
AMP GitHub Repository
Video presentation from AMP Conf 2018 showcasing the work that’s gone into the AMP for WordPress plugin
Official blog post outlining the future of the AMP Project

WPWeekly Meta:

Next Episode: Wednesday, March 28th 3:00 P.M. Eastern

Subscribe to WordPress Weekly via Itunes

Subscribe to WordPress Weekly via RSS

Subscribe to WordPress Weekly via Stitcher Radio

Subscribe to WordPress Weekly via Google Play

Listen To Episode #309:

by Jeff Chandler at March 22, 2018 02:34 PM under xwp

Matt: Don’t Like Change

If you don't like change, you're going to like irrelevance even less.

General Eric Shinseki

I actually heard this on the Farnam Street podcast with Patriots coach Michael Lombardi, but it seems like General Shinseki said it first so attributing it there.

by Matt at March 22, 2018 12:01 AM under Asides

March 21, 2018

HeroPress: Keeping Community Alive

Pull Quote: Be a pillar of support for your community.

In the last year or so I’ve been a lot more involved with the business side of WordPress than the community side. The business side isn’t nearly as loving and supportive as the community side, and some of that is out of necessity. Business is business, and people need to eat.

The problem comes when people get so focused on the business side of things that they forget they’re dealing with people. Recently Carl Hancock mentioned on twitter that there are things that happen in business in the WordPress community that would horrify people. I don’t know who those people are that do those things, and I don’t even know what the things are, but I have hope that the community can be bigger and better than that.

There will always be selfish jerks who abuse the system for personal gain, but I have hope that the WordPress community can generally rise above that, and perhaps even change the hearts of poor players.

This week’s HeroPress replay is from David Laietta, about how our community changes lives.

A Community of Acceptance

The post Keeping Community Alive appeared first on HeroPress.

March 21, 2018 03:39 PM under Replay

WPTavern: A Plea For Plugin Developers to Stop Supporting Legacy PHP Versions

Iain Poulson has published a thoughtful request on the Delicious Brains blog asking WordPress plugin developers to stop supporting legacy PHP versions. He covers some of the benefits of developing with newer versions of PHP, what Delicious Brains is doing with its plugins, and using the Requires Minimum PHP Version header in readme.txt.

While we wait for the Trac discussion to roll on and the WordPress development wheels to turn we can take action ourselves in our plugins to stop them working on installs that don’t meet our requirements.

We do this in our own plugins where it is strictly necessary (WP Offload S3 relies on the Amazon Web Services S3 SDK, which requires PHP 5.3.3+ and will we will move to PHP 5.5 in the future), and the more plugins that do this out of choice will help move the needle further.

Iain Poulson

Poulson mentions the ServeHappy project in his post and it's worth a mention here as well. The ServeHappy project was launched earlier this year by a group of volunteers.

Its main goal is to reduce the number of WordPress installs running on unsupported PHP versions through education, awareness, and tools to help users update their site's PHP versions.

This project is in need of contributors. If you're interested, join the #core-php channel on WordPress Slack. The team has meetings every Monday at 11:00 AM EDT. You can also follow the #core-php tag on the Make WordPress.org Core site where links to chat logs and meeting summaries are published.

by Jeff Chandler at March 21, 2018 12:31 AM under servehappy

March 20, 2018

WPTavern: How to Disable Push Notification Requests in Firefox

Have you noticed how many sites ask if you want to enable push notifications? I've answered no to every request but thanks to a tip suggested by Thomas Kräftner, you can disable requests from appearing altogether in Firefox.

Last week, Mozilla released Firefox 59.0 and added a new privacy feature that allows users to block sites from sending push notification requests. To enable it, open the Options panel in Firefox 59.0 and click the Privacy&Security tab.

Scroll down to the Permissions section. Click on the Settings button for Notifications and check the box that says Block new requests asking to allow notifications.

Settings panel for Notifications

Click the Save Changes button and enjoy one less thing interrupting your browsing experience.  To accomplish the same thing in Chrome, follow this tutorial published by Field Guide.

by Jeff Chandler at March 20, 2018 11:32 PM under notifications

March 16, 2018

WPTavern: Without Context, Some Lyrics Inside the Hello Dolly Plugin Are Degrading to Women

There have been many discussions over the years on whether or not Hello Dolly should be unbundled with WordPress. Seven years ago, it was argued that the lyrics are copyrighted and could potentially violate the GPL license.

The latest issue with Hello Dolly is that some lyrics that appear in users dashboards with the plugin activated can be degrading to women without context.

Two examples are:

  • Find her an empty lap, fellas
  • Find her a vacant knee, fellas

Joe McGill has created a trac ticket proposing that those two lines be removed. "The Hello Dolly plugin has been bundled in WordPress for many years, being a simple example of how to build a plugin for WordPress while also adding a bit of whimsy to admin," he said.

"However, there are several passages of text from this song which are inappropriate to display without any context to people using WordPress—particularly as the WordPress project seeks to promote inclusivity for all."

The discussion within the ticket suggests creating a black list or replacing the lyrics with less offensive versions. In many of the Google search results for Hello Dolly lyrics by Jerry Herman, shows that the lyrics inside the plugin and those in the song are different.

The lyrics say, "Find me a vacant knee, fellas." In a video on YouTube of Hello Dolly featuring Sarah Gardner singing the lyrics, she clearly says "Find her an empty lap, fellas." In a YouTube video of Louis Armstrong singing Hello Dolly live, he says "Find her an empty lap, fellas."

Putting aside the debate of which version of the lyrics are used, displaying the text above without context can and is seen as degrading women. At a time when WordPress and its community are doing what it can to be more inclusive, changing or removing the lyrics seems like an easy win.

by Jeff Chandler at March 16, 2018 08:45 PM under inclusive

WPTavern: Watch WordCamp Miami 2018 Via Free Livestream

Tickets for the event may be sold out, but you can watch the event from anywhere thanks to a free livestream. The stream starts today and covers both the E-Commerce and developers workshops. The stream begins tomorrow at 8:30AM EDT with separate links to morning and afternoon sessions.

by Jeff Chandler at March 16, 2018 04:18 PM under wordcamp miami

March 15, 2018

WPTavern: Let’s Encrypt Wildcard Certificates Are Now Available

In July of last year, Let's Encrypt announced that it would begin issuing Wildcard certificates for free in January of 2018. Although a little late, the organization has announced that Wildcard certificate support is now live.

In addition to these certificates, the organization has updated its ACME protocol to version 2.0. ACMEv2 is required for clients that want to use Wildcard certificates.

Wildcard certificates enable site administrators to secure all sub domains with a single certificate. This can be especially convenient for WordPress Multi-site networks.

Let's Encrypt is working on transitioning all clients and subscribers to ACMEv2, though it hasn't set a time table on when it will expire the ACMEv1 API.

In July of 2017, Let's Encrypt was securing 47 million domains. Today, the organization is securing nearly 70 million domains with 54 million certificates. In the United States, nearly 80% of sites loaded in Firefox are through HTTPS.

Let's Encrypt is an open certificate authority that's part of the non-profit Internet Security Research Group. It's mission is to make 100% of the web HTTPS. Operations are financed through sponsors and donations. If this is a mission you believe in, please consider donating to the project.

by Jeff Chandler at March 15, 2018 05:23 PM under wildcard

WPTavern: WPWeekly Episode 308 – Wildcard SSL Certificates For All

In this episode, John James Jacoby and I discuss the news of the week including the results from the 2018 Stack Overflow survey, Tech Crunch’s rebuild, and Let’s Encrypt adding support for wildcard certificates. We also talk about Google working towards AMP or parts of it becoming official web standards. I ranted about how the mobile experience on the web sucks, and we end the show with some event news.

Stories Discussed:

Stack Overflow Survey Respondents Still Rank WordPress Among the Most Dreadful Platforms
Inside Google’s plan to make the whole web as fast as AMP
ACME v2 and Wildcard Certificate Support is Live
TechCrunch rebuilt using the REST API
WPCampus Scheduled for July 12-14 in St. Louis, MO

Picks of the Week:

Designing Themes with Gutenberg Blocks and Sketch

DDJ-1000 The 4-channel professional performance DJ controller for rekordbox dj

WPWeekly Meta:

Next Episode: Wednesday, March 21st 3:00 P.M. Eastern

Subscribe to WordPress Weekly via Itunes

Subscribe to WordPress Weekly via RSS

Subscribe to WordPress Weekly via Stitcher Radio

Subscribe to WordPress Weekly via Google Play

Listen To Episode #308:

by Jeff Chandler at March 15, 2018 01:09 AM under techcrunch

March 14, 2018

HeroPress: A look back: Tamsin Taylor, Freedom Through Blogging

Pull Quote: We cannot know the end of any journey until we find ourselves there.

In August of 2016 I saw a WordCamp talk on WordPress.tv called “A Hero’s Journey”, and I thought that seemed like something I should know a lot more about.  A short time later I was speaking with Tamsin Taylor on Slack.

A greeting conversation

I love telling stories, but I love hearing them more. Tamsin told me a story grief and loss, and how WordPress provided an outlet for those feelings. I hope her story resonates with you as well.

The Bumpy Journey of Becoming

The post A look back: Tamsin Taylor, Freedom Through Blogging appeared first on HeroPress.

March 14, 2018 12:46 PM under Essays

WPTavern: Stack Overflow Survey Respondents Still Rank WordPress Among the Most Dreadful Platforms

Stack Overflow, a Q&A community for developers, has published the results of its 2018 developer survey. The survey was held between January 8th through the 28th and includes responses from 101,592 software developers from 183 countries across the world. This is nearly twice the amount of responses compared to last year’s survey.

Last year, WordPress was the third most dreaded software platform behind Salesforce and SharePoint. This year, WordPress has improved in the rankings and is the sixth most dreaded platform. Respondents found Windows Phone, Mainframe, Salesforce, Drupal, and SharePoint to be more dreadful.

WordPress is the sixth most dreaded software platform

Despite making headway, WordPress has consistently ranked near the top in Stack Overflow’s survey for most dreadful platform. Asking developers why is probably akin to opening Pandora’s box.

JavaScript was once again the most popular technology with HTML, CSS, and SQL following closely behind. Among the various JavaScript frameworks and libraries that exist, Node.js is the most commonly used followed by Angular and React.

The survey introduced a few new topics this year, including questions about artificial intelligence and ethics. When posed with a hypothetical situation in which a developer was asked if they would write code for unethical purposes, more than half of the respondents said no. Also of note is that less than half of the respondents say they contribute to open source.

There are a lot of interesting data points in the survey. I encourage you to check out the results and let me know in the comments what sticks out to you.

Updated 3/14/2018 Corrected to say that WordPress has improved in the rankings and is therefor, less dreadful than before.

by Jeff Chandler at March 14, 2018 10:08 AM under technologies

March 13, 2018

WPTavern: WPCampus Scheduled for July 12-14 in St. Louis, MO

WPCampus, an in-person conference dedicated to WordPress in higher education has announced its third annual event will be held July 12-14 at Washington University in St. Louis, MO. The call for speakers is open until April 7th. The event is two months after WordCamp St. Louis which will also be held at Washington University.

WPCampus held its first event in 2016 in Sarasota, FL, and its second in 2017 in Buffalo, NY. The schedule is not yet finalized but to get an idea on what to expect, check out the video presentations from previous events. Organizers expect about 200 attendees and are accepting sponsorship inquiries.

Tickets are not yet available but those interested in attending can sign up to the WPCampus mailing list where ticket information will be distributed first.

by Jeff Chandler at March 13, 2018 12:12 AM under wpcampus

March 10, 2018

Post Status: Network effects and WordPress — Draft podcast

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, Brian and Brian discuss the power of network effects and how they relate to WordPress’ increasing market share and maturity. WordPress has recently hit two major milestones, turning 15 years old and reaching 30% market share of the top 10 million websites, and we spend this episode reflecting on the innovations that brought us here and where innovations are likely to occur over the next 10 years.

We’ve come quite a long way in these 15 years. From the famous 5-minute install to being entirely pre-installed. From a supportive band of volunteers and vast ecosystem of free software to the commercially supported and highly-polished products that exist today. There is a lot about WordPress to be thankful for, and a lot of great things that will exist in the future because of it. And you can hear a bit about all of that on this episode of the Post Status Draft podcast.

Links

Sponsor: Yoast

Yoast SEO Premium gives you 24/7 support from a great support team and extra features such as a redirect manager, recommended internal links, tutorial videos and integration with Google Webmaster Tools! Check out Yoast SEO Premium.

by Katie Richards at March 10, 2018 08:18 PM under Everyone

March 09, 2018

WPTavern: Yoast Launches Fund to Increase Speaker Diversity at Tech Conferences

In an effort to increase speaker diversity at conferences worldwide, the team at Yoast SEO has launched a diversity fund. The fund will pledge a minimum of €25,000 each year. Its purpose is to remove the financial burdens that can cause minorities or underrepresented groups to speak at conferences.

“There are WordCamps throughout the world, these are conferences about, by and for the WordPress community,” Joost de Valk said.

“While we already sponsor a lot of them, they tend to not have the budget to pay for speakers’ travel and accommodation cost. The same applies to other conferences about open source, certainly those that are not commercially run. We want to take away that particular reason for not having a diverse conference.”

Eligible candidates will be reimbursed €1,000 for travel and accommodations per event. In order to qualify for the fund, speakers must meet the following requirements:

  • Is a part of – or identifies as part of – a typically underrepresented group.
  • The conference is not commercial.
  • The conference targets either the WordPress, Magento, or TYPO3 community.
  • Has been accepted as a speaker to the conference.

To submit an application, email diversity-fund at yoast.com where applications are reviewed within a week.

by Jeff Chandler at March 09, 2018 03:20 AM under yoast

March 08, 2018

WPTavern: WPWeekly Episode 307 – Thirty Percent of the Web

In this episode, John James Jacoby and I start with a continued discussion of AMP from last week. We cover the big releases of the week including Jetpack, Genesis, Yoast SEO, and Gutenberg. We discuss a new project that aims to determine Gutenberg compatible plugins, debate the terminology used to describe WordPress’ market share, and a new plugin that makes WordPress updates more secure.

Stories Discussed:

Gutenberg 2.3, Now With Nested Blocks
Genesis 2.6
Yoast SEO 7.0
Jetpack 5.9
4,500 Plugins Need Your Help in Determining Gutenberg Compatibility
New Plugin Makes WordPress Core Updates More Secure by Requiring Cryptographic Signature Verification
WordPress Now Used on 30% of the Top 10 Million Sites

Picks of the Week:

Mel Choyce’s presentation on Customizing the Future at LoopConf.

Felix Arntz’s presentation on a Global Admin, a deep dive into multi-network organization at LoopConf.

WPWeekly Meta:

Next Episode: Wednesday, February 14th 3:00 P.M. Eastern

Subscribe to WordPress Weekly via Itunes

Subscribe to WordPress Weekly via RSS

Subscribe to WordPress Weekly via Stitcher Radio

Subscribe to WordPress Weekly via Google Play

Listen To Episode #307:

by Jeff Chandler at March 08, 2018 03:39 AM under yoast

March 07, 2018

Matt: Back to Blogging

I really enjoyed Tom Critchlow's post Small b blogging.

by Matt at March 07, 2018 10:59 PM under Asides

Follow our RSS feed: 

WordPress Planet

This is an aggregation of blogs talking about WordPress from around the world. If you think your blog should be part of this site, send an email to Matt.

Official Blog

For official WordPress development news, check out the WordPress Core Blog.

Subscriptions

Last updated:

April 04, 2018 12:45 AM
All times are UTC.