23 Nov 2017

feedWordPress Planet

WPTavern: Workarounds for the Page Template Bug in WordPress 4.9

WordPress 4.9 "Tipton" was released last week and although it's largely trouble-free, there is one particular issue users and developers are running into that's causing frustration. In 4.9, custom page templates that are created fail to display in the Template drop-down menu. The issue is related to changes made to the file editor.

Previous versions of WordPress listed files 2-levels deep in the editor. In 4.9, the entire directory tree for a theme is listed regardless of its depth. Caching was added to help limit the performance impacts of loading large WordPress themes. "An unintended side effect of the caching is that the same directory listing function get_files is used both for the theme editor and for gathering page templates," Weston Ruter, Co-Release Lead for WordPress 4.9 said.

Within the trac ticket, developers suggests that a button be added that flushes all caches or disabling the cache if WP_DEBUG is set to true. Neither suggestion turned into a patch committed to core. Instead, Ruter has released a plugin as a workaround that flushes the template cache. Other workarounds include, bumping the theme's version, running the wp cache flush command in WP CLI, or waiting 60 minutes for the cache to expire.

The ticket is marked as a high priority but because of the upcoming holidays in the US and WordCamp US next weekend, it could be at least a few weeks before WordPress 4.9.1 is released.

23 Nov 2017 12:42am GMT

22 Nov 2017

feedWordPress Planet

WPTavern: Tide Project Aims to Audit and Score WordPress Themes and Plugins based on Code Quality

Last week XWP dropped an intriguing preview of a new project called Tide that aims to improve code quality across the WordPress plugin and theme ecosystems. The company has been working with the support of Google, Automattic, and WP Engine, on creating a new service that will help users make better plugin decisions and assist developers in writing better code.

XWP's marketing manager Rob Stinson summarized the project's direction so far:

Tide is a service, consisting of an API, Audit Server, and Sync Server, working in tandem to run a series of automated tests against the WordPress.org plugin and theme directories. Through the Tide plugin, the results of these tests are delivered as an aggregated score in the WordPress admin that represents the overall code quality of the plugin or theme. A comprehensive report is generated, equipping developers to better understand how they can increase the quality of their code.

The XWP announcement also included a screenshot of how this data might be presented in the WordPress plugin directory:

XWP plans to unveil the service at WordCamp US in Nashville at the Google booth where they will be inviting the community to get involved. Naturally, a project with the potential to have this much impact on the plugin ecosystem raises many questions about who is behind the vision and what kind of metrics will be used.

I contacted Rob Stinson and Luke Carbis at XWP, who are both contributors to the project, to get an inside look at how it started and where they anticipate it going.

"Tide was started at XWP about 12 months ago when one of our service teams pulled together the idea, followed up by a proof of concept, of a tool that ran a series of code quality tests against a package of code (WordPress plugin) and returned the results via an API," Stinson said. "We shortly after came up with the name Tide, inspired by the proverb 'A rising tide lifts all boats,' thinking that if a tool like this could lower the barrier of entry to good quality code for enough developers, it could lift the quality of code across the whole WordPress ecosystem."

Stinson said XWP ramped up its efforts on Tide during the last few months after beginning to see its potential and sharing the vision with partners.

"Google, Automattic and WP Engine have all helped resource (funds, infrastructure, developer time, advice etc) the project recently as well," Stinson said. "Their support has really helped us build momentum. Google have been a big part of this since about August. We had been working with them on other projects and when we shared with them the vision for Tide, they loved it and saw how in line it is with the vision they have for a better performant web."

The Tide service is not currently active but a beta version will launch at WordCamp US with a WordPress plugin to follow shortly thereafter. Stinson said the team designed the first version to present the possibilities of Tide and encourage feedback and contribution from the community.

"We realize that Tide will be its best if its open sourced," he said. "There are many moving parts to it and we recognize that the larger the input from the community, the better it will represent and solve the needs of the community around code quality."

At this phase of the project, nothing has been set in stone. The Tide team is continuing to experiment with different ways of making the plugin audit data available, as well as refining how that data is weighed when delivering a Tide score.

"The star rating is just an idea we have been playing with," Stinson said. "The purpose of it will be to aggregate the full report that is produced by Tide into a simple and easy to understand metric that WordPress users can refer to when making decisions about plugins and themes. We know we haven't got this metric and how it is displayed quite right. We've had some great feedback from the community already."

The service is not just designed to output scores but also to make it easy for developers to identify weaknesses in their code and learn how to fix them.

"Lowering the barrier of entry to writing good code was the original inspiration for the idea," Stinson said.

Tide Project Team Plans to Refine Metrics Used for Audit Score based on Community Feedback

The Tide project website, wptide.org, will launch at WordCamp US and will provide developers with scores, including specifics like line numbers and descriptions of failed sniffs. Plugin developers will be able to use the site to improve their code and WordPress users will be able to quickly check the quality of a plugin. XWP product manager Luke Carbis explained how the Tide score is currently calculated.

"Right now, Tide runs a series of code sniffs across a plugin / theme, takes the results, applies some weighting (potential security issues are more important than tabs vs. spaces), and then averages the results per line of code," Carbis said. "The output of this is a score out of 100, which is a great indicator of the quality of a plugin or theme. The 'algorithm' that determines the score is basically just a series of weightings."

The weightings the service is currently using were selected as a starting point, but Carbis said the team hopes the WordPress community will help them to refine it.

"If it makes sense, maybe one day this score could be surfaced in the WordPress admin (on the add new plugin page)," Carbis said. "Or maybe it could influence the search results (higher rated plugins ranked first). Or maybe it just stays on wptide.org. That's really up to the community to decide."

In addition to running codesniffs, the Tide service will run two other scans. A Lighthouse scan, using Google's open-source, automated tool for improving the quality of web pages, will be performed on themes, which Carbis says is a "huge technological accomplishment."

"For every theme in the directory, we're spinning up a temporary WordPress install, and running a Lighthouse audit in a headless chrome instance," Carbis said. "This means we get a detailed report of the theme's front end output quality, not just the code that powers it."

The second scan Tide will perform measures PHP compatibility and will apply to both plugins and themes.

"Tide can tell which versions of PHP a plugin or theme will work with," Carbis said. "For users, this means we could potentially hide results that we know won't work with their WordPress install (or at least show a warning). For hosts, this means they can easily check the PHP compatibility before upgrading an install to PHP 7 (we think this will cause many more installs to be upgraded - the net effect being a noticeable speed increase, which we find really exciting and motivating)."

