I’ve find out the problem in the local installation, the plugin REST API - Head Tags, that had been suggested in another post, breaks the category view.
While on other online sites, I think that it’s or a CORS problem mutuated with a problem with the category base.
Why the CORS problem is happening, it’s intriguing.
Would be natural to me if CORS keeps happening at every interaction, but this happens only with a link following action. If I reload the page on a category url, all works fine and that’s really strange.
The category base problem instead happens even in the local installation, so if I change the category base from “category” to “cat”, frontity cannot retrieve the data.
Hi, this is the screen from a category view:
Same for the author archive page.
On the terminal I got this error:
Error: post type from endpoints “posts,pages,media” with slug “muoversi-a-napoli” not found
at Object.eval (webpack-internal:///./node_modules/@frontity/wp-source/src/libraries/handlers/postType.ts:8:21)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at eval (webpack-internal:///./node_modules/@frontity/wp-source/src/actions.ts:12:100)
The Search has a strange behavior.
If I search for something I gotta a blank page, maybe because of the CORS error (see screenshot below) but this happens even with a blank WordPress installation.
But the strange comes here, if I do a force reload to the page, results are shown but the CORS error is still here.