Frequently asked questions
Does the plugin work offline?
Yes. The bundled catalog ships with the plugin. The library still loads even when the cloud API is unreachable - the cloud catalog just goes empty until the next successful fetch.
Can I import the same template twice?
No. Imports are idempotent on _orv_tpl_key post meta. Re-importing the same key reuses existing posts. If you want a clean slate, run Orv_Tpl_Importer::cleanup( $key ) first to trash everything imported under that key.
How do I migrate from the old demo seed?
The activation hook detects legacy options (orravo_demo_seed_v1, orravo_demo_seed, orravo_demo_installed) and stores the result in orv_tpl_legacy_seed_detected. The admin shows a one-time notice with the option name and timestamp. There is no automated migration - import the new template you want, then delete the old seed pages.
Where do remote images go?
Into the WP Media Library, side-loaded by Orv_Image_Sideloader. Failures are logged to the orv_tpl_sideload_reports option and surfaced as an admin notice you can dismiss.
Can I prevent the plugin from talking to the cloud?
Yes. POST to /orravo-templates/v1/cloud-optout (admin-only) and the plugin only returns bundled templates from that point on.
What is ORV_TPL_API_BASE_OVERRIDE for?
Set it in wp-config.php to point the plugin at a different catalog API - useful for staging, self-hosting, or running an internal mirror.