Troubleshooting
Modules don't fire
Open DevTools and check the Network tab for the orv-fx script. If it isn't loading, the most common causes are:
force_disablesetting is on (Settings -> Settings -> uncheck)- A caching plugin stripped the tag. Bust your cache
- Conditional load is on and your page contains no
data-orv-fxmarkup (this is working as designed)
Theme registers its own orv-fx handle
This is fine. Orravo FX deregisters the theme's copy at wp_enqueue_scripts priority 11 and registers its own. If you've registered a different handle name (my-fx, for example), there's no conflict.
Two animations stutter when used together
A module's requires array can resolve to false if a prerequisite is disabled. Check the Modules tab; modules with unmet requirements show a tooltip. Enable the prerequisite or disable the dependent module.
CSP errors in the console
Turn on csp_strict in Settings. The runtime stops emitting inline event handlers, which lets a strict CSP (script-src 'self', no unsafe-inline) pass.
Build artifacts missing after upgrade
If the plugin folder lost its assets/js/orv-fx*.js files (rare, usually a botched WP-CLI install), reinstall the plugin. The PHP side will register the handle but the script will 404 until the file is back.