Carbis said that the team is currently working in the short term to get the PHP Compatibility piece into the WordPress.org API, which he says could start influencing search results without any changes to WordPress core.

"We'd also like to start engaging with the community to find out whether surfacing a Code Quality score to WordPress users is helpful, and if it is, what does that look like? (e.g. score out of 100, 5 star rating, A/B/C/D, etc.)," Carbis said. "We will release our suggestion for what this could look like as a plugin shortly after WordCamp US."

More specific information about the metrics Tide is currently using and how it applies to plugins and themes will be available after the service launches in beta. If you are attending WordCamp US and have some suggestions or feedback to offer the team, make sure to stop by the Google sponsorship booth.

22 Nov 2017 9:21pm GMT

Matt: Adam Robinson on Understanding

This is a long quote/excerpt from Adam Robinson I've been holding onto for a while, from Tribe of Mentors. Worth considering, especially if you strive to work in a data-informed product organization.

Virtually all investors have been told when they were younger - or implicitly believe, or have been tacitly encouraged to do so by the cookie-cutter curriculums of the business schools they all attend - that the more they understand the world, the better their investment results. It makes sense, doesn't it? The more information we acquire and evaluate, the "better informed" we become, the better our decisions. Accumulating information, becoming "better informed," is certainly an advantage in numerous, if not most, fields.

But not in the eld of counterintuitive world of investing, where accumulating information can hurt your investment results.

In 1974, Paul Slovic - a world-class psychologist, and a peer of Nobel laureate Daniel Kahneman - decided to evaluate the effect of information on decision-making. This study should be taught at every business school in the country. Slovic gathered eight professional horse handicappers and announced, "I want to see how well you predict the winners of horse races." Now, these handicappers were all seasoned professionals who made their livings solely on their gambling skills.

Slovic told them the test would consist of predicting 40 horse races in four consecutive rounds. In the first round, each gambler would be given the five pieces of information he wanted on each horse, which would vary from handicapper to handicapper. One handicapper might want the years of experience the jockey had as one of his top five variables, while another might not care about that at all but want the fastest speed any given horse had achieved in the past year, or whatever.

Finally, in addition to asking the handicappers to predict the winner of each race, he asked each one also to state how confident he was in his prediction. Now, as it turns out, there were an average of ten horses in each race, so we would expect by blind chance - random guessing - each handicapper would be right 10 percent of the time, and that their confidence with a blind guess to be 10 percent.

So in round one, with just five pieces of information, the handicappers were 17 percent accurate, which is pretty good, 70 percent better than the 10 percent chance they started with when given zero pieces of information. And interestingly, their confidence was 19 percent - almost exactly as confident as they should have been. They were 17 percent accurate and 19 percent confident in their predictions.

In round two, they were given ten pieces of information. In round three, 20 pieces of information. And in the fourth and final round, 40 pieces of information. That's a whole lot more than the five pieces of information they started with. Surprisingly, their accuracy had flatlined at 17 percent; they were no more accurate with the additional 35 pieces of information. Unfortunately, their confidence nearly doubled - to 34 percent! So the additional information made them no more accurate but a whole lot more confident. Which would have led them to increase the size of their bets and lose money as a result.

Beyond a certain minimum amount, additional information only feeds - leaving aside the considerable cost of and delay occasioned in acquiring it - what psychologists call "confirmation bias." The information we gain that conflicts with our original assessment or conclusion, we conveniently ignore or dismiss, while the information that confirms our original decision makes us increasingly certain that our conclusion was correct.

So, to return to investing, the second problem with trying to understand the world is that it is simply far too complex to grasp, and the more dogged our at- tempts to understand the world, the more we earnestly want to "explain" events and trends in it, the more we become attached to our resulting beliefs - which are always more or less mistaken - blinding us to the financial trends that are actually unfolding. Worse, we think we understand the world, giving investors a false sense of confidence, when in fact we always more or less misunderstand it.
You hear it all the time from even the most seasoned investors and financial "experts" that this trend or that "doesn't make sense." "It doesn't make sense that the dollar keeps going lower" or "it makes no sense that stocks keep going higher." But what's really going on when investors say that something makes no sense is that they have a dozen or whatever reasons why the trend should be moving in the opposite direction.. yet it keeps moving in the current direction. So they believe the trend makes no sense. But what makes no sense is their model of the world. That's what doesn't make sense. The world always makes sense.

In fact, because financial trends involve human behavior and human beliefs on a global scale, the most powerful trends won't make sense until it becomes too late to profit from them. By the time investors formulate an understanding that gives them the confidence to invest, the investment opportunity has already passed.

So when I hear sophisticated investors or financial commentators say, for example, that it makes no sense how energy stocks keep going lower, I know that energy stocks have a lot lower to go. Because all those investors are on the wrong side of the trade, in denial, probably doubling down on their original decision to buy energy stocks. Eventually they will throw in the towel and have to sell those energy stocks, driving prices lower still.

22 Nov 2017 4:33pm GMT

HeroPress: Finding WordPress in Cameroon

Pull Quote: The more I share knowledge with someone the more I gain in return.

My name is Michaël Nde Tabefor, I reside in Cameroon. I grew up in the economic capital of the country surrounded by so much diversity and culture.

Yet I was still very young when I developed an interest in technology, back in Primary school I had a PC at home I used to play around, most especially Spider Solitaire hahaha. Well that game sound crazy but it's educative, it built up my reflex with the mouse and yeah it worth it. When I arrived in Secondary school I quickly picked up the subject.

I began educating myself on the trend of Technology and how they work. I developed a great interest for organisations such as Google, what they doing for humanity not just about technology. So I understood that no matter the position I get, I must always contribute to Humanity by volunteering.

When I got to the University back in 2014 as a Freshman, I enrolled into Software engineering program where I began excelling and widening my thinking and reflex, met with other enthusiasts of technology.

Taking Another Path

Unlike other students I decided to go in for an internship at my first year (am one of those who believe university is good but it contribute to just about 10 - 20% of what builds up skill, people must be passionate about what the do, that passion alone will get you have the skills and be able to learn more and more).

On my first day of internship, my internship coordinator gave me a task to go and install WordPress on my computer and create with the use of an external template (not there default themes) the website of my university.

Let me make this point, I didn't know about WordPress. Had no idea of what it's meant for. Completely blank.

I went back to my university, I met one of my professors, explained it to him, he redirected me to a senior student who once did internship and had to use WordPress.

I went home, got my environment set up and called my senior, She did the guiding all through the installation on phone, till installing the template, my curiosity did the rest of the job hahaha, end of story. The next day I went back to the office, my coordinator didn't expect me that soon Lol.

