WPWeekly Episode 312 – Dragon Drop, WordPress Accessibility Statement, and WooCommerce GDPR

In this episode, John James Jacoby and I start the show by sharing our thoughts on Mark Zuckberberg’s congressional hearing. We then discuss what’s new in Gutenberg 2.6 and describe our user experience. We let you know what’s in WooCommerce 3.3.5 and discuss what the development team is doing to prepare for GDPR compliance.

Stories Discussed:

Gutenberg 2.6 Introduces Drag and Drop Block Sorting
Theme Review Changes Place More Onus Onto Theme Authors
WordPress Accessibility Statement
WooCommerce 3.3.5 Released
How WooCommerce is tackling GDPR

Picks of the Week:

AtomBlocks by Mike McAlister

WPWeekly Meta:

Next Episode: Wednesday, April 18th 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 #312:

                                <br><a href="https://wptavern.com/wpweekly-episode-312-dragon-drop-wordpress-accessibility-statement-and-woocommerce-gdpr">Source link </a>

Theme Review Changes Place More Onus Onto Theme Authors

The WordPress Theme Review team has implemented changes that simplify the process and places more responsibility onto theme authors. Theme reviewers now only need to check the following items to pass a theme.

  • Licensing
  • Malicious or egregious stuff
  • Content Creation
  • Security

Although the bar to pass a theme is significantly lower, theme authors are still expected to follow the required and recommended requirements listed in the theme handbook.

Moderators will check themes after they’ve gone live to make sure the author is following guidelines. If a moderator discovers any issues, a request will be made to the theme author to correct them. Failure to do so could lead to a temporary or permanent suspension.

Justin Tadlock clarified in the comments examples of egregious issues.

  • Illegal
  • Dishonest
  • Morally offensive
  • PHP Errors

In the past two years, The Theme Review Team has battled the theme review queue with moderate success. In early 2017, the number of themes in the queue dropped below 200. Although there has been some work on automating the process, it’s largely reliant on humans.

Even though it hasn’t been updated in more than a year, theme authors are highly encouraged to use the Theme Check plugin before submitting themes for review.

With a simplified process to get a theme live, reviewers are hoping it will free them up to focus on larger projects.

                                <br><a href="https://wptavern.com/theme-review-changes-place-more-onus-onto-theme-authors">Source link </a>

An Update to My Gutenberg Experience

Not long after I published my experience with Gutenberg, developers reached out to me to work on some of the issues I mentioned. Riad Benguella figured out why meta boxes were not collapsing or expanding.

It turns out that some meta boxes depend on the post script which has a side effect of calling the window.postboxes.add_postbox_toggles( postType ) twice, causing meta boxes to break.

Gutenberg 2.6 released earlier this week, fixes the issue and all meta boxes function properly again. This also fixes the issue I had with the Telegram for WordPress plugin.

Public Post Preview still doesn’t work in Gutenberg but the plugin’s developer, Dominik Schilling, shared some experiments he has conducted with adding support for Gutenberg on Twitter.

In the preview video, you can see Public Post Preview’s options added to the sidebar and in addition to generating a link, you can choose when that URL expires which is better than what’s currently available in the plugin.

I mentioned how Tags would sometimes disappear and there overall behavior was inconsistent. This pull request that made it into Gutenberg 2.6, fixes the issue by only including the term in the Tag selector if it’s known.

Although I’m still bummed that certain plugins are not yet compatible with Gutenberg, I’m pretty happy that two of the major pain points I experienced have been fixed. Thanks to Riad, Tammie Lister, and others for helping to solve these problems so quickly.

                                <br><a href="https://wptavern.com/an-update-to-my-gutenberg-experience">Source link </a>
‘Try Gutenberg’ Prompt Pushed Back to A Later Release

‘Try Gutenberg’ Prompt Pushed Back to A Later Release

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

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

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

Gary Pendergast

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

We have been working to expand our collection of data about how well plugins function with Gutenberg. To help with that effort, we would like to explore using feedback collected from WordPress users through the Try Gutenberg effort to add to the existing database on WordPress plugin compatibility if that could be worked out.
The goal of this project is to make sure everyone can use Gutenberg without having to worry about plugin incompatibilities.

Jadon N

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

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

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

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

Gutenberg Call Out Prototype by Chris Lema

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

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

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

                                <br><a href="https://wptavern.com/try-gutenberg-prompt-pushed-back-to-a-later-release">Source link </a>

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

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

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

Stories Discussed:

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

Picks of the Week:

How to Disable Push Notification Requests in Firefox

Facebook Container Add-on for Firefox

WPWeekly Meta:

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

Subscribe to WordPress Weekly via Itunes

Subscribe to WordPress Weekly via RSS

Subscribe to WordPress Weekly via Stitcher Radio

Subscribe to WordPress Weekly via Google Play

Listen To Episode #310:

                                <br><a href="https://wptavern.com/wpweekly-episode-310-community-management-php-and-hello-dolly">Source link </a>
Noteworthy Changes Coming in WordPress 4.9.5

Noteworthy Changes Coming in WordPress 4.9.5

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

“Cheatin’ uh?” Error Message is Replaced

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

Cheatin’ Uh Error Message

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

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

Recommended PHP Version Increased to 7.2

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

Offensive Lyrics Removed From Hello Dolly

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

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

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

Source link

Page 1 of 6812345...102030...Last »

Pin It on Pinterest