I’m using Plasmic CMS for our blog and using API to get some of the data. Recently we are experiencing “downtimes” where api call does not return anything so we’re stuck with a loading status. But then after a while it loads. This has just been happening recently is there anything we can do to solve this or is this more on Plasmic side?
Access to fetch at '<https://posthog.plasmic.app/capture>' from origin '<https://stories.thinkingmachin.es>' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
I’m getting a cors issue though this only stared happening recently.
Sorry that you’re seeing that error, but you should be able to ignore it
Can you share a live URL where we can inspect the issue?
https://stories.thinkingmachin.es/data-governance-for-business/ - currently it’s working but then it goes down every once in a while.
I’ve attached an image of what it looks like when it’s down.
This is a big issue for us since we use plasmic cms for our blogs and we can’t have them like this frequently
Hi @attractive_wasp, we’re investigating, but one issue I’m noticing is that these pages are querying for CMS data at all from the browser, which shouldn’t be necessary given that these are static blog content pages.
Plasmic supports loading data during pre-render, e.g. a server side static build. What does your Plasmic integration look like - do you do these steps?
https://docs.plasmic.app/learn/nextjs-quickstart/
In particular, the extractPlasmicQueryData step - this has more details:
also noticed this message, which is forcing a client-side fetch of Plasmic designs as well; you’ll want to add Chip to the list of components to fetch in your PLASMIC.fetchComponentData() in getStaticProps()
We’re also rolling out improvements to make cms queries more robust