WordPress Planet

November 13, 2018

Dev Blog: WordPress 5.0 Beta 4

WordPress 5.0 Beta 4 is now available!

This software is still in development, so we don’t recommend you run it on a production site. Consider setting up a test site to play with the new version.

There are two ways to test the WordPress 5.0 Beta: try the WordPress Beta Tester plugin (you’ll want “bleeding edge nightlies”), or you can download the beta here (zip).

The WordPress 5.0 release date has changed, it is now scheduled for release on November 27, and we need your help to get there. Here are some of the big issues that we’ve fixed since Beta 3:

Block Editor

The block editor has been updated to match the Gutenberg 4.3 release, the major changes include:

  • An Annotations API, allowing plugins to add contextual data as you write.
  • More consistent keyboard navigation between blocks, as well as back-and-forth between different areas of the interface.
  • Improved accessibility, with additional labelling and speech announcements.

Additionally, there have been some bugs fixed that popped up in beta 3:

  • Better support for plugins that have more advanced meta box usage.
  • Script concatenation is now supported.
  • Ajax calls could occasionally cause PHP errors.


We’ve added an API for translating your plugin and theme strings in JavaScript files! The block editor is now using this, and you can start using it, too. Check out the developer note to get started.

Twenty Nineteen

Twenty Nineteen is being polished over on its GitHub repository. This update includes a host of tweaks and bug fixes, including:

  • Menus now properly support keyboard and touch interactions.
  • A footer menu has been added for secondary page links.
  • Improved backwards compatibility with older versions of WordPress.

Default Themes

All of the older default themes—from Twenty Ten through to Twenty Seventeen—have polished styling in the block editor.

How to Help

Do you speak a language other than English? Help us translate WordPress into more than 100 languages! 

If you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, file one on WordPress Trac, where you can also find a list of known bugs.

isation is a word with
many syllables.

Meta boxes are
the original style block.
Old is new again.

by Gary Pendergast at November 13, 2018 01:27 AM under 5.0

WPTavern: WordCamp Nordic Tickets Now on Sale, Sponsorship Packages Sold Out in Minutes

Tickets for the first ever WordCamp Nordic went on sale today and 100 seats sold within 20 minutes. The event is scheduled to be held in Helsinki, Finland, March 7-8, 2019. There are currently 97 regular tickets and 59 micro-sponsor tickets remaining in the first batch, but more will be released in another round.

If there was any question about whether this new regional WordCamp would gain support, the record-setting buy up of all the sponsor packages has put them to rest. All of the Gold packages (3000 €) were purchased within one minute. Silver packages (1500 €) and Bronze packages (750 €) were all purchased within four minutes and 35 minutes, respectively.

“Sponsor packages tend to go in a few hours whenever there’s a WordCamp in Finland, largely thanks to our communications team and the fact that most companies involved with WordPress follow the conversations on our local Slack/Twitter where these things get announced,” co-organizer Niko Pettersen said. “But this must have been a record even for us. WordCamp Nordic seems to be drawing a lot of interest.”

The call for speakers opened on November 7 and submissions close January 7, 2019. All of the sessions will be held in English and the camp is planning to have two tracks. Those interested to speak may apply for a long talk (40 minutes) or a lightning talk (15 minutes). Selections will be made by mid-January and speakers will be announced in February. Follow @WordCampNordic for all the latest news from the event.

by Sarah Gooding at November 13, 2018 12:30 AM under WordCamp Nordic

November 12, 2018

WPTavern: WP GDPR Compliance Plugin Patches Privilege Escalation Vulnerability

At the end of last week, a plugin called WP GDPR Compliance sent out a security update for a privilege escalation vulnerability that was reported to the WordPress Plugin Directory team on November 6. The plugin was temporarily removed and then reinstated after the issues were patched within 24 hours by its creators, Van Ons, a WordPress development shop based in Amsterdam.

The changelog for the most recent release states that previous versions are vulnerable to SQL injection due to “wrong handling of possible user input in combination with unsafe unserialization.” The fixes are in version 1.4.3, which includes the following:

  • Security fix: Removed base64_decode() function
  • Security fix: Correctly escape input in $wpdb->prepare() function
  • Security fix: Only allow modifying WordPress options used by the plugin and by the user capabilities

Van Ons said they requested the Plugin Directory team do a forced update but they said it was not an option in this case.

WP GDPR Compliance has more than 100,000 active installs. According to Wordfence, the vulnerability is being actively exploited in the wild and many users are reporting new administrator accounts being created on their affected sites. The Wordfence blog has a breakdown of how attackers are taking advantage of these sites:

We’ve already begun seeing cases of live sites infected through this attack vector. In these cases, the ability to update arbitrary options values is being used to install new administrator accounts onto the impacted sites.

By leveraging this flaw to set the users_can_register option to 1, and changing the default_role of new users to “administrator”, attackers can simply fill out the form at /wp-login.php?action=register and immediately access a privileged account. From this point, they can change these options back to normal and install a malicious plugin or theme containing a web shell or other malware to further infect the victim site.

Wordfence has seen multiple malicious administrator accounts present on sites that have been compromised, with variations of the username t2trollherten. Several WP GDPR Compliance plugin users have commented on the Wordfence post saying they were victims of the exploit, having found new admin users with a backdoor and file injections added.

The plugin has its own website where the vulnerability was announced. Its creators recommend that anyone who didn’t update right away on November 7, 2018, should look for changes in their databases. The most obvious symptom of attack is likely to be new users with administrator privileges. Any unrecognized users should be deleted. They also recommend restoring a complete backup of the site before November 6 and then updating to version 1.4.3 right away.

The WP GDPR Compliance plugin lets users add a GDPR checkbox to Contact Form 7, Gravity Forms, WooCommerce, and WordPress comments. It allows visitors and customers to opt into allowing the site to handle their personal data for a defined purpose. It also allows visitors to request data stored in the website’s database through a Data Request page that allows them to request data to be deleted.

While the name of the plugin includes the word “compliance,” users should note that the plugin details includes a disclaimer:


A relatively new amendment to section 9 of the plugin development guidelines restricts plugin authors from implying that a plugin can create, provide, automate, or guarantee legal compliance. Heather Burns, a member of WordPress Privacy team, worked together with Mika Epstein last April to put this change into effect. This guideline is especially important for users to remember when a plugin author uses GDPR Compliance in the name of the plugin. It isn’t a guarantee of compliance, just a useful tool as part of larger plan to protect users’ privacy.

by Sarah Gooding at November 12, 2018 08:20 PM under security

Akismet: Version 4.1 of the Akismet WordPress Plugin Is Now Available

Version 4.1 of the Akismet plugin for WordPress is now available and contains the following changes:

  • We added a WP-CLI method for retrieving Akismet stats: wp akismet stats
  • Akismet now hooks into the new “Personal Data Eraser” functionality from WordPress 4.9.6 to ensure that any personal data stored by Akismet is erased when requested.
  • We’ve updated the plugin to more quickly clear outdated alert messages.

To upgrade, visit the Updates page of your WordPress dashboard and follow the instructions. If you need to download the plugin zip file directly, links to all versions are available in the WordPress plugins directory.

by Christopher Finke at November 12, 2018 07:51 PM under General

November 10, 2018

WPTavern: Matt Mullenweg Addresses Controversies Surrounding Gutenberg at WordCamp Portland Q&A

Matt Mullenweg joined attendees at WordCamp Portland, OR, for a Q&A session last weekend and the recording is now available on WordPress.tv.

The first question came from a user who tried Gutenberg and turned it off because of a plugin conflict. She asked if users will have to use Gutenberg when 5.0 is released. Mullenweg said one of the reasons Gutenberg has been tested so early is to give plugin developers time to get their products compatible. He also said that it has been the fastest growing plugin in WordPress’ history, with more than 600,000 installations since it was first made available.

In response to her question he said users will have the option to use the Classic Editor and that the team is considering updating it to include per-user controls and the possibility to turn it on/off for different post types.

Subsequent questions went deeper into recent controversies surrounding Gutenberg, which Mullenweg addressed more in depth.

“The tough part of any open source project – there’s kind of a crucible of open source development which can sometimes be more adversarial and sometimes even acrimonious,” he said. “Working within the same company, you can kind of assume everyone is rowing in the same direction. In a wide open source ecosystem, some people might actually want the opposite of what you’re doing, because it might be in their own economic self-interest, or for any number of reasons.

“I liken it much more to being a mayor of a city than being a CEO of a company. I’ve done WordPress now for 15 years so I’m pretty used to it. It might seem kind of controversial if you’re just coming in, but this is not the most controversial thing we have ever brought into WordPress. The last time we had a big fork of WordPress was actually when we brought in WYSIWYG the first time. Maybe there’s something about messing with the editor that sets people off.”

Mullenweg commented on how polarizing Twitter can be as a medium and how that can impact conversations in negatives ways. He said people tend to read the worst into things that have been said and that has been a new challenge during this particular time in WordPress’ history. WordPress tweets are sprinkled into timelines along with politics and current events in a way that can cause people to react differently than if the discussion was held in a trac ticket, for example.

One attendee asked, “With Gutenberg there’s a lot of uncertainty. Where do you see the tipping point where you see people become more favorable to Gutenberg than the Classic Editor?”

“Part of getting these two plugins, Gutenberg and Classic Editor, out early, was that it could remove uncertainty for people,” Mullenweg said. “Months before they were released you could kind of choose your path. The hope is that the 5.0 release day is the most anti-climactic thing ever. Because we have over a million sites that have either chosen to not use Gutenberg, which is totally ok, or have already opted in and have been getting these sometimes weekly updates. We have hosts that have been actually been pre-installing, pre-activating Gutenberg with all of their sites.”

Mullenweg said hosts that have pre-installed Gutenberg have not reported a higher than normal support load and that it has basically been “a non-event.” It’s the users who are updating to 5.0 after many years of using WordPress who will have the most to learn.

“Gutenberg does by some measures five or ten measures more than what you could really accomplish in the classic editor,” Mullenweg said. “That also means there’s more buttons, there’s more blocks. That is part of the idea – to open up people’s flexibility and creativity to do things they would either need code or a crazy theme to do in the past. And now we’re going to open that up to do WordPress’ mission, which is to democratize publishing and make it accessible to everyone.”

Gutenberg’s current state of accessibility has been a hot topic lately and one attendee asked for his thoughts about the recent discussions. Mullenweg said there is room for improvement in how this aspect of the project was handled and that WordPress can work better across teams in the future:

Accessibility has been core to WordPress from the very beginning. It’s part of why we started – adoption of web standards and accessibility things. We’ve been a member of the web standards project for many many years. We did kind of have some project management fails in this process where we had a team of volunteers that felt like they were disconnected from the rapid development that was happening with Gutenberg. Definitely there were some things we could do better there. In the future I think that we need – I don’t know if it makes sense to have separate accessibility as a separate kind of process from the core development. It really needs to be integrated at every single stage. We did do a lot, as Matias did a big long post on it. We’ve done a ton of keyboard accessibility stuff, there’s ARIA elements on everything. One of their feedbacks was that we did it wrong, but we did it the best that we knew how to and it’s been in there for awhile. There’s been over 200 closed issues from really the very beginning. We also took the opportunity to fix some things that had been poorly accessible in WordPress from the beginning. It’s not that WordPress is perfectly accessible and all WCAG AA and it’s reverting. It’s actually that huge swaths of WP are inaccessible – they just might not be considered core paths from the current accessibility team but I consider them core.