Diving Deeper

So I worked on some tutorial on building themes and plugin from scratch from Lynda.com but I took a break from building cuz I didn't have much skills in PHP, in first year we didn't do web technologies, I began hacking on PHP on my own, basic'ly I learnt almost every skill on my own via research and practice.

I worked on several sites that used WordPress and began installing for others. My coordinator told me it would be interesting to start a WordPress Community so others could benefit from it. Actually the more I share knowledge with someone I gain 100% in return too, it builds up my mastery and ability to debug and resolve issues.

I began our local community and everyday I kept understanding WordPress more and more.

After a couple of months I officially joined the WordPress Volunteer Community in doing more reach outs in (November 2015 - via Rocio Valdiva) and on April 15, 2017 I organized the very first WordCamp in the whole of Central Africa that brought together over 240 persons. Complete gallery on Flickr, Video on YouTube.

After the WordCamp I later on built a Mobile Money Payment Gateway with a local Network Operator web payment API using WooCommerce.

The post Finding WordPress in Cameroon appeared first on HeroPress.

22 Nov 2017 3:45pm GMT

WPTavern: Envato Elements Adds Unlimited WordPress Theme and Plugin Downloads to Subscription Plan

Envato has added unlimited WordPress theme and plugin downloads to its Elements digital assets subscription service. The company is including a curated collection of 210 WordPress themes and 100 plugins along with 400,000 other design assets already offered through the service.

Envato is the largest WordPress theme marketplace on the web with 39,102 themes and website templates for sale. Last year the company celebrated 10 years in business and reported that the community earned more than $40 million, with a significant portion of that revenue coming from WordPress products.

The new "all you can eat" style package for WordPress themes on Envato Elements was introduced to boost the value of the service's annual subscription plan and is not available to monthly subscribers. For $228/year, annual subscribers can change themes as often as they choose, which is the chief selling point of the new addition. However, the subscription service does not provide direct item support for the themes, as they are submitted by independent designers.

Current Elements subscribers have the option to change their payment plans from monthly to annual to gain access to the unlimited WordPress products. Several disgruntled customers have taken to Twitter to express their dissatisfaction with the WordPress additions being withheld from existing monthly subscribers and perceive it to be heavy-handed a tactic for locking in more annual subscribers before raising the price.

Not cheeky ask at all, your roadmap did not say anything about this price change, but got people signed up at $19 per month with the understanding this was going to be an added edition. Shocking way to treat loyal customers. #moneyhungry

- TVBanterUK 💭 (@TVBanterUK) November 15, 2017

Why hold monthly subscribers ransom by only allowing annual subscribers access? Feels somewhat unfair to long term subs!

- Paul Charlton (@ipixel_design) November 16, 2017

Yes we were on the understanding us early day loyal subscribers signed up would get what the roadmap said, it's such a sneaky way to get people locked in to the annual plan which you will then increase in year 2, seen it all before.

- TVBanterUK 💭 (@TVBanterUK) November 16, 2017

An Envato support representative offered some background on the decision in response to monthly subscribers who do not appreciate being excluded from additions to the service.

"We chose this pricing model because we think it creates the fairest platform for both our subscribers and our authors," the representative said. "A huge amount of time and dedication goes into creating and maintaining WordPress themes and plugin so this allows us to help protect the earnings of the authors who provide our community with premium assets."

22 Nov 2017 4:01am GMT

21 Nov 2017

feedWordPress Planet

Matt: Tribe of Mentors

Tim Ferriss's new book Tribe of Mentors is out. I have finished it already, and can say it's really excellent and I even liked it more than Tools of Titans even though I'm not in this one. 🙂 As I said in a message to Tim:

Curious how Tribe of Mentors is different from Tools of Titans? Here's a text to me from Matt Mullenweg (@photomatt, CEO Automattic)… pic.twitter.com/D9kvA2rFFC

- Tim Ferriss (@tferriss) October 16, 2017

I learned a lot from it, took a ton of notes to follow up on, and wrote down about twenty more books I have to read.

21 Nov 2017 11:55pm GMT

WPTavern: Tailor Page Builder Plugin Discontinued, Owners Cite Funding, Gutenberg, and Competition

Enclavely, Inc., the owners of the Tailor Page Builder plugin, have announced that they will be discontinuing its development effective immediately.

Andrew Worsfold, the original developer, launched Tailor in April 2016 and the plugin received an enthusiastic reception from the WordPress community. After performing a critical review of the major page builders available to users in September 2016, Pippin Williamson found only three that he could happily recommend to his customers: Tailor, Pootle Page Builder, and Beaver Builder. This recommendation was based primarily on code quality, usability, and compatibility with other plugins.

The plugin came under new management in July 2017 after the original developer no longer had enough time to dedicate to the project. Worsfold sold it to Enclavely, whose owners were early and enthusiastic users of the plugin, for what he said was "a nominal amount." Three months later, the new owners cite the cost of keeping up with Gutenberg and other competitors as the primary reason for discontinuing its development:

Gutenberg is going to be bundled with WordPress itself. That's definitely going to give a tough time to all 3rd party page builders and even that is not the case there are some really big players around like Elementor, Divi, Beaver Builder, and others which are going to be hard for us to compete with, being a completely free project and providing almost all the great features in free version…

So the main reason for us to discontinue Tailor is due to finances, which Tailor needs to keep on its development and marketing to compete with all the big players and especially Gutenberg.

This instance seems to be more of a case of the new management running out of funds, rather than Gutenberg preemptively killing off a page builder. Enclavely was no longer willing to invest in developing a product that could compete against some of the more widely used page builders.

"Tailor needs a lot of effort and money, which was much more than we estimated," an Enclavely representative said when I contacted the company. "And even if we continue to put effort and money in this project, we all know that Gutenberg is going to smash this space soon and we won't be able to survive, and so will be the case with some other page builders. This is why we decided to end this now."

Tailor currently has more than 3,000 active installations, according to WordPress.org. Fans of the plugin commented on the announcement, asking if the original developer might be able to pick the project back up again.

When I contacted the company, they said the original developer was no longer involved with the project.

"The original developer has parted ways since the acquisition," an Enclavely representative said. "He was involved with some stuff in the start but not that much, thus the decision is mainly taken by us based on the issues we were facing in maintaining this project."

However, Worsfold's account of his involvement with Tailor following the acquisition differs greatly from Enclavely's report.

