WPTavern: Members 2.0 Adds Capability Registration System, Introduces New Settings Screen for Add-Ons

Eight years ago, Justin Tadlock moved back home to Alabama and was living in the spare bedroom of his grandparents’ house with nothing more than a laptop and a suitcase. Over the course of a few months he started going deeper into learning about writing WordPress plugins and produced Members, a role management plugin for WordPress. The first major overhaul of the plugin came in 2015 with version 1.0’s expansion of features and a new UI for editing roles.

Members has built up a user base of more than 100,000 active installs since it first launched in 2009. Tadlock estimates that over the last couple years, 40% of Theme Hybrid customers are primarily there for support and small tweaks to the Members plugin. He decided it was time to begin investing more in the plugin and its community.

Tadlock released Members 2.0 this week. The plugin manages core WordPress capabilities but 2.0 adds the ability for plugins to register custom capabilities. The labels for the capabilities can be internationalized so users can manage the plugin in their own languages in human-readable form.

This release also adds the ability to use the WordPress editor for writing custom post error messages, making it easy to direct visitors to registration or other important information regarding access to the content.

Members 2.0 lets users add multiple roles when creating a new user from the Add User screen. It also introduces the ability to bulk add or remove roles from users, even when multiple roles have been enabled.

This version of the plugin serves some of its data using the WP REST API and a new setting was added to authenticate users who are accessing the REST API endpoints. This protects content from being exposed on sites that have the “private site” setting enabled. Tadlock plans to write a tutorial about what he has learned in integrating the REST API with the plugin.

Tadlock Aims to Monetize Members with Add-Ons, Renews Efforts to Develop a Community of Add-On Developers

Members 2.0 introduces a new Settings screen that ties in with Tadlock’s future plans to monetize the plugin. The new screen includes a view for add-ons. Tadlock has two add-ons available currently and has written an API for third-party developers to register their own add-ons to be visible on this screen.

“The plan is to create some small add-on plugins,” Tadlock said. “There’s already two: Members – Role Levels, which is paid, and Members – Role Hierarchy, which I was hired to build and was allowed to release to the community for free. I’ve got a few small plugins like those in mind that’ll be in a lower price range.”

Tadlock also plans to release a more robust version of the “Content Permissions” feature as another add-on. He has received numerous feature requests from users over the years about what they would like to see in this plugin. The add-on will offer a variety of different ways to show/hide content.

I asked Tadlock if he has considered building payment gateway add-ons so users can charge for memberships. He said the idea is on the table.

“I’m not sure if I’m going to build those or someone else,” Tadlock said. “I’ve mentioned it to some other developers. It would be a good place to start building add-ons.” His current setup uses Easy Digital Downloads with a couple of plugins to bridge it with Members and ThemeHybrid.com.

A plugin like Members has the potential to have a large, third-party ecosystem of plugins for payments and additional features, but Tadlock was focused on other projects during the first few years after it launched.

“I haven’t actively pursued the add-on angle,” Tadlock said. “Instead, I focused more on themes during most of that time. Now, I’m focusing more on plugin development. It’s my fault for not nurturing a community of add-on developers, which is something I’m trying to do more of now.”

Tadlock said many of the developers he knows are working with Members because they like that it gives them a solid foundation to build on for client work. He hopes to persuade some of them to release some of that code back as commercial add-ons or free plugins in the WordPress plugin directory.

Since launching the plugin eight years ago, Tadlock has aimed to make it behave as if it were a natural part of WordPress. At its core, Members is a role and capability management plugin and not a one-size-fits all membership plugin.

“It’s more or less a UI over what you could do with code already,” Tadlock said. “Most of all, it tries not to get in your way. Every membership site has its own unique needs. It’s tough building something that suits everyone. That’s why I’d rather have that foundation of Members just exposing the roles/caps system with third-party add-ons that suit various users’ needs.

“Other membership plugins often try to please everyone or pigeon-hole everything into their custom system. I like more to have a bit more flexibility without the bloat.”

Source: planet

WPTavern: WordPress 4.8.1 Adds a Dedicated Custom HTML Widget