In response to a question about the future of React in WordPress, Mullenweg went more in depth on the vision he had when he urged the WordPress community to learn JavaScript deeply in 2015. At that time he said “it is the future of the web.” He described how each block can be a launching point for something else – via a modal, such as updating settings, doing advanced things with an e-commerce store, zooming in and out of those screens from the editor. This was perhaps the most inspirational part of the Q&A where the potential of Gutenberg shines as bright as it did in the early demos.

“The other beautiful thing is that because Gutenberg essentially allows for translation into many different formats,” Mullenweg said. “It can publish to your web page, your RSS feed, AMP, blocks can be translated into email for newsletters, there’s so much that the structured nature of Gutenberg and the semantic HTML it creates and the grammar that’s used to parse it, can enable for other applications. It becomes a little bit like a lingua franca that perhaps even crosses CMS’s. There’s now these new cross-CMS Gutenberg blocks will be possible. It’s not just WordPress anymore. It may be a JavaScript block that was written for Drupal that you install on your WordPress site. I mean, hot diggity! How would that have ever happened before? That’s why we took two years off; it’s why we’ve had everyone in the world working on this thing.”

JavaScript is what makes this cross-platform collaboration possible and it’s already evident in the work the Drupal Gutenberg contributors are doing, as well as the platform-agnostic Gutenberg Cloud project. When Gutenberg is released in 5.0, it will enable more for WordPress and the web than we can predict right now.

“This is not the finish line,” Mullenweg said. “5.0 is almost like the starting point. Expect just as much time invested into Gutenberg after the 5.0 release as before – to get it to that place where we don’t think it’s just better than what we have today but it’s actually like a world-class web-defining experience, which is what we want to create and what you all deserve.”

by Sarah Gooding at November 10, 2018 03:30 PM under gutenberg

November 09, 2018

WPTavern: WordPress 5.0 Release Date Update to November 27

The WordPress 5.0 release date has been pushed back to November 27. The previous schedule outlined the possibility of a slip date where the first target date could slip by up to eight days if necessary.

“As discussed during the Core devchat this week, the initial November 19th target date is looking a bit too soon for a release date,” Gutenberg technical lead Matias Ventura said in today’s announcement on the make.wordpress.org/core blog. “After listening to a lot of feedback — as well as looking at current issues, ongoing pull requests, and general progress — we’re going to take an extra week to make sure everything is fully dialed in and the release date is now targeted for November 27th.”

Ventura outlined a new plan where beta 4 and beta 5 releases will coincide with Gutenberg 4.3 and 4.4 releases. RC1 is expected to be released November 19. He said contributors will be posting daily high level updates on the current status of the release, including things like open pull requests to be reviewed and outstanding bugs, to the #core-editor channel.

The announcement also includes a short video demonstration of Gutenberg fully integrated with the new default Twenty Nineteen theme.

Given the recent pushback on the timeline from prominent WordPress developers and business owners, the updated November 27 timeline may still not offer enough time to resolve the issues remaining and allow the ecosystem to prepare training materials that accurately reflect late stage UI changes.

At a spontaneous Q&A session at WordCamp Portland this weekend, Matt Mullenweg said WordPress 5.0 was branched from 4.9.8 so this release has been tightly wound to the previous one to allow for a more seamless transition.

The next targeted release day falls on the Tuesday after Cyber Monday, which should be a relief to anyone running a WordPress-powered e-commerce site. If WordPress misses the updated November 27 release date, it will be pushed back to the secondary target date of January 22, 2019.

by Sarah Gooding at November 09, 2018 08:06 PM under WordPress 5.0

WPTavern: WPWeekly Episode 337 – Gutenberg User Experiences, Release Timelines, and the Classic Editor

In this episode, John James Jacoby and I break down what’s happening with Gutenberg. We discuss our trials and tribulations with the editor, the release timeline, and calls from members of the community to delay WordPress 5.0 until January. We also share details on how long the Classic Editor plugin will be supported. Last but not least, we talk about the possible release strategy of shipping point releases every two weeks after WordPress 5.0 is released.

Stories Discussed:

How to Add an Image to A Paragraph Block in Gutenberg

Adding Aligned Images to Paragraphs in Gutenberg Is Not as Tough as I Thought

WordPress 5.0 Beta 3 Released, RC 1 Expected November 12

WordPress 5.0 needs a different timeline   

WordPress 5.0 is Not Ready

Classic Editor Plugin May Be Included with 5.0 Updates, Support Window Set to End in 2021

WPWeekly Meta:

Next Episode: Wednesday, November 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 #337:

by Jeff Chandler at November 09, 2018 05:21 PM under WordPress 5.0

Matt: Gutenberg in Portland Oregon and Podcasts

I’ve had the opportunity to talk about Gutenberg at two great venues recently. The first was at WordCamp Portland which graciously allowed me to join for a Q&A at the end of the event. The questions were great and covered a lot of the latest and greatest about Gutenberg and WordPress 5.0:

Last week I also joined Episode 101 of the WP Builds podcast, where as Nathan put it: “We talk about Gutenberg, why Matt thinks that we need it, and why we need it now. We go on to chat about how it’s divided the WordPress community, especially from the perspective of users with accessibility needs.”

They may be out of seats already, but I’ll be on the other coast to do a small meetup in Portland, Maine this week. As we lead up to release and WordCamp US I’m really enjoying the opportunity to hear from WordPress users of all levels all over the country.

by Matt at November 09, 2018 04:45 AM under Asides

WPTavern: Calls to Delay WordPress 5.0 Increase, Developers Cite Usability Concerns and Numerous Bugs in Gutenberg

Developers and business owners are waiting anxiously in the wings, as Gutenberg is 11 days away from its debut in WordPress 5.0. There is still a chance that the release could be delayed to the secondary date (January 22, 2019), but the decision has not yet been announced.

“I am lukewarm on the 19th, but not because of the number of open issues (which isn’t a good measure or target) — more that we’ve been a day or two behind a few times now,” 5.0 release lead Matt Mullenweg said during yesterday’s dev chat. He said that reports “from the field” continue to be good and companies that have already installed and activated the plugin haven’t reported a higher than normal support burden.

“My concern can be summed up as this,” Aaron Jorbin said. “There are approximately 400 issues that need either code or a decision to punt. Assuming five minutes per issue, that means there are about 33 hours worth of bug scrubs that need to take place between now and RC.”

“I don’t think we can make a decision on moving the date in the next 45 minutes,” Gary Pendergast said in response to concerns raised at the meeting. “I do think it’s fair to say that the Gutenberg and 5.0 leadership teams are hearing all the feedback, and are actively looking whether the timeline is still correct.”

Mullenweg said open issues are not a good measure of whether the release is on target but the numerous bugs the community is encountering has precipitated a flurry of posts advocating for the release to be delayed.

In a post titled “WordPress 5.0 needs a different timeline,” Joost de Valk, author of Yoast SEO, cites accessibility concerns and the stability of the project as reasons for a delay. de Valk identifies himself a strong supporter of Gutenberg and his team has already built compatibility and Gutenberg-first features into their plugin, which has more than 5 million active installs.

“It’s arguably one of the biggest leaps forward in WordPress’ editing experience and its developer experience in this decade,” de Valk said. “It’s also not done yet, and if we keep striving for its planned November 19th release date, we are setting ourselves up for failure.”

de Valk gave two reasons for why he believes the November 19th timeline to be untenable:

There are some severe accessibility concerns. While these aren’t new and a few people are working hard on them, I actually think we can get a better handle on fixing them if we push the release back. Right now it looks to me as though keyboard accessibility has regressed in the last few releases of Gutenberg.

The most important reason: the overall stability of the project isn’t where it needs to be yet. There are so many open issues for the 5.0 milestone that even fixing all the blockers before we’d get to Release Candidate stage next week is going to prove impossible. We have, at time of writing 212 untriaged bugs and 165 issues on the WordPress 5.0 milestone.

WordPress developer Mark Root-Wiley published a post the same day titled “WordPress 5.0 is Not Ready.” He outlined why he believes the release needs to be delayed and suggested the project pursue more auditing and quality assurance testing before shipping it out.

“WordPress 5.0 can and should be a positive change to WordPress, but if it is released in late November as planned, it won’t be,” Root-Wiley said. “There are simply too many bugs in the editor, and the experience is not polished enough. This is because the rate of development has prevented systematic quality assurance (QA) and user testing. Both types of testing are required to ensure the editor is ready and to increase the community’s confidence in the update.”

Root-Wiley describes a buggy experience when attempting to write blog posts with the new editor, which echoes many others’ recent experiences.

“I’m doing my best to give feedback, but it’s exhausting and there are so many little bugs that I struggle to isolate and replicate the one I’m reporting without running into another,” Root-Wiley said. “How is it possible for me to find so many bugs without trying from just writing 1.5 blog posts?”

Root-Wiley also suggested removing what he deemed to be unnecessary features in order to streamline the editing experience and focus on the fundamentals. These features include the tables block, paragraph background colors, spotlight and fullscreen mode, dropcaps, verse block, among others.

“The pace of development has been blistering,” Root-Wiley said. “That speed has been great for developing a lot of features and iterating on those features quickly, but it hasn’t allowed for sufficient testing. What’s needed now is more time for people to find and report bugs with the editor features in their proposed final state.”

Gutenberg criticism is often characterized as coming from people who are resistant to change, but these strong messages about delaying the release come from developers who believe the new editor is the future and have heavily invested in contributing to its success.

Both de Valk and Root-Wiley’s posts seem to have resonated with many who have had similar experiences with the editor. Other core developers and committers have also publicly lent their voices to the call to delay the release.

Opinions on Gutenberg’s readiness vary wildly depending on the person’s perspective and involvement in the project. Those who are working on it full-time have not publicly offered opinions indicating that it might not be ready for the November 19 timeline.

“The 5.0 milestone is in a very manageable place, but if the volume becomes more worrying in the next couple days or it becomes clear milestones won’t be made, we’ll revise as needed,” Gutenberg technical lead Matias Ventura Ventura said during yesterday’s dev chat. He confirmed that the fast pace of development will continue.

Regardless of when 5.0 is released, users can count on getting minor releases every two weeks to address bugs and issues that pop up after Gutenberg is in the hands of millions more users.

“Hopefully as people get used to the more regular cadence they can plan around it, much like they used to complain a ton about, but then got used to, 3 major releases a year,” Mullenweg said during the dev chat.

In 2016, Mullenweg began describing how WordPress could become “the operating system of the web,” with open APIs that others can build on. While that idea encompasses a lot more than just release schedules, WordPress seems to be moving in the direction of shipping updates that come more frequently and eventually more invisibly in the background, similar to how users update their browsers. Releasing Gutenberg in its current state, with frequent updates following, could prove to be a major testing ground to see if greater world of WordPress users are ready to embrace this new era of rapid iteration.

by Sarah Gooding at November 09, 2018 12:03 AM under WordPress 5.0

November 08, 2018

WPTavern: Adding Aligned Images to Paragraphs in Gutenberg Is Not as Tough as I Thought

Last week, I published an article that describes the process I went through in Gutenberg to try to add an aligned image to a paragraph block. I concluded that performing the task in the Classic Editor was easier than in Gutenberg. In response to the article, William Earnhardt compared the process and showed how it can be accomplished in two steps in Gutenberg.
  1. Drag an image into editor where you want it to go.
  2. Click align right.
Dragging and dropping images into WordPress is not something I do. It’s not how I write. His method is simpler but I prefer to work within the interface. His second suggestion of accomplishing the task is the method I’ll use from now on.
  1. Click the block inserter above the paragraph you want to insert the image before.
  2. Select the image block.
  3. Drag the image onto the block.
  4. Click align right.
