If you have added custom code to your site that's impacting its performance or preventing you from editing it, it is most likely due to the code not being formatted correctly or not being HTTPS compliant.
Custom code is very unpredictable. There are many factors as to why your custom code may not be working with our platform. If you need help getting the custom code working on your site, it might be worth hiring a Duda Expert to help you get your code working on your site.
Solution
The following can help you troubleshoot your custom code issues:
- Restore a backup of your site to a point before the custom code was added (even if you haven't created a backup, the editor creates one for you when you publish or enter developer mode)
- Access Developer mode to fix the issue manually
- Load the non-secured version of the editor to load scripts that were not embedded via a secure connection. To do so, log into http://my.Duda.co?nossl
- If you are unable to access the editor when your site loads initially, try accessing your editor on a new page by entering a different URL in your editor link, such as https://my.Duda.co/home/site/XXXXXXX/about. When you get there, you can delete and re-add the page that is causing problems, or access developer mode to fix the issue on the site's code
If you have any links in your code (http:// or //) and your site is using HTTPS or you're in the preview, then you will have to change it to https:// instead
- If custom code is disappearing when you add it to the head section, see this article.
Consent management apps are not able to prevent code from running prior to consent when the code is placed in the header HTML. This is because Duda optimizes the structure and order of how content loads, based on performance best practices on the site. We place scripts and CMP banners lower on the page, in order to improve the performance of primary content. Because of this, it is recommended to place code in the body-end when using a consent management app.