The following are some common issues might encounter in the content editor or with live content and the typical steps for resolution.
Content editor won't save changes
In the content editor, you may see a dialog box alerting you that your recent changes haven't been saved. This occurs when the same piece of content is open in multiple tabs or windows, either on the same device or multiple devices.
To resolve this alert:
In the dialog box, clickGo back to editorto return to the content editor.
Copyany content that you've updated since the last save.
Close any duplicate tabs or windows so the problem doesn't persist. If no duplicates exist, check the revision history to see if another user has been editing the content.
Reload the editor. This will load the most recently saved version of the page.
When no live page exists at the URL entered in the browser's address bar, the browser displays a 404 error that the page cannot be found. If you encounter this error for a HubSpot-hosted page, verify the following:
If a HubSpot-hosted website won't load, try accessing the site on a mobile device with Wi-Fi turned off. If the website loads successfully on the mobile device, the issue is likely based in the network used to access it. In this case, visitors not using that network should be able to access the website without issue.
Network issues loading a specific website are often caused by an error in the network's internal DNS structure relating to that website's DNS records. It's recommended to partner with your IT team to verify that the website's CNAME records in the internal DNS configuration match those in HubSpot.
Content hosted on SSL displays mixed-content warnings
If your HubSpot-hosted website is set up with SSL (HTTPS), assets that load over HTTP will be blocked from loading. This issue will only occur with external resources, as HubSpot-hosted resources are designed to load regardless of protocol.
The most common sources of mixed-content warnings are: the src attribute of images, @font-face declarations for external fonts, and @import declarations of external stylesheets.
To resolve mixed content warnings for external resources, you can either:
Use the HTTPS version of the asset's URL.
Upload the asset to the files tool, then reference the file's URL instead.