"I handed over control of the project in July, although all releases since then were also written by me and deployed on their behalf," Worsfold said. "Given that I haven't been asked to help with anything recently, and there have been no further releases, it looks like development has already ended."

The plugin is available free on WordPress.org and licensed under the GPL, so anyone who wants to can fork it. Worsfold doesn't anticipate having the time to maintain the project himself and said he was under the impression that Enclavely is attempting to sell it.

"I made the decision to hand over control of Tailor as work and other commitments meant that I couldn't dedicate enough time to the project," Worsfold said. "I had hoped that the new team would continue development, provide support, and ensure the needs of existing users were met. However after just three months they've decided to give up. That's obviously very disappointing."

Worsfold said that when he sold it to them, it was with the understanding that they would continue to develop and maintain it. He doesn't anticipate being able to re-adopt it due to a lack of time to dedicate to the project.

"I'm in much the same situation I was in before and it seems they are wanting to on-sell it themselves, so I can't imagine I will be able to readopt it," Worsfold said. "I have mixed feelings about the whole situation. Ultimately I see Gutenberg doing most of what page builders currently do, but in a better, more standardized, way. Hopefully, whatever's left (custom blocks, styles, functionality etc.) will build on the framework and serve to reduce the amount of fragmentation in the ecosystem."

Worsfold is still limited on free time but said he would be willing to contribute to the project if someone decided to fork it and keep it alive.

"It would be a shame to see something I built, and that people use, simply die," he said. "Hopefully someone will either fork it or take over development."

21 Nov 2017 12:15am GMT

18 Nov 2017

feedWordPress Planet

WPTavern: GitHub Launches Security Alerts for JavaScript and Ruby Projects, Python Support Coming in 2018

Last month GitHub launched its Dependency Graph feature that tracks a repository's dependencies and sub-dependencies under the Insights tab. This week the company rolled out an expansion of the feature and will now identify known vulnerabilities and send notifications with suggested fixes from the GitHub community.

Dependency graphs and security alerts are automatically enabled for public repositories, provided the repository owner has defined the dependencies in one of the supported manifest file types, such as package.json or Gemfile. (Private repo owners have to opt in.) The vulnerability alerts are not public - they will only be shown to those who have been granted access to the vulnerability alerts.

GitHub uses data from the National Vulnerability Database to alert repository owners about publicly disclosed vulnerabilities that have CVE IDs. Vulnerability detection is currently limited to JavaScript and Ruby projects but Python support is next on the roadmap for 2018. PHP, which is a bet less widely used in projects on GitHub, is likely further down the list.

18 Nov 2017 12:25am GMT

17 Nov 2017

feedWordPress Planet

WPTavern: WordCamp Europe 2018 Speaker Applications Now Open

WordCamp Europe 2018 has opened the call for speakers and will be accepting applications through January 15. The organizing team recommends that speakers already have some experience ahead of applying to speak at the largest WordPress event in Europe, but a dedicated Content Team will also be available with resources for helping speakers create a successful presentation.

The 2017 event received a total of 235 speaker applications and 43 were selected for the main event. Organizers plan to stick to the same format and are calling for 40-minute talks (30 min + 10 min Q&A) as well as 10-minute lightning talks. This year the event will experiment with hosting community workshops and organizers plan to open a separate call for workshop leaders next week.

The Content Team put out a specific call for more technical talks at the 2018 event after a community survey showed that more developer-oriented talks are what the audience is looking for. More than half of those surveyed identified themselves as developers (54%), with business owners (12%) the next largest demographic.

The survey also showed that 37% of respondents have been working with WordPress for more than 9 years and roughly 90% of attendees have been using WordPress for 4-9+ years. Advanced development was the most highly requested topic for presentations, selected by 53% of respondents, followed by design (45%).

The survey results offer some insight about which topics might fare well at WCEU in 2018. Organizers have also compiled an extensive list of ideas and topics to inspire speaker applicants.

A batch of 1,000 Early Bird tickets recently went on sale and there are still 680 available. Attendees who purchase a ticket before December 31, 2017, will receive a limited-edition swag item. The organizing team plans to release tickets in batches, as in previous years, but will not be setting specific expectations on sales this year, according to PR representative Letizia Barbi. The Sava Center venue, an international congress and cultural center, is the largest audience hall in Serbia and will accommodate all who want to attend WCEU 2018. Barbi said it should also scale down nicely in case of a smaller turn out.

17 Nov 2017 7:19pm GMT

WPTavern: WooCommerce Explores the Possibilities and Challenges for E-Commerce in the Gutenberg Era

The next release of WordPress (5.0) will introduce the new Gutenberg editor and contributors plan to keep it rolling towards the eventual goal of providing a full site building experience. Nearly every WordPress theme and plugin developer will be impacted by the change and many are starting to look ahead to how their products may interact with Gutenberg in the future.

What will e-commerce look like in the Gutenberg era? The WooCommerce design team has published a preview of some of their "Wootenberg" experiments, along with a gif demonstrating what a block-based editing experience may look like in the context of working with products. The team sees a lot of potential for putting the power of visual product editing into the hands of users.

The example shows a quick exploration of page layout with product blocks and the team also posted an idea of what basic product authoring may look like with a predefined product template that includes the featured image, product title, description, and price as new Gutenberg blocks. But will it be possible to have complex product creation fit into a block-based editor? The WooCommerce team admits in the post that they don't yet know how this will work.

"One thing that isn't yet 100% clear is how complex plugins like WooCommerce will work with Gutenberg," Automattic designer/developer James Koster said. "A simple product with a description, a price, and a category is one thing. But a product with variations, for each of which you want to upload a different image, and need to manage/track stock is quite another. Imagining a WYSIWYG editing experience for that kind of data is a little fuzzier."

Koster referenced Gutenberg's newly merged support for meta boxes, the first step in making product authoring possible. However, the Gutenberg team is still experimenting and isn't yet set on a solution for implementing meta boxes.

"How this works with WooCommerce in the long term is unclear," Koster said. "But you can rest assured it's something we'll be dedicating more time to investigating as WordPress approaches the 5.0 release." Koster concludes the post by asking readers if visual product editing, with the flexibility to rearrange product/shop layouts, is something that interests them.

"If there's one thing that WooCommerce should perhaps learn from Shopify's rapid growth, it's that many 'would-be' shop owners don't care to spend hours upon hours tweaking the layout of their shop, and that pre-built easy-to-use software that looks good and feels good, but can still be extended in complex ways, is what attracts many users," Jesse Nickles commented on the post. "While this may be the underlying goal of Gutenberg, it perhaps doesn't crossover clearly to the e-commerce world."

