Hi Team Plasmic
When I duplicate a page, publish and try to access the duplicated page, I am getting a 404 error. Please see the below of the 404 error.
I’ve tried accessing the pages from a different device. I have also tried incognito mode.
Relevant links:
Hello @aihe_team, can you confirm the page route that you are unable to access?
Hi @sarah_ahmed
I’m grateful for your response.
The paths I am trying to access are:
https://aita.aihe.dev/teacher-login-6
https://aita.aihe.dev/teacher-login-7
https://aita.aihe.dev/teacher-login-8
I do not see Plasmic Hosting action set up in your project. Are you trying to publish your codegen site? In that case, you would have to utilize your own custom publish workflow to be able to publish your changes.
Hi again @sarah_ahmed ,
I’m grateful for the response.
We are using the Headless API. That isn’t the same as codeGen right?
Prior, on the same project, we made changes to pages and had the changes reflected.
I am not sure why it is now not the same case?
Thank you in advance.
OK thank you for the confirmation. Can you share your plasmic-init.ts file, or share your github repo with me @sarahsga?
Thank you @sarah_ahmed I will share our plasmic-init.ts file with you. Would you still need access to our github repo if I share the plasmic-init.ts file?
Thank you in advance!
The new pages are accessible when running the loader project on localhost.
In loader case, you need to somehow trigger a re-deploy after you publish a new version of your Plasmic project. This is explained in our Deployment and Automation docs: Deployments and automation | Learn Plasmic
When you use the Headless API, your Plasmic content is usually fetched at build-time and cached for lightning-fast initial pages loads. Therefore, to deploy updates from Plasmic, you need to trigger a re-deploy on your deployment platform.
We’ll be using webhooks to trigger a re-deploy when an editor publishes your project. Most deployment platforms already provide webhooks for triggering re-deploys. If your deployment platform doesn’t, you can still build custom automation to enable this behavior.
I see that in your Publish dialog, there are no webhooks configured. That possibly explains why the live app is unaware of the latest published version of the Plasmic project.