When I post on the site, they are published directly. There is no problem with this. However, if I update a published post, that content title appears on the home page for a few minutes, but when I try to visit it, it gives a 404 error.
When we update only the content of the post we published, that post continues to appear on the homepage in Frontity, but when we click it, we encounter a 404 error. After a few minutes, the 404 error goes away, we can see the latest version of the post.
We do not change the slug, we only update in content.
Iām not sure but might it be related to the codesanbox instance? I mean, does the same happen if you use a local Frontity project (npx frontity create)?
Before deciding whether to migrate our project to Frontity, I wanted to install a demo and try it out. I havenāt created a project from scratch and examined it in detail yet.
Hovewer, after installing and trying it from scratch, I will inform you if I encounter this problem again.
Your new documentation prepared very well, congratulations and thank you.
I created the project just like on this page. All I did was use the command frontity create and then replace state.source.url with my site. Then I ran the server with the frontity dev command.
The site opened at localhost:3000 looks normal. But when I go into an article and refresh the page, I get a 404 error. If I donāt refresh the page, itās okay. However, when I want to go back and open the page again I get a 404 error. This problem happens only on my WordPress address. What could the problem be about and how can I solve it?
Iāve used the Frontity CodeSandbox boilerplate to create a Frontity project where i just have changed the state.source.api setting to point to https://koinbulteni.com/wp-json
I guess the error must come from the .html generated for each url.
Is this final .html added for a specific reason from your WordPress? You donāt really need that extension at the end of the URL and I think SEO would even be better without it
Thank you for your interest and detailed explanation.
We do not have a special reason to use the .html extension, but the link structure has been like this for 4 years. It would not be healthy to update the link structure as āpost nameā as stated in the document, because we have more than 20,000 articles. So the only thing we can do is remove the ā.htmlā at the end of the link.
But you will appreciate that making such a link structure change directly on an authoritative site like this can be risky for Google indexes.
Thereās been some more progress on the issue and the fix itās fairly straight. Would you be open to contribute with the fix yourself?
We would love and welcome any contribution! We have a fairly easy to start contribution guide. Thereās nothing else like fixing an issue on an open-source software.
Let me know if thereās more that I can do in here.
Have a great one!
I tried this in mars-theme index.js file. It didnāt work. I also tried in console but nothing changed. I can reach the same post multiple times with different browser tabs but when I press refresh button, it gives me 404 error.
Did you tried this action? Maybe Iām missing something.