-
-
Notifications
You must be signed in to change notification settings - Fork 348
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Blog posts aren't updating #30
Comments
The same thing happens to me. when I am in developer mode the posts update without problems but in build mode when I make a post it only updates in the carousel () but not in the body . The only way these changes show is if I make push the changes to github, and redeploy to vercel. |
Try to use
|
with revalidate, now it's working perfectly. Thank you so much!!
…________________________________
From: Juan Jiménez ***@***.***>
Sent: Friday, June 17, 2022 5:15 AM
To: adrianhajdin/project_graphql_blog ***@***.***>
Cc: manuetov ***@***.***>; Comment ***@***.***>
Subject: Re: [adrianhajdin/project_graphql_blog] Blog posts aren't updating (Issue #30)
Try to use revalidate property<https://nextjs.org/docs/basic-features/data-fetching/incremental-static-regeneration> in the index.jsx.
export async function getStaticProps() {
const posts = (await getPosts()) || [];
return {
props: { posts },
revalidate: 10
};
}
—
Reply to this email directly, view it on GitHub<#30 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ARPC62MLXEPGGWUBQMEIYJDVPPUUZANCNFSM5V7ODU5Q>.
You are receiving this because you commented.Message ID: ***@***.***>
|
I seem to have everything set up correctly, no error messages etc, and it really is a great Blog app.
One issue that I notice is that once I publish a post in GraphCMS, I don't seem to be able to update it - it just stays as it was on the first publish.
Say I want to go back to the post content and correct a spelling, add to it, or change it in any way, the latest changes never show up on the live site, despite Graph CMS saying that the updates have been saved and published.
The only way these changes show on the live site, is if I make a change to the files in VS Code, and then push the changes to github, and redeploy to Vercel
The text was updated successfully, but these errors were encountered: