The new WordPress Executive Director recently just resigned from her post as the Head of TikTok Americas, Governance and Experience. She worked as the Head from January 2023 until her subsequent resignation to take up her new post. But this is not Hubbard’s first time working at WordPress. She worked as the Chief Product Officer for WordPress.com from January 2012 till March 2023.

Mary Hubbard has an extensive working history as presented on her LinkedIn profile. She worked as the Chief Product Officer at TruRating from 2017 till 2020. The WordPress Executive Director also has worked at companies such as eBay, Walmart eCommerce, Assurant, and VBZ Inc. Her educational background includes International Business and Chinese at California State University and Language Business Studies and International Business at Hong Kong Baptist University.

Mary Hubbard: Reception of the news of her appointment as Executive Director

The overall reception to Mary Hubbard’s appointment as WordPress Executive Director has been met with positivity welcoming her on board. However, there are still tons of comments from the online community expressing their disappointment or concerns over the entire WordPress-WP Engine drama.

The feud between the two companies snowballed into a legal lawsuit filed by WP Engine accusing WordPress of extortion. Mullenweg has offered up a generous severance package for employees who want to resign. Employees who wanted to leave were offered $30,000 or six months of pay. Employees could choose whichever amount was higher.

Josepha Haden Chomphosy resigned from her position as Executive Director of WordPress very recently but there are no details about the reasons for her resignation.

Suggested:

WordPress Executive Director Formally Resigns

WordPress.org Blocks WP Engine

Image Credits: Photo by Erik Mclean on Unplash

The post Mary Hubbard is WordPress New Executive Director appeared first on Tricky Enough.

Chomphosy uploaded a notice on her blog, officially announcing her resignation as the WordPress Executive Director. Her blog expresses her strong belief in the ‘global community of contributors’. She also believes there is a long way to go in attaining a self-sustaining future of open source. The former Executive Director has also acknowledged the need for more opportunities that open sources can provide.

Co-founder of WordPress and CEO of Automattic, Matt Mullenweg confirmed Chomphosy’s resignation on October 2. Mullenweg had posted on X that he had spoken to Chomphosy and confirmed she was no longer working with the company. However, the post was later deleted as Chomphosy posted her response the very next day. In her post, she apologised for the delivery of the news and said that it was not how she expected it to be announced.

WordPress’ Executive Director resigned during the feud

The former WordPress Executive Director announced her resignation at the peak of the WordPress-WP Engine drama. This entire feud by started by Matt Mullenweg and later snowballed into an entire lawsuit by WP Engine accusing the Automattic CEO of extortion and libel.

It is up in the air regarding the reasons behind Chomphosy’s resignation. Although her resignation came in during the whole feud between the two companies, there is no confirmation that she resigned because of the feud. In her resignation announcement, Chomphosy did not make any mention of the fiasco either.

Mullenweg has also uploaded a blog post with an exit offer for Automattic employees who did not agree with Mullenweg. Over 8% of employees had exited and they were compensated with a severance package of $30,000 or six months of salary.

Suggested:

WordPress.org Blocks WP Engine

Matt Mullenweg Critizes WP Engine at WordCamp US 2024

Image Credit: Photo on pixabay.com

The post WordPress Executive Director Formally Resigns appeared first on Tricky Enough.

The Automattic CEO started this public battle with WP Engine as he believed WP Engine was violating the WordPress trademarks. Mullenweg even went so far as to call WP Engine a ‘cancer’ to WordPress. Shortly after, more fuel was added to the fire when WordPress announced that it was blocking WP Engine. The hosting provider was thus banned from using its free resources such as plugins and themes. This resulted in a huge backlash from WP Engine customers. These users were left vulnerable due to the discontinuation of crucial security updates from WordPress. The ban was later lifted temporarily until the 1st of October. Automattic also asked WP Engine to pay them 8% of their gross monthly revenue if they want to continue using the WooCommerce and WordPress trademarks. However, WordPress has not accepted these terms by Automattic.

WP Engine had even sent WordPress a cease-and-desist letter demanding that Mullenweg retract his statements about WP Engine. However, Automattic responded with their cease-and-desist letter where they accused WP Engine of infringing on the WooCommerce and WordPress trademarks.

WP Engine Sues Matt Mullenweg: More on this issue

WP Engine has accused Mullenweg of allegedly extorting money from them. As WP Engine sues Matt Mullenweg, the hosting provider also accused the Automattic CEO of abusing his power and being greedy.

The hosting provider is seeking to stop Mullenweg and Automattic from continuing on this tirade against WP Engine and the WordPress community as a whole. The lawsuit has also accused Mullenweg of having an alleged history of blurring the real facts.

Suggested:

Matt Mullenweg Critizes WP Engine at WordCamp US 2024

WordPress Lifts Ban On WP Engine Temporarily

The post WP Engine Sues Matt Mullenweg and Automattic appeared first on Tricky Enough.

LiteSpeed, also termed as LSCache is a WordPress website builder. It ensures fast and quick page load time and an overall enhanced user experience. Additionally, this plugin also makes improvements to the positions of Google Search Results. This plugin also supports bbPress, WooCommerce, and Yoast SEO among others. It is an extremely flexible and powerful cache solution benefiting both large and small websites.

Patchstack researchers have stated that LiteSpeedCache publically exposed the debug.log file. The bug carried a 7.5 severity score. Version 6.4.1 and the previous versions have been considered vulnerable to attacks.

LiteSpeed Cache Plugin: Steps to take against this vulnerability

It has been reported that the critical vulnerability comes from a debug log being exposed in public. This file is called /wp-content/debug.log and the public exposure of this file could let unauthenticated attackers access important information within the file.

Steps should be taken to proactively purge the vulnerabilities. Users have been advised to keep their plugins updated to the newest versions to minimize the risks of attacks. Users are asked to update LiteSpeed Cache to the latest Version 6.5.0.1. Cautions have been put out as the vulnerability, CVE-2024-44000 could lead to attackers taking hold of users’ accounts. The updated patch moves the log file to a different folder inside the LSCache folder. Furthermore, it also randomizes the name of the files.

To reduce the threat of attacks, users have also been asked to place a .htaccess rule denying direct access to log files. This method is helpful as the unauthorized actors can still access the log files by simply knowing the file name.

Suggested:

WordPress 6.6.1: New Maintenance Release for WordPress 6.6.

WordPress Tracks Down XSS Vulnerability- Users To Update To 6.5.2.

The post LiteSpeed Cache Plugin Has A Critical Security Vulnerability appeared first on Tricky Enough.