Revalidation broken for Custom Post Types

Renesauve

Works for "Pages" and "Posts" but when I update a custom post type like "Projects" for example it will do the first revalidate (sometimes) and then when I change it back it doesn't revert the change and no longer revalidates anymore

CalebBarnes

Can you add more info, where it was deployed (Vercel, Netlify, etc), and what version of Next.js?

Renesauve

Both sites I've tired this on were hosted on Vercel, I also tried adding to Netlify with Next.js Runtime v5 active and still didn't work (I didn't test this as thorough though so I may need to do it again) Tested on Next v 14.1.4 I noticed there was a new version 14.2.0 today so I'll test that out

CalebBarnes

Any update on that?

Renesauve

Oddly enough I can't even get it working for posts anymore even now that I'm trying it out a new site. I've updated on-demand revalidation to latest version instead of 1.1.3. I've also tried following their instructions (not using the nextwp revalidation hook) I'm a bit stumped tbh. I added this to the page.tsx: export const fetchCache = "force-no-store"; This disabled the vercel caching: https://vercel.com/docs/infrastructure/data-cache/manage-data-cache But definitely not ideal... It honestly seems like it's the vercel caching that is causing the issue. I'm gunna give Netlify another college try and see if I can make some magic happen

Renesauve

Seems to be fixed in next version 14.3.0-canary.42 for posts specifically Doesn't seem to be working for custom post types still

CalebBarnes

Just for posts or also pages?