The readme gives two rules for sites that use a caching or minify plugin.

1. Do not combine or minify VisionScaper’s JavaScript. Exclude assets/js/*.js in this plugin from JavaScript combining and minification. They are ES modules, which break when merged into one file.
2. Do not page-cache the VisionScaper API. Exclude /wp-json/dreamscaper/* from page caching.

The app loads many small JavaScript module files and talks to the server through REST routes. Cached API replies can show the wrong person’s data or stale results. Merged modules stop loading.

1. Open your caching or optimization plugin’s settings.
2. Find the JavaScript or “minify/combine” exclusion list.
3. Add the path to this plugin’s scripts: /wp-content/plugins/<plugin-folder>/assets/js/. Use your real folder name.
4. Find the “never cache URLs” list.
5. Add /wp-json/dreamscaper/ (or the pattern /wp-json/dreamscaper/*).
6. Clear the cache.
7. Open your Designer and Hub pages in a private window and click each button.

• Library photos and materials are loaded from lists with a version number added to the address, so a replaced photo should not stay stale. Click Rebuild photo list if you copied files in by FTP.
• If you use a CDN, make sure it also passes /wp-json/dreamscaper/ through uncached.

• Test after every change to your optimization plugin.
• Exclude the plugin folder from “delay JavaScript” features too if the button stops responding. This is general advice; the readme only names combining and minifying.

• Button does nothing or the app is blank. A script is being combined, delayed or minified. Remove it from the optimizer.
• Someone sees old data. The API may be cached. Add the exclusion and clear everything.
• Console shows “unexpected token” or module errors. That points to minified modules.

• Add the shortcodes and create your pages
• System requirements
• WP-Cron, backups and updates