unable to load new story or duplicate story

Hello @sunil2900 thanks for getting in touch. Sorry to hear that you have been having issues with your Web Stories since changing domain. To help you further with this please could you provide the following:

1. Your Site Health information or You can share privately if you prefer via this form.
2. When creating or duplicating a Web Story do you notice any browser console errors?
3. If you could provide a video recording of what you are seeing that would be very helpful. You can use services such as Loom to do this.

Once I have this information I can advise on next steps to take.

Hi @sunil2900 thanks for providing the screenshot and video that’s very helpful. I can see from your screenshot that you are receiving CORS related errors. This is because the browser is trying to access images from a different domain to your new domain. I presume that utsukhindi.in was your old domain?

There are a couple of ways you can address this:

1. Update your stories to that the media being used is the media on your new domain. If you have a site developer you can discuss this with them.

2. Set up your CORS headers so that you don’t get these CORS errors. You will need to make sure that your setup has the correct CORS configuration. Specifically, you need to set the following headers:

Access-Control-Allow-Origin headers
Access-Control-Allow-Origin: *

This is something that your hosting provider or site developer may be able to help you with.

Once you have implemented one of the options you should no longer get this issue but please do let me know if you continue to have problems and we can continue to investigate.

When you migrated from utsukhindi.in to vskub.org, your image links within your stories remain pointing to your old domain.

This is usually not a problem. After all, your stories still look fine when you view them.

However, because of how the story editor works, the browser cannot load the images in the editor for security reasons, because they are on the old subdomain and not the new one.

This is what the term CORS refers to. And this is why these HTTP headers are needed to fix the problem.

I recommend you to reach out to your hosting providers support to explain that you need assistance with modifying HTTP headers for the vskub.org site.

If it helps, from what I can see, you need to log into your Hostinger hPanel control panel and locate the .htaccess config file as explained here: https://www.hostinger.co.uk/tutorials/locate-and-create-htaccess

You would need to add the following to that .htaccess file to fix these CORS issues:

<FilesMatch ".(png|jpg|jpeg|mp4|webp|webm)">
Header set Access-Control-Allow-Origin "*"
</FilesMatch>

Ask Hostinger support to help you with any of the above steps if needed. Point them to this thread if needed.

Unfortunately we can’t really help you any further with this, as it’s well beyond the scope of our support offering for the story editor. Hope this helps to clear the issues and please let me know if you are still facing issues with your Web Stories after the above changes have been made.

@sunil2900 This needs to be added on the new domain. If you copy your stories over to another domain then you will have this same issue if you create a new site and stories from scratch then you won’t have the issue as long as you upload your media used for the stories to that site.

Hope this helps. Let me know if you have any further questions.

@sunil2900 Can you confirm if this has helped you to be able to create or duplicate stories or are you still facing the issue?

If you are still having the issue could you once again send any browser console errors you are seeing?

@sunil2900 sorry to hear this hasn’t helped with the issue and thank you for your continued patience. It would be good here to rule out any potential theme or plugin conflict. To do this could you please follow the steps below and let me know how you get on.

Use the Health Check & Troubleshooting plugin and enable its troubleshooting mode. This mode disables active plugins and switches to a default theme safely because it only affects the experience of the logged-in user.

• Please enable the Web Stories plugin and let me know if you still get the issue.
• Enable plugins and your theme one by one in this mode may help pinpoint if something else is involved.
• Note you can disable troubleshooting mode from the plugins page.

These steps will not affect what a user to your site will see while testing this.