Skip Navigation

[Resolved] After migrating site to new domain, can't edit template with Divi builder

This support ticket is created 4 years, 11 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Karachi (GMT+05:00)

This topic contains 2 replies, has 2 voices.

Last updated by Michelle Dodd 4 years, 11 months ago.

Assisted by: Waqar.

Author
Posts
#1481191
Screen Shot 2020-01-27 at 10.29.49 AM.png

I am trying to:

Everything is working well on the staging site, but after moving the site to the new domain I can't open/edit the templates in Divi. I have activated the Toolset license and the Divi API key on the new domain, everything seems to be set the same, but the builder just spins and there's a sad face where the builder should be.

Everything is working fine on the front end.

Thanks,
Michelle

#1482501

Hi Michelle,

Thank you for contacting us and I'd be happy to assist.

If you'll check the browser's console of a page where the Divi's page builder doesn't load, you'll see an error similar to this:

Refused to display '.....' in a frame because it set 'X-Frame-Options' to 'deny'.
( screenshot: hidden link )

It seems that on your new website's server, the "X-Frame-Options" is set to 'deny' which blocks all the content that is shown through iframes.
( ref: hidden link )

Since the Divi builder's editor relies on an iframe to work, you're not able to edit those templates.

I'll recommend getting in touch with your hosting support team, to set "X-Frame-Options" to 'sameorigin' and it should work.

regards,
Waqar

#1483617

Thank you so much! That solved it. I had set up a security plugin and set that particular option incorrectly. I had it set right on the staging site so it was working there.

Thanks again,
Michelle