@MsDiamondPearl@jamesckemp@WooCommerce I see. Are you using any third party extension/plugin to customise those invoices?
In general we do not support third party extensions on Woo mobile. However, if the extension you are using is an official WooCommerce extension we can look into adding support for it.
@MsDiamondPearl@jamesckemp@WooCommerce@MsDiamondPearl On the issue with the zero orders stats, it's hard to tell what's going on without some more details. Would you mind reaching out to support directly from the Woo app "Menu/Settings/Help & Support/Contact support" so we can take a closer look at the issue?
@MsDiamondPearl@jamesckemp@WooCommerce Hi there @MsDiamondPearl, Jorge from woo mobile team.
I think you can do both, print receipts and manage stock directly from the app. Sharing a couple screen recordings that should help.
What other "maintenance" things would you like to handle from the app? Happy to help 🙂
Today’s the day!
State of the Word 2025, the biggest annual @WordPress event, is finally here. Let’s celebrate how far open source has come and where we’re going.
🔹Catch the livestream and keynote from @photomatt at 8 p.m. UTC (12 p.m. PT/3 p.m. ET).
🔹And if you’re in San Francisco, attend our IRL watch party at Tinker Tendo warehouse.
Livestream and watch party in 🧵💙.
TIL https://t.co/4tfyLZlXps provides a performance dashboard with slice and dice capability
E.g., you can sort big WordPress hosts by TTFB. Below are the fraction of sites that are "good" (I'd prefer to see the distribution, but this is easily available)
https://t.co/YkCbFbIyX4
Looking for WP Engine alternatives? 🧐
https://t.co/wpM7JXVOgq
WPBeginner explores top hosting providers with features & pricing options that might be a better fit for your needs.
Find your perfect #WordPress home!
There's been much discussion about @automattic and WP Engine in the @WordPress community over the past week. Protecting community-powered and beloved brands is hard, and I wanted to share some thoughts from my experience in this space. ✍ 🖖 🧠
https://t.co/IDN0JYNJUx
my one mid thought for the WordPress and WP Engine situation is this
with the disclaimer for Quinn Emanuel staff and others that I have no insider knowledge and DYOR
Here's my thought: @photomatt called WP Engine a "cancer" within the WordPress ecosystem
Matt does not pick his words lightly, so why would he use this word?
I think cancer in this context means something harmful that spreads and grows within an organization
Why might Matt have publicly called WP Engine a cancer now and chosen this nuclear option?
Why is that cancer growing, and why might it be important to nip WP Engine in the bud?
If your gut reaction is to say pressure from Automattic investors or to extort licensing fees or fear of competition...
I think I defer to Matt who has been deeply involved in the OSS movement for 20 years and is making overweight investments in the space, versus a PE firm pushing for IPO
Instead, here's what I think:
- WP Engine has done good in the past. For the WP community, for the Austin tech ecosystem, for their clients, employees, etc
- WP Engine is under new ownership of Silverlake who allegedly DGAF about open source. Their relative contributions speak for themselves
- WP Engine, under this new ownership, is allegedly actively prohibiting... well I won't make assumptions but I believe there's a lot we aren't hearing about what WP Engine is doing behind the scenes
We aren't hearing the full story because Matt and Automattic are not idiots and know this whole thing will go to trial and that the full story will come out in discovery
And so here's the larger scene that I see:
WP Engine is almost too big to fail but they are a net-negative actor in the WordPress environment
On the push to their IPO and before they go public I think Matt wanted to bring them back in check to be a more positive contributor to the ecosystem they have taken so much from
Remember the word cancer here--
A cancer is detrimental to the overall health or well-being of the system and tends to grow or spread if not addressed
WP Engine has had many chances to negotiate, discuss, contribute etc over the last 5+ years that have all happened behind the scenes out of the public eye
But they have allegedly just strung a8c along with empty chats and false hopes
So this is the nuclear option
This is the chemo to find a cure
disclosures: I've never contributed anything to the WP community myself besides using WordPress on my blogs. I'm a personal friend or acquaintance of Matt so I have extreme bias towards him, I've had dinner once with Jason Cohen - Founder of WP Engine, and I'm a current customer of WP Engine - tho I'm moving my sites off for a combination of reasons. I don't know what I'm talking about so I defer to others who contribute and have more input on the WP community
This is not how open-source works, it's how open-source dies.
Of course, there is no legal obligation to contribute, it's only necessary if one wants a project to thrive.
PE companies like that don't care. When the project dies, they'll move on to another one.
I think it’s very unfortunate that your leadership is putting your already obscene profits ahead of its customers and ahead of WordPress.
When you make the amount that WP Engine does off of WordPress it’s only fair that they pay back into Core.
It’s always better for an organization to do so through Five For The Future, to align your priorities and needs with WordPress. You’ve had multiple occasions to make that right. You refuse to do so. A licensing fee then to Automattic is absolutely fair, as they maintain and build the product on which you profit.
You expect Automattic to underwrite all development of the software your entire business is built upon. Incredible level of entitlement.
When you make 400 million while doing nothing to build or maintain WordPress Core you’re effectively stealing, not just from Automattic but all the smaller companies and organizations that do contribute.
All these people in the replies defending a giant private equity firm. Strip mining businesses and extracting every last ounce of profit they can from them is literally their business model. No good has ever come from PE firms buying a business - other than their investors making giant multiples. What WordPress is asking for is not that much. The fact that this PE backed company refuses to engage in good faith and even make a meaningful contributor to this community is pretty distasteful.
It helps that our sites don’t run on WP Engine but seems like Matt is on the right side of it, PR disasters notwithstanding.
@pootlepress@automattic@photomatt This was something I realized the more I contributed as well. The wider ecosystem provides a ton of visible value but Matt has been putting an insane amount of resources into keeping the lights on and the engine running.
Automattic is deeply committed to open source, and we will continue to safeguard its ideals and the community that supports it. We want to make this clear: Using "WP" is not a trademark issue.
Recently checked the @photomatt@automattic Responds to WP Engine’s Cease and Desist with Legal Action
I remember getting restrictions of using "Genesis" in domain from WPEngine for writing Genesis Tutorials and was asked to put two disclaimers, top and bottom.
They 100% are not obligated. But that is not the issue here. It's the mixture of trademark infringement and not contributing.
As I understand it, they have been profiteering off the misuse of the WordPress trademark, and they are the first (my guess of many) that are going to be held accountable.
If you call it WordPress Hosting, the market confusion is that its WordPress offering this. If you call it Hosting For WordPress (my prediction is everyone will have to switch to this) the same is not implied.
Automattic can call it WordPress hosting because they have the legal rights to the trademark and in exchange they pump tens of millions per year into the open source project.
So your options then are to license the trademark, and that money would go to the open source project, or stop calling it WordPress hosting. Seems simple and straightforward enough.
I wonder what WordPress would look like if @photomatt was not having Automattic fund 200,000 man-hours per year to the open source project.
I don't know the exact cost, but with salary and benefits, that would be $15m - $20m per year.
What does WordPress look like, long term, if that were to go away?