When WordPress 4.8 was released last month, it introduced TinyMCE functionality to the Text widget. Unfortunately, this caused issues for those who use Custom HTML as the Visual editor often strips out portions of the code.

WordPress 4.8.1 Beta 1 is available for testing and addresses this problem by including a dedicated Custom HTML widget.

“For advanced users or any user who needs to paste in HTML snippets, there is now a dedicated ‘Custom HTML’ widget that is specifically for adding arbitrary HTML to your sidebar,” Weston Ruter, said.

“This widget will retain the application of the widget_text filters, in addition to having a new dedicated widget_custom_html_content filter.

“For use cases that involve adding content to your sidebar, the Text widget will continue to feature the same Visual editing interface that the post editor has (TinyMCE).”

Users who access Text widgets that have Custom HTML in WordPress 4.8.1, will see a note at the top of the widget that suggests using the Custom HTML widget.

If a user pastes or types HTML into a text widget with the Visual editor active, WordPress displays an Admin Pointer suggesting that they use the Text tab instead or use the Custom HTML widget.

Text Widget Admin Pointer

The Custom HTML widget works similar to the Text widget in WordPress 4.7 and below.

Custom HTML Widget

Sites that have existing Text widgets containing custom HTML that may be modified by the Visual editor, are opened in a legacy mode.

Legacy mode retains the old Text widget interface, including the checkbox on whether or not to automatically add paragraphs. This change prevents the Visual editor from altering code.

Ruter says the ideal way to test these improvements is to install it on a staging site that has Text widgets containing HTML and are known to be problematic in WordPress 4.8. After upgrading, check to see if the widgets open in legacy mode.

WordPress 4.8.1 is scheduled to be released on August 1st. Please report any bugs or errors you encounter in as much detail as possible to the WordPress Alpha/Beta section of the support forums.

Source: planet

WPTavern: Petition to Re-License React has been Escalated to Facebook’s Engineering Directors

photo credit: manu schwendener

React users are petitioning Facebook to re-license React.js after the Apache Software Foundation announced its decision to ban Apache PMC members from using any technology licensed with Facebook’s BSD+Patents License. So far the GitHub issue has received 627 “thumbs up” emoji and 66 comments from concerned React users who are hoping for a change in licensing.

Many respondents on the thread said that ASF’s decision affects their organizations’ ability to continue using React in projects.

“Apache CouchDB and others will switch away from React if we have to,” CouchDB committer Robert Newson said. “We’d rather not, it’s a lot of work for no real gain, but we don’t have a choice. Changing license can be simple (RocksDB completed that change in a day).”

“My team, at LinkedIn, is also having legal troubles using React for our internal projects,” LinkedIn software Denis Ivanov said. “We would love to see a change on this front.”

Software developer Clark Evans commented on how React’s current licensing might affect medical research institutes, and suggested that Facebook consider an Apache 2.0 license because it includes equitable patent grants.

Since U.S. based universities rely upon patent licensing as part of their legislatively mandated technology transfer initiatives, they are growing far more cautious in their due diligence. For this reason, at some universities, software written with React may be shunned. Existing projects using React software may be asked to remove the React software software dependency. Please strongly consider this proposal, since our RexDB work is used at major universities, we do not wish to rework to use a React alternative.

Several participants in the discussion commented that they would like to use React but the licensing makes it impossible for their companies.

“Other large companies such as mine (Adobe) can’t use React, Pop, etc. for the very same reason,” Corey Lucier said. “We’d love to participate in the project, contribute to each, etc. but Facebook’s heavy-handed PATENTS clause is a showstopper.”

“Even mid-size companies like mine (ViaSat) are starting to disallow the use of Facebook’s ‘open-source’ projects for this reason,” software developer Aaron Yoshitake said. “We’d like to build React web and native apps, but it seems that any sensible legal department will recommend against agreeing to Facebook’s asymmetric patent grant.”

Internal Discussions Continue at Facebook, Re-Licensing Issue has been Escalated to Engineering Directors

