Wordpress News

Medical Theme

Drupal Themes - Fri, 11/23/2018 - 18:40

Medical Theme is a beautiful theme for health and medical purposes, with a modern and catchy design. It comes with a quick and nice great icons, smart content structure, and a clean and simple look.

YG News

Drupal Themes - Fri, 11/23/2018 - 08:07

Tailwind CSS Starter Kit

Drupal Themes - Fri, 11/23/2018 - 00:52

YG Creative

Drupal Themes - Thu, 11/22/2018 - 11:30

Clinic Zymphonies Theme

Drupal Themes - Wed, 11/21/2018 - 16:02

Clinic Zymphonies Theme is Mobile-first Drupal 8 responsive theme. This theme features a custom sideshow, responsive layout, multiple column layouts and is highly customizable. Read more

Live Demo Advanced Themes

Support & Customisation

Contact us for theme installation, customization, custom theme and all other Drupal service. Read more

Contact Zymphonies

Follow us in Twitter & Like us on Facebook to get free/premium theme updates, Drupal tips, tricks & news

Theme designed by FreeBiezz.com & developed by Zymphonies.com

Features

  • Drupal 8 core
  • Bootstrap v4
  • Font Awesome v5
  • Mobile-first responsive theme
  • Custom menu bar
  • Light weight theme
  • Fully responsive design
  • Included Sass & Compass source file
    • Colors are stored in Sass variable
    • Well organized Sass code
  • Static home page banner image
Banner Configuration

Banner can configure completely from theme settings page. It has control to upload image, add title and description etc.

Connect with Zymphonies Contact Zymphonies

Have Queries? Click here to contact Zymphonies

  • Free theme customisation & additional features
  • Drupal custom theme development
  • Drupal website design & development
  • Drupal website migration

Sponsored by Zymphonies

YG Business

Drupal Themes - Thu, 11/15/2018 - 07:16

WPTavern: Maximum Ticket Prices for WordCamps Will Increase to $25 per Day in 2019

Wordpress Planet - Wed, 11/14/2018 - 19:25

For the last seven years, the maximum amount of money WordCamp organizers could charge for ticket prices was $20 per day. In 2019, this will increase to $25 per day.

The new amount accounts for inflation and provides breathing room for organizers. According to the Bureau of Labor Statistics inflation calculator, $20 in January of 2006 is equal to $25.51 in October of 2018.

Organizers don’t have to charge this amount and are encouraged to keep the ticket price as low as possible. The increase is also part of a delicate balancing act between not being a financial burden and getting 80% or more of attendees to show up.

“The ticket price does not reflect on the value of the event,” Andrea Middleton, Community organizer said.

“In an ideal world, all WordCamp tickets would be free just like WordPress is free but to avoid organizing a conference for 500 registrants and only having 50 people show up on the day of the event, we charge as little as we possibly can for tickets, but just enough that people will show up for the event if they’re sleepy that morning or got a last-minute invitation to a pool party or something.”

When the proposal to increase the maximum ticket price was published in September, many commenters approved of the increase with some suggesting an even higher amount to account for inflation for the next few years. Ian Dunn questioned whether or not budget shortfalls were due to organizing teams spending money on extra things.

“Beyond that, though, I’m curious why camps are having more trouble today than they were 5 or even 10 years ago?” Dunn said.

“Is it harder to get sponsorships? It seems like the opposite is true, especially given how much the global sponsorship program covers.

“Based on experiences in my local community, I suspect that the primary reason for budget shortfalls is that the organizing team is choosing to do extra things, beyond what’s necessary to meet the goals of a WordCamp. For example, holding after-parties at trendy venues, expensive speaker gifts, professional A/V (which I’ve advocated for in the past, but not at the cost of higher ticket prices), etc.”

It is interesting to ponder how much money WordCamps could save globally by eliminating the materialistic aspects of the event such as t-shirts, speaker gifts, lanyards, badges, signs, etc.

At there core, WordCamps are about gathering the local community together in a physical location to share knowledge. Not every WordPress event needs to mimic WordCamp US or WordCamp Europe, two of the largest events in the world.

Although the WordPress Community team tracks data such as how much each WordCamp charges for ticket prices, the information is not readily available. This is because of the large volume of data that would need to be calculated and displayed. It would be interesting to see an info-graphic of this data where you can compare the average ticket price for WordCamps per country.

Hugh Lashbrooke, a WordPress Community team contributor who has access to the data says that, “globally the majority of camps have lower prices.”

WordCamp organizers are highly encouraged to keep track of attendance as the data is used to help make better informed decisions. The team will review the no-show rates at WordCamps at the end of 2019 to determine if the price increase had any effect. If not, the team may increase the price again for 2020.

WPTavern: Google Developers Demo AMP Stories Integration with Gutenberg at Chrome Dev Summit

Wordpress Planet - Wed, 11/14/2018 - 00:27

Alberto Medina and Weston Ruter gave a presentation on Progressive Content Management Systems yesterday at Chrome Dev Summit 2018 in San Francisco. Medina is a developer advocate at Google and Ruter recently transitioned into a new role as a Developer Programs Engineer after eight years at XWP.

