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.

The ban on WP Engine prevented its customers from using WordPress’ free resources such as themes and plug-ins. The prevention of updates left the sites vulnerable and put them at security risk. This move by WordPress was met with criticism in online spaces. WP Engine customers also took to social media to share security concerns brought by the ban.

Matt Mullenweg has made a few statements following the backlash. Mullenweg criticised Silver Lake for this feud. For context, Silver Lake is the private equity firm that owns WP Engine. In an official blog post, Mullenweg acknowledges the frustration coming from WP Engine customers. He also says that Silver Laks’s commercial decisions affected WordPress negatively.

WordPress Lifts Ban on WP Engine: More on this feud

This feud started when Mullenweg made a few comments criticising WP Engine at the WordCamp event. He then posted two more blog posts criticizing WP Engine further, one of which announced the ban on WP Engine. In the first blog post, Mullenweg called WP Engine a ‘cancer’ to WordPress. WP Engine has been allegedly lacking in its contributions towards WordPress despite using its free resources. Furthermore, WP Engine has also been accused of profiting off of the WP Engine and WordPress confusion, which has been emphasized over and over by Mullenweg. In fact, Mullenweg has reiterated a few times that ‘WP Engine is not WordPress’.

After the scathing comments and subsequent ban by WordPress, WP Engine sent Automattic a cease-and-desist letter. The hosting provider demanded for Mullenweg to retract his previous statements. In a turn of events, Automattic sent over their cease-and-desist letter to WP Engine and accused them of infringing on WordPress’ trademark.

Suggested:

Matt Mullenweg Critizes WP Engine at WordCamp US 2024

WordPress.org Blocks WP Engine

The post WordPress Lifts Ban On WP Engine Temporarily appeared first on Tricky Enough.

In a blog post, Matt Mullenweg, co-founder of WordPress and CEO of Automattic has alleged that WP Engine aims to control the WordPress experience. Sites from WordPress do not get hacked as often as they used to. This is due to WordPress working with hosts to stop ‘vulnerabilities at the network layer. Mullenweg continues by saying that the hosting provider will have to figure out a way to recreate WordPress’ security research by themselves. He also questions the logic of why WordPress has to give free services to WP Engine considering their attacks on WordPress.

The Automattic CEO says WP Engine can proceed with offering customers a bastardized version of WordPress’ GPL code. He ends the blog posts by emphasising that WP Engine is not WordPress.

As WordPress.org blocks WP Engine, loads of WP Engine users have taken to social media to voice their concerns. WP Engine customers have been left vulnerable due to the absence of security updates. The hosting provider has acknowledged this issue and ensured its customers that there is currently no impact regarding security, performance and other concerns. WP Engine has responded to Mullenweg’s claims stating that the Automaacttic CEO interfered with operations within WP Engine.

WordPress.org Blocks WP Engine: Background on this feud

Earlier this week, Mullenweg criticised WP Engine at the WordCamp US 2024 event. After his comments at the event, he later went on to publish a blog post with even more scathing comments. Mullenweg claimed that WP Engine profited off WordPress since 2010 and disabled most of the features that made WordPress what it is.

In his blog post, Mullenweg also called WP Engine a ‘cancer’ to WordPress. Mullenweg stated that WP Engine turned off the revision system. Furthermore, the hosting service has also been alleged to profit from the confusion that exists between WordPress and WP Engine. Mullegnweg has stressed over and over that WordPress is not affiliated with WP Engine by any means.

Suggested:

Matt Mullenweg Critizes WP Engine at WordCamp US 2024.

WordPress 6.7 Update: Final 2024 WordPress Update.

The post WordPress.org Blocks WP Engine appeared first on Tricky Enough.

WordPress co-founder, Matt Mullenweg criticised WP Engine at the WordCamp US 2024 event, and his comments against the competing firm have subsequently received backlash.

Mullenweg, also the CEO of Automattic, clarified his opinions about WP Engine. He claims WP Engine has profited off of WordPress since 2010. He has also maintained that key WordPress features have been disabled, features which drove WordPress to the top. Mullenweg made these critical statements during WordCamp US 2024 held in Portland, Oregon. This event is a conference set up by the WordPress community to get together and share ideas.

The WordPress co-founder has claimed that WP Engine has benefited from the confusion between the non-existent connection between WordPress and WP Engine. Many have assumed that WP Engine is under WordPress as the company makes it seem like they are offering customers a product of WordPress. Taking an example from his personal life, Mullenweg says his mother had confused WP Engine being an official WordPress service.

Matt Mullenweg and his recently published blog post

After the first day of the conference concluded, Matt Mullenweg wrote a blog post going on a detailed tirade about WP Engine. In this blog post, he also went on record calling WP Engine a ‘cancer’ to WordPress. He has also extended his criticism towards Silver Lake, the private equity firm that controls the WP engine. He took the comparison between WP Engine and Automattic, stating that the former contributed only 40 hours a week. Meanwhile, the smaller-sized Automattic contributed back 3,915 hours weekly. Furthermore, he alleges that WP Engine has turned off the revision system which helped in correcting mistakes. So whatever mistake a user makes cannot be rectified.

