jlengstorf / netlify-plugin-gatsby-cache

185 stars 21 forks source link

It's caching an older version of the image if it has the same name #39

Closed sameersegal closed 3 years ago

sameersegal commented 4 years ago

The repo shows an updated file with the same name but what get's deployed is the older version.

jlengstorf commented 4 years ago

hey there — if you disable this plugin, does it still happen? have you loaded the site with caching disabled to makes sure it's pulling the latest version?

sameersegal commented 4 years ago

Yes, when I disable the plugin it gets deployed correctly. However, when I re-enable the plugin it, I guess, used the old cache to deploy the older version.

Finally, I changed the name of the file to ensure it works correctly.

On Tue, Jul 14, 2020 at 9:07 PM Jason Lengstorf notifications@github.com wrote:

hey there — if you disable this plugin, does it still happen? have you loaded the site with caching disabled to makes sure it's pulling the latest version?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jlengstorf/netlify-plugin-gatsby-cache/issues/39#issuecomment-658251639, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAKFTK6DMF3QQUDXBZOHM3LR3R3TTANCNFSM4OZPKSGQ .

jlengstorf commented 4 years ago

I'll see if I can reproduce this. thanks!

sameersegal commented 4 years ago

Hey, any luck with this?

Also, I saw another interesting behavior with the plugin enabled:

Build one has a page /old-route Deployed Successfully Change /old-route to /new-route Build and Deploy successfully

On the live site both /old-route and /new-route work.

jlengstorf commented 4 years ago

@sameersegal have you tried that locally to make sure it's not a Gatsby behavior? I'm not sure Gatsby does garbage collection, so you may have to clear the cache to get rid of old pages

jlengstorf commented 3 years ago

I'm going to close this issue since it's been quiet for a while. if anyone else hits this behavior, please feel free to open a new issue or comment on this one!