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.
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.
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
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
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:
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.
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.
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.
A few other notable features in this release include the following:
- Added @-mention autocomplete for users in a site
- Allow pasting standalone images and uploading them (also supports pasting base64 encoded images)
- Full design update to focus styles around the UI
- Placed “table of contents” button in the header area, disabled when there are no blocks in the content, added paragraph count
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.
In the lead-up to WordCamp US we're in right now I chatted with Brian Krogsgard at Post Status in an hour podcast and we spoke about the core releases this year, Gutenberg, React, WooCommerce, and WordPress.org. On the 29th I'll be talking to WP Tavern, so tune in then as well. For something completely different, I was on the new OFF RCRD podcast with Cory Levy about the earliest days at Automattic and entrepreneurship.
My first website was built using Frontpage. Then I discovered Geocities, which at the time made it easy to break and fix code and have it instantly live for others to find on the world wide web. It was an optimal learning environment for me. I learned HTML and CSS by copying, pasting, and then tweaking every which way until it was doing something absurd like flashing hot pink text. It was the Wild West and there were no real rules yet except for those in this new language.
Like any language, I was learning little by little in search of ways to bend the rules and “speak” like a native.
I only coded for fun, but many years later, I made a website for a job. I used Dreamweaver because I was told all professionals used Dreamweaver. I found it easy to use, much easier than Frontpage, especially for building a larger more complex website. I started learning how to read PHP and doing a lot of what was needed in the metadata and the code for basic SEO.Finding WordPress
Fast forward another few years. I set up several free sites for nonprofits using Webs, Weebly, other page builders whose names I can’t recall, Joomla, and then, one day I stumbled upon WordPress. I wasn’t sure if I liked it at first because the out of the box theme was ugly and I couldn’t figure out how to manipulate it. Then, I found a theme on Themeforest that installed the styles and the demo content. This was worth the $30. This gave me the ability to tweak the theme because I knew enough HTML and CSS to change things in the file editor. I was still coding like I did in my Geocities days, only my aesthetics had improved.
I cringe relaying that experience now. I knew enough to be really dangerous. I didn’t do any form of version control, I didn’t do any backups, I didn’t vet my plugins, or even know how to properly vet my plugins.
I am so lucky nothing went terribly wrong.
On one hand, WordPress gave me an easy way to dive right in and do everything on my own. On the other hand, it made it too easy for me to download bad plugins, edit things I probably should not have been touching, and in the end, I guess that’s okay because when I was serious about maintaining a website, I did take the time to learn more about what I needed to know.Finding What I Needed
What I know today is that I am not a developer. I’m not even a designer. I have fun with the creation process, but there are other people who are much more talented and efficient in those processes and I’m happy to pay them for their expertise. I have learned what I need to know about the framework and can talk to designers and developers about what I’m looking for and ensure they know what they’re doing. I can pick out reliable themes and plugins. I can advise our clients, who are mostly nonprofits and social enterprises, on the best path for a sustainable website. I understand the need for disaster recovery, backups, and security. I understand the value of paid premium licenses and ongoing support.
These are all things that in my days of starting out I didn’t know I needed. Even if someone tried to explain it to me, I probably wouldn’t have felt that I needed them. Sometimes I can be stubborn and I need to experience the pain points myself before I buy into what everyone else is saying. I used to learn best from failure.
I still learn from failure, but when it comes to WordPress, I have also surrounded myself with a community who help me grow and learn.
In 2013, I started attending the Fort Worth WordPress meetup. The group was still pretty small at the time, but they were very inviting. I picked up some new tips and tricks that I used right away. While my eyes glazed over at some of the more advanced details, I understood the possibilities and that the work was beyond my capabilities. I learned how to ask for help with those things. Remember, I’m not a designer or a developer, so this meant hiring for those skills from the network of people I met in the WordPress community.
Over the last 4 ½ years I’ve been able to sell numerous WordPress projects and some of them are incredibly custom and complex. In return, I’ve been able to provide freelance work for members of my community; I’ve been able to give back via WordCamps sharing my experience with project scoping, sales, and negotiations. We all have something of value to share. No matter your area of expertise, you can give something back to the community.The Real Value
The best thing about WordPress is not the tool itself. It’s the people who use it or are wanting to try it. The WordPress community is what makes WordPress and WordCamps really great. My hope is that as a community we can help WordPress evolve and adapt and that we can leverage technology, including WordPress, for the greater good.
We’ve already done this and that’s why WordPress powers almost 30% of the web. We’ve been doing it for years, but the technology landscape is changing rapidly. Are we keeping up?
A few weeks ago, Chris Lema asked me and a group of other WordPressers, “What could destroy WordPress, and how would you fix it?” We answered this a number of ways and you’ve probably come up with your own answer. My answer? I think that the evolution of technology could destroy WordPress.
To fix that we would need to evolve, dream big, and create the innovative changes that would keep WordPress alive. We can’t wait until the changes are already in place. It would take far too long for such a large ecosystem to catch up, and in the meantime, it would start to disappear. Look at Kodak; my kids don’t even know what a Kodak moment is. That’s just sad.What is our dream as a community?
Will people talk about WordPress in the past tense or will we find ways to help it thrive?
Even as we work towards the same dream, there are still complex challenges to overcome. We’ll likely fail many times as we try to innovate. This is actually good; we’ll learn from those mistakes, but we might become jaded. We’ll certainly have moments of frustration. We might even try another framework, and the grass might actually be greener on the other side. Yet, the fact that we are such a close knit community sets us apart.
Imagine what could happen if a community this large banded together towards one dream.
We could pave a path towards something really great. It feels like a huge undertaking. It’s something that could paralyze us if we tried to get it “right” before we started. The key is to set common goals, but to individually start working and living on purpose. Then, we can come together in a more meaningful way.
In my recent keynote at WordCamp DFW I shared a bit of my heritage and my life story so that people could understand my passion for social impact. Everyone has a story that makes them a unique fit to tackle different challenges. When we put our collective skills together, we can make a difference.
John F. Kennedy said, “One person can make difference, and everyone should try,” and Nelson Mandela said, “It is in our hands to make a difference.”
Many paths have been paved so that we could live in a different world. Now, our dreams pave the way for future. Together we’ll create the future of WordPress.
The post My journey to WordPress taught me that my talents are best used elsewhere. appeared first on HeroPress.
iA Writer 5 for iOS was released last week, nearly a year after version 4. This update is free for those who purchased version 4 from the iOS App Store. iA Writer 5 for Mac is still in the works. The free Android version of the app is receiving incremental improvements that will bring it to parity with version 5 in the near future.
iA Writer is a plain text writing and editing app that is popular with authors, academics, and long-form writers. It’s also a favorite among WordPress users who look to third-party apps for to provide a more focused, distraction-free writing environment. In April 2016, version 3.1.4 for Mac and iOS introduced publishing drafts to WordPress.com and Jetpack-powered sites.
Version 5 focuses on making everything accessible through the keyboard by bringing the Open Quickly feature in iA Writer for Mac to iOS. The app’s creators said the goal of the design process was to “allow the writer to do everything without leaving the keyboard, including file handling, export, and all commands.” The new Quick Search feature is now built into the keyboard bar along with with a fully configurable keyboard. This allows users to quickly do things like create new files, switch to night mode, and export to PDF without leaving the keyboard.
This release adds new organization features that allow users to select multiple files and folders and move, rename, or delete them from the Library. It also introduces Smart Folders which can be created based on a set of rules. Version 5 adds support for iOS11’s Files system, allowing users to open and edit text files from any storage provider that works with Files. Support for Dropbox, Google Drive, and Box is already available with more providers coming soon.
The makers of iA Writer are interested in exploring other platforms if there is sufficient interest, including the possibility of creating a Windows version. Demand doesn’t seem to be very high, as the writing app’s fans are primarily Apple-only users.
How badly do you want a Windows version of iA Writer?
— iA Writer (@iAWriter) October 17, 2017
However, users across multiple platforms have requested a web version of iA Writer, and the company confirmed in September that they are already working on it. After releasing a big Material Design update to the iA for Android app in October, the creators said Android users will be the first to have access to the web version:
The biggest request from you was collaboration, in other words, iA Writer for Web. iA Writer for Android will stay free and you will be able to connect and subscribe to the Web version via the app, if you wish to. If you could tell us what you’d expect to pay for it, that would be very helpful…As part of our commitment to continually improve iA Writer on all platforms, Android will likely be the first to gain access to the upcoming Web collaboration.
The upcoming web version should provide a sort of bridge for users on other desktop platforms without an iA Writer app.
There’s no target release date for iA Writer 5 for Mac but iA Inc has confirmed that it will also be a free update for those who have purchased the previous version.
If you didn’t watch the live stream or attend WooConf in-person, you’re in luck as videos from the event are starting to come online. The first talk highlights is the State of the Woo by Todd Wilkens, Head of WooCommerce. Wilkens shares stats, provides an overview of projects the team is working on, what to expect in new versions, and explains the relationship between WooCommerce and Jetpack.
The video is available to watch for free, but viewers must provide their first and last name as well as an email address. Clicking the play button without entering this information displays a message that says Please enter your full name. This is a classic technique used by many internet marketers.
Although you can provide fake information in order to watch the video for free, I feel it’s an unnecessary burden. The WooCommerce team could obtain the same information with a form in the post. An alternative to watching the video is reading the company’s great overview of Wilkens’ session. The team plans to publish other talks from WooConf in the coming weeks.
Updated November 14th: An Automattic employee has removed the email form and made it skippable.
Umami is the theme that will be used in the Umami installation profile for Drupal core.
Development takes place on github. Please file any issues there.
Documentation does not exist yet - perhaps you'd like to start writing some for us?
Yacht Charter Booking Drupal Theme
Sailor is a Drupal port of the Sailor HTML Template
Install with Composer:composer require drupal/sailor
Composer will also then execute NPM. You will be asked for your Envato Market token. You can also put this in the npm config like this:npm config envato_token YOURTOKEN
or it can be added as an environment variable with the name: NPM_CONFIG_ENVATO_TOKEN
When I look back over the last 25 years, in some ways what seems most precious is not what we have made but how we have made it and what we have learned as a consequence of that. I always think that there are two products at the end of a programme; there is the physical product or the service, the thing that you have managed to make, and then there is all that you have learned. The power of what you have learned enables you to do the next thing and it enables you to do the next thing better. — Jony Ive
WPTavern: WP-SpamShield Plugin Removed from WordPress.org, Author Plans to Pull All Plugins from the Directory
The WP-SpamShield plugin was removed from the WordPress.org directory this week due to what the Plugin Review Team has deemed a violation of the guidelines and a possible miscommunication.
Two weeks ago, the author of WP-SPamShield and the author of the Plugin Organizer plugin exchanged contentious remarks in a support forum thread where each accused the other of targeting each others’ plugins. This resulted in both parties adding code that disabled the others’ plugins, and both were asked by the Plugin Team to remove the code.
WP-SpamShield’s author, Scott Allen, has published an account of his interactions with the Plugin Team with updates for users who are monitoring the status of the plugin. Although the team rarely discloses why a plugin was removed, representative Mika Epstein responded to Allen when he said he had not received an answer about what guideline the plugin had violated:
Sorry, I thought it was clear that it’s issues regarding the forum guidelines and rule #9:
Intentionally attempting to exploit loopholes in the guidelines.
To whit, you were asked to make a change and did so incompletely. If this was not intentional, then I apologize.
I’ve sent you a followup email, trying to clarify what we would accept as solutions to the issue (I came up with 3 options, but I’m open to hearing more).
I understand why you’re angry and we will respect any decision you make regarding this. Nothing that has happened thus far is insurmountable or permanent.
In the post Allen published, he said his experiences with the Plugin Team over the past 10 years have caused him to decide to move his plugins off of WordPress.org. When I contacted him to see if he plans to update his code according to the Plugin Team’s suggestions, he said he doesn’t agree with the solutions the team is offering, nor their assessment of the situation.
“They really were not solutions,” Allen said. “It was just rehashing the same issues we’d already discussed. Unfortunately, neither Otto nor Mika have the security expertise to be making the dictates they were making, so there were no realistic solutions.”
Allen also claimed that Epstein’s report about him making a change and it being incomplete was not accurate and that the Plugin Team did not seem to be on the same page:
We literally did exactly what they asked and made the changes. Two weeks ago Mika had emailed me and indicated things were good. (No code updates since then.) Then two weeks of silence, and then angry email from Otto out of the blue yesterday telling us it was booted. The issue he brought up was different code.
The two of them cannot make up their minds on what is acceptable, and what is not. The arbitrary removal was the last straw though. WordPress.org is the only venue that would do that. We repeatedly asked them what rule we broke, to no answer. Only after I called Mika out on the forum did she come up with something – Rule 9 – exploiting a loophole in the rules. Seriously? It’s impossible for developers to comply with rules that are constantly changing.
Allen confirmed that his team at Red Sand Media Group plans to pull all seven of its plugins from WordPress.org as the result of the incident but will continue maintaining and hosting them elsewhere.
“Developers cannot operate like that,” Allen said. “People depend on us. While it might hurt a bit in the short term, in the long term, we have to do it. There really need to be some major reforms to the way plugins are handled.”
WP-SpamShield was installed on more than 100,000 WordPress sites before it was removed. There is currently no standard way to notify users why a plugin was removed from the directory, but the original dispute between the WP-SpamShield and Plugin Organizer authors is public, as well as a few exchanges between Allen and the Plugin Team. Allen said he is still working out the details of how to notify users that his plugins will be hosted elsewhere from now on.
“We’ll come up with a good plan in the next few days,” he said. “Some people have been notified already because WordFence let them know yesterday that WPSS was removed. (They knew before I did.)”
Samuel “Otto” Wood said the Plugin Team is still willing to put Allen’s plugins back up if he removes the code in question and that the team is not offended by a plugin developer being angry over a decision. At this time Allen appears to be unwilling to comply with the team’s most recent requests.
In the meantime, users who know that WP-SpamShield was been removed are waiting to hear if they need to begin looking for a replacement. Allen said that users shouldn’t need to replace the plugin, since the it will continue to work as before. However, some users are not comfortable installing free plugins hosted outside of WordPress.org. Allen’s team is figuring out a plan for how they will deliver updates to the plugin and will post more information for users on the Red Sand Marketing blog.
WPTavern: Weglot Passes €44K in Monthly Revenue, Plans to Expand into More CMS and E-commerce Markets
Weglot, a SaaS-based multilingual plugin that entered the WordPress market last year, has passed €44,000 in monthly revenue. The company received €450K in seed funding in May 2017 and has nearly doubled its user base in the past six months. Co-founder Rémy Berda reports that the plugin is approaching 20,000 users and that more than 20,000 websites are connected to the Weglot API, if you include the company’s Shopify product and those using the JS script directly.
WordPress customers currently represent 75% of Weglot’s revenue with Shopify at 25%, but Berda says the two markets are growing at the same rate. In May, the company’s customer distribution was primarily in the US and France, which made sense as the product’s founders are French and Weglot was first marketed to the French WordPress community. Weglot’s customer distribution has become more global over the past six months and the US has now overtaken France as the strongest market for the multilingual plugin. Canada has also passed Germany, and Berda said he thinks the distribution will eventually align progressively with global WordPress usage.Weglot customer distribution as of November 2017
Despite having only recently entered the WordPress community in a niche with well-established competitors, Weglot’s cofounders are confident their SaaS approach is the road to success for becoming the best multilingual solution for WordPress. The team is aiming for its product to become the highest rated multilingual plugin in the WordPress directory within the next six months.
WPML, a purely commercial product and the most widely used, has been in business since 2009 and is active on more than 500K sites. Polylang, a popular free plugin with a commercial option, is installed on more than 300,000 sites and has a 4.7-star rating on WordPress.org. qTranslate X is also a formidable competitor with more than 100,000 active installs and a 4.7-star rating.
“For now the two biggest plugins in terms of active installs are WPML and Polylang,” Berda said. “Both don’t have a SaaS approach. Polylang recently released the PRO version (it was only free previously) but it is still sold as a piece of software, not a SaaS. We are convinced that SaaS is the right approach as it allows us to be in constant relation with users and make the product evolve faster. It’s also healthier in terms of business.”
Although he has no precise statistics on how many, Berda said he sees a lot of former WPML and Polylang users (freelancers and agencies) in their support center who have opted to use Weglot on their new projects. This indicates that Weglot may not so much be whittling away at the existing customer base of other plugins but is finding success at attracting customers who are starting new projects.
In their efforts to stake a claim in the WordPress ecosystem, the Weglot team has found that being active in the community is important to having a successful product.
“WordPress is really huge so there is no magical formula for marketing,” Berda said. “I think what is important is to accept that it takes time. You must keep improving your product forever while being active in the community and do it not only with high intensity but for a long time.”
The €450K in seed funding Weglot received earlier this year has helped the team to expand its support and development team, but it has also made it possible for the company to invest more in the community. They have now sponsored a dozen WordCamps across the world, including WordCamp Europe in Paris.
Berda’s advice to other WordPress entrepreneurs who are looking for funding is to consider the option carefully and understand how it will impact the company’s future and ability to act independently.
“My recommendation would be to think twice about raising money as it takes time,” Berda said. “It changes your governance and it temporarily distracts you from your number one focus – your users. Raise only if you are sure you will have a return with the money invested. Not every business need to raise money.”
Fueled by their success in the WordPress market, Weglot plans to expand into other CMS and e-commerce markets, including BigCommerce and Jimdo, followed by Drupal, Magento, and Joomla. Berda said the company also plans to release an open version of the API for developers to integrate their non-CMS websites built on technologies like Symfony and Laravel.
“In 2018, we will be adding many things: We will start using machine learning to improve the quality of automatic translations,” Berda said. “We will also leverage the fact that we are SaaS to add some insights about language usage for the users so they can see what languages are performing better. Finally, we will add extra features to manage multilingual SEO. In terms of monthly recurring revenue, we aim to reach €70,000 in 6 months.”
WPTavern: Jetpack 5.5 Removes Syntax Highlighting and Gallery Widget for Compatibility with Upcoming WordPress 4.9 Release
Jetpack 5.5 was released yesterday with several important changes that ensure the plugin is compatible with the upcoming WordPress 4.9 release scheduled for November 14. The plugin will be able to shed some weight, as core improvements will make Jetpack’s syntax highlighting and gallery widget obsolete.
WordPress 4.9 incorporates CodeMirror, which brings syntax highlighting, linting, and auto-completion to the built-in code editors. Jetpack 5.5+ will rely on WordPress to handle syntax highlighting and the Custom CSS module has been updated to be fully compatible with core’s new code editing improvements.image credit: make.wordpress.org
Jetpack 5.5 also adds compatibility for WordPress 4.9’s new core gallery widget. When users update to 4.9, Jetpack will automatically migrate its own gallery widgets to use the widget included in core.
The release also includes several other changes for compatibility with WordPress 4.9:
- Press This sharing button removed, since the feature is being removed from core in favor of a plugin
- Changes to ensure compatibility with role and capability updates in WordPress 4.9
- Remove code for processing Contact Form shortcodes in widgets, as WordPress adds support for shortcodes in widgets in 4.9
Jetpack 5.5 also improves the connection process between the plugin and WordPress.com, which should reduce recent issue users have experienced when migrating their sites from HTTP to HTTPS. A full list of the changes in this release is available in the plugin’s changelog.
WordPress wasn’t the first blogging platform I tried. My very first blog was set up using Blogspot (now Blogger). I didn’t even know I wanted a blog to tell you the truth. But let me take a step back.
I am a techie. A very “untechie” techie, but a techie nonetheless. I actually went to university with a plan to study mathematics and become an actuarial scientist (math and money made for a perfect career, I thought). After one year of university-level mathematics, I decided that I was done with the subject and I stuck with the computer science courses I had also taken. It turned out I had a knack for programming and was often found in the computer lab, debugging my friends’ assignments.
Following my graduation, I worked for several years as a programmer before deciding that I had no interest in coding for the rest of my life. I moved on and up, studying management and information systems, which led me into more managerial positions. On my way there, I decided that I needed to have a personal website. I bought a domain (not my real name though) and starting looking into building my website.
My very first job out of university had been with a web development company as web administrator, where I had picked up quite a bit of HTML, so I figured it would be easy to just build my own website. While researching the latest and best, it struck me that being able to easily add content would be cool, as I had seen early content management systems used back in that job (Tango, anyone?).Blogging Begins
Suddenly my search results were showing me something called blogging. This was 2005, and blogs were still pretty new. I was excited by the concept, that I could have an easy way to put my thoughts out into cyberspace. I signed up for Blogspot and dove in. For all of 2 days. I wanted to change the design and the layout of my new blog, but I couldn’t. I was stuck in the box that Blogspot provided. A little more searching and I found WordPress.
WordPress meant I could install it myself on my own hosting and play around to my heart’s content. It was a techie’s dream. In April 2005, WordPress was at version 1.5 and I was in heaven. I spent days and nights tweaking and customizing my brand new website and blog. I was a WordPresser.
I was an avid blogger, sharing posts everyday — longer thought-pieces and short asides (who remembers that concept?). The blogging community in Jamaica was small but we were an enthusiastic bunch. Many of my friends were still using other platforms, but I was a diehard WordPress lover. They took comfort in the ease of use of their hosted platforms, while I reveled in being able to completely mess my site up myself (and fix it!).
I played with themes, and experimented with plugins. Two years later, I was helping other people set up and customize their WordPress blogs, and doing migrations from Blogspot.
I was a WordPress freelancer. I didn’t even know this was a thing people did.
It took me several years before I officially created my freelance consultancy, L’Attitude Studios and actually looked to bring in clients.
Despite the fact that WordPress is the most popular blogging platform in Jamaica, and is used by many web developers to built CMS-based websites, there is not much of a WordPress community. And despite my reading all about WordCamps and community meetups, I didn’t really think of myself as part of an actual community. WordCamps started back in 2006 and there have been hundreds since, but I only went to my first WordCamp in 2016, in Miami.Finding a Place
The organizers of WordCamp Miami made me feel so welcome. They were excited to have me come from Jamaica “just” to attend their event. For the first time, I understood that I have a place in the community, not just as a user. I signed up with the WordPress Community team as an organizer of the WordPress Kingston meetups. Full of enthusiasm I came home, ran a survey to find out how people were using WordPress and declared I was starting local meetups. The sound of crickets followed as the interest was low.
I started a new job and didn’t have time to focus on WordPress, so the meetups fell by the wayside. But I still wanted to contribute. So In 2017, I made the leap to speaking. I decided that there were things I could offer the WordPress community based on my own experiences. WordCamp Ottawa became the first WordCamp I spoke at.
Again, the WordCamp organizers (one of which I had met at WordCamp Miami) were thrilled to have me travel from Jamaica to participate. Funnily, I had to point out to several people that it took less time to get from Jamaica to Ottawa than it did for those traveling from San Francisco.
Everyone I met at WordCamp Ottawa made me feel like a part of the WordPress family, like I belonged.
I still hadn’t got my local meetups going, but I had started making connections in the WordPress space locally. And there seemed to be more interest. I proposed a series of workshops to the organizer of Caribbean Bloggers’ Week. It wouldn’t quite be a WordCamp, which we wouldn’t get permission for, but we could try to do an educational community event to spur interest and raise awareness. WP in the City was born! Sadly, it had to be postponed, but it will still take shape for 2018.WordCamp US
Now bitten by the bug, I set my speaking sights even higher and made a submission to WordCamp US. A month later, I was notified that one of my two proposals was accepted. I was to be a WordCamp US speaker! Now an even bigger part of the WordPress community would be open to me. I set about making plans for Nashville in December.
By the time you read this, I will be able to announce that I was selected as the recipient of the Kim Parsell Memorial Scholarship. When they notified me, I didn’t even remember I had applied. Kim Parsell was an active member of the WordPress community until her passing in 2015. She was nicknamed “WPMom” because of the care she took in making sure any member of the WordPress community she met felt welcomed and valued.
Kim was already gone before I actively started taking part in the wider WordPress community. But the community I encountered definitely made me feel welcomed and valued, and now I want to help others feel that way. Going to WordCamp US is going to be an amazing opportunity, in part because of the size and breadth of the community I will get to interact with.Bringing it Home
Jamaica is a small country, an island in the middle of the Caribbean sea. Most people know about our biggest stars (like Bob Marley and Usain Bolt), our culture (reggae music and jerk cooking) or our beaches. The people who go usually remember the people. Our community is what makes us a powerhouse. And I want to tap into that for WordPress.
I want to bring Jamaica into the WordPress community, and bring the WordPress community to Jamaica. I want to get more Jamaicans to WordCamps and actively participating in the WordPress community in other ways (through contributing and meetups).
I want to bring more WordPressers to Jamaica to share and exchange knowledge, not just enjoy the beach.
When I started out, WordPress was just a tool to get me to my goal. For a long time, I didn’t think much about the people behind WordPress, much less considering getting involved myself. Despite my own technical background, I am a newbie where it comes to WordPress development, having remained a tinkerer for much of the last decade. But WordPress is so much more than just code.
Through WordPress, I have been able to express myself through blogging and poetry. I have been able to help others achieve their own success. I have found people willing to share their knowledge for others (like me) to learn. I have found people willing to hear about my WordPress experiences. I have built a network of contacts always willing to help out.
Reading through the other essays on HeroPress, it is also clear that WordPress has changed lives. It has given people a voice. It has brought people together.
WordPress is community. WordPress is my community.
Out-of-the-box, WordPress provides the ability to blacklist comments or configure a set of options to send comments to moderation. If all comments are moderated, there are no options to whitelist comments.
Searching the plugin directory for comment whitelisting provides few, if any, solutions. However, a cursory search of Google led me to the Comment Whitelist plugin by Alejandro Carravedo.Comment Whitelist Box
Comment Whitelist adds a ‘Put in Whitelist’ quick moderation link to comments that makes adding email addresses to the list an easy task. One thing to keep in mind is that the whitelist uses email addresses and it’s possible comments from people impersonating whitelisted users may get published.
Despite not being updated in more than nine years, the plugin works as advertised. You’ll need to download the zip file and manually install it as you won’t be able to find it by searching the plugin directory from the WordPress backend.
The discussion surrounding the use of iframes for meta boxes in Gutenberg became more heated over the weekend, as concerned developers implored the team to consider the detriments of the current approach. Responses from Gutenberg’s leadership initially deflected concerns, presenting the iframe implementation as an experiment that “works ‘for now'” but isn’t what the team would ship.
Instead of getting a response to the specific concerns about performance and accessibility of the iframes approach, Kevin Hoffman was urged to think about the future of meta boxes and “the cases (if any) that would not be converted to blocks.” When the developer community is repeatedly asked to test and offer feedback but is met with deflection on issues that are critical to sites using WordPress as a CMS, the GitHub discussions begin to get more heated.
“People are worried, and getting frustrated and it seems to me that they have every right to do so because the perception is that the team working on Gutenberg has little understanding of how meta boxes are being used, little concern for what the impact will be, and is going to move forward with their vision no matter what,” Jimmy Smutek, lead developer at the office of external affairs at Johns Hopkins, said in response to a Gutenberg collaborators’ admission to having been dismissive of feedback.
After several rounds of developers joining the thread to debunk the notion that iframes for meta boxes “work for now,” Gutenberg lead developer Matias Ventura joined the discussion yesterday and confirmed that the experiment is likely to be dropped fairly soon.
“I’m glad the conversation refocused in the end to the topic’s issue: is the current approach to meta-boxes in an iframe viable? With the answer being no,” Ventura said. “The iframes are an implementation detail I think we can drop relatively easy. So let’s focus on that.”
He also addressed the popular opinion that WordPress should make iterative enhancements to the editor itself (and not the full page) before proceeding with overhauling meta boxes.
“What some people have called as the pragmatic approach is not concomitant with the design direction this project has had from the start — heading towards full site customization — and what has dictated our decisions so far,” Ventura said. “Nothing here has to be a final solution, we are exploring what is possible within the design premises and putting it out there for testing.”
Ventura said that not making changes to the other aspects of the edit screen would certainly be the simplest path for Gutenberg to take but that it “would not be fair to the goals of the project and the long term users of WordPress.”
WordPress developer Gary Jones contended that pursuing a more iterative approach would not change the goals of the project but would make it possible for more sites to come along during the process.
“Going one step at a time does not, in any way, compromise the goals of the project,” Jones said. “You can still head to full-size customization if that’s the goal, but by doing it in a stepped way, you’ll bring the rest of the developer community along with you.” Jones cited the Customizer as an example of a feature within WordPress with a concept that is being realized over time with many iterations.
Ventura responded with clarification on the Gutenberg team’s approach to iterating on the project, a paradigm shift that supports block-based content creation from the outset.
“We have proposed a staged approach, from Matt’s original new focuses post, it just considers the steps differently,” Ventura said. “There are generally three stages for the Gutenberg project: from the post editor, to page templates, to site building. What is primordial is that the paradigm is one where the content is a single area, with the block as the primary concept, and where the outcome can be visually represented with clarity and without excessive abstractions.”
Ventura also assured those following along on the discussion that the project will not be dropping support for meta boxes but needs more time to experiment with different interface options.
“WordPress always moves with the user, and we take the burden of figuring out development paths to ease transitions for our existing code,” he said. “As a project, we have said before that we were not dropping support for meta-boxes from WordPress, but also that we had to explore what interface decisions we would have to make within the new paradigm, including the possibility of loading the classic editor when we detect meta-boxes we cannot handle or that directly conflict with an editor that seeks to more clearly delineate what is content and what is meta-data.”
He also said the team plans to create more mechanisms to handle incompatibilities as well as “allowing more things to be opt-in (say if you are comfortable with your meta-boxes showing in Gutenberg you could declare support for it, or vice versa.”
A new approach to rendering meta boxes without using iframes is currently underway. Riad Benguella has created a pull request that attempts to undo the iframes and implement a suggestion that Tom Nowell offered during the discussion:
Instead of loading Gutenberg on a settings page, lets load it into the main classic editors page, load metaboxes in their native environment, then hoist their container DOM node into a component via JS.
We then use a different kind of toggle to make sure the classic editor can still be used. This way:
– we avoid the iframe nonsense
– metaboxes work as they always have done as far as registration is concerned
– the existing JS works as expected, and no hacks are necessary to make things work on the PHP end
The new approach has the advantage of no problems with links, modals, duplicate stylesheets, and the other drawbacks to using iframes.The Gutenberg Team Needs a New Communication Strategy
The discussion regarding the long-term viability of using iframes for meta boxes has highlighted a lack of a unified message or communication strategy among Gutenberg leads. Collaborators on the project have grown impatient with the community for not grasping the vision, but communication is scattered across various blogs, comments, Slack channels, and GitHub discussions.
Morten Rand-Hendriksen has opened a new issue requesting a centralized resource that can serve as a plain language outline of Gutenberg’s scope, direction, and goals.
“My observation is the community is struggling to see the wider scope of the Gutenberg project due to lack of a single authoritative plain language resource containing this information,” Rand-Hendriksen said. “This creates a high degree of speculation, miscommunication, and frustration from all parties and the project suffers as a consequence.”
Gutenberg does have a documentation hub, but so far those documents are more technical and lack a practical roadmap for how the team is aiming to accomplish its goals. The FAQ section of the current docs is the closest thing to the plain language resource that Rand-Hendriksen is requesting in his ticket. The readme.txt files for both Gutenberg’s GitHub repository and the WordPress.org plugin give the impression that the project is simply updating the current editor to be block-based, not overhauling the entire editor screen.
“Due to the fractured nature of this information it is challenging for anyone to get a clear picture of the entire project, and though Matias and Matt’s posts do a good job at explaining the grand vision of the project, they lack concrete plain language breakdowns of the essentials the community need to get a firm understanding of what this project is and where it’s headed,” Rand-Hendriksen said. “They also exist as independent satellites of information circling the project rather than core parts of the project itself.”
The community is chiming in on the GitHub issue with questions they would like to see answered in a more transparent plain language product roadmap. A document like this might help the Gutenberg team to better communicate the goals of the project and avoid sending mixed messages that cause unnecessary confusion.