Jetpack breaks WooCommerce email preview

Resolved

(@nothin7)

Email preview (in WooCommerce > Settings > Emails) only works if I deactivate Jetpack. Otherwise I see…

There was an error rendering the email preview. This doesn't affect actual email delivery. Please contact the extension author for assistance.

…in the email preview window, and…

[16-Aug-2025 04:49:41 UTC] PHP Fatal error:  Uncaught Error: Object of class Sabberworm\CSS\Rule\Rule could not be converted to string in /wp-content/plugins/woocommerce/vendor/pelago/emogrifier/src/Css/StyleRule.php:57
Stack trace:
#0 /wp-content/plugins/woocommerce/vendor/pelago/emogrifier/src/Css/StyleRule.php(57): implode(' ', Array)
#1 /wp-content/plugins/woocommerce/vendor/pelago/emogrifier/src/CssInliner.php(588): Pelago\Emogrifier\Css\StyleRule->getDeclarationAsText()
#2 /wp-content/plugins/woocommerce/vendor/pelago/emogrifier/src/CssInliner.php(185): Pelago\Emogrifier\CssInliner->collateCssRules(Object(Pelago\Emogrifier\Css\CssDocument))
#3 /wp-content/plugins/woocommerce/includes/emails/class-wc-email.php(834): Pelago\Emogrifier\CssInliner->inlineCss('\n/*\n* Temporary...')
#4 /wp-content/plugins/woocommerce/src/Internal/Admin/EmailPreview/EmailPreview.php(316): WC_Email->style_inline('<!DOCTYPE html>...')
#5 /wp-content/plugins/woocommerce/src/Internal/Admin/EmailPreview/EmailPreview.php(246): Automattic\WooCommerce\Internal\Admin\EmailPreview\EmailPreview->render_preview_email()
#6 /wp-content/plugins/woocommerce/includes/admin/class-wc-admin.php(274): Automattic\WooCommerce\Internal\Admin\EmailPreview\EmailPreview->render()
#7 /wp-includes/class-wp-hook.php(324): WC_Admin->preview_emails('')
#8 /wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array)
#9 /wp-includes/plugin.php(517): WP_Hook->do_action(Array)
#10 /wp-admin/admin.php(176): do_action('admin_init')
#11 /wp-admin/index.php(10): require_once('/home/donttell/...')
#12 {main}
  thrown in /wp-content/plugins/woocommerce/vendor/pelago/emogrifier/src/Css/StyleRule.php on line 57

…in the WP_DEBUG log.

**Environment:**
- WooCommerce: 10.1.0
- Jetpack: 14.9.1 (modules enabled: Brute Force Protection, JSON API, and Secure Sign On)
- WordPress: 6.8.2
- PHP: 8.2.29

The page I need help with: [log in to see the link]

Viewing 15 replies - 1 through 15 (of 16 total)

1 2 →

Thread Starter Zade
(@nothin7)

2 months, 3 weeks ago

Same with Point-Of-Sale (POS) mode on a tablet using the Woo app. Unless I deactivate Jetpack, I see “Error trying to process payment. Try again.” when using Cash payment and tapping “Mark payment as complete”.

Plugin Support Alin (a11n)
(@alinclamba)

2 months, 3 weeks ago

Hi @nothin7,

This looks like a conflict between WooCommerce’s email preview and one of Jetpack’s modules. Can you try disabling Jetpack modules one by one (Protect, JSON API, Secure Sign On) to see which one triggers the error? That’ll help us narrow it down. The fastest way to disable Jetpack Modules is from here:

https://YOURWEBSITEUR/wp-admin/admin.php?page=jetpack_modules

For the POS issue: it’s likely Protect blocking the request. Please try turning off Brute Force Protection and check if payments go through. If that fixes it, you can re-enable Protect and add your IP to the allowlist. If it’s still not working, I’d recommend reaching out to the WooCommerce team for support WooCommerce.com > My Account > Support

Let me know if this helps.

Thread Starter Zade
(@nothin7)

2 months, 2 weeks ago

Without updating any plugins, I temporarily reactivated the Jetpack plugin, didn’t deactivate any modules, and the email preview now works. So it sounds like this was caused by Brute Force Protection, which should not be blocking internal Woo features like this.

The night before reporting this, I discovered my wp_actionscheduler_actions and wp_actionscheduler_logs had become severely bloated with thousands of Jetpack-initiated tasks (on a site with only 6 products, 14 pages, no posts, 58 images, 5 users, and 19 orders), slowing WP admin down to a halt. You should not be scheduling ANY tasks with only Protect, JSON API, and Secure Sign On enabled.

Maybe there’s a connection there (or lack thereof). In any case, there’s no excuse for Jetpack suddenly breaking the ability to process orders via Woo POS mode when customers are hoping for a smooth payment experience. This issue my client had was replicated on my own tablet 80 miles away using a different IP address.

I had been using Jetpack on 36 of my 100+ sites and this is yet another reminder of why Redditors recommend avoiding this plugin like the plague.

Plugin Support lastsplash (a11n)
(@lastsplash)

2 months, 2 weeks ago

Hi @nothin7 –

We’d like to look into this issue, but we need more information to do so.

Could you please post your site URL here so that we can have a look?

If you want it to remain private, you can also contact us via this contact form:

https://jetpack.com/contact-support/?rel=support&hpi=1

If you choose to reach out directly, please include a link to this thread. Once we have the URL where the issue was happening, we can take a look.

Thanks!

Thread Starter Zade
(@nothin7)