Dan Abramov, co-author of Redux, Create React App, and React Hot Loader, shared with participants that Facebook is having internal discussions about the re-licensing issue but cautioned them to temper their optimism. He returned to throw some ice on the conversation, which has grown more heated over the past few days, when he said it could only remain an open discussion if everyone involved remains civil. Many participants are concerned about the future of the React-based software that they have already invested thousands of hours of work into.

“I understand that everyone is frustrated about this issue,” Abramov said. “Personally I am just as frustrated to spend time, energy, and emotional wellbeing on legal mumbo jumbo that is preventing people from using React. I would much prefer to spend this time on working together to make it better.

“But the reality of this situation is that the maintainers of React (people like me that you’re interacting on the issue tracker) are not the ones making these decisions. Each of us is doing what we can to show different perspectives on this issue to the people who can make those decisions, and we appreciate your feedback too. But we can only keep discussion open if everyone stays civil and respectful.”

Abramov also pointed out in a follow-up update that a bug tracker isn’t the best avenue for a legal discussion, especially since most participants are software developers and not lawyers. Many have mistaken the thread as a way to communicate with Facebook but there are just a handful of software developers who are representing the React community’s concerns.

“We have heard you very well, and we have passed on your concerns,” Abramov said. “But repeating the same points over and over in different threads does not help move this forward, and creates a lot of noise and stress for the maintainers who are already empathetic to your cause.”

Several participants expressed frustration that the React community cannot participate in the discussions more directly. However, as React is both an open source project and a product of Facebook, the company’s leadership has the last word on licensing issues.

“I understand that software developers like us are not the best people to discuss legal details,” software consultant Erik Doernenburg said. “However, wouldn’t the logical consequence be that the Facebook Legal team, who make such decisions, become active in this forum? Shouldn’t it be possible that all relevant details pertaining to a piece of open source software are discussed in the open? It is incredibly frustrating to have such an important aspect of open software discussed behind closed doors.”

It’s not known whether Facebook is considering another change to its Patents grant or a complete re-licensing. Participants in the discussion are also concerned about other Facebook open source projects like GraphQL, Relay, React Native, and Flow, which share the same BSD+Patents License and are widely used by the open source community.

Dan Abramov left an update today to let the community know that no resolution is available this week. However, the update seemed more positive than the first one, which discouraged participants from being optimistic about a change.

“I want to point out that there is a real momentum behind this discussion internally,” Abramov said. “There are going to be more meetings next week escalating this up to the engineering directors. As you imagine they are quite busy, so this is taking more time than we thought.

“Again, I can’t promise you any specific conclusion, and there is no clarity on where this will land. But please know there are people working on getting your voice heard.”

Source: planet

WPTavern: WPWeekly Episode 282 – Talking WooCommerce with Cody Landefeld

In this episode, John James Jacoby and I are joined by Cody Landefeld, Senior web strategist and founder of Mode Effect. Landefeld describes some of the challenges that shop owners face and provides insight into a couple of WooCommerce projects Mode Effect has recently built.

We discussed the future of WooCommerce and the odds of it turning into a SaaS product. Landefeld shares his thoughts on WooCommerce dropping its 50% renewal discount on subscriptions. Even though the discount is gone, he believes it’s still an affordable option for most users. To close out the show, Jacoby and I discuss the news of the week.

Stories Discussed:

AJ Morris Acquires iThemes Exchange
Jetpack Professional Plan Introduces Unlimited Access to 200+ Commercial Themes
bbPress 2.5.13 Readds Sanitization to Anonymous User Data
WP Rollback Adds Multisite Compatibility and Changelog Preview
Gutenberg 0.5.0 Adds New Verse Block for Poetry and a New Display for Recent Blocks

Picks of the Week:

Gutenberg Boilerplate For Third-Party Custom Blocks by Ahmad Awais. The boilerplate is a great way to learn the basics on creating custom blocks for Gutenberg. It comes with four example blocks.

  • A block with custom CSS for editor and front end
  • A block with ES6 or ESNext and a Webpack build process
  • A block with editable content
  • A block to click Tweet the contents of that block

