Deeproots Help Documentation Help Center

Compatibility

The WordPress and PHP environments the plugin supports, plus how it behaves alongside common plugins, themes, hosts and browsers.

Updated October 1, 2026

Supported WordPress and PHP environments

WordPress

Version
Practical minimum 5.8
Recommended 6.4 or newer

Below 5.8 the plugin may load but is untested, and some taxonomy and REST behaviour differs.

PHP

Version
Practical minimum 7.0 — whatever WordPress itself supports
Recommended 8.1 or newer

The plugin does not enforce a PHP floor of its own. The cart’s session handling branches on the version explicitly: on PHP 7.3 and above it uses the array form of session_set_cookie_params() to set SameSite=Lax; below that it falls back to appending the attribute to the cookie path, which works but is the less robust route.

So the plugin runs on older PHP, and there is no reason to stay there. Run 8.1 or newer.

Server requirements

Requirement Minimum Recommended
Outbound HTTPS to api-dispense.deeproots.io Required —
HTTPS on the site itself Required —
max_execution_time 60s 300s
memory_limit 128M 256M+
PHP sessions enabled Required in Full storefront mode —
WP-Cron, or a server cron Required for scheduled syncing Server cron every 5 minutes
MySQL / MariaDB 5.7 / 10.3 8.0 / 10.6

PHP extensions

Extension Why
curl or allow_url_fopen HTTP requests
json Everything
mbstring String handling
session The cart, in Full storefront mode

All are standard on any host running WordPress.

Hosting

Works well

Any host with normal WordPress support and unrestricted outbound HTTPS. In practice: Kinsta, WP Engine, SiteGround, Cloudways, Pressable, Flywheel, and most mainstream shared hosting.

Things to check with your host

Outbound requests. Some managed hosts block outbound HTTP or keep an allow-list. Ask them to allow api-dispense.deeproots.io.

Server-level caching. Managed hosts run their own caches above WordPress. They usually exclude admin-ajax.php and common checkout paths, but they will not know about /dispense-checkout/. Ask for it to be bypassed.

PHP sessions. A few hosts disable them, or clean them very aggressively. The plugin mirrors the cart handle into long-lived cookies precisely to survive that, but sessions must be available at all in Full storefront mode.

WP-Cron. Ask whether it is disabled in favour of a server cron. If it is, make sure the server cron runs often enough for your sync interval.

Execution limits. Some hosts cap PHP execution below 300 seconds regardless of set_time_limit().

On a large catalogue that means syncs are cut short — which is safe, since the next run continues, but worth knowing.

Known-awkward configurations

Configuration Consequence
Outbound firewall with no allow-list entry Nothing syncs; gateway_unreachable
Sessions disabled The cart cannot work; use Sync only mode
Aggressive mod_rewrite page caching Bypasses PHP, so session-based exclusions are ignored
A reverse proxy stripping cookies Carts empty between pages
A strict Content Security Policy Can block the checkout frame and AIQ Ecommerce-hosted images

Plugin compatibility

Caching plugins

All work with configuration. See Caching & Site Speed.

Plugin Notes
WP Rocket Exclude checkout and the cart cookies. Exclude AIQ Ecommerce JS from delay/defer.
W3 Total Cache Reject the cart cookies. Exclude AIQ Ecommerce JS from minification.
LiteSpeed Cache Exclude checkout and the cookies. Turn JS Defer off or exclude the AIQ Ecommerce scripts.
WP Super Cache Reject the cookies. Expert mode bypasses PHP, so avoid it.
Cloudflare Bypass checkout. Turn Rocket Loader off — it reliably breaks the cart.

Page builders

Builder Support
Elementor Pro Native dynamic tags. Loop Grid works over dispense_product. Pro required — the free version has no dynamic tags.
Bricks Native dynamic data provider. Query loops and taxonomy queries work.
Breakdance Three native groups, including offers, plus ACF fields. The fullest coverage.
Gutenberg Shortcode blocks and query loops work. No dedicated blocks.
Divi, Beaver Builder, others Shortcodes work. No native fields, but ACF and post-meta modules can read the field keys.

The shared limitation: no builder passes a term loop’s current term to custom dynamic fields.

So an all-offers listing built as a term loop has empty banners in every builder. Use [dispense_offers], which resolves server-side. Single offer pages are unaffected.

Filtering plugins

Plugin Support
FacetWP Direct support, including automatic facet pre-selection on brand and category archives.
Search & Filter Works against dispense_product and its taxonomies.
WP Grid Builder Works, configured against the post type and taxonomies.

SEO plugins

Yoast, Rank Math, SEOPress and All in One SEO all handle products as ordinary posts. Points to note:

  • The plugin outputs no product structured data. Add it in your SEO plugin if you want rich results, and be careful with price and availability, which change on every sync.
  • With Localized URLs, set canonicals if duplication across locations concerns you.
  • Mark the checkout and any thank-you page noindex.

ACF

ACF is supported and the plugin registers its own field groups. It is not required — everything is readable through get_post_meta() and get_term_meta().

WooCommerce

Fully independent. No conflict, and no requirement. You can run both, though you would be maintaining two catalogues.

Multilingual plugins

Plugin Notes
WPML, Polylang Your own page content translates normally. Product content does not persist, because it is overwritten on every sync — translate it in AIQ Ecommerce, or maintain your own separate fields.

Security plugins

Wordfence, Sucuri, iThemes Security and similar are all fine, with two things to watch:

  • Do not block admin-ajax.php for logged-out visitors — every cart operation uses it.
  • Do not block outbound requests to api-dispense.deeproots.io.

Optimisation plugins

Anything that delays, defers or combines JavaScript can break the cart. Exclude:

dispense-cart.js
dispense-product-filters.js
dispense-product-details.js

Theme compatibility

The plugin registers a post type, taxonomies and shortcodes; your theme handles layout. Almost anything works.

The one recurring issue

Sticky headers and the checkout frame. A position: fixed header takes up no layout space, so the checkout iframe cannot measure around it and the header may overlap the top of the frame.

Fixes, in order of preference:

  1. Use the default minimal shell, which has no header at all.
  2. Make the header non-sticky on the checkout page.
  3. Add top padding to the checkout page equal to the header’s height.

Block themes

Full site editing themes work. Use a Shortcode block, or build templates with query loops over dispense_product.

Browser support

Front end

Browser Support
Chrome, Edge Current and previous major versions
Firefox Current and previous
Safari 14+
iOS Safari 14+
Chrome for Android Current

The cart uses fetch, URLSearchParams and sessionStorage, all of which have been universal for years.

Browser settings that cause trouble

Setting Effect
Cookies blocked The cart cannot persist
Session storage blocked The purchase event cannot fire — the cart snapshot lives there
Third-party frames blocked The checkout may not load
Strict tracking prevention Can interfere with the checkout frame

These affect a small number of visitors who have deliberately configured them. Nothing on your side fixes it.

Admin

Any current browser. The settings screens use standard WordPress admin markup.

Diagnosing a compatibility problem

  1. Reproduce it on staging, never by deactivating plugins on a live site.
  2. Switch to a default theme — Twenty Twenty-Four. Still broken? Not the theme.
  3. Deactivate other plugins, then reactivate one at a time.
  4. Check the browser console for JavaScript errors.
  5. Check debug.log with WP_DEBUG_LOG on.
  6. Check Site Health — Tools → Site Health → Info for versions and limits.

Send the findings with your support request — see Getting Help.

Did this answer your question?