Skip to content
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

Cache is not invalidated when programatically build pages and the data is changed #28281

Closed
vstoyanoff opened this issue Nov 25, 2020 · 1 comment · Fixed by #28590
Closed
Labels
type: bug An issue or pull request relating to a bug in Gatsby

Comments

@vstoyanoff
Copy link

vstoyanoff commented Nov 25, 2020

Description

I am using Netlify CMS with markdown files and generating pages from certain collections. When the data for an entry in the collection changes the page is not updated with new data after the build. The site is deployed in Netlify and a caching plugin is used to persist cache between builds for faster builds.

Steps to reproduce

Use Netlify CMS with markdown files and build pages in gatsby-node using a certain collection.

Expected result

Page data should be updated with the changes.

Actual result

The page is displaying old data.

Environment

System:
OS: macOS 10.15.7
CPU: (4) x64 Intel(R) Core(TM) i7-4578U CPU @ 3.00GHz
Shell: 5.7.1 - /bin/zsh
Binaries:
Node: 12.17.0 - ~/.nvm/versions/node/v12.17.0/bin/node
Yarn: 1.22.1 - ~/.yarn/bin/yarn
npm: 6.14.4 - ~/.nvm/versions/node/v12.17.0/bin/npm
Languages:
Python: 3.8.5 - /Users/macintoshhd/.pyenv/shims/python
Browsers:
Chrome: 86.0.4240.198
Firefox: 72.0.2
Safari: 14.0
npmPackages:
gatsby: ^2.27.1 => 2.27.1
gatsby-image: ^2.3.1 => 2.6.0
gatsby-plugin-i18n: ^1.0.1 => 1.0.1
gatsby-plugin-mailchimp: ^5.2.2 => 5.2.2
gatsby-plugin-manifest: ^2.3.3 => 2.7.0
gatsby-plugin-netlify: ^2.6.0 => 2.6.0
gatsby-plugin-netlify-cms: ^4.5.0 => 4.5.0
gatsby-plugin-offline: ^3.1.2 => 3.5.0
gatsby-plugin-purgecss: ^5.0.0 => 5.0.0
gatsby-plugin-react-helmet: ^3.2.1 => 3.5.0
gatsby-plugin-robots-txt: ^1.5.0 => 1.5.3
gatsby-plugin-sass: ^2.2.1 => 2.6.0
gatsby-plugin-sharp: ^2.5.3 => 2.9.0
gatsby-plugin-sitemap: ^2.3.2 => 2.7.0
gatsby-remark-images: ^3.2.2 => 3.6.0
gatsby-source-filesystem: ^2.2.2 => 2.6.1
gatsby-transformer-remark: ^2.7.1 => 2.11.0
gatsby-transformer-sharp: ^2.4.3 => 2.7.0

@vstoyanoff vstoyanoff added the type: bug An issue or pull request relating to a bug in Gatsby label Nov 25, 2020
@gatsbot gatsbot bot added the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label Nov 25, 2020
@LekoArts
Copy link
Contributor

I'll close this as a duplicate of #26520

@LekoArts LekoArts removed the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label Nov 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug An issue or pull request relating to a bug in Gatsby
Projects
None yet
2 participants