Compatibility
Herodotus uses WordPress post types, taxonomies, shortcodes and block rendering. Compatibility still depends on the actual theme, builder, caching setup and their versions.
Page Builders
Use a builder's dedicated shortcode element when available. Paste [herodotus] into a component that explicitly processes WordPress shortcodes. A raw HTML/code component does not necessarily execute shortcodes.
| Environment | Recommended insertion |
|---|---|
| WordPress block editor | Herodotus block for its native controls, or the standard Shortcode block |
| Classic Editor | Shortcode in content |
| Elementor | Shortcode widget |
| Divi, Beaver Builder, WPBakery, Oxygen or Bricks | Use that builder's shortcode-capable component and verify the frontend |
Caching Plugins and CDNs
The plugin query cache is separate from WP Super Cache, W3 Total Cache, LiteSpeed Cache, WP Rocket and CDN page caching. Cached HTML may keep yesterday's events or the same random result. Configure exclusions or a timed purge; see Caching.
SEO Plugins
The code detects Yoast SEO, Rank Math, All in One SEO and The SEO Framework and suppresses Herodotus SEO output to avoid duplication. Other SEO plugins, including SEOPress and Slim SEO, need a rendered-page check for duplicate tags.
Theme Compatibility
Shortcode output has dedicated CSS classes. Classic and block themes can affect its surrounding width and typography. Version 1.6.7 added block-theme header/footer handling for event category archives in Free and tag archives in Pro. See Developer Reference for supported template paths.
For a conflict test, use a staging copy with a standard WordPress theme. A successful test in one theme or builder is not a certification of every version or configuration.
WordPress Multisite
Events, categories and settings use site-specific WordPress storage. Validate activation, licensing, uploads and output for each intended site in your network before deploying broadly. This page does not claim a complete Multisite test matrix.
Requirements
The 1.6.8 packages declare WordPress 5.6+, PHP 7.4+ and Tested up to WordPress 7.1. These declarations do not replace testing your own environment. Active Pro requires active Free and a valid licence or trial.