2 months, 1 week ago

Hey, these are back end issues, but you can see the front end at https://www.sapientstews.com

Plugin Support Alin (a11n)
(@alinclamba)

2 months, 1 week ago

Hi @nothin7,

Appreciate you sharing the site link — I realize the issue itself shows up in the backend, but having the URL does help us check your site’s setup and plugin versions on our side.

I also tried to reproduce the email preview error here with the latest Jetpack and WooCommerce (10.1.2), but I couldn’t trigger the fatal error you mentioned earlier. Looking at your site, I can see you’ve since updated to WooCommerce 10.1.2 as well, while at the time of your report you were on 10.1.0. That makes me wonder if this was tied to that earlier version.

Could you let us know if the problem still shows up now when Jetpack Protect is active? If it does, we’ll be glad to dig further; if not, it’s likely the WooCommerce update already resolved it.

On the POS side, if you reinstall Jetpack and Protect seems to block the “Mark payment as complete” action, the quickest fix is to allowlist the device’s IP under Jetpack → Settings → Security.

Thanks again for sticking with this — let us know how things look on your end now.
Thread Starter Zade
(@nothin7)

2 months ago
Hi @alinclamba,

I appreciate your efforts. As explained in my previous reply, this was not a persistent issue. Overactive security filter problems are not easy to replicate. I know that makes them hard to diagnose, but I would not consider this issue resolved until one of the following occurs:
1. The cause of the Sabberworm fatal error is discovered and patched.
2. Jetpack is updated to never interfere with email preview and especially POS.
3. Jetpack is updated so that if there is a suspected bad actor and functionality is limited, the email preview and POS display a message indicating what’s going on, so genuine admins know how to work around the temporary problem.
I realize the usual process is to replicate a problem before considering it a bug, but given how brute force protections work, this is the kind of issue that may require the help of AI and a master developer or security expert.
Plugin Support lastsplash (a11n)
(@lastsplash)

2 months ago

Hi @nothin7 –

Thanks for your response and feedback.

It looks like there was some confusion in our earlier response. Jetpack’s Brute Force Protection module shouldn’t affect email previews inside WooCommerce. Brute Force Protection only acts against login attempts. I think we can rule it out as a cause here. However, if you want to be absolutely sure, you can also turn it off entirely by going to “Jetpack → Settings → Security”.

In WooCommerce v10.1.2 there were some updates to the email preview functionality:

https://developer.woocommerce.com/2025/08/27/woocommerce-10-1-2-dot-release/

It sounds like the error was intermittent so it may be difficult to track down, but I’d recommend installing Jetpack again and trying the email preview functionality to see if you still have the issue. If you do, please share the debug log so we can take a look.

Thread Starter Zade
(@nothin7)

2 months ago

Interesting. So you think the JSON API or Secure Sign On module is the reason why email preview only worked if I disabled the Jetpack plugin?

Plugin Support Chatoxz (a11n)
(@chatoxz)

2 months ago

Hi there, Sebastian Carreras from Jetpack here,

We are unsure about the reason this is happening. It doesn’t look like it’s related to JSON API or Secure Sign On module, but to get a clearer picture, we’ll need you to share more details from the error logs if the issue comes up again after activating Jetpack.

If this happens again, I recommend writing to us privately and mentioning this thread, so we can involve our development team. You can do that using this form:

https://jetpack.com/contact-support/?rel=support&hpi=1

Warm regards.

Thread Starter Zade
(@nothin7)

1 month, 4 weeks ago

Hi Sebastian,

Good to know. So the development team doesn’t review these support threads? This is definitely the kind of thing that makes no sense to share with a non-developer.

What “more details from the error logs” do you need?
Plugin Support Alin (a11n)
(@alinclamba)

1 month, 4 weeks ago
Hi @nothin7,

I totally get why this feels like something a developer should look at directly. On our side, the forums are handled by the Jetpack Happiness team — and when we spot something that looks like a bug, we loop our developers in internally. They don’t usually watch the forum threads themselves.

That’s why we pointed you to the private support form:
https://jetpack.com/contact-support/?rel=support&hpi=1
It gives us a safe place to share the details our devs will actually need.

Since we already have your site URL (https://www.sapientstews.com), the two things that would help most now are:
- the full PHP error log around the time the preview fails,
- and the steps you were taking when it happened.
If you can send those over privately, we’ll make sure it gets in front of the right people.

I know intermittent issues like this can be a pain to catch, but the detail you’ve already shared makes a real difference.

Thank you!
Thread Starter Zade
(@nothin7)

1 month, 4 weeks ago

Okay, I created ticket #10227619 and linked back to this thread. I believe I already provided the full PHP error log and steps I was taking.

I’ve noticed in the past that tickets get marked resolved before the issue is resolved, simply because I submitted a private ticket. Can we consider this topic “resolved” only when it is actually resolved? I don’t want to mislead any other customers who encounter the same problem.

Plugin Support lastsplash (a11n)
(@lastsplash)

1 month, 4 weeks ago

Of course! We’ll keep this thread open while the email ticket is open.

Internal Reference: 10227619-zen

Thread Starter Zade
(@nothin7)

1 month, 3 weeks ago

Via email I was informed that this issue would not be investigated unless I’m able to replicate it with WooCommerce v10.1.2. Since I have no interest in risking problems by reactivating Jetpack, I suppose this will never be resolved. Ah well, at least I tried to let you know.

Viewing 15 replies - 1 through 15 (of 16 total)

1 2 →

You must be logged in to reply to this topic.