Custom Code Guidelines

Our editor is quite versatile in the sense that you may extend the feature of your site by adding any custom script or code, though custom code has the tendency to break or deactivate the editor or take additional steps to work. As a result, we have certain rules for you to follow while testing custom code.

HTTP vs HTTPS

If you're dealing with custom code, you should be aware that scripts and resources can only be loaded inside the same HTTP or HTTPS session.

The editor is always loaded through HTTPS by default. When you use an HTTP script in the editor, it will not be seen since it is loaded over a secure connection, but it will be visible on the live site because it is loaded over an unsecured connection.

To fix this, always load your resources through a secure connection.

Custom Header Code

When adding custom code to a header, make a copy of the site and test your code on the duplicate site. If it fails, simply remove the site.

You can also test the header code on a separate blank page on the same site. If the page crashes, just delete it or go into developer mode to access the code.

Custom Page Code

When adding custom code:

1. Make a copy of the page, then insert your custom code.
2. If that fails, you can get to the HTML/CSS of the page by moving to another page and entering developer mode from there.
3. You may also duplicate the page and remove it to start again.
4. If your homepage contains custom code, you can try visiting your editor by adding/contacting another URL to the end of your editor's link.
   

Page Speed Optimization

Page speed optimization has an impact on how some scripts are executed. PageSpeed optimization is enabled on most pages in Website Builder, which may create problems with your custom code. When troubleshooting code, you may determine whether it is a PageSpeed issue by:

1. Using your scripts, duplicate the page.
2. Change the URL to "testing_scripts".
3. Publish and check the page on your live site.

If your code functions properly on that page, contact support to disable PageSpeed optimization for your site.

If you're using a script, you can also try making sure it runs asynchronously. This won't always fix the problem of scripts not executing right in the browser.

To enable async on scripts, make the following changes to your code:

• Old code: <script src="https://example.com/script.js"></script>
• New code: <script src="https://example.com/script.js" async defer></script>

Disable Animated Navigation

The dynamic navigation function of Website Builder sometimes interferes with the way custom code is loaded. In responsive sites, you may stop animated navigation by right-clicking your navigation element in the editor, selecting Edit, and then clicking Turn off animated navigation.

Troubleshooting

When a site is broken by custom code, the editor usually loads a blank page (or breaks your editing features). If your site was broken by custom code, you have many options:



• If you have a backup, go to the left panel and select Settings, Backup Site, then Restore to Backup.
• Log in to http://my.Website Builder. co?nossl, our platform's code-friendly version.
• If you can't get to it in your editor by loading it, you might be able to work around it by loading a new page.
• To resolve this issue, open your editor on a new page. You may accomplish this by changing the URL in your editor link. This is a link to a site's "About Us" page, such as https://my.Website Builder. co/home/site/XXXXXXXX/about
• If the editor is malfunctioning, try forcing it open by using the element inspector's keyboard shortcut.
• Mac. Command+Option+C
• PC. Ctrl+Alt+C

Website Builder's Custom Code Policy

We cannot troubleshoot why a custom-coded element may not work on a site due to the unpredictable nature of custom code.

We do not have any developers available to debug custom code at the moment, so please follow the recommendations above when experimenting with custom code on your site.