Troubleshooting
Fixes for the most common problems when installing, building and publishing a Wooprex product.
Install problems
"npm" or "node" is not recognized
Node.js isn't installed, or your terminal opened before it was. Install the LTS version from nodejs.org, then open a new terminal.
Errors about the Node.js version
Check your version with node -v and compare it with the product's Installation section. After you update Node.js, reinstall:
rm -rf node_modules npm install
On Windows, delete the node_modules folder by hand, then run npm install.
EACCES: permission denied, in the npm cache
Some files in your npm cache belong to another user, usually after running npm with sudo. On macOS or Linux, this command gives them back to you:
sudo chown -R $(whoami) ~/.npm
Warnings during install
Lines marked npm warn, such as deprecated packages, are usually safe to ignore. Only npm error stops the install.
Build and preview problems
Port already in use
Another program is using that port, often an old development server. Close it, or use the new address the tool suggests.
My changes don't appear
- Hard-refresh the browser with Ctrl+Shift+R, or Cmd+Shift+R on a Mac.
- On the HTML format, recompile the SCSS. The pages load the compiled CSS.
- On a live site, upload the new build and clear your host's or CDN's cache.
Problems on a live site
The page is blank, or styles are missing
Open the browser console (F12) and look for files that fail to load. This usually means the files are in the wrong folder, or the site is in a subfolder without the setting from Publishing in a subfolder.
A page shows 404 when reloaded
On Vue, the server needs the rewrite rule in Vue: make reloads work.
The contact form doesn't send
Forms have to be connected first. Read Forms need a back end.