Medina began the session with a quick overview of the increasingly complex CMS space, which is growing, according to figures he cited from w3techs: 54% of sites are built with some kind of CMS (11% YoY growth). Many CMS’s face common challenges when it comes to integrating modern web technologies into their platforms, such as large code bases, legacy code, and technical debt.

In addressing the challenges that WordPress faces, Google is looking to make an impact on a large swath of the web. Medina outlined the two-part approach Google is using with the WordPress ecosystem. This includes AMP integration via the AMP plugin for WordPress. It’s currently at version 1.0 RC2 and the stable version is scheduled for release at the end of this month.

The second part of the approach is integration of modern web capabilities and APIs in core, so that things like service workers and background sync are supported natively in a way that the entire ecosystem can take advantage of them. Google has invested resources to get these features added to core.

Ruter demonstrated a single page application built in WordPress using a standard theme as the basis and the AMP plugin as a foundation. Medina said the team plans to continue expanding this work integrating AMP content into WordPress, specifically in the context of Gutenberg. He gave a quick demo of how they are working to help content creators easily take advantage of features like AMP stories via a Gutenberg integration.

Medina said AMP stories are formed by components and work well with Gutenberg, since everything in the new editor corresponds to a block.

“We want powerful components like these to become available across all CMS’s,” Medina said. “The CMS space is moving steadily along the progressive web road.”

Check out the video below to learn more about Google’s experience integrating modern web capabilities and progressive technologies into the WordPress platform and ecosystem.

Dev Blog: WordPress 5.0 Beta 4

Wordpress Planet - Tue, 11/13/2018 - 01:27

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.
Internationalisation

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.

International-
isation is a word with
many syllables.

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

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

Wordpress Planet - Tue, 11/13/2018 - 00:30

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.

WPTavern: WP GDPR Compliance Plugin Patches Privilege Escalation Vulnerability

Wordpress Planet - Mon, 11/12/2018 - 20:20

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:

“ACTIVATING THIS PLUGIN DOES NOT GUARANTEE YOU FULLY COMPLY WITH GDPR. PLEASE CONTACT A GDPR CONSULTANT OR LAW FIRM TO ASSESS NECESSARY MEASURES.”

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.

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

Wordpress Planet - Mon, 11/12/2018 - 19:51

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.

YG Construction

Drupal Themes - Mon, 11/12/2018 - 09:21

YG Construction is modern Drupal 8 theme developed to help you to create a stunning websites for construction.

Features

  • Drupal 8 core
  • Bootstrap v4
  • Services
  • Projects
  • Works
  • Blog
  • Testimonials

Live Demo Download Demo Site

It is highly recommended to install the demo site and customize it to get the exact look. Here is the link for the documentation to install demo site

Demo login credentials : admin / admin@123

Thanks for checking out our theme. We can install the theme in your server for free!

Contact us for free installation


Other YG Business themes


Credits

Drupal theme by Young Globes

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

Wordpress Planet - Sat, 11/10/2018 - 15:30

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.”

YG Interior

Drupal Themes - Sat, 11/10/2018 - 13:30

YG Interior is modern Drupal 8 theme developed to help you to create a stunning websites for Interior and Furniture.

Features

  • Drupal 8 core
  • Bootstrap v3
  • Services
  • Work
  • Products
  • Blog

Live Demo Download Demo Site

It is highly recommended to install the demo site and customize it to get the exact look. Here is the link for the documentation to install demo site

Demo login credentials : admin / admin@123

Thanks for checking out our theme. We can install the theme in your server for free!

Contact us for free installation


Other YG Business themes


Credits

Drupal theme by Young Globes

YG Plumbing

Drupal Themes - Sat, 11/10/2018 - 07:14

YG Plumbing is modern Drupal 8 theme developed to help you to create a stunning websites.

Features

  • Drupal 8 core
  • Bootstrap v3
  • Services
  • Work
  • Gallery
  • Testimonials

Download Demo Site

It is highly recommended to install the demo site and customize it to get the exact look. Here is the link for the documentation to install demo site

Demo login credentials : admin / admin@123

Thanks for checking out our theme. We can install the theme in your server for free!

Contact us for free installation


Other YG Business themes


Credits

Drupal theme by Young Globes

WPTavern: WordPress 5.0 Release Date Update to November 27

Wordpress Planet - Fri, 11/09/2018 - 20:06

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.

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

Wordpress Planet - Fri, 11/09/2018 - 17:21

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:

Matt: Gutenberg in Portland Oregon and Podcasts

Wordpress Planet - Fri, 11/09/2018 - 04:45

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.

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

Wordpress Planet - Fri, 11/09/2018 - 00:03

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.

My thoughts are very much aligned here. I'm super excited for the release — I think it's crucial for WordPress' success. But I don't think it, nor the ecosystem, are quite ready following the shortened release cycle. https://t.co/R0nZt0mk41

— Mike Schroder (@GetSource) November 7, 2018

This: https://t.co/wpcQ02qcTw They are missing almost every milestone on their release schedule, leaving me 1 week to test with RC before Thanksgiving, and plugin/theme authors no time to develop/test with stabler code. It should just come out with their backup January date.

— Lisa Woodruff (@lisa_m_woodruff) November 8, 2018

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.

Pages