In the last few months of using Gutenberg, I’ve become accustomed to adding new blocks by pressing enter at the end of a paragraph block or by clicking the plus sign to the left of a block. I haven’t used the plus sign between blocks but it makes sense and indeed, it’s quicker to accomplish the task. According to Earnhardt, there are even more ways to complete the task in Gutenberg. This brings up an important question, how many different ways and user interfaces should there be to accomplish a task? If you don’t do it a certain way, are you doing_it_wrong?
Take for example, adding captions to images. In Gutenberg, there are at least two opportunities to add a caption. The first is the attachment details screen after uploading or selecting an image from the media library. The second is the Image block user interface. When using the Image block interface, my cursor gets stuck in the caption area and I need to click outside of the block in order to continue. If I use the attachment details screen, it automatically puts the caption text into the image block, bypassing the hurdle. Which interface am I supposed to use and which method is considered doing_it_wrong?
Adding a Caption via the Image Block Interface

I’m Willing to Learn

I understand the long vision of Gutenberg and what it means for the future of WordPress. For the past several months, I’ve used the plugin and interface exclusively to craft content. I’ve been learning things along the way and trying to readjust my workflows but the question I keep coming back to when doing things in Gutenberg is why? Why is this button hidden? Why are there three differently located buttons to add blocks when it would be nice to memorize one? Why does this do that and vice versa? Where is all of the research and usability testing that explains the why behind so many of the interactions and flows? Am I just a moron or is it the interface that guides me in the wrong direction? Many of my experiences in using Gutenberg this past year have been echoed by Mark Root-Wiley. He does a great job of saying what I’ve been feeling and thinking for a long time. When I and thousands of others watched Matías Ventura‏ perform a live demo of Gutenberg at the 2017 State of Word, people were blown away. But this is someone who has been creating Gutenberg from the core and is proficient in all that it offers. Is this the level of Gutenberg proficiency I and others need in order to get things done? Probably not, but at times, it sure feels that way.

by Jeff Chandler at November 08, 2018 07:37 AM under gutenberg

November 07, 2018

WPTavern: Classic Editor Plugin May Be Included with 5.0 Updates, Support Window Set to End in 2021

Gary Pendergast announced this morning that the Classic Editor plugin will be officially supported until December 31, 2021. The plugin eases the transition for sites where plugins or themes are not yet compatible with Gutenberg and gives users the opportunity to preserve their existing workflows.

“Since the Classic Editor plugin is central in this transition, we are considering including it with upgrades to WordPress 5.0,” Pendergast said. “New WordPress installs would still add it manually, and we’ve included it in the Featured Plugins list to increase visibility. If you have thoughts on this idea, please leave a comment.”

Pendergast clarified that “officially supported” means that the plugin “will be guaranteed to work as expected in the most recent major release of WordPress, and the major release before it.” He also said the project will evaluate the continuing maintenance of the plugin in 2021 and may possibly extend the date.

The post has already received quite a bit of feedback and generally positive reactions to the prospect of including the Classic Editor along with 5.0 updates for existing sites.

WordPress Core Committer Pascal Birchler asked for a clarification on what “we” referred to in Pendergast’s post, and Pendergast clarified that he is speaking on behalf of the WordPress project. Other commenters pressed for more information, as the announcement was delivered as something that had already been decided and the conversation surrounding the decision was not public.

“I’m grateful for the communication on a hard date for support of the classic editor,” Darren Ethier commented on the post. “It helps many people depending on WordPress for their livelihood to make plans surrounding things depending on it. But for volunteers who ‘show up’ at meetings and in contributing, the process for arriving at these kinds of decisions in an open source project is very opaque and seems to be increasingly so.”

This announcement highlights a trend in recent decision making for the project where decisions on important items appear to have been made behind closed doors without community input. Matthew MacPherson’s proposal for an independent accessibility audit, which had broad support from the community, was shut down in a similar way. MacPherson was named WordPress 5.0’s accessibility lead but didn’t seem to be fully vested with the power to lead that aspect of the release in the community’s best interests. I asked MacPherson if he could further clarify how the decision to forego the audit was reached, as it seemed even a surprise to him in the GitHub issue thread. He said he had “no comment” on how the decision came about.

WPCampus is now pursuing an accessibility audit in order to better serve its community of more than 800 web professionals, educators, and others who work with WordPress in higher education.

“We’re receiving a lot of interest and I’m holding meetings with potential vendors to answer their questions,” WPCampus director Rachel Cherry said. “We’ve received a lot of messages from individuals and organizations wanting to contribute financially.”

The recent report from the accessibility team demonstrates critical issues that prevent the team from recommending Gutenberg to users of assistive technology. These issues also have a major impact on those using WordPress for higher education, as the law requires them to meet certain standards. Several in this particular industry commented on Pendergast’s post to advocate for shipping the Classic Editor plugin with new installs as well.

“Many organizations who use WordPress are required by law to provide accessible software under Section 508,” Rachel Cherry said. “Until such a time when the accessibility of Gutenberg has been improved, and Section 508 compliance is clear, these organizations will require use of the Classic Editor.

“Not to mention the users who will be dependent upon the Classic Editor to have an accessible publishing experience.

“Please consider bundling Classic Editor with all versions of core, new and updated, going forward so that every end user has the easy and inclusive option of using it from day one.”

Elaine Shannon, another WordPress user who works in academia, also commented on the Pendergast’s post to recommend having the Classic Editor bundled with new versions of WordPress, due to many education sites running on multisite installations.

“Some institutions are on managed hosts, where they’ll receive 5.0 without initiating the update themselves,” Shannon said. “Others are managed by on-campus IT services, where one campus admin will push the update and affect thousands of users. In many cases, these are MultiSites where end users – the ones who need the choice of whether to use Gutenberg or Classic Editor – do not have the ability to add a plugin. So regardless of whether these users are in a brand-new shiny install or just an updated existing one, many users are going to need to fall back to the Classic Editor, and if it’s not bundled with Core there will be some folks left having to contact their administrator.”

Pendergast’s post said the WordPress project is considering including the plugin with upgrades to 5.0 but did not identify where or when that decision will be made. However, users who depend on the plugin now have a clear idea of how long it will be supported.

“As for the EOL on Classic Editor support, that’s probably more clarity than [the core team] has ever really given on a feature-to-plugin transition and I’m in favor of having that hard date,” WordPress core developer Drew Jaynes said. “It sets the right tone that the plugin is not intended as a long-term solution, rather a stopgap with a definitive EOL.”

by Sarah Gooding at November 07, 2018 08:13 PM under gutenberg

WPTavern: Nidhi Jain Is Awarded the Kim Parsell Travel Scholarship

In 2015, the WordPress Foundation created a travel scholarship in memory of Kim Parsell. The scholarship covers travel expenses, lodging, and a ticket to the event. This year’s recipient is Nidhi Jain from Udaipur, Rajasthan, India. Jain is a volunteer organizer for WordCamp Udaipur, a WordPress developer, contributor, and a seasoned traveler.
“Being selected for the Kim Parsell Memorial Scholarship is an honor, achievement and a proud moment for me,” Jain told the WordCamp US organizing team when asked what it means to be selected.  “I will try my best to make the most out of it and give back to the community in all possible ways. Since I have been a WordCamp volunteer and organizer in the last few years, I am excited to see and learn from WordCamp US. I am sure, I will have a lot of sweet memories and wonderful learnings to take back home.” Previous winners include Elizabeth Shilling in 2016 and Bianca Welds in 2017. If you’re not familiar with who Kim Parsell is, I recommend reading this essay which provides some context as to why the scholarship was created in her memory.

by Jeff Chandler at November 07, 2018 01:59 PM under wordcamp us

HeroPress: Accidental Activist

Pull Quote: Imagine a world where more kinds of people are speaking up. That's a world I'm excited to see.

I never meant to become an activist. I swear. It was an accident.

And yet here I am, celebrating my one year anniversary of leading the Diversity Outreach Speaker Training working group in the WordPress Community team. We are causing waves in the number of women and other underrepresented groups who are stepping up to become speakers at WordPress Meetups, WordCamps, and events. Pretty cool, right?

How did this happen?

Let’s start this story with how I got into WordPress. Back in 2011, I was looking for a practicum placement for the New Media Design and Web Development college program I was in in Vancouver, BC. We had touched on WordPress only briefly in class. I was curious about it, so I got a Practicum placement working on a higher education website that was built in WordPress. (It was in BuddyPress, even! Ooh. Aah.) As a thank you, my practicum advisor bought me a ticket to WordCamp Vancouver 2011: Developer’s Edition. That event was the start of my love affair with WordPress and I began taking on freelancing gigs. I’ve been a WordPress solopreneur for most of the time since.

The following year my practicum advisor, who had become a client, was creating the first ever BuddyCamp for BuddyPress. He asked me to be on his organizing team. (Side note: I was especially excited to moderate a panel with Matt Mullenweg and other big names on it!) I was noticed and I was invited to be on the core organizing team for the next year’s WordCamp Vancouver by the lead organizer. I was thrilled. It was quite an honour!

This is where the real story begins… after an important disclaimer.

Disclaimer: For simplicity in this story, I’ll be using the terms women and men, though in reality gender is not a simple binary and is actually a wide spectrum of different identities.

The Real Beginning

There were three of us—myself and two men—and it was our first time any of us were organizing a WordCamp. We were having dinner in one of our apartments and we had 40 speaker applications spread out before us. The plan was to pick 14 to speak. It was hard. They were all really good.

The lead organizer grabbed 6 out of the 7 that came from the women and said, “Well, we are accepting all of these.”

At this point I didn’t know that not many women were applying to speak at tech conferences at the time.

So I was the one saying, “Wait, wait. Who cares what gender they are? Let’s go through them and pick based on the topics that would fit the conference’s flow.”

They both said that the 6 of the women’s pitches were really good, fit with the flow, and frankly, we needed to accept as many as we could or we’d get called out. (This is embarrassing to say now, but that was the conversation back in 2013.)

Here’s how it went down:

After we accepted the six, two of the women dropped out for family emergencies. (Guess how many men dropped out for family emergencies?) Also we had added a third speakers’ track. Now there were only 4 women out of 28 speakers. Only 1 in 7. That is 14%, my friends. That is not great.

So not great, in fact, that we did get called out. People did talk about it, question us about it, and even wrote blog posts about it.

More Experience

So when later that year I went to WordCamp San Francisco—the biggest WordCamp at the time (before there was a WordCamp US)—I took the opportunity to chat with other organizers at a WordCamp organizer brunch.

I found out that many of the organizers had trouble getting enough women presenters.

I was surprised to find that we actually had a high number of women applicants in comparison to others, as many of them had zero! They were asking me how we got such a high number. They all said they would happily accept more if only more would apply.

So then I needed to know, why was this happening? Why weren’t we getting more women applicants? I started researching, reading, and talking to people.

Though this issue is complex, one thing that came up over and over was that when we would ask the question, “Hey, will you speak at my conference?” we would get two answers:

  • “What would I talk about?”
  • “I’m not an expert on anything. I don’t know enough about anything to give a talk on it.”

That’s when the idea happened.

The Idea

As it goes, the idea happened while I was at a feminist blanket-fort slumber party. Yes, you heard right. And as one does at all feminist blanket-fort slumber parties, we talked about feminist issues.

When I brought up my issue about the responses we were getting, one of the ladies said, “Why don’t you get them in a room and have them brainstorm topics?”

And that was it. That set me on the path.