Koster said he agrees that users don't always need visual editing experiences and that simple things like price changes should be quick and painless.

"How we present data-driven editing alongside the Gutenberg experience will ultimately determine the success of the project from a WooCommerce perspective," Koster said.

Support for meta boxes is one the most challenging aspects of the Gutenberg project that the team has yet to solve. Exploring the possibilities of flexible page layouts for products is exciting, but even the WooCommerce team is left wondering how this is all going to work with more complex CMS data. Smaller product teams without the collective knowledge and resources of WooCommerce may have a more difficult time finding the bandwidth to experiment and rebuild their products in time for WordPress 5.0.

The WooCommerce team invites any users interested in Gutenberg-related UX changes to join the plugin's design feedback group, as they continue to explore how the new editor will work in the context of complex e-commerce product creation and display.

17 Nov 2017 4:30am GMT

16 Nov 2017

feedWordPress Planet

WPTavern: GDPR for WordPress Project Gains Momentum, Proposal Receives Positive Response from Developer Community

Community feedback on the new GDPR for WordPress project, created by WordCamp Denmark organizer Kåre Mulvad Steffensen and WP Pusher creator Peter Suhm, has started rolling in after the two launched a survey for developers. The project aims to provide an industry standard for getting plugins compliant with EU General Data Protection Regulation (GDPR) legislation ahead of the May 2018 deadline.

Steffensen published some initial results of the survey after having it open for two weeks. So far, 90% of respondents have answered that they would consider implementing a GDPR "file" types solution for their plugins if a standard was available. Only 4.9% of the 40 developers who responded said they have a plan for making their plugins GDPR compliant and 43.9% said they do not currently have a plan. The remaining 24.4% were developers of plugins that do not handle personal data.

"Our talks with Paul Sieminski from Automattic and Dovy Paukstys from the Redux options framework have reassured us that we still do have a need for a GDPR structure which can help the community establish a basis for handling GDPR compliance," Steffensen said.

Steffensen and Suhm created a GitHub repository where they have outlined their proposal for a PHP object interface that plugin developers could add to their codebases as a standard way of indicating how their plugins work with personal data.

"The nature of such an interface puts some responsibility in the hands of the developer to identify any place personal data is stored," Steffensen said. "What kind of data it is, and for what purpose as well as how it should be handled upon deletion. The Interface approach will allow a community-wide adoption, without setting limitations on how plugin developers choose to work with their data - something we obviously can't control."

The idea is that plugin developers could then build other tools on top of this framework using specific functions that correspond to GDPR requirements, such as functions that allow users to access their data, implement the right to be forgotten, report data breaches, and delete and anonymize data. Developers could also build plugins that offer a plain language description of what personal data a plugin collects and how it is handled.

In speaking with Dovy Paukstys on how this could work with Redux, Steffensen said the options framework may be able to facilitate compliance for the 500,000+ sites where it is active and the developers who use it to build plugins.

"Dovy from Redux has a coder's view on this," Steffensen said. "Our object interface (PHP) would be something his framework could provide an easy way to utilize for the many developers using Redux. The redux users (developers) could essentially do this themselves also, but since Redux is a framework it makes sense to see if they can build something that will make it near instant for developers to provide compliance for the GDPR."

Steffensen said the team is aware that the first version of the interface will not render plugins, and by extension their sites, instantly compliant. The interface they are proposing is not one that could be held legally accountable, but the goal is to make it possible for developers to build accountable systems on top of it.

GDPR for WordPress Project Founders Consider Accepting Sponsorships

With 189 days remaining before the GDPR goes into effect, the team will need to work quickly to make a solution available with enough time for interested developers to incorporate it into their plugins. They have not yet set up a way to accept donations but are considering it.

"We aren't actively seeking funding, but would love any funds that would help us allocate the time needed to keep the momentum going," Steffensen said. "We're lucky that the WP Tavern article brought attention to our GDPR approach and have caught the eyes of some of the key players in the ecosystem. One such company is Mailpoet that was the first to raise the idea of sponsoring our work."

Steffensen works at Peytz.dk, a Danish WordPress agency that wants to support the community and has allocated some of his time to work on the project. He said any funding/donations they receive would be spent on pushing the roadmap forward, investing time in coding, and possibly seeking further advice from people who they cannot expect to be in it for free.

In addition to looking at ways to receive donations, the team plans to keep the survey open for developers for awhile longer to try to make more connections in the community. Steffensen said they hope respondents will help them gain insight on the developer community's readiness and also enable them to reach out to any plugin owners who could play a key role in a wider adoption.

16 Nov 2017 8:58pm GMT

WPTavern: Consultants Are WordPress’ Boots on the Ground

A business can't survive without strong sales & customer service, two competencies that are arguably the lifeblood of a company.

Many of you reading this fill that exact gap for the open source WordPress project. I don't mean this as a slight to the thousands of wonderful people who build the software, document it, and support it in the forums, but that consultants (doing it right or wrong) are also fueling this locomotive too.

There are no official sales or customer service channels at WordPress.org and us consultants bear the brunt of it - for better or worse - and that's where our job comes in. Just as you trust a core contributor to spot-check her code and ensure that we've sanitized all the things!

Consultants are the boots on the ground, and as you'll see below in my feedback section, represent a disproportionate ratio of launching many more websites than an individual website owner. - Matt Medeiros

From The blue-collar WordPress worker and the 2,500+ websites built to grow the CMS.

16 Nov 2017 8:07pm GMT

WPTavern: WPWeekly Episode 294 – HeroPress, Community, and WinningWP With Topher DeRosia

In this episode, John James Jacoby and I are joined by Topher DeRosia, founder of HeroPress. DeRosia provides an update on HeroPress and explains his new role creating WordPress training videos for WinningWP. Jacoby and I discussed the news of the week including, Press This removed in WordPress 4.9, Meta box support in Gutenberg, and WP-SpamShield removed from the directory.

Near the end of the show, we discuss whether or not consultants, agencies, and site builders have been left out of the discussion and not factored into WordPress' growth over the years.

Stories Discussed:

Press This Removed from WordPress 4.9 in Favor of a Plugin
Bianca Welds Awarded Kim Parsell Travel Scholarship
WordCamp Europe 2018 Early Bird Tickets Now on Sale
Gutenberg Contributors Explore Alternative to Using iframes for Meta Boxes
WP-SpamShield Plugin Removed from WordPress.org, Author Plans to Pull All Plugins from the Directory
The blue-collar WordPress worker and the 2,500+ websites built to grow the CMS

