Troubleshooting
Last updated
Was this helpful?
Last updated
Was this helpful?
In this guide we offer solutions to common issues detected in Frontity projects
@frontity/wp-source
If you launch your site locally with npx frontity dev
and you get this in the browser
And you get something like this error in the terminal when attempting to load the page in the browser:
It may be because your WP doesn't have permalinks activated (which is a requisite of the @frontity/wp-source
package)
From your WP, go to Settings -> Permalinks
and check one of the pretty permalinks options, rather than the plain one:
Related Threads:
If you get this error in the terminal when you do npx frontity serve
:
This may be caused because you're not executing this command from the root of your Frontity project (maybe you're launching it from the build
folder)
Run npx frontity serve
from the root of your Frontity project
Related Threads:
If you are getting these types of warnings in the console:
This is NOT an issue that should be ignored or "fixed" under normal circumstances. We recommend you use the following solutions only if you're getting these messages because of some third-party CSS that you don't have no control over (e.g. from a CSS framework or a component library or another external source).
components/index
You could also define functions to search and replace the selectors causing the warnings by the recommended ones
helpers/css
So then you can do in your code...
components/index
Related Threads:
This is caused by an issue:
As by Frontity our code should take into account what can and cannot be done using CSS in JS with emotion
For this specific issue, there's that seems to work pretty well to solve this issue in a Frontity project