I became the lead of a small group creating a workshop in Vancouver. In one of the exercises, we invited the participants to brainstorm ideas and show them that they have literally a hundred ideas. (Then the biggest problem becomes picking one. 🙂 )

In our first iteration, we covered:

  • Why it matters that women (added later: diverse groups) are in the front of the room
  • The myths of what it takes to be the speaker at the front of the room (aka beating impostor syndrome)
  • Different speaking formats, especially story-telling
  • Finding and refining a topic
  • Tips to becoming a better speaker
  • Practising leveling up speaking in front of the group throughout the afternoon

Other cities across North America got wind of our workshop and started running it as well, and they added their own material.

Our own participants wanted more support, so the next year we added material created from the other cities as well as generated more of our own:

  • Coming up with a great title
  • Writing a pitch that is more likely to get accepted
  • Writing a bio
  • Creating an outline
  • Creating better slides

We did it! In 2014—in only one year since we started—we had 50% women speakers and 3 times the number of women applicants! Not only that, but it was a Developer’s Edition. It’s more challenging it is to find women developers in general, let alone those who will step up to speak.

Building On

Impressive as that is, the reason I am truly passionate about this work is because of what happened next:

  • Some of the women who did our workshop and started publicly speaking stepped up to be leaders in our community and created new things for us. For example, a couple of them created a new Meetup track with a User focus.
  • A handful of others became WordCamp organizers. One year Vancouver had an almost all-female organizing team – 5 out of 6!
  • It also influenced local businesses. One local business owner loved what one of the women speakers said so much that he hired her immediately. She was the first woman developer on the team, and soon after she became the Senior Developer.

It is results like these that ignited my passion. I’ve now seen time and again what happens when different kinds of folks speak in the front of the room. More kinds of people feel welcome in the community. The speakers and the new community members bring new ideas and new passions that help to make the technology we are creating more inclusive as well as generate new ideas that benefit everyone.

This workshop has been so successful, with typical results of 40-60% women speakers at WordCamps, that the WordPress Community Team asked me to promote it and train it for women and all diverse groups around the world. We created the Diversity Outreach Speaker Training working group. I started creating and leading it in late 2017.

Thanks to our group, our workshop has been run in 17 cities so far this year, 32 have been trained to run it, and 53 have expressed interest in 24 countries. Incredible!

I love this work so much that I’m now looking at how to do this for a living. I’m proud of how the human diversity represented on the stage adds value not only to the brand but also in the long-term will lead to the creation of a better product. I’m inspired by seeing the communities change as a result of the new voices and new ideas at the WordPress events.

“Jill’s leadership in the development and growth of the Diversity Outreach Speaker Training initiative has had a positive, measurable impact on WordPress community events worldwide. When WordPress events are more diverse, the WordPress project gets more diverse — which makes WordPress better for more people.”

– Andrea Middleton, Community organizer on the WordPress open source project

I’m exploring sponsorships, giving conference and corporate trainings, and looking at other options so that I can be an Accidental Activist full-time and make a bigger impact. Imagine a world where more kinds of people are speaking up. That’s a world I’m excited to see.


Workshop: http://diversespeakers.info/

More info and please let us know if you use it or would like help using it: https://tiny.cc/wpwomenspeak

Diversity Outreach Speaker Training Team—Join us! https://make.wordpress.org/community/2017/11/13/call-for-volunteers-diversity-outreach-speaker-training/

How to build a diverse speaker roster: Coming soon. Contact Jill for it.

The post Accidental Activist appeared first on HeroPress.

by Jill Binder at November 07, 2018 12:00 PM

November 06, 2018

WPTavern: Authors of Popular WordPress.org Themes Rolling Out Gutenberg Compatibility Updates Ahead of 5.0 Release

Astra, a free theme that has steadily been growing in popularity, is now fully compatible with Gutenberg. The theme was first released in May 2017 and has more than 100,000 active installations. It was downloaded approximately 2,000 – 4,500 times per day over the past month and currently maintains a 5-star average rating on WordPress.org after 844 reviews.

Astra’s creators advertise the theme as fast, lightweight (less than 50KB on frontend), and compatible with many page builders. These features have been key to its rapid growth. Last week they announced full Gutenberg compatibility, which means sites built with Astra will be able to take advantage of all the new features in the editor when 5.0 is released.

Astra’s Gutenberg compatibility update includes front-end styles displayed in the editor and support for the full-width alignment option. The width of the content in the editor matches that of the frontend, and the same is true for the typography, colors, and background.

The theme also ensures that the default Gutenberg blocks, i.e. quotes and galleries, will inherit Astra customizer styles to match the rest of the site.

Astra’s creators support the theme by offering commercial packages that include additional features and plugins, starter sites, add-ons for page builders, and support. They plan to offer additional Gutenberg features in commercial add-ons. Astra’s Ultimate Addons product will introduce custom blocks, such as Section, Heading, Info Box, Post Grid, Google Map, Table, Social Share, Menu, Buttons, along with pre-made starter templates.

After two months of weekend work, Anders Norén reported that all 18 of his free themes on WordPress.org have been updated to be compatible with Gutenberg. Norén’s popular minimalist style themes have a cumulative rating of 4.97 out of 5 stars and have been downloaded more than 2.2 million times. They are active on an estimated 100,000 WordPress installations.

“There are no custom blocks or other fancy stuff to be found in the updates, but if you’re running one of my themes, you should be able to update to WordPress 5.0 and start using Gutenberg without any hitches, in the editor or on the front-end,” Norén said. “If you plan to keep using the classic editor, things should look mostly the same after you install the update.”

The Gutenberg compatibility update for Norén’s themes includes editor styles, with layout, typography and colors matching the theme, styles for core blocks and new alignment options, and custom font sizes and color palette in the editor. Norén also took the opportunity to do an overall code cleanup and add improvements for older versions of PHP, accessibility and localization improvements, and bug fixes, amounting to 17,525 lines of code added or modified.

“The past couple of weekends have been grueling, but knowing that my themes will be ready for WordPress 5.0 – whether it hits the November 20th release date or not – was worth it,” Norén said.

Themeisle has updated Hestia with Gutenberg compatibility in the theme’s 2.0 release. The popular Material Design WordPress theme is the company’s flagship product and is installed on more than 100,000 WordPress sites. The company is planning to release a brand new theme that will be fully Gutenberg compatible. They have not yet announced if Zerif Lite (100,000+ installs) will be updated for the new editor.

Six weeks ago, searching the WordPress.org Theme Directory for “Gutenberg” produced 26 results where compatibility is mentioned in the theme descriptions. That number has jumped to 53. Support for the new editor seems to have happened much faster in the commercial theme space where searching for Gutenberg on Envato already turns up hundreds of results before the editor has even landed in core. Authors of free themes on WordPress.org don’t always have the same motivation. Those who support popular themes are more likely to have their themes compatible by the time WordPress 5.0 arrives, especially if the free theme is connected to a paid product.

by Sarah Gooding at November 06, 2018 04:34 AM under gutenberg

November 05, 2018

WPTavern: WordPress 5.0 Beta 3 Released, RC 1 Expected November 12

WordPress 5.0 Beta 3 was released this morning. This beta incorporates all the changes from Gutenberg 4.2 RC1, which was released last week. It fixes a bug with the display of the custom fields meta box and also improves REST API requests.

Gutenberg has undergone a few UI tweaks and introduces a Formatting API for adding new RichText components. The inserter between blocks was updated to provide a more consistent experience that matches the other “add block” buttons. Version 4.2 also adds support for displaying icons in new block categories to better organize groups of blocks. The example pictured in the release post shows the Jetpack icon. The Jetpack team has been working on a number of blocks for existing features and is expected to release those soon.

WordPress 5.0 Beta 3 brings in updates from Twenty Nineteen’s GitHub repository, including support for selective refresh widgets in the customizer, support for responsive embeds, and tweaks to improve the experience on mobile devices.

Updates to WordPress 5.0 Schedule: More Beta Releases and a Shortened RC Period

WordPress 5.0 is now two weeks away from its projected release date of November 19. Last week Gary Pendergast announced some updates to the 5.0 release schedule that build in extra time for betas. After pushing out Beta 3 Pendergast said he expects to release Beta 4 later this week. He also offered an explanation for why RC1 is scheduled for release on November 12, allowing for just one week of last-minute testing following RC.

“The block editor has been available for over a year,” Pendergast said. “It’s already had a longer testing period, with 30 times the number of sites using it, than any previous WordPress release. The primary purpose of the beta and release candidate periods is to ensure that it’s been correctly merged into Core.”

Initial feedback on the schedule changes indicate that some user would appreciate a longer RC period, since the code being tested has changed so often.

“The API freeze just happened in version 4.2, so saying the editor has been available for over a year in anywhere near its current state doesn’t make sense for a 7-day RC period on such a major change,” WordPress trainer and developer Brian Hogg said.