Picks of the Week:

How to Whitelist Comments in WordPress

Dark Mode is an experimental feature plugin that darkens the colors of the WordPress backend.

WPWeekly Meta:

Next Episode: Wednesday, November 22nd 3:00 P.M. Eastern

Subscribe To WPWeekly Via Itunes: Click here to subscribe

Subscribe To WPWeekly Via RSS: Click here to subscribe

Subscribe To WPWeekly Via Stitcher Radio: Click here to subscribe

Listen To Episode #294:

16 Nov 2017 3:13am GMT

WPTavern: WordPress 4.9 Released with Major Improvements to Customizer Workflow, Updated Code Editors, and New Core Gallery Widget

WordPress 4.9 "Tipton" was released today, named for Oklahoma-born jazz musician William Lee Tipton, a gifted pianist and saxophonist. This update introduces major improvements to the design and collaboration workflow in the Customizer, improves WordPress' built-in code editor, and enhances core text and media widgets.

Draft, Schedule, and Preview Changes in the Customizer

Prior to 4.9, users could get a live preview of their sites in the Customizer but any changes they made would need to be saved immediately or discarded. This update makes it possible to draft and schedule changes in the Customizer, and even share a preview link to collaborate on changes before making them live. Users can now stage content, such as new pages, a new set of widgets, a different combination of menu items, and schedule it all to publish at a future date.

This release also brings the ability to search, browse, and preview themes directly in the Customizer. The search interface includes filters for subject, features, and layout, just like the ones on the "Add Themes" screen in wp-admin. It does not yet include the featured, popular, latest, or favorites tabs, so users will need to navigate back to the admin if they want to browse those categories.

The menu creation process has also been updated in the Customizer to be less confusing with a rethink of the UI and revised copy.

Syntax Highlighting and Error Checking Added to the Code Editors

WordPress 4.9 brings syntax highlighting, linting, and auto-completion to the built-in code editors by incorporating the CodeMirror library. These long-awaited improvements are now available in the theme and plugin editors as well as the custom HTML widget and additional CSS box in the Customizer. The feature comes with prominent warnings about directly editing themes and plugins and protection against saving code that would cause a fatal error.

New Core Gallery Widget and Support for Shortcodes and Embedded Media in the Text Widget

WordPress 4.9 adds a new gallery widget to the collection of core media widgets (audio, image, and video) that were introduced in 4.8. It brings the same gallery-creation features to widgets that have long been available in the post and page editors.

These incremental changes will help users get ready for Gutenberg's block-based interface. The plan is to eventually transition widgets over to blocks after Gutenberg is in core and the plugin already has support for a gallery block, as well as a Custom HTML block.

As of 4.9, users can now embed media in the Text widget, including images, video, and audio by clicking the "Add Media" button. In order to make this possible, WordPress contributors also needed to add shortcode support to widgets, a feature that users have requested for nearly a decade. With this now built into core, hundreds of thousands of WordPress sites will no longer need additional code from plugins and themes to use shortcodes in widgets.

Widgets have also been improved to offer a better migration experience with updated logic for mapping widgets between two themes' widget areas.

On Towards Gutenberg

WordPress 4.9 also includes a notice in the about.php page of the admin, inviting users to help test or contribute to Gutenberg. It is the first time a feature plugin has been highlighted so prominently on the page users see after they update to the latest version.

The Gutenberg project has been getting a lot of attention over the past few months as the WordPress community looks ahead to the 5.0 release that will introduce the new editor to the world. Meanwhile, contributors to 4.9 have been working in tandem to make significant improvements to existing features, enabling users to do more with widgets and overall site design than ever before. This release was led by Weston Ruter and Mel Choyce with help from 443 contributors, 42% (185) of them contributing to WordPress for the first time.

16 Nov 2017 1:24am GMT

Dev Blog: WordPress 4.9 “Tipton”

Major Customizer Improvements, Code Error Checking, and More! 🎉

Version 4.9 of WordPress, named "Tipton" in honor of jazz musician and band leader Billy Tipton, is available for download or update in your WordPress dashboard. New features in 4.9 will smooth your design workflow and keep you safe from coding errors.

Featuring design drafts, scheduling, and locking, along with preview links, the Customizer workflow improves collaboration for content creators. What's more, code syntax highlighting and error checking will make for a clean and smooth site building experience. Finally, if all that wasn't pretty great, we've got an awesome new Gallery widget and improvements to theme browsing and switching.


Customizer Workflow Improved

Draft and Schedule Site Design Customizations

Yes, you read that right. Just like you can draft and revise posts and schedule them to go live on the date and time you choose, you can now tinker with your site's design and schedule those design changes to go live as you please.

Collaborate with Design Preview Links

Need to get some feedback on proposed site design changes? WordPress 4.9 gives you a preview link you can send to colleagues and customers so that you can collect and integrate feedback before you schedule the changes to go live. Can we say collaboration++?

Design Locking Guards Your Changes

Ever encounter a scenario where two designers walk into a project and designer A overrides designer B's beautiful changes? WordPress 4.9's design lock feature (similar to post locking) secures your draft design so that no one can make changes to it or erase all your hard work.

A Prompt to Protect Your Work

Were you lured away from your desk before you saved your new draft design? Fear not, when you return, WordPress 4.9 will politely ask whether or not you'd like to save your unsaved changes.


Coding Enhancements

Syntax Highlighting and Error Checking? Yes, Please!

You've got a display problem but can't quite figure out exactly what went wrong in the CSS you lovingly wrote. With syntax highlighting and error checking for CSS editing and the Custom HTML widget introduced in WordPress 4.8.1, you'll pinpoint coding errors quickly. Practically guaranteed to help you scan code more easily, and suss out & fix code errors quickly.

Sandbox for Safety

The dreaded white screen. You'll avoid it when working on themes and plugin code because WordPress 4.9 will warn you about saving an error. You'll sleep better at night.

Warning: Potential Danger Ahead!

When you edit themes and plugins directly, WordPress 4.9 will politely warn you that this is a dangerous practice and will recommend that you draft and test changes before updating your file. Take the safe route: You'll thank you. Your team and customers will thank you.


Even More Widget Updates

The New Gallery Widget

An incremental improvement to the media changes hatched in WordPress 4.8, you can now add a gallery via this new widget. Yes!

Press a Button, Add Media

Want to add media to your text widget? Embed images, video, and audio directly into the widget along with your text, with our simple but useful Add Media button. Woo!


Site Building Improvements

More Reliable Theme Switching

