WoodMart triggers repeated external API/update checks on every backend save with

Hello WoodMart Support,

we are currently investigating a significant backend performance issue on a WooCommerce site using WoodMart.

The issue occurs when a persistent Redis Object Cache is enabled. With WoodMart active, saving or updating a page/product in the WordPress backend repeatedly triggers external API/update requests that would normally be cached via WordPress transients.

Examples of affected requests:

• api.wordpress.org – plugin/theme update checks
• updates.wpbakery.com
• rankmath.com
• download.vendidero.de
• service.borlabs.io
• WooCommerce-related update APIs

This noticeably increases the loading time after backend save operations.

Environment

• WordPress 7.0.4
• PHP 8.2
• WooCommerce
• WoodMart + WoodMart Core
• Hosting: Raidboxes
• Persistent Redis Object Cache via the Raidboxes/LiteSpeed Object Cache implementation

Tests already performed

Our hosting provider has verified that the persistent Object Cache itself works correctly across separate requests/processes.

Reproduction:

1. Disable all other plugins except WoodMart Core.
2. Enable the persistent Redis Object Cache.
3. Activate WoodMart.
4. Save/update a page in the WordPress backend.

The repeated update/API requests occur.

If I keep the same configuration and only switch the active theme from WoodMart to another theme like Twenty Twenty-Four, the repeated requests disappear.

WoodMart Core remains active in both tests.

This strongly indicates that the behaviour is triggered by the active WoodMart theme rather than Redis itself or another plugin.

Additional Object Cache debugging

Immediately before saving a page, the WordPress update transients are present and valid in Redis:

`
UPDATE_PLUGINS
Redis found: YES
last_checked: valid
Installed plugins: 37
Checked plugins: 37

UPDATE_THEMES
Redis found: YES
`

Immediately after the save operation, on the redirect back to the editor, they are no longer available:

`
UPDATE_PLUGINS
Redis found: NO
last_checked: 0
Checked plugins: 0

UPDATE_THEMES
Redis found: NO
`

The site-transient group is also not configured as ignored/non-persistent:

`
site-transient ignored: NO
Ignored groups:
`

As a consequence, WordPress executes its update checks again:

`
_maybe_update_plugins()
wp_update_plugins()

_maybe_update_themes()
wp_update_themes()
`

Third-party plugins attached to these update checks then perform their external API requests again.

What we would like you to investigate

Could you please check whether WoodMart performs any cache invalidation during save_post, post updates, admin saves, or related operations that may remove or invalidate WordPress’ update_plugins and update_themes site transients?

In particular, we are interested in WoodMart code involving mechanisms such as:

`
wp_cache_flush()
wp_cache_delete()
wp_cache_flush_group()
delete_site_transient()
wp_clean_plugins_cache()
wp_clean_themes_cache()
`

or any WoodMart-specific cache clearing mechanism that could indirectly invalidate these entries.

Sandbox available

We have a dedicated sandbox where the problem is reproducible. Credentials are attached.

Thank you for looking into this.

Best regards
Nico