In Adobe Muse, choose File > Site Properties. From the Advanced tab, deselect the Enable In-Browser Editing option.
Resolving Typekit issues in Adobe Muse
Use these troubleshooting techniques to resolve issues that occur when you use Typekit fonts through Adobe Muse.
Typekit fonts are not displayed properly in Adobe Muse live sites
When you publish your site using Business Catalyst, some Typekit fonts are not displayed properly in your live site. The fonts in the published site either revert to a default font like Arial, or the fonts appear small and different.
Solution: Turn off In-Browser Editing
This is a known issue in Adobe Muse. You must disable In-Browser Editing to resolve this issue.
Republish your site as HTML, or by using FTP.
Typekit fonts are not exported from Adobe Muse
When you use Typekit fonts in your site and export your site as HTML, the font is not exported. Instead, you see a standard font in your published site.
When you export your site as HTML, or upload your site to an FTP host, you see the following error: “Internal Error: 403 Forbidden operation.”
Solution: Add all your domain names
Web fonts from Typekit are served only to those domains that you specify when you export your site. When you export your site from Adobe Muse to HTML, or when you upload your site to an FTP host, you need to add all your domain names.
Follow this procedure to add a domain name or a site URL when you export your site as HTML:
Open Adobe Muse, and choose Publish > Export as HTML.
In the pop-up window, you are prompted to provide the site URL. Add all your domain names as a comma-separated list in this field.
Upload the new HTML to your web server. The Typekit fonts work within a few minutes.
Follow this procedure to add domain names when you upload your site to an FTP host:
Open Adobe Muse, and choose Publish > FTP Host.
Connect to the FTP server using your credentials.
In the Upload to FTP Host dialog box, enter all the domain names or the site URLs for your website.Note:
If there is any redirect involved in your site, or if your site loads from a different domain, you cannot see the Typekit fonts in your live site.
Unable to generate web fonts when publishing your site
When you publish your Adobe Muse website, you see the following error message: “Error 0: Not Connected. Could not generate code to enable one or more web fonts on page.”
Solution: Sign out of the Creative Cloud desktop app, and then sign in again
This error was fixed in the September 2015 update of the Creative Cloud desktop application. However, if there is a mismatch between your Muse login status, Typekit, and the Creative Cloud desktop app, you continue to see this error.
To resolve this issue:
Close your Adobe Muse application.
Go to the Creative Cloud Desktop app and Sign Out from Preferences.
Quit the Creative Cloud desktop app.
Relaunch the Creative Cloud desktop app, and sign in.
Relaunch Adobe Muse.
You can now publish and upload your site, and your Typekit fonts work without errors.
Unable to use the Skolar Web and Modesto fonts from the Typekit library
You are not able to browse, select, or use the Skolar Web and Modesto fonts in your Adobe Muse sites.
Solution: Use other fonts for new sites
Typekit no longer supports Skolar Web and Modesto fonts. See this announcement from Typekit for more information.
Your account does not have access to Typekit
When you click Add web fonts, you see an error that your account does not have access to Typekit.
Solution: Contact Customer Service to make sure your payments are current
You cannot access Typekit through your account if your payment is under processing or if your payment has not been successful. The subscription account goes to a suspended state until the payment goes through. During this time you can use all the Creative Cloud services except Typekit.
To rectify this issue, contact the Customer Service team.