Matt Mullenweg has advised WP Engine customers to get at least 3 revisions to be turned on. This could protect the customer by preventing any loss of anything important.

Suggested:

WordPress 6.6.2 Maintenance Release Fixes 26 Bug Issues

WordPress Superhero Challenge Opened by Wordfence

The post Matt Mullenweg Critizes WP Engine at WordCamp US 2024 appeared first on Tricky Enough.

The maintenance release was led by members, Vicente Canales and Tonya Mork and mentorship from Aaron Jorbin. This new WordPress update fixes 15 issues in Core such as CSS specificity changes for specific themes. It was found that implementing CSS came with some problems that changed the look of a web page. 

CSS refers to the code that determines the look of a web page. It has to do with spaces, colours, sizes and the like. Adding on to this, CSS Specificity refers to rules from WordPress’ Core that decide the CSS properties to be applied particularly when there is a sense of vagueness or doubt on which properties should be applied. 

WordPress 6.6.2: More Fixes From This Maintenance Update

Some more fixes in Core include the Site Health Tool properly loading directory sizes. There was a bug which removed content from the templates when the templates were removed. The new WordPress 6.6.2 update has thus fixed this issue. Issues regarding text-wrapping issues from the About page have also been fixed in this release. 

Furthermore, this update fixes around 11 Block Editor issues, The Post Editor has been improved upon this the 6.6.2 update. Pseudo-element selectors have also been fixed in the custom block CSS. Duplication of template parts in non-block-themes has also been prevented. In the Data Views section, the action modal will not be rendered in the absence of eligible items. 

Suggested:

WordPress 6.7 Update: Final 2024 WordPress Update.

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

The post WordPress 6.6.2 Maintenance Release Fixes 26 Bug Issues 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.

Automattic has announced that Tumblr blogs will be moving all of its blogs to the WordPress backend. Tumblr will slowly be migrating over half a billion blogs over to WordPress which is a tricky and lengthy process but doable.

In an official blog post, Automattic has put out official statements clarifying Tumblr’s migration. Tumblr is stated to remain the same as it used to be. Users will not notice a difference on the outside. However, the backend operation will be transferred over to WordPress. There will be changes in terms of internal operations.

This transfer of Tumblr blogs to WordPress is expected to make it easier for blogs to be shared across platforms. Tumblr will be run on a solid infrastructure backed by WordPress and it will thus benefit from an open-source project such as WordPress. Furthermore, the blog post also stated that WordPress would also benefit from this transfer. WordPress will have the advantage of Tumblr’s tools and creativity that the teams invest in the site.

Tumblr Blogs After Automattic Acquisition in 2019

Automattic is the parent company of both Tumblr and WordPress. The company acquired Tumblr back in 2019 for only $3 million. This acquisition came six years after Yahoo acquired Tumblr for $1.1 billion which is a drastic amount compared to the $3 million that Automattic spent on buying Tumblr. However, Automattic’s CEO, Matt Mullenweg believed that Tumblr’s future still had promise. Since Automattic acquired Tumblr, the company has worked towards improving the blogging site and bringing Tumblr back to its glory days.

However, even with Mullenweg’s optimistic outlook, Tumblr kept losing money at a whopping $30 million yearly. Due to Tumblr’s losses, Mullenweg had to transfer most of Tumblr’s teams to Automattic in 2023. Additionally, Tumblr employees had also been laid off. Tumblr continues to generate revenue through ads, subscriptions and other digital services.

Suggested:

WordPress Superhero Challenge Opened by Wordfence.

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

The post Tumblr Blogs Are Moving To WordPress appeared first on Tricky Enough.

Automattic, WordPress’ parent company has stated that it would sponsor approximately five members from the Release Squad. This sponsorship excludes Matt Mullenweg who is the current CEO of Automattic. Hector Prieto, one of the beneficiaries has maintained that Release Squad is carefully working with the Release Coordination and Marcomms role combination. However, he states that this might be reversed depending on the feedback they receive.

WordPress 6.7: Default Theme Twenty Twenty-Five

WordPress 6.7 will have a default theme which will be called the Twenty Twenty-Five. The default theme has been developed with the principle that simple things are meant to be intuitive and complex things are meant to be possible. This principle came from Matt Mullenweg, who described the eleven principles for WordPress development.

Twenty Twenty-Five represents the optimum level of adaptability and flexibility. The new default aims to deliver different ways and means by which WordPress lets users write their stories by choosing between different design elements.

There are various kinds of patterns, styles and templates for users to choose from. The new update offers users fonts with multilingual support to appease a global user base. It also features a diverse set of colour palettes. The new default theme will also feature an array of templates for users. As with the previous update, WordPress 6.7 is compatible with Site Editor and utilises new design tools such as Pattern Styles and Grid Block.

Beatriz Fialho led the design team for the WordPress 6.7 update. Furthermore, Juanfra Aldasoro and Carolina Nymark led the WordPress 6.7 development team.

Suggested:

WordPress 6.6.1: New Maintenance Release for WordPress 6.6.

WordPress 6.6 ‘Dorsey’ Update and its Features

The post WordPress 6.7 Update: Final 2024 WordPress Update appeared first on Tricky Enough.