Troubleshooting
Find solutions to common preview, image, styling and build issues, check the requirements for connected services, and learn what to include in a support request.
Styles or images are missing
Section titled “Styles or images are missing”Keep the full assets/ folder beside your HTML pages. Check filename spelling and letter case; hosting servers may treat uppercase and lowercase names differently. Use the browser’s Network panel to find missing files. If you replaced a photo, check its srcset candidates as well as src.
JavaScript does not work after double-clicking a page
Section titled “JavaScript does not work after double-clicking a page”Preview through a local HTTP server. Browsers can block JavaScript modules on file:// URLs. Source users can run npm run dev, or npm run build followed by npm run preview.
My changes disappeared or only affect one page
Section titled “My changes disappeared or only affect one page”Building from Source overwrites generated HTML changes in dist/. Keep permanent changes in Source when using that workflow. For shared header/footer changes, edit the shared source and rebuild. Direct HTML editing changes only the file you edited.
If a new Tailwind class has no effect, add its complete name to the source template and rebuild. Check whether custom.css overrides the rule, and refresh the browser cache after uploading changed files.
The development server or build fails
Section titled “The development server or build fails”Run commands inside Source/, using the Node.js version required by its package.json, and install with npm ci. Keep the supplied lockfile and install dependencies on your own computer rather than copying another machine’s node_modules/.
Check the terminal’s first error for a missing image, invalid JSON or an undefined template value. If port 5176 is busy, run npm run dev -- --port 5180 and open the address printed in the terminal. Stop preview before rebuilding if it is locking an output file on your system.
Forms, checkout or login do not submit real data
Section titled “Forms, checkout or login do not submit real data”These screens are interface examples. A “Preview only” message after submitting a form is expected until you connect a backend. Email delivery, payments, orders, accounts and comments need your own backend integration. See Deployment and Backend Services.
A map or video is blank
Section titled “A map or video is blank”Check your internet connection, provider access and browser content blockers. Map tiles and remote videos depend on external services.
Get help
Section titled “Get help”For product troubleshooting, open a support ticket. Include your template version, the affected page, the steps to reproduce the issue and any error message. Remove credentials and private customer data before sharing files or screenshots.
Get all RT-Themes designs, updates and support with a single Club license.
Join the Club