“As an example, just in the last version or two the hover-over menu to remove a block has been taken out and tucked away at the top menu (which was available as shown in https://youtu.be/yjqW_IS6Q7w?t=80), with little time for anyone to provide usability feedback on changes like this.”

Those who are creating training materials and videos have been waiting for a bit of a reprieve in Gutenberg development to make sure their materials are accurate and ready for 5.0.

“Knowing it’s an RC means we can assume a level of ‘this is how it will be’ that just isn’t necessarily with pre-RC versions,” Modern Tribe developer George Gecewicz commented on the post. “That relative certainty is useful for testing aggressively, finalizing design/UI stuff, and revealing post-merge bugs.”

Gutenberg 4.1 was supposed to be the “UI freeze” milestone, but that hasn’t happened yet with several changes introduced in 4.2.

There should be short window of time before 5.0 is released where training materials can be finalized. However, the Gutenberg team plans to continue on from there with its same pace of development.

“Over the past six months, there has been a release every two weeks,” Pendergast said. “We’ll plan to continue that over the first few WordPress 5.0.x releases, to ensure that bug fixes are available as quickly as possible. How soon should we expect WordPress 5.0.1? Approximately two weeks after WordPress 5.0, unless we see bug reports that indicate a need for a faster release.”

WordPress 5.0 is on schedule for its original release date, but there is still a possibility for the the release to be delayed. Matt Mullenweg, commenting on responses to the accessibility team’s assessment of Gutenberg, said that delaying the release has “definitely been considered” and that it may still happen. His response also indicates that WordPress users can expect the pace of core development to continue along the path Gutenberg has carved.

“Despite some differences that still need be resolved, there’s general consensus that the long-term way to create the best WP experience for all types of users is not something you can tack on with 5-6 weeks at the end, but will be the result of continuing the continuous iteration we’ve had with the 42 public releases of Gutenberg so far,” Mullenweg said. “It means we can get improvements into the hands of users within weeks following a release, not months (or years) as was the old model with WordPress.”

by Sarah Gooding at November 05, 2018 06:39 PM under gutenberg

Dev Blog: WordPress 5.0 Beta 3

WordPress 5.0 Beta 3 is now available!

This software is still in development, so we don’t recommend you run it on a production site. Consider setting up a test site to play with the new version.

There are two ways to test the WordPress 5.0 Beta: try the WordPress Beta Tester plugin (you’ll want “bleeding edge nightlies”), or you can download the beta here (zip).

WordPress 5.0 is slated for release on November 19, and we need your help to get there. Here are some of the big issues that we’ve fixed since Beta 2:

Block Editor

The block editor has been updated to include all of the features and bug fixes from the upcoming Gutenberg 4.2 release. Additionally, there are some newer bug fixes and features, such as:

  • Adding support for the “Custom Fields” meta box.
  • Improving the reliability of REST API requests.
  • A myriad of minor tweaks and improvements.

Twenty Nineteen

Twenty Nineteen has been updated from its GitHub repository, this version is full of new goodies to check out:

  • Adds support for Selective Refresh Widgets in the Customiser.
  • Adds support for Responsive Embeds.
  • Tweaks to improve readability and functionality on mobile devices.
  • Fixes nested blocks appearing wider than they should be.
  • Fixes some errors in older PHP versions, and in IE11.

How to Help

Do you speak a language other than English? Help us translate WordPress into more than 100 languages! 

If you’re able to contribute with coding or testing changes, we have a multitude of bug scrubs scheduled this week, we’d love to have as many people as we can ensuring all bugs reported get the attention they deserve.

If you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, file one on WordPress Trac, where you can also find a list of known bugs.

WordPress Five Point Oh
is just two short weeks away.
Thank you for helping!

by Gary Pendergast at November 05, 2018 12:20 AM under Releases

November 02, 2018

WPTavern: GitHub Rolls Out More Small Improvements as Part of Project Paper Cuts

In August, GitHub announced Project Paper Cuts, an effort aimed at bringing small improvements to the developer and project maintainer experiences. These are fixes for issues that don’t generally fall within larger initiatives. Some of the first improvements that have already been implemented include the following:

  • Unselect markers when copying and pasting the contents of a diff
  • Edit a repository’s README from the repository root
  • Access your repositories straight from the profile dropdown
  • Highlight permalinked comments
  • Remove files from a pull request with a button
  • Branch names in merge notification emails
  • Create new pull requests from your repository’s Pull Requests Page
  • Add a teammate from the team discussions page
  • Collapse all diffs in a pull request at once
  • Copy the URL of a comment

One of the latest improvements allows repository admins to transfer an issue that has been misfiled to another repository where it belongs. At the moment it only works within the same GitHub organization account. Initial feedback from users indicates many would appreciate this feature require push permissions, instead of admin permissions, as there are likely more users who can help in the bug tracker with moving issues, setting labels, and closing bugs.

The “suggested changes” feature GitHub introduced in beta two weeks ago seems to have been adopted fairly quickly by users. Suggested Changes lets users suggest a change to code in a pull request. These changes can be accepted by the author or assignees with one click and then committed.

GitHub reports more than 10 percent of all reviewers suggested at least one change. They have received 100,000 suggestions and estimate that 4% of all review commits created have included a suggestion. Based on feedback so far, GitHub put the following improvements on the roadmap for the Suggested Changes feature:

  • The ability to suggest changes to multiple lines at once
  • The ability to accept multiple changes in a single commit

Project Paper Cuts is borrowing heavily from Refined GitHub, a browser extension that simplifies the GitHub interface and adds useful features.

“Full-time open source developer Sindre Sorhus has built a great browser extension that builds on and improves the GitHub experience, along with a fantastic community that has come together to discuss workflows and build their favorite features,” GitHub product manager Luke Hefson said. “Project Paper Cuts has taken inspiration from a lot of Refined GitHub’s additions, and we’re building some of the most-loved features right into GitHub itself.”

GitHub is aiming to be more open and transparent with user feedback after the 2016 fiasco with disgruntled open source project maintainers. These fixes for small annoyances add up in the grand scheme of things to improve project workflow for millions of developers and project maintainers. The improvements are shipping out regularly and are all outlined in GitHub’s public changelog.

by Sarah Gooding at November 02, 2018 06:58 PM under github

WPTavern: WPWeekly Episode 336 – Interview With Andrew Roberts, CEO and Co-founder of Tiny

In this episode, John James Jacoby and I are joined by Andrew Roberts, CEO and Co-founder of Tiny. Tiny is the company behind the popular open source library TinyMCE. Roberts shares his entrepreneurial journey, what the company plans on doing with its recent round of funding, and the relationship between TinyMCE and Gutenberg.

Here is an excerpt from the show on what Roberts thinks about Gutenberg.

I think that ultimately Gutenberg will be more innovative than just incrementally changing from the old editor experience toward block-based editing.

I think you know Matt’s probably had a tough year with some of the criticisms around Gutenberg but I admire his courage and leadership because if he hadn’t put his brand equity on the line, if he hadn’t invested his goodwill in doing this, this would never be launching in a month from now.

There may be a painful year or two but in the grand scheme of things this will turn out for the better. It’s taken a lot of courage and bravery for him to do that. He’s taken a lot of shots in the back, but you know that’s why he gets paid the big bucks as they say.

Stories Discussed:

WordPress 5.0 Beta 1
WordPress Accessibility Team Delivers Sobering Assessment of Gutenberg: “We have to draw a line.”
WooCommerce 3.5 Introduces REST API v3, Improves Transactional Emails
WP Engine Acquires Array Themes

WPWeekly Meta:

Next Episode: Wednesday, November 7th 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 #336:

by Jeff Chandler at November 02, 2018 01:25 PM under tinymce

WPTavern: How to Add an Image to A Paragraph Block in Gutenberg

WordPress 5.0 is on the horizon and with it comes a number of opportunities to explain how to get things done in the new editor.

Testing Scenario

A user has written three paragraphs and decides to add an image to the second paragraph. This user wants the image to be aligned to the right.

Accomplishing the Task in the Classic Editor

The classic editor is essentially one big block. Adding media to a paragraph is as quick as placing the mouse cursor at the beginning of a paragraph, clicking the add new media button, selecting or uploading an image, and choosing its alignment.

Accomplishing the Task in Gutenberg

In Gutenberg, each paragraph is a block and each block has its own toolbar. This is important because after writing three paragraphs, you can’t click on an add media button. Instead, you need to create an image block.

Once you’ve selected an image, you need to move the image block above the paragraph block where you want to insert it. At first, you might try to drag and drop the image into the paragraph but that doesn’t work. You need to use the up and down arrows or drag the block into position.

Once the image block is in the correct location, click the align right icon. The image will be inserted into the right side of the paragraph block.

A Right Aligned Image Inside of A Paragraph Block

If you want to move the image to a different paragraph block, you’ll need to click the Align center button which turns the image back into its own block and repeat the process described above.

Adding Images to Paragraphs in the Classic Editor Is Easier

The task I described above is one I think millions of users will have trouble completing when WordPress 5.0 is released. In the Classic editor, the writing flow doesn’t feel disjointed when you want to add images or embed content into posts.

In Gutenberg, everything is a block which in many cases, causes the flow to be disrupted as you need to figure out what block you need, how to manipulate it, where to move it, find where the options are, etc.

The process of adding images to paragraphs will likely improve after WordPress 5.0 is released but until then, the Classic editor wins this use case.

by Jeff Chandler at November 02, 2018 11:35 AM under images

WPTavern: Google’s reCAPTCHA v3 Promises a “Frictionless User Experience”

Google introduced reCAPTCHA v3 this week, which promises a new “frictionless user experience.” Earlier versions of the API stopped bots but also drew the ire of internet users across the globe. Users were regularly inconvenienced with distorted text challenges, street sign puzzles, click requirements, and other actions to prove their humanity.

v3 offers a marked improvement by detecting bots in the background and returning a score that tells the admin if the interaction is suspicious. It scores traffic with its Adaptive Risk Analysis Engine instead of forcing human users to perform interactive challenges. The score can be used three different ways:

  • Set a threshold that determines when a user is let through or when further verification needs to be done, i.e. two-factor authentication or phone verification.
  • Combine the score with your own signals that reCAPTCHA can’t access, such as user profiles or transaction histories.
  • Use the reCAPTCHA score as one of the signals to train your machine learning model to fight abuse.

v3 give site owners more options to customize the thresholds and actions for different types of traffic. The video below explains how it works and the developer docs have more information on frontend integration and score interpretation.

Site owners can view their traffic in the reCAPTCHA admin console. It also displays a list of all of your sites and what version of the API they are using.

The admin console also has a form for registering new sites:

The WordPress Plugin Directory has dozens of standalone plugins and contact forms that make use of reCAPTCHA in some way. Sites that are already set up to use v2 or the Invisible CAPTCHA, will not automatically update to use v3. There’s a different signup and implementation process that the site owner has to perform before having it integrated on the site.

WordPress plugin developers who offer reCAPTCHA will have to decide if they want to update existing plugins to use v3 or package a v3 offering in a new plugin. The reCAPTCHA v1 API was shut down earlier this year in March. Google’s reCAPTCHA PHP client library on GitHub is still actively encouraging use of both v2 and v3. A date has not been announced for v2 to be deprecated.

by Sarah Gooding at November 02, 2018 12:09 AM under recaptcha

November 01, 2018

Dev Blog: Quarterly Updates | Q3 2018

To keep everyone aware of big projects and efforts across WordPress contributor teams, I’ve reached out to each team’s listed representatives. I asked each of them to share their Top Priority (and when they hope for it to be completed), as well as their biggest Wins and Worries. Have questions? I’ve included a link to each team’s site in the headings.


  • Contacted: @joedolson, @audrasjb, @arush
  • Priority: Work on authoring a manual for assistive technology users on Gutenberg, led by Claire Brotherton (@abrightclearweb). Continue to work on improving the overall user experience in Gutenberg. Update and organize the WP A11y handbook.
  • Struggle: Lack of developers and accessibility experts to help test and code the milestone issues. Still over 100 outstanding issues, and developing the Gutenberg AT manual helps expose additional issues. The announcement of an accessibility focus on 4.9.9 derailed our planning for Gutenberg in September with minimal productivity, as that goal was quickly withdrawn from the schedule.
  • Big Win: Getting focus constraint implemented in popovers and similar components in Gutenberg.


  • Contacted: @danielbachhuber, @schlessera
  • Priority: Current priority is v2.1.0 of WP-CLI, to polish the major refactoring v2.0.0 introduced. You can join in or follow progress on their site.
  • Struggle: Getting enough contributors to make peer-review possible/manageable.
  • Big Win: The major refactoring of v2 was mostly without any negative impacts on existing installs. It provided substantial improvements to maintainability including: faster and more reliable testing, more straight-forward changes to individual packages, and simpler contributor on-boarding.



  • Contacted: @jeffpaul
  • Priority: Continued preparation for the 5.0 release cycle and Gutenberg.
  • Struggle: Identifying tasks for first time contributors, as well as for new-to-JS contributors.


  • Contacted: @melchoyce, @karmatosed, @boemedia, @joshuawold, @mizejewski
  • Priority: Preparing for WordPress 5.0 and continuing to work on better onboarding practices.
  • Struggle: Identifying tasks for contributor days, especially for small- to medium-sized tasks that can be fit into a single day.
  • Big Win: Regular contributions are starting to build up.


  • Contacted: @kenshino
  • Priority: Getting HelpHub out before WordPress 5.0’s launch to make sure Gutenberg User Docs have a permanent position to reside
  • Struggle: Getting the documentation from HelpHub into WordPress.org/support is more manual than initially anticipated.
  • Big Win: Had a good discussion with the Gutenberg team about their docs and how WordPress.org expects documentation to be distributed (via DevHub, Make and HelpHub). Getting past the code blocks to release HelpHub (soon)


  • Contacted: @mikeschroder, @jadonn
  • Priority: Helping Gutenberg land well at hosts for users in 5.0.
  • Struggle: Short time frame with few resources to accomplish priority items.
  • Big Win: Preparing Try Gutenberg support guide for hosts during the rollout and good reception from users following it.


  • Contacted: @bridgetwillard
  • Priority: Continuing to write and publish case studies from the community.
  • Big Win: Onboarding guide is going well and is currently being translated.

Meta (WordPress.org Site)

  • Contacted: @tellyworth, @coffee2code
  • Priority: Support for other teams in the lead up to, and the follow-up of, the release of WP 5.0. ETA is the WP 5.0 release date (Nov 19) and thereafter, unless it gets bumped to next quarter.
  • Struggle: Maintaining momentum on tickets (still).
  • Big Win: Launch of front-end demo of Gutenberg on https://wordpress.org/gutenberg/


  • Contacted: @elibud
  • Priority: Have an alpha version of Gutenberg in the WordPress apps, ETA end of year 2018.
  • Struggle: Unfamiliar tech stack and the goal of reusing as much of Gutenberg-web’s code as possible.
  • Big Win: Running mobile tests on web’s PRs.


  • Contacted: @ipstenu
  • Priority: Cleaning up ‘inactive’ users, which was supposed to be complete but some work preparing for 5.0 was necessary.
  • Struggles: Devnotes are lacking for the upcoming release which slows progress.
  • Big Win: No backlog even though a lot were out!



  • Contacted: @clorith
  • Priority: Preparing for the upcoming 5.0 release
  • Struggle: Finding a good balance between how much we want to help people and how much we are able to help people. Also, contributor recruitment (always a crowd favorite!)
  • Big Win: How well the team, on a global level, has managed to maintain a good flow of user engagement through support.

Theme Review

  • Contacted: @acosmin, @rabmalin, @thinkupthemes, @williampatton
  • Priority: Implementing the Theme Sniffer plugin on WordPress.org which is one step forward towards automation. ETA early 2019
  • Struggle: Not having so many contributors/reviewers.
  • Big Win: Implementing multiple requirements into our review flow, like screenshots and readme.txt requirements.


  • Contacted: @bethsoderberg, @juliek
  • Priority: Getting the learn.wordpress.org site designed, developed, and being able to publish lesson plans to it.
  • Struggle: Getting contributors onboard and continually contributing. Part of that is related to the learn.wordpress.org site. People like to see their contributions.
  • Big Win: We have our new workflow and tools in place. We are also streamlining that process to help things go from idea to publication more quickly.

Interested in updates from the last quarter? You can find those here: https://wordpress.org/news/2018/07/quarterly-updates-q2-2018/

by Josepha at November 01, 2018 04:46 PM under Updates

Dev Blog: The Month in WordPress: October 2018

Teams across the WordPress project are working hard to make sure everything is ready for the upcoming release of WordPress 5.0. Find out what’s going on and how you can get involved.

The Plan for WordPress 5.0

Early this month, the planned release schedule was announced for WordPress 5.0, which was updated a few weeks later. WordPress 5.0 is a highly anticipated release, as it’s the official  launch of Gutenberg — the new block editor for WordPress Core. For more detail, check out this  granular timeline.

Along with the planned release schedule, @matt, who is heading up this release, announced leads for critical focuses on the project, including @matveb, @karmatosed, @laurelfulford, @allancole, @lonelyvegan, @omarreiss, @antpb, @pento, @chanthaboune, @danielbachhuber, and @mcsf.

WordPress 5.0 is currently in its second beta phase and will soon move to the release candidate status. Help test this release right now by installing the WordPress Beta Tester plugin on your site.

Want to get involved in building WordPress Core? Follow the Core team blog and join the #core channel in the Making WordPress Slack group. You can also help out by testing or translating the release into a local language.

New Editor for WordPress Core

Active development continues on Gutenberg, the new editing experience for WordPress Core. The latest release is feature complete, meaning that all further development on it will be to improve existing features and fix outstanding bugs.

Some have raised concerns about Gutenberg’s accessibility, prompting the development team to detail some areas in which the new editor is accessible. To help improve things further, the team has made a public call for accessibility testers to assist.

Want to get involved in building Gutenberg? Follow the Gutenberg tag on the Core team blog and join the #core-editor channel in the Making WordPress Slack group. Read this guide to find areas where you can have the most impact.

Migrating HelpHub to WordPress.org

HelpHub is an ongoing project to move all of WordPress’ user documentation from the Codex to the WordPress Support portal.

HelpHub has been developed on a separate staging server and it’s now time to migrate the new documentation to its home on WordPress.org. The plan is to have everything moved over  before WordPress 5.0 is released, so that all the new documentation will be available on the new platform from the start.

The HelpHub team has published a call for volunteers to help with the migration. If you would like to get involved, join the #docs channel in the Making WordPress Slack group, and contact @atachibana to get started.

A New Default Theme for WordPress

A brand new default theme — Twenty Nineteen — has been announced with development being led by @allancole. The theme is packaged with WordPress 5.0, so it will be following the same release schedule as Core.

The new theme is designed to integrate seamlessly with Gutenberg and showcase how you can build a theme alongside the new block editor and take advantage of the creative freedom that it offers.

Want to help build Twenty Nineteen? Join in on the theme’s GitHub repo and join the #core-themes channel in the Making WordPress Slack group.

Further Reading:

  • The Support team are putting together more formal Support Guidelines for the WordPress Support Forums.
  • The group focused on privacy tools in Core has released some details on the work they have been doing recently, with a roadmap for their plans over the next few months.
  • The Core team released an update about how WordPress will be compatible with PHP 7.3.
  • The Theme Review Team have published some new requirements regarding child themes, readme files and trusted authors in the Theme Directory.
  • The WordCamp Europe team are working on a PWA service for all WordCamp websites.

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

by Hugh Lashbrooke at November 01, 2018 08:40 AM under Month in WordPress

October 31, 2018

WPTavern: Gutenberg Cloud Plugin for WordPress is Now in Beta

Frontkom, the team behind the Gutenberg Cloud project, has published the beta version of its WordPress plugin to the official repository. Cloud Blocks serves as a connector, allowing WordPress users to browse and install open source blocks from Gutenberg Cloud. The blocks are hosted on NPM and their assets are served from CloudFlare using unpkg.com.

Gutenberg Cloud’s online library of blocks is CMS agnostic, offering blocks for both Drupal and WordPress sites, and more CMSs in the future. The service advertises three key benefits for developers who host blocks on Gutenberg Cloud:

  • Wider adoption: Your blocks can be used outside of WP
  • Discoverability: Your blocks will pop up in the Cloud Blocks UI
  • Faster development: No plugin/SVN needed, just publish to NPM

Frontkom is actively recruiting WordPress developers to add blocks to the cloud to test the process. Documentation for migrating blocks from a plugin is available on GitHub. Frontkom has also produced a new boilerplate generator for building Gutenberg Cloud blocks.

Users should note that the team is still ironing out the experience for developers adding blocks to the cloud, so the plugin isn’t yet ready for general use. It’s currently under active development.

WordPress Developers Say Gutenberg Cloud May Not be the Best Way to Release Blocks but Platform has Potential

I contacted some WordPress developers who have tested sending their blocks to Gutenberg Cloud to get their initial reactions to the platform.

“The idea that folks will be able to install blocks a la carte is interesting,” CoBlocks author and ThemeBeans founder Rich Tabor said. “It’s pretty much as easy as installing plugins.”

Tabor experimented with migrating his Block Gallery blocks and said the process was not difficult but he foresees difficulties in maintaining blocks across parent plugins and Gutenberg Cloud.

“As a developer, I’m still not entirely convinced Gutenberg Cloud is the best way to release blocks, aside from relatively simple blocks,” Tabor said. “I personally lean towards building suites of blocks that share a relative purpose, instead of one plugin (or one Cloud Block instance) per block. For one, it cuts down on maintenance quite a bit, as custom components can be shared between blocks. And there’s much better discoverability on getting relative blocks in the hands of users — if they’re grouped together.”

Block collections have been criticized for making it difficult to search for and discover individual blocks, but Tabor makes some good arguments for improving block discoverability by grouping together features users often need. That is the whole point of successful plugins like Jetpack, but this type of packaging also lends itself to criticism about bloat.

“It’s a similar conundrum when we look at grouped/not grouped shortcode plugins,” Tabor said. “I suppose the main difference is that the nature of blocks is much more complicated than that of shortcodes. History seems to repeat itself.”

Tabor said he is considering distributing a few of his free blocks through Gutenberg Cloud but he hasn’t fully decided yet.

WordPress core contributor, Josh Pollock, who has worked extensively with React and Gutenberg, also tested the Gutenberg Cloud platform. He said he thinks it has a lot of potential for developers who write blocks that are mainly JavaScript already.

“I could see how an agency that builds WordPress sites could save a lot of time and hassle building out a block library,” Pollock said. “As a plugin developer with a lot of little ideas, the pain and time of setting up a block and block environment, which no one has gotten right yet, makes me very excited about this.”

Pollock also reported a positive experience with the create-cloud-block generator.

“The code that create-cloud-block generates is well-written, but not too opinionated,” Pollock said. “The developer experience is both really cool — you preview your block in a functional Gutenberg-powered editor with no WordPress site attached — and a little frustrating as there is no live reload yet. I know they are just getting started and the tool doesn’t lock you into any structure, which is great. I’ll be keeping my eye on this project.”

Frontkom CTO Per André Rønsen said his team will continue testing the cloud internally until they get more developer feedback on the corresponding WordPress plugin. For Drupal users, Gutenberg Cloud will be shipped as a submodule of Gutenberg, which means all sites that install Gutenberg will also get the Cloud module. It can, however, be disabled. Rønsen said his team plans to showcase Gutenberg Cloud for D8 at DrupalCamp Oslo in November.

by Sarah Gooding at October 31, 2018 11:12 PM under Gutenberg Cloud

Matt: What’s in My Bag, 2018 Edition

  1. SDR Kashmir Travel Folio, made with this super-cool material called Dyneema, which is twice as strong as Kevlar and 15 times as strong as steel, but virtually weightless.
  2. Garmin Forerunner 935 which is a triathlon watch, so it can tell me how much I don’t run, how much I don’t bike, and how much I don’t swim. Crazy sensors on it, and it’s lighter than an Apple Watch, which I tried again to use this year but wasn’t able to handle another device in my life that I had to charge daily. It has a weird charger, pictured next to it, but only needs charging once every few weeks so I don’t mind at all.
  3. This is the latest 15” grey touchbar MacBook Pro, customized by Uncover to have the Jetpack logo on it. I like the keyboard quietness and performance improvements of latest generation.
  4. Fit Pack 2 from Aer is the same I wrote a whole blog post about last year, and I still love and adore it every day. They have a few bigger and smaller packs, but the quality is just fantastic and I love all the pockets. Mine is starting to tear a little bit by one of the shoulder straps, but I do keep ~18lbs in it regularly.
  5. This is a grey wool buff, which works as a scarf, a hat, or an eye cover if I’m trying to sleep. I tried this out because of one of Tynan’s also-great gear posts.
  6. Passport, because you never know when you’ll need to leave the country.
  7. Kindle Oasis with this random case on it. I dig that this one is apparently waterproof — which I’ve never tested — but doesn’t feel like we’ve found the perfect size and weight balance yet. Reading is my favorite activity right now so this is my most-loved item.
  8. Imazing 10k charger. Great capacity, charges via USB-C. (2nd year)
  9. I’ve started carrying around some stationery so I can write notes to people when I’m on the road. Now I just need better handwriting…
  10. Delfonics is a funky-cool Japanese stationery, and this 3”x4” Rollbahn notebook is tops, and actually fits in my pocket. The Amazon one linked might be larger, I found it at Paper-Ya on Granville Island.
  11. A small leather bracelet I got in Seoul, Korea.
  12. Two things here: a rolled-up chamois cloth for cleaning glasses, inspired by my late friend Dean, and a WordPress ring I wear sometimes.
  13. Three pens here: A cool customized one we did for Automatticians; a Lamy Accent 4pen which has red, blue, black, and a mechanical pencil built in; a Sharpie for signing stuff.
  14. Have gone away from the carbon fiber clip and now using this small Paul Smith card wallet.
  15. Apple Magic Mouse 2. When this one breaks I’ll switch it out for a black one.
  16. Charger for the MacBook Pro.
  17. A super small international adapter, which is also nice for converting the 3-prong in the next item into a 2-prong. It’s Lenmar but I’m not going to link Amazon because they’re charging too much, just picked up in an airport store.
  18. Probably my favorite new item of the year: I have given Native Union a hard time in the past but super love this combo extension cord and USB charger. It is an 8-foot extension cord, which is remarkably handy, has two AC outlets, 3 USB ports, and one USB-C. Total life-saver.
  19. A dyneema accessory pouch, retaW aoyama / tokyo fragrance lipcream, Aveda Peppymint breath refresher, Aesop Ginger Flight Therapy roller, a spray hand cleanser, and Mintia COLDSMASH.
  20. District Vision makes these these running sunglasses in Japan, which I found at the Snow Peak store in NYC.
  21. These sunglasses are a collaboration between Salt and Aether.
  22. A single-use packet of Sriracha. Hot sauce in your bag? Swag.
  23. A palo santo smudge stick, smells great when you burn it. I’m turning into a hippie.
  24. Hermes business card holder.
  25. iPhone XS with a Jetpack Popsocket.
  26. Pixel 2, now replaced by a Pixel 3 XL.
  27. This is a bag with some small opals I gave as a Burning Man gift.
  28. iPad Pro 10.5 and Apple sleeve with Pencil holder, which is still one of my favorite gadgets of the year. Everything about this device just works and is a pleasure to use, and I’ve already ordered the new 11″ Pro and related accessories.
  29. Half meter (the perfect size) lightning cable.
  30. Apple USB-C dongle.
  31. Cool multi-function USB cable with lightning, two micro-USBs, and USB-C. I give these away all the time now and it’s nice to pair with the battery in #8 because I know I can charge anybody with this thing.
  32. Short USB-C.
  33. Combo micro-USB and Lightning.
  34. Short lightning cable, just like 29.
  35. Velcro cable ties, great for tidying pretty much anything. I just take a few out of the big pack and roll them up to travel with.
  36. Retractable USB-C, don’t love these as they break but it’s the best of what’s out there.
  37. USB-C to Lightning, great for super-fast charging.
  38. My favorite USB-C hub so far, the Satechi Aluminum Type-C Multimedia Adapter with 4K HDMI, Mini DP, USB-C PD, Gigabit Ethernet, USB 3.0, Micro/SD Card Slots. Pretty much everything you could possibly need.
  39. A pretty handy Ventev dashport car port charger that’s small and light. (2nd year)
  40. A few spare SIM cards, some SD cards, thingy to poke SIM card holder, and combo USB-C / USB-A 64gb stick.
  41. Lockpick set. (4th year)
  42. Bragi Pro custom earphones. For many years I had custom in-ear monitors, but the convenience of wireless overcame that, even before they started taking headphone jacks out of phones. Bragi now allows you to send in ear molds from an audiologist and they’ll make these custom true wireless headphones that fit and sound great, but I have trouble recommending because the case is so heavy and once got so jammed I almost thought I’d have to throw the whole thing away, and the app has never been able to “connect” for me because it gets stuck on turning on some fitness sensors. If it could connect I think I could turn off the other feature that is annoying, which is the touch controls that I find get triggered by my hat or when my head is against a chair. So, a qualified “maybe try this.”
  43. Sennheiser Culture Series Wideband Headset, which I use for podcasts, Skype, Facetime, Zoom, and Google Hangout calls with external folks and teams inside of Automattic. Light, comfortable, great sound quality, and great at blocking out background noise so you don’t annoy other people on the call. I’d love to replace this with something wireless but haven’t found one with as high fidelity audio.
  44. GL.iNet GL-AR750 Travel AC Router which I use to create wifi networks different places I go, which is often faster than hotel/etc wifi, and I can also VPN encrypt all my traffic through it. Pretty handy! But not user-friendly. Often keep it in my suitcase and not my backpack. I have a retractable Ethernet and micro-USB attached to it.
  45. Matte black Airpods. I love Airpods and these look super cool, I think these were from BlackPods which looks shut down now but Colorware has some alternatives. (2nd year)
  46. Westone ES49 custom earplugs, for if I go to concerts or anyplace overly loud. (4th year)
  47. An ultralight running jacket I think I got at Lululemon Lab in Vancouver. They don’t have anything like it available online right now but it folds up ultra-tiny, weighs nothing, and is a nice layer for on an airplane. My only complaint (as with all Lululemon products) is the low quality of the zipper. (2nd year)

That’s it for this year. As a bonus I’ll link some of my favorite other-bag items including toiletries: Muji dopp kit bag, these amazing travel bottles for creams, travel atomizer, Elysium Basis, Muji q-tips, Aesop Two Minds Facial Hydrator, Sunleya Sun Care SPF 15, folding brush / comb, Philips Sonicare Brush, Aesop toothpaste, Tom’s SLS-free toothpaste, Orabrush cleaner.

If you’re curious, here are the previous years: 2014, 2016, 2017.

If you have any questions please leave them in the comments!

by Matt at October 31, 2018 03:44 AM under In My Bag

WPTavern: WordPress.com and Jetpack Launch New Activity Feature for Monitoring Website Changes

WordPress.com launched a new Activity feature today, a tool for monitoring changes that occur on the site and actions initiated through the admin. It’s also available for Jetpack-enabled sites and the activity log can be viewed on WordPress.com or on the WordPress mobile apps.

Activity logs the following actions and presents them in an easy-to-read timeline on WordPress.com:

  • Published or updated posts and pages
  • Comment submission and management activity
  • Settings and options modifications
  • Login attempts by registered site users
  • Plugin installations, updates, and removals
  • Theme switches, installations, updates, and deletions

The Activity log can be useful for debugging client sites where the client cannot remember the actions they performed that changed their website. Users can also update plugins and themes directly from the activity log.

WordPress.com’s new Activity feature is reminiscent of XWP’s Stream plugin, which launched in 2013 with similar admin logging features stored locally. It offers support for multisite as well as several popular plugins, such as ACF, bbPress, BuddyPress, EDD, Gravity Forms, WooCommerce, Yoast SEO, and Jetpack. Stream hasn’t gained much traction in recent years with just 30,000 active installations.

In 2014, Stream’s creators explored offering Stream as a service where the logs were stored in AWS and included configurable SMS notifications. The service was shut down in 2015 in favor of storing the activity logs locally due to the expense of cloud storage. Shortly after that it was acquired by XWP.

Automattic is also exploring offering its new Activity feature as a paid service. Currently sites on the Free plan only have access to the last 20 most recent events. Access is tiered based on the plan. Personal and Premium users have access to activities from the last 30 days and Professional users can see all activities for the past year. The ability to filter activities by type is also restricted to paid users only.

Jetpack site owners should note that Activity is activated by default – it’s not a module that can be turned on or off. The feature doesn’t send any new data to WordPress.com but rather offers a new interface for data that is already synced.

The full list of activities the feature collects, as well as privacy information related to data retention, is available for WordPress.com and Jetpack sites in the documentation for the feature. Users can report bugs to the Calypso GitHub repository.

by Sarah Gooding at October 31, 2018 03:04 AM under wordpress.com

October 30, 2018

WPTavern: WordPress Accessibility Team Delivers Sobering Assessment of Gutenberg: “We have to draw a line.”

photo credit: classroomcamera DSC03657(license)

WordPress’ accessibility team has published a statement on the level of overall accessibility of Gutenberg. The team, largely a group of unpaid volunteers, collaborated on a detailed assessment that publicly challenges Gutenberg’s readiness for core in a way that no other WordPress team has done through official channels to date. After a week of testing the most recent version of the plugin, the team concluded that they cannot recommend Gutenberg to be used by anyone who relies on assistive technology.

The Accessibility team – like any team in WordPress – has no specific authority over the project. Because we’re a small team of volunteers, we’ve been pragmatic in how we apply the guidelines. We have made tradeoffs in prioritization. Gutenberg is a place where we feel it is necessary to draw a line. The ability to author, edit, and publish posts is the primary purpose of WordPress.

Accessibility team rep Joe Dolson, speaking on behalf of the team, cited cognitive load and complexity, inconsistent user interface behavior, heavy reliance on keyboard shortcuts, and difficulties with keyboard navigation through blocks, among other concerns about Gutenberg. He outlined an example of the keyboard sequence required to do something as simple as change the font size in a paragraph block. It currently requires 34 separate keyboard stops, and even more if the tester doesn’t have prior knowledge of how to navigate Gutenberg.

“Because the complexity of interaction with Gutenberg is an order of magnitude greater than in the classic editor, we believe that Gutenberg is less accessible than the existing classic editor, though it offers many great features that are not available in the current editor,” Dolson said.

This assessment echoes many of the common themes found in Gutenberg’s reviews on WordPress.org, even among the most recent reviews of the latest version. Ratings are currently hovering at 2.3 out of 5 stars. Users have repeatedly said the interface is “far too heavily reliant on hover based functionality.” Even those without accessibility needs find it confusing, unintuitive, and difficult to navigate content. Some testers find it nearly impossible to do what they want to do with it.

The positive reviews recognize the software as a work in progress and testers seem more aware of the overall vision for the plugin. They are excited about some of the more advanced features that blocks offer, but many positive reviewers urge WordPress to give it more time before making it the default editor.

The accessibility team is convinced that the main accessibility issues in Gutenberg stem from design issues.

“Gutenberg is the way of the future in WordPress, but the direction it has taken so far has been worrying,” Dolson said. “We do not want to miss the opportunity to build a modern and inclusive application for WordPress, but in order to achieve that goal, accessibility needs to incorporated in all design processes in the project.

“These problems are solvable. Retrofitting accessibility is not an effective process. It is costly in terms of time and resources.”

In a recent post titled Iterating on Merge Proposals, Gary Pendergast, who is leading the merge of Gutenberg into core, acknowledged that they could have asked for the accessibility team’s help much earlier in the process.

“The Accessibility team should’ve been consulted more closely, much earlier in the process, and that’s a mistake I expect to see rectified as the Gutenberg project moves into its next phase after WordPress 5.0,” Pendergast said. “While Gutenberg has always aimed to prioritize accessibility, both providing tools to make the block editor more accessible, as well as encouraging authors to publish accessible content, there are still areas where we can improve.”

At this time there has been no official response to the accessibility team’s assessment. It does not look like it will meaningfully impact the release date, as Beta 2 went out last night and RC 1 is planned for release today. If the core dev chats are any indication, contributors involved in 5.0 seem to be on board with the ambitious timeline for its release.

In a post titled “Accessibility in Gutenberg is not a one-more feature,” core developer Drew Jaynes urges the project’s leadership and contributors not to compromise core accessibility standards for the sake of an expedited timeline.

“Please let’s not make the ‘new standard’ be that we’re willing to ship technically accessible but perhaps not entirely usable-for-all features; let’s not define it as one that sacrifices standards core to the WordPress experience in the name of perceived expediency; let’s not define it as the new default authoring experience for all users when not all users can use it well,” Jaynes said.

WordPress 5.0 release lead Matt Mullenweg has frequently said the release will ship when it’s ready. He contends that the interface has been continually modified for accessibility needs throughout the process of developing Gutenberg.

Matthew MacPherson, Gutenberg’s accessibility lead, was not immediately available for comment on the team’s assessment. Ultimately, the decision to delay the release will fall to Mullenweg and his leadership team. The accessibility team, however, will not lend its endorsement of Gutenberg at this time:

The accessibility team will continue to work to support Gutenberg to the best of our ability. However, based on its current status, we cannot recommend that anybody who has a need for assistive technology allow it to be in use on any sites they need to use at this time.

Gutenberg is now 20 days away from landing in WordPress 5.0, but this does not leave enough time to solve the design and architectural issues the accessibility team has identified. They have proposed a notice on the 5.0 release to inform administrators of Gutenberg’s inadequacy for users of assistive technology, with a prompt to install the Classic Editor plugin. Many people with accessibility needs depend on the WordPress editor in order to do their work and will need to stick with the old interface. The proposal has been closed with a note indicating that 5.0 will point users to the Classic Editor plugin if they need it.

The mistake of not having consulted accessibility experts in the design phase cannot be easily rectified at this point, but the Classic Editor is still available for those who need to preserve their same workflow. The conflict lies in whether WordPress should ship a new editor that those with accessibility needs cannot immediately use. It is a somewhat painful and frustrating outcome for those users when the entire ecosystem is rapidly moving towards Gutenberg as the standard.

Either the accessibility and usability issues the team identified are not as bad as they purport or this document is a last-minute clarion call that could prevent WordPress from shipping an editor that excludes users who rely on assistive technology. Due to the gravity of their claims, the accessibility team’s statement on Gutenberg demands an official response.

by Sarah Gooding at October 30, 2018 07:16 PM under gutenberg

Dev Blog: WordPress 5.0 Beta 2

WordPress 5.0 Beta 2 is now available!

This software is still in development, so we don’t recommend you run it on a production site. Consider setting up a test site to play with the new version.

There are two ways to test the WordPress 5.0 Beta: try the WordPress Beta Tester plugin (you’ll want “bleeding edge nightlies”), or you can download the beta here (zip).

WordPress 5.0 is slated for release on November 19, and we need your help to get there. Here are some of the big issues that we fixed since Beta 1:

Block Editor

We’ve updated to the latest version of the block editor from the Gutenberg plugin, which includes the new Format API, embedding improvements, and a variety of bug fixes.

Meta boxes had a few bugs, and they weren’t showing at all in the block editor, so we’ve fixed and polished there.


We’ve added support for registering and loading JavaScript translation files.

Twenty Nineteen

The Twenty Nineteen repository is a hive of activity, there have been a stack of minor bugs clean up, and some notable additions:

  • There’s now a widget area in the page footer.
  • Navigation submenus have been implemented for mobile devices.
  • Customiser options have been added for changing the theme colours and feature image filters.

Everything Else

The REST API has a couple of bug fixes and performance improvements. PHP 7.3 compatibility has been improved.

We’re fixing the bugs:
All the ones you’ve reported.
Some that we’ve found, too.

by Gary Pendergast at October 30, 2018 05:04 AM under 5.0

October 29, 2018

WPTavern: php[world] 2018 to Feature Full-Day Gutenberg Development Workshop

The fourth annual php[world] conference is just two weeks away. The event is dedicated to uniting the PHP community and will be held November 14-15, 2018, in Washington, D.C.

This year the organizing team created a “Content Advisory Board” to ensure the event included sessions that will appeal to everyone. The board includes two WordPress Developers, two Drupal developers, and two more more general PHP developers. They reviewed all incoming talk submissions and gave organizers ideas on what they thought would be of greatest interest to each community.

php[world] has traditionally included several topics and speakers from the WordPress world. This year the program features a full-day training workshop on Gutenberg development led by Josh Pollock and Zac Gordon. The workshop is called The Future of WordPress Development and is available through a separate day ticket.

“We’ve always tried to focus php[world] on being the PHP conference that appeals to WordPress and Drupal developers as well,” conference co-chair Eli White said. “We all write PHP (and JavaScript) code, and the DC area is full of WordPress and Drupal development shops. In fact, the majority of people in the local PHP user groups are doing WordPress development anyway. So we should all just be learning from each other.

“For WordPress, that was obviously Gutenberg. Currently the release date for WordPress 5.0 and Gutenberg is November 19th, just a few days after php[world], and so it’s a really important topic for any developer who works with WordPress to be familiar with.”

Workshop attendees can expect to become better acquainted with extending Gutenberg. The instructors plan to cover the basics of block creation as well as more advanced topics like making blocks dynamic and creating advanced blocks with the WordPress REST API and Redux.

“For the workshop, our goal is to get folks comfortable with what they could do with Gutenberg,” Josh Pollock said. “We’ll cover the anatomy of a block, and different patterns for creating simple and complex blocks. We’ll go over each of the types of block types you can create and have hands-on time to play with these new skills and ask real time questions.

“Developers should leave with an understanding of the different types of blocks they can build and why. They’ll also get plenty of example code, links, and advice they can use when it’s time to build blocks for their own WordPress projects.”

The event includes a few other sessions geared towards WordPress developers: David Wolfpaw is giving a workshop called “Building WordPress Themes: A Primer” and Mo Jangda from Automattic is giving a talk on “How to Handle a Site Outage.” There is another full-day training on modern PHP security that happens the day before the Gutenberg workshop that White said the WordPress Developers on the content board urged them to include.

The main conference is also hosting many sessions that would benefit WordPress developers who want to sharpen their PHP skills. A few highlights include:

Check out the full schedule on the php[world] website.

by Sarah Gooding at October 29, 2018 10:36 PM under php[world]

October 27, 2018

WPTavern: WooCommerce 3.5 Introduces REST API v3, Improves Transactional Emails

WooCommerce 3.5 was released this week. It’s a minor update that has been in development since May and began testing in September. The release should be backwards compatible to version 3.0 of the plugin but users are always advised to test all of their themes and extensions before updating.

Store owners can expect to see a change in the copy of the default transactional emails. They have been updated to be friendlier and more human. This is particularly important for the customer-facing emails. All of the following have been updated: on-hold, processing, completed, refunded both full and partially, invoice both with a pending and non-pending status, customer notes, password reset, new account. The default content in the store admin emails has also been improved.

The WooCommerce team anticipates that the updates to the transactional emails will reduce the need for store owners to customize their email templates. It also gives customers a better, friendlier connection to the store. More updates to the email content editing experience are planned for 2019.

Store owners may also benefit from the new option to set a low stock threshold in the inventory tab for individual products, export products by category to the CSV exporter, and define custom product placeholder images that will resize to correct store aspect ratio.

The WooCommerce REST API continues to evolve with v3 introduced in this release. It adds new endpoints required for the wc-admin feature plugin, the React-powered WooCommerce admin interface that was featured at last week’s WooSesh. REST API v3 also adds new features to existing endpoints while maintaining backwards compatibility with legacy API versions.

WooCommerce 3.5 introduces support for the Custom Product Tables feature plugin, which is being developed to improve store performance and scalability. In some cases storing product data in custom tables has brought 30% faster page loads.

In version 3.5 the “Preview Changes” button was removed from the publish meta box when editing products. If you’re missing it, Rémi Corson published a quick CSS snippet to bring it back.

Check out the release post for a full rundown of all the updates, deprecations, and template file changes in version 3.5.

by Sarah Gooding at October 27, 2018 02:15 AM under woocommerce

October 26, 2018

WPTavern: WP Engine Acquires Array Themes

WP Engine has acquired Array Themes and Atomic Blocks from Mike McAlister for an undisclosed amount. McAlister has been developing WordPress themes since 2009. He initially sold his themes on ThemeForest. In 2011, he founded Array Themes.

I reached out to McAlister to learn why he chose to be acquired, what excites him most about Gutenberg, and what the plans are going forward.

Interview with Mike McAlister

What ultimately made you decide to move on from managing your own theme and products company to a larger, more established company?

The catalyst was when Brian Gardner reached out this summer and started a conversation about joining his team at WP Engine. As I told him at the time, he certainly wasn’t the first to make that offer, but he was definitely the most interesting. I had always respected Brian’s ethos on quality and design and really enjoyed our chats over the years.

Once I started meeting folks at WP Engine like Jason Cohen and David Vogelpohl, it became obvious that we were all striving for the same future and outcome for customers. It just made sense to join forces to make it happen together.

This was also a unique opportunity for me to start fresh and focus on crafting products with a stellar team. Although I was able to create an industry-respected theme collection and recently the Atomic Blocks plugin for Gutenberg, I wanted a new challenge.

Couldn’t Array Themes have been built to directly support the Genesis framework without being acquired by WP Engine?

It would be a lot of work to infuse the Array Themes collection and Genesis. The idea wasn’t exactly to bring Genesis to Array, rather to bring the expertise and craft of Array and Atomic Blocks to WP Engine, StudioPress and Gutenberg.

StudioPress already has one of the biggest and best theme collections out there and is doubling down on Gutenberg support. I’m going to contribute what I’ve learned building Array Themes and Atomic Blocks to make the StudioPress offering even better.

Will future themes require the Genesis framework?

Although there will not be any new themes released under the Array Themes brand, some of the designs will live on as StudioPress themes in the future and those will be powered by the Genesis framework.

We’re working on some really exciting new themes and features for Genesis that are going to continue making it the go-to solution for creating beautiful websites on WordPress, especially in the Gutenberg era.

What do you think of the consolidation of brands in the WordPress space?

We’re seeing a very unique and transitional time in the WordPress industry. The old way of doing things is going out the window as WordPress and its community changes before our eyes.

Now, more than ever, WordPress needs companies with stellar talent to help usher it through to the next era and contribute to its long term success. I’m excited to be part of a team that is willing to take on that challenge!

I can’t speak to the motivations of other businesses in the WordPress space, but the WP Engine acquisition of the Array product suite makes a lot of sense.

With their recent acquisition of StudioPress, Array Themes, and Atomic Blocks, WP Engine is showing its customers and the WordPress community that they are doubling down on quality, design, Gutenberg, and an unmatched customer experience. These are all shared qualities between these individual entities and part of the long term strategy at WP Engine.

What excites you most about Gutenberg?

I’ve been excited about Gutenberg for over a year now. I was one of the first WordPress product developers to release a blocks plugin, a Gutenberg-friendly theme, a blog with tutorials, and the Gutenberg News site.

I created all of these resources as a way of learning Gutenberg as well as contributing back to the community, and I will continue to do that with WP Engine and StudioPress!

Gutenberg unlocks the WordPress editor and the endless opportunities that follow for content creators, developers, and everyone in between. Gutenberg is already responsible for a flood of new products and new solutions to problems the classic editor couldn’t solve and it hasn’t even been merged into core yet!

The reality here is that Gutenberg isn’t just the future of WordPress, it’s the future of the Internet.

Discounts Available for Array Themes Customers

McAlister is joining WP Engine as a full-time employee. In addition, John Parris, a code wrangler for Array Themes has also joined WP Engine.

StudioPress and WP Engine are offering discounts to single theme and theme club members. Those who purchased a lifetime membership will receive free access to the StudioPress Pro Plus All-Theme package with support and updates.

To learn more about these discounts and how the acquisition came about, check out McAlister’s post where he says thanks and farewell to his customers.

by Jeff Chandler at October 26, 2018 11:08 PM under wp engine

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.


Last updated:

November 13, 2018 10:45 PM
All times are UTC.