Awais also shared his thoughts on the Gutenberg project.

Add Admin CSS – Using this plugin you’ll easily be able to define additional CSS (inline and/or files by URL) to be added to all administration pages. You can define CSS to appear inline in the admin head (within style tags), or reference CSS files to be linked.

WPWeekly Meta:

Next Episode: Wednesday, August 2nd 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 #282:

Source: planet

WPTavern: The State of JavaScript 2017 Survey is Now Open

The State of JavaScript 2017 Survey is now open to web professionals of all backgrounds. The intent of the survey is to provide an overview of the rapidly changing landscape of JavaScript frameworks and tools by gauging which technologies are growing in popularity and which ones people are liking and using less.

The survey, created by Sacha Greif and Michael Rambeau, should take approximately 10 minutes to complete. Topics include JavaScript frontend and backend tools and frameworks, state management solutions, testing tools, CSS, build tools, mobile and desktop technologies, package managers, text editors, salaries, and more.

Last year’s 89-question survey received more than 9,300 responses. Results showed that React ranked higher than other front-end frameworks in terms of developer satisfaction at 92%, followed closely by Vue.js at 89%.

It will be interesting to see if and how these results change with many open source project and companies growing wary of using React after the Apache Software Foundation’s recent decision to ban Apache PMC members from using any technology licensed with Facebook’s BSD+Patents License. A licensing issue that jeopardizes more companies’ ability to use Facebook’s popular open source technologies could precipitate a decline in React’s preeminence among frontend frameworks.

Sacha Greif reports that the survey has received more than 3,500 responses in less than 24 hours, a remarkable number compared to 9,300 over the course of three weeks last year. This response affirms the value that last year’s results provided to web professionals who are attempting to navigate the ever-expanding JavaScript ecosystem.

Source: planet

WPTavern: Gutenberg 0.5.0 Adds New Verse Block for Poetry and a New Display for Recent Blocks

Another round of Gutenberg updates was released today. Last weekend brought version 0.4.0, which didn’t have too many noteworthy visible changes on the frontend but introduced an API for handling pasted content. Gutenberg developers are aiming to have specific handling for converting pasted content from applications like Word, Markdown, and Google Docs to native WordPress blocks. Version 0.4.0 also added navigation between blocks using arrow keys and included a new approach for rendering embed frames.

Gutenberg 0.5.0 hit dashboards today. One major improvement to the writing flow is that the editor will now avoid showing block UI while the user is typing and/or starting a new paragraph in a text block. You can test this by typing and pressing enter twice to begin a new text block. No UI should be visible during this process. Small improvements like this one are gradually bringing a bit more zen to the editor, which is still full of confusing and surprising experiences.

Version 0.5.0 adds the ability to upload images via drag-and-drop onto image block placeholders. The example below shows one of my tests. While the image is uploading, it fades in and out. This experience is a bit disconcerting, especially if the upload never resolves. I’m not certain this UI provides the best communication for the status of the image upload.

This version also introduces a new Verse block, which is intended for poetry. It has a slight indent, as compared to a plain text block, but it doesn’t yet work well with copy and paste. Unless you are a poet composing in WordPress, it’s far more likely that you will be pasting in poetry content from somewhere else on the web. Other than the initial bugs, it’s a useful block for those who often post verse.

With the growing number of block types, it can be cumbersome to sort through all of them when adding a new block. Gutenberg 0.5.0 implements a new display for recent blocks. A maximum of eight are shown and the most recently used ones are displayed at the top. It does not yet persist between editor sessions, but Gutenberg contributors plan to add that in the future.

Other notable improvements in this release include the following:

Writing Long-Form Content with Gutenberg is Still a Frustrating Experience

Gutenberg in its current state is a long way away from being an editor that users would embrace for long-form writing. It still contains many unnerving bugs that steal user confidence. For example, when pasting in multiple paragraphs from a lorem ipsum generator, the editor gave me a white screen and I lost all of the content in my post. After a bit of testing I found that pasting in paragraphs one at a time worked.