When you switch themes, widgets sometimes think they can just move location. Improvements in WordPress 4.9 offer more persistent menu and widget placement when you decide it's time for a new theme.

Find and Preview the Perfect Theme

Looking for a new theme for your site? Now, from within the Customizer, you can search, browse, and preview over 2600 themes before deploying changes to your site. What's more, you can speed your search with filters for subject, features, and layout.

Better Menu Instructions = Less Confusion

Were you confused by the steps to create a new menu? Perhaps no longer! We've ironed out the UX for a smoother menu creation process. Newly updated copy will guide you.


Lend a Hand with Gutenberg 🤝

WordPress is working on a new way to create and control your content and we'd love to have your help. Interested in being an early tester or getting involved with the Gutenberg project? Contribute on GitHub.

(PS: this post was written in Gutenberg!)


Developer Happiness 😊

Customizer JS API Improvements

We've made numerous improvements to the Customizer JS API in WordPress 4.9, eliminating many pain points. (Hello, default parameters for constructs! Goodbye repeated ID for constructs!) There are also new base control templates, a date/time control, and section/panel/global notifications to name a few. Check out the full list.

CodeMirror available for use in your themes and plugins

We've introduced a new code editing library, CodeMirror, for use within core. CodeMirror allows for syntax highlighting, error checking, and validation when creating code writing or editing experiences within your plugins, like CSS or JavaScript include fields.

MediaElement.js upgraded to 4.2.6

WordPress 4.9 includes an upgraded version of MediaElement.js, which removes dependencies on jQuery, improves accessibility, modernizes the UI, and fixes many bugs.

Roles and Capabilities Improvements

New capabilities have been introduced that allow granular management of plugins and translation files. In addition, the site switching process in multisite has been fine-tuned to update the available roles and capabilities in a more reliable and coherent way.


The Squad

This release was led by Mel Choyce and Weston Ruter, with the help of the following fabulous folks. There are 443 contributors with props in this release, with 185 of them contributing for the first time. Pull up some Billy Tipton on your music service of choice, and check out some of their profiles:

Aaron D. Campbell, Aaron Jorbin, Aaron Rutley, Achal Jain, Adam Harley (Kawauso), Adam Silverstein, AdamWills, Adhun Anand, aegis123, Afzal Multani, Ahmad Awais, Ajay Ghaghretiya, ajoah, Akash Soni, akbarhusen, Alain Schlesser, Alex Dimitrov, Alex Goller, Alexandru Vornicescu, alibasheer, alxndr, Andrea Fercia, andreagobetti, Andrew Duthie, Andrew Nacin, Andrew Norcross, Andrew Ozz, Andrew Taylor, Andy Fragen, Andy Meerwaldt, Andy Mercer, Angelika Reisiger, anhskohbo, Ankit K Gupta, Anthony Hortin, Anton Timmermans, antonrinas, appchecker, arena94, Arnaud Coolsaet, ArnaudBan, Arun, Ashar Irfan, atachibana, Atanas Angelov, audrasjb, Avina Patel, Ayesh Karunaratne, Barry Ceelen, bduclos, Bego Mario Garde, Behzod Saidov, Ben Cole, Ben Dunkle, benoitchantre, Bharat Parsiya, bhavesh khadodara, Biplav, Biranit, Birgir Erlendsson (birgire), biskobe, BjornW, Blackbam, Blobfolio, bobbingwide, bonger, Boone B. Gorges, Boro Sitnikovski, Brad Parbs, Brady Vercher, Brandon Kraft, Brent Jett, Brian Layman, Brian Meyer, Bruno Borges, bseddon, Bunty, Carl Danley, Carolina Nymark, Caroline Moore, carolinegeven, Charlie Merland, Chetan Chauhan, chetansatasiya, choong, Chouby, Chris Hardie, Chris Runnells, Christian Chung, Christoph Herr, chsxf, cjhaas, Cliff Seal, code-monkey, Collins Agbonghama, corvidism, csloisel, Daedalon, Daniel Bachhuber , Daniel James, Daniele Scasciafratte, dany2217, Dave Pullig, DaveFX, David A. Kennedy, David Aguilera, David Anderson, David Binovec, David Chandra Purnama, David Herrera, David Shanske, David Strauss, David Trower, Davide 'Folletto' Casali, daymobrew, Derek Herman, designsimply, DiedeExterkate, dingo-d, Dion Hulse, dipeshkakadiya, Divyesh Ladani, Dixita Dusara, dixitadusara, Dominik Schilling, Dominik Schwind, Drew Jaynes, dsawardekar, Dzikri Aziz, Eaton, eclev91, Edd Hurst, EGregor, Ella Iseulde Van Dorpe, elvishp2006, enrico.sorcinelli, Eric Andrew Lewis, euthelup, Evan Mullins, eventualo, Fabien Quatravaux, FancyThought, Felipe Elia, Felix Arntz, fergbrain, Florian TIAR, Gabriel Mariani, Garth Mortensen, Gary Pendergast, Gennady Kovshenin, George Stephanis, Girish Lohar, Govind Kumar, Graham Armfield, Greg Ross, Gregory Cornelius, grosbouff, Guido Scialfa, Gustave F. Gerhardt, guzzilar, Hardeep Asrani, Hazem Noor, hazimayesh, Helen Hou-Sandí, Henry, Henry Wright, herregroen, Hinaloe, Howdy_McGee, Hugh Lashbrooke, Hugo Baeta, Iacopo C, imath, Ippei Sumida, Ipstenu (Mika Epstein), Irene Strikkers, Ivan Kristianto, ixmati, J.D. Grimes, j.hoffmann, James Nylen, Janki Moradiya, Jason Stallings, Jeff Paul, Jennifer M. Dodd, Jeremy Felt, Jeremy Pry, Jip Moors, jjcomack, jkhongusc, Joe Dolson, Joe Hoyle, Joe McGill, John Blackbourn, John Eckman, John James Jacoby, John Regan, johnpgreen, johnroper100, Jonathan Bardo, Jonathan Desrosiers, Jonny Harris, Joost de Valk, Josepha, Josh Pollock, Joy, jrf, jsepia, jsonfry, Juhi Saxena, Julien, Justin Kopepasah, Justin Sternberg, K.Adam White, Karthik Thayyil, keesiemeijer, Kelly Dwan, Kevin Newman, Kim Parsell, Kiran Potphode, Kite, Konstantin Kovshenin, Konstantin Obenland, Konstantinos Galanakis, koopersmith, Kristin Kokkersvold, lalitpendhare, Lance Willett, Laurel Fulford, lemacarl, lessbloat, llemurya, Luke Cavanagh, Mário Valney, m1tk00, Maedah Batool, Mahesh Prajapati, Mahvash Fatima, Maja Benke, Mako, manolis09, manuelaugustin, Marcel Bootsman, Marius L. J., Marius Vetrici, Mark Jaquith, Mark Root-Wiley, markcallen, Marko Heijnen, MatheusGimenez, Matt Gibbs, Matt Mullenweg, matthias.thiel, mattyrob, Maxime Culea, mdifelice, megane9988, Mel Choyce, Menaka S., Michael Arestad, Michele Mizejewski, Miina Sikk, Mike Crantea, Mike Hansen, Mike Schinkel, Mike Schroder, Milan Dinić, Milana Cap, Milind More, Mirucon, Mitch Canter, Mithun Raval, mkomar, monikarao, Morgan Estes, moto hachi ( mt8.biz ), msebel, munyagu, MyThemeShop, N'DoubleH, Nathan Johnson, nenad, nic.bertino, Nick Diego, Nick Halsey , Nicolas GUILLAUME, nicollle, Nidhi Jain, Nikhil Chavan, Nilambar Sharma, Nileshdudakiya94, Nishit Langaliya, Norris, obradovic, Ov3rfly, Paal Joachim Romdahl, palmiak, Parth Sanghvi, Pascal Birchler, Pat O'Brien, patel, Paul Bearne, Paul Biron, Paul Dechov, Paul Wilde, Payton Swick, pcarvalho, Pedro Mendonça, Pete Nelson, Peter "Pessoft" Kolínek, Peter J. Herrel, Peter Toi, Peter Westwood, Peter Wilson, Philip John, Piotr Delawski, Pippin Williamson, Plastikschnitzer, powerzilly, Pratik Gandhi, Presslabs, Punit Patel, Purnendu Dash, r-a-y, Rachel Baker, rafa8626, Rahmohn, Rami Yushuvaev, ramon fincken, Ravi Vaghela, RC Lations, redrambles, RENAUT, Reuben Gunday, rfair404, Riad Benguella, Rian Rietveld, Riddhi Mehta, Rinku Y, Rob Cutmore, Rodrigo Primo, Ronak Ganatra, rugved, Rushabh Shah, Ryan Boren, Ryan Duff, Ryan Holmes, Ryan Marks, Ryan McCue, Ryan Neudorf, Ryan Plas, Ryan Welcher, ryanrolds, ryotsun, Sabuj Kundu, Sagar Prajapati, sagarladani, Said El Bakkali, Sami Keijonen, Sampat Viral, Samuel Sidler, Samuel Wood (Otto), sarah semark, sathyapulse, sboisvert, Scott DeLuzio, Scott Kingsley Clark, Scott Lee, Scott Reilly, Scott Taylor, scribu, Sebastian Pisula, SeBsZ, Sergey Biryukov, Sergio De Falco, Shamim Hasan, Shawn Hooper, shital, shramee, Siddharth Thevaril, Simon Prosser, skostadinov, Slava Abakumov, someecards, Soren Wrede, spencerfinnell, spocke, Stanko Metodiev, Stephane Daury (stephdau), Stephen Edgar, Stephen Harris, Steve Grunwell, Steve Puddick, stevenlinx, Subrata Mal, Subrata Sarkar, Sudar Muthu, Susumu Seino, svrooij, Takahashi Fumiki, Takayuki Miyauchi, Tammie Lister, Taylor, tejas5989, terwdan, tharsheblows, thingsym, Thoriq Firdaus, Thorsten Frommen, Timothy Jacobs, tmatsuur, tobi823, Todd Nestor, Tor-Bjorn Fjellner, Torsten Landsiedel, Toru Miki, toscho, transl8or, truongwp, tuanmh, TV productions, uicestone, Ulrich, Umang Vaghela, Umesh Nevase, upadalavipul, Utkarsh, vhauri, williampatton, withinboredom, Wojtek Szkutnik, Xenos (xkon) Konstantinos, Yahil Madakiya, yonivh, yrpwayne, zachwtx, and Zane Matthew.

Finally, thanks to all the community translators who worked on WordPress 4.9. Their efforts bring WordPress 4.9 fully translated to 43 languages at release time, with more on the way.

Do you want to report on WordPress 4.9? We've compiled a press kit featuring information about the release features, and some media assets to help you along.

If you want to follow along or help out, check out Make WordPress and our core development blog.

Thanks for choosing WordPress!

16 Nov 2017 1:16am GMT

15 Nov 2017

feedWordPress Planet

WPTavern: Gutenberg 1.7 Adds Multi-Block Transform Functionality, Drops iframes Implementation of Meta Boxes

Gutenberg 1.7 was released today, two weeks after version 1.6, with a fresh round of new features, design updates, and the groundwork for nested blocks and block extensibility.

Last week contributors began exploring an alternative to using iframes for meta boxes. This experiment has landed in 1.7 so that the plugin now renders meta boxes inline. Gutenberg engineer Riad Benguella, who wrote and merged the code, said that it doesn't fix all the meta box issues and might create some new ones, but it "gets us closer to where we want to go." Pre-rendering meta boxes and creating a migration path for existing ones is next on the agenda.

One of the most exciting new features in 1.7 is the multi-block transform functionality that allows users to select multiple blocks and instantly transform them into other block types. It works like a little bit of Gutenberg magic. By default, users can select multiple paragraphs and transform them into a list or select multiple images and transform them into a gallery.

After selecting two or more blocks, the user can click on the block's settings in the toolbar to transform them. They can also be easily changed back to single blocks. The multi-block transform functionality has been added to the Blocks API so that developers can set isMultiBlock to true to specify blocks that can be transformed.

Version 1.7 introduces a new toggle that the team is testing for switching between the top fixed toolbar and the contextual toolbars attached to each block. It provides an easy way for users to test both types of toolbar styles, but may be temporary as the pull request was submitted as a suggestion for an A/B test.

Gutenberg 1.7 paves the way for nested blocks in the data structure. It also adds hooks for block extensibility and contributors are currently testing how these work internally.

A few other notable features in this release include the following:

Gutenberg's documentation has also been moved to https://wordpress.org/gutenberg/handbook/, signaling the project is getting closer to becoming part of WordPress. The new editor will be included in WordPress 5.0, which will ship when Gutenberg is ready. A notice in the 4.9 about.php page invites users to start testing the feature plugin ahead of its inclusion in core.

15 Nov 2017 11:57pm GMT