This kind of frustrating and unexpected behavior has caused many testers to wonder why it isn’t being referred to as alpha software instead of beta. WordPress contributor Jon Brown summed up this common sentiment in a comment on the 0.4.0 release post.

“It’s getting better, but it honestly still feels more like a 0.0.4 alpha than a 0.4.0 beta,” Brown said. “I’ve tried writing long form content several times with each version since 0.1.0 and each time I’m quickly frustrated by the lack of flow between blocks. It’s more frustrating than TinyMCE.”

Gutenberg needs to make significant progress before it can be suitable for writing anything more than a few short paragraphs. It’s nearly impossible to get into the flow of creating long-form content with the prominence of the block UI. Right now, the editor just gets in the way. The current UI is skewed heavily towards frequent block creation. It is clutter-some and distracting for pure writing tasks. Following the evolution of the editor, with its fast-paced development cycle, is exhilarating after years of stagnation. But the project is sorely in need of a breakthrough where the Gutenberg UI finally gets out of the way of writing.

Source: planet

WPTavern: Jetpack Professional Plan Introduces Unlimited Access to 200+ Commercial Themes

Automattic has been teasing its plan to add commercial themes to Jetpack for several months after introducing theme installation for self-hosted users from WordPress.com. In March, the plugin opened up access to all of WordPress.com’s free themes via the Jetpack Manage interface. All signs pointed to Automattic developing the infrastructure to offer commercial themes via Jetpack upgrades. At that time, however, Jetpack team member Richard Muscat said that Automattic had “no immediate plans to sell themes at this time.”

Yesterday those subscribed to the Jetpack Announcements email were notified that commercial themes have landed in the Jetpack Professional plan, which is regularly priced at $24.92/month or $299/year. Customers will have unlimited access to more than 200 commercial themes that are already available on WordPress.com. Jetpack users on the free plan will see all the themes available in the WordPress.com theme browser with a prompt to upgrade for the ones that are commercial.

The announcement also noted that any themes users elect to use will be automatically backed up and regularly scanned for malware as part of the security services included in the package. For those who are running a multisite network, each site will need its own Jetpack Professional subscription to have access to the commercial themes.

For years the WordPress community has speculated about what Automattic’s long game was for Jetpack, and many believed it was only a matter of time before the plugin started offering commercial upgrades. It was introduced to the WordPress world in 2011 as a way to provide feature parity between WordPress.com and self-hosted sites. The first version included just eight modules, but fellow plugin developer and entrepreneurs in the community were immediately aware of its commercial potential.

In 2016, Automattic CEO Matt Mullenweg identified both Jetpack and WooCommerce as “multi-billion dollar opportunities” that could each individually be larger than WordPress.com. The plugin is now active on more than 3 million WordPress sites. Automattic’s aggressive commercialization of Jetpack in the past two years is the fulfillment of initial predictions about where the plugin was headed.

The new commercial themes offering significantly raises the value of the Jetpack Professional plan, which was previously targeted at business users who require unlimited storage, Google Analytics, and additional SEO features. With the addition of unlimited use of 200+ themes, Automattic has expanded the Professional plan to be more compelling for non-business users who are simply interested in gaining access to a collection of professionally-supported themes.

Source: planet

BuddyPress: BuddyPress 2.9.0 Release Candidate 1

Today sees BP 2.9.0 move to The final testing phase Release Candidate 1.

This is the last chance to test out this release and report back any issues found before final release in approximately two weeks time.

Any issues found can be reported to our trac ticket home , or raised on the support forum.

Amongst other improvements and fixes to look out for are:

  • Fixing display of older activity comments.
  • Correction of message when removing friends that are not friends.
  • Group invites – omit sending to previously invited members.
  • Profile image upload fix for IE Edge breaksIOS fix.
  • Correct issue with hidden group & CSS specificity.
  • URL compatibility for LightSpeed.
  • Fix inability resizing of member avatar for cyrillic character filenames.

For a full list of commits see 2.9 tickets A full changelog will be available when we release the final version.

You can download the plugin to test from the WP repo BP 2.9.0-RC1 or grab a copy from our SVN repo.

A reminder to all theme developers that there are changes to template markup that could effect layouts and ask that they check their themes carefully, the changes are listed below along with changelog links; again any issues or problems please report as soon as possible to the BP trac or slack channel.

Template changes

In this release there are a number of improvements to templates that add a level of improved a11y performance and markup changes for better semantics & Standards.

Theme authors may want to pay particular attention to changes to profile field visibility links and the profile field descriptions where significant markup changes are made that effect positioning of these elements – changesets for these are r11617 & r11618

Nouveau – new template pack

If you’re looking for Nouveau as we mentioned in the beta2 announcement we have delayed the release of this new template pack to ensure it receives as much code checking & refinement as possible and we’ll be looking to probably package this as it’s own release shortly after 2.9 is released.

We thank you in advance for all testing and reports and it need not be mentioned but please don’t run Beta or RC releases in a production environment only on test installs.

The BuddyPress team.

Source: planet

WPTavern: CoKinetic Systems Pursues $100 Million GPL License Violation Case Against Panasonic Avionics

photo credit: Paper Plane(license)

Open source software has made its way into nearly every industry, but a recent open source security and risk analysis shows widespread license compliance risks, with 75% of the audited applications including GPL license conflicts. Although most violations are unintentional, there are some cases where companies do not comply with the license in order to block competitors from developing similar software.

GPL enforcement doesn’t often lead to litigation. When it does, most other avenues of resolving the complaint have already been exhausted. A lawsuit in the air transport industry is currently bringing more attention to the gravity of not complying with open source software licensing requirements.

CoKinetic Systems, a developer and manufacturer of in-flight entertainment (IFE) software, has filed a case against Panasonic Avionics that includes allegations of a fairly egregious breach of the GPL. The complaint alleges that Panasonic Avionics has monopolized the Panasonic IFE Software and Media Services Market by deliberately refusing to distribute the source code for its open-source Linux-based operating system:

More specifically, Panasonic has built the Linux-Based Panasonic Core Software using the open-source Linux kernel, which is clearly governed by the GPL, together with Panasonic’s own modified Linux modules, which are likewise governed by the GPL.

Indeed, Panasonic has itself affirmatively identified its own modified modules as being subject to the GPL, because the original Linux modules were specifically designed to generate warning messages if other code is linked with or otherwise combined with the Linux modules that are not licensed under the GPL. To suppress these warnings, Panasonic willfully acted to insert code into its own modules to indicate that they were licensed under the GPL.

Panasonic has incorporated a massive amount of open source modules, programs, and libraries into the Linux-Based Panasonic Core Software, without distributing notices or source code to the Linux-Based Panasonic Core Software, or even to any part of it…By deliberately refusing to distribute the source code to the Linux-Based Panasonic Core Software in accordance with its GPL obligations, Panasonic intentionally deprives competitors in the market from having the ability to develop software that can access the basic features and capabilities of Panasonic IFE Hardware.

CoKinetic Systems contends that Panasonic’s refusal to distribute its source code voids its GPL license and “potentially exposes Panasonic to billions of dollars in statutory damages for hundreds of thousands of hardware installations that willfully infringe copyrights belonging to hundreds or even thousands of software developers that freely contributed source code to Linux.”

Furthermore, the complaint details how competitors have to rely on Panasonic’s APIs in order to offer software services to airlines using Panasonic’s IFE hardware, because they do not have access to the source code for the Linux-based core software. CoKinetic claims that Panasonic also deliberately blocks competitor products by its selective distribution of its APIs, resulting in stifled industry innovation and monopoly control over the Panasonic IFE Software and Media Services Market.

Perhaps the worst and most grave allegation in the complaint is that, in addition to locking up the source code and doling out access to the APIs, Panasonic also maliciously sabotaged its own APIs in order to give the appearance that it is the only reliable software service provider for its hardware, which CoKinetic claims is inferior and sold at monopolistic prices.

Panasonic also is able to use its control over the Linux-Based Panasonic Core Software in order to make ongoing, undisclosed, and often malicious modifications to its source code, deliberately “breaking” Panasonic’s own APIs in order to purposely and maliciously sabotage the performance of third-party software products that Panasonic deems a competitive threat — particularly CoKinetic software.

In the introduction to the case, CoKinetic cites a litany of anti-competitive conduct the company has engaged in over the past decade before detailing the current allegations. The case is not purely an open source license dispute, as the plaintiff also alleges that Panasonic abused regulatory processes, engaged in acts of corporate espionage, defamed CoKinetic, paid commercial bribes, and employed unlawful means to monopolize the Panasonic IFE Software and Media Services Market.

CoKinetic is seeking compensatory damages for Panasonic’s GPL ongoing GPL breaches. The specific amount would be determined at the trial but the company believes it to be in excess of $100 million. The company also wants the court to compel Panasonic to publicly disclose and distribute the source code.

This isn’t a case where distributing the source code is just a small sticking point or just a matter of principle. It has the potential to open up the IFE industry for faster progress and greater innovation. Many reading this article have undoubtedly used Panasonic’s IFE products when flying with the company’s customers, which include Emirates Airlines, Delta Air Lines, Virgin America, and United Airlines. With the source code available, airline customers could remove Panasonic’s software from their IFE hardware and replace it with their own software solutions.

The complaint, which was filed in the Southern District of New York in March, demands a jury trial. An initial pre-trial conference was held in May, but the case has been slow moving. The Court gave a deadline for the Defendant to file its motion to dismiss, but deadlines have since been extended. The Court also strongly recommended that the two parties retain a private mediator but it’s not clear how outside mediation could solve such a far-reaching matter that impacts so many vendors. Additional documents are due over the next few months, so it will be some time before there are updates on the progress of the case.

Source: planet

WPTavern: AJ Morris Acquires iThemes Exchange

In 2013, iThemes released Exchange, an e-commerce platform that aimed to make selling online as simple as possible. Today, the company announced that AJ Morris, Product Manager at Liquid Web, has taken over the project.

“When approached about taking over iThemes Exchange early this year, we wanted to be sure the project and our customers went into very competent hands, someone who will love and care for them as much as we do,” Cory Miller, founder of iThemes, said.

“Having spent four and a half years investing in the project and in you and your success, we did not take this lightly.

“After numerous conversations over the past several months, we believe the best home for Exchange is with ExchangeWP LLC led by AJ Morris.”

Everything iThemes Exchange related will transition to ExchangeWP.com. Toolkit, Plugin Suite, Exchange Pro Pack, and iThemes Exchange Add-on customers will be given accounts for free support and upgrades through August 2018 at ExchangeWP.com.

Beginning today, customers will no longer be able to purchase Exchange or its add-ons through iThemes as the company transfers licenses and products to ExchangeWP. However, iThemes will continue to provide customer support until the transition is completed, expected to happen in early August.

Morris says he’ll continue to focus on making e-commerce simple and will provide regular updates to customers to provide insight into what goes into transition a product from one company to another and where the product is heading.

“These days, it’s very easy to get WordPress up and running so you can start blogging,” Morris said. “But when you want to add e-commerce to the mix, it’s a bit different.”

“With big players like WooCommerce out there, it becomes too much too quickly for the average content producer to get their store up and running.

“Exchange is going to continue focusing on the independent publishers that want to keep the revenue they can, while providing a simplistic experience in an easy-to-use e-commerce plugin that will help get their stores online quickly.”

Allowing Morris to take over the project frees up resources for iThemes to focus on three of its flagship products; BackupBuddy, iThemes Security, and iThemes Sync. In addition to their core products, the company says it will soon release a new project.

“My job as CEO is to be a steward of the time and resources we have at iThemes in order to serve you best,” Miller said.

“We’ve realized for a while that it was past time for us to refocus our finite resources on the projects that have the most growth and potential for our company and you.

“That meant we either needed to find a new home for Exchange or sunset the project. I’m thankful we didn’t have to do the latter.”

Morris is a long-time member of the WordPress community and has spoken at several WordCamps. With Morris taking over the reigns, existing customers won’t have to worry about finding a replacement.

Source: planet