Read this article to resolve Javascript errors and files missing errors when you upload your Adobe Muse file.

Issue

When you update Adobe Muse CC to a newer version and then republish your Adobe Muse site to the web server, you see the following error message:

Some files on the server may be missing or incorrect.

Resolution

Update to Adobe Muse 2017.0.3 release.

After updating to Muse 2017.0.3 release, if you continue to see this error, it could be due to the different cache settings of your server and your client browser. Clear your browser cache and reload your .muse file.

If the error persists, perform the following workaround:

Note:

The following workaround applies to Adobe Muse 2017.0.3 and later.

Workaround

If you are comfortable with editing xml files, perform the following workaround.

Open the AppPrefs.xml file in your system. 

You can open AppPrefs.xml from the following location:

  • Win: C:\Users\(username)\AppData\Roaming\Adobe\Adobe Muse CC\2017.0
  • macOS: Library > Preferences > Adobe > Adobe Muse CC > 2017.0

Modify the <key>SuppressMissingFileError</key> value from <false/> to <true/>.

By modifying the preference key in Adobe Muse, you can suppress the error message from appearing at your client's system or browser.

Note:

When you modify the <key>SuppressMissingFileError</key>, genuine missing files errors (if any) are also suppressed.

Any file missing in any page element, including third-party widgets, are also suppressed.

Caution:

It is recommended that you use this setting only for your production site, where client’s are encountering the errors. You should not modify the AppPrefs.xml settings for your sites in the testing environment.

It is also advisable to try the following resolutions mentioned in the table before you edit the xml file. Read on to know some of the possible causes and the workarounds for this error.

Possible Cause Solution/Workaround
One or more files are missing from the server. The permissions to your files and folders are not set properly. On server systems, files and folders are given permissions that tell the system what actions can be performed with these files, and who is allowed to perform these actions. When the files or folders have incorrect permissions, the browser can't access some files in your site.
Ensure that the permissions are set right for your files and folders and then reload your .muse file.
Files on the server are from mixed versions of Adobe Muse, or mixed versions of your site. For example, your mypage.html may be a different version than your mypage.css. When you upgrade to a different version of Adobe Muse, delete all the files from the server and upload the files to the server once more.
Browser loads one file from the local cache and another file from the server. This can result in a mismatch if the version on the server is newer than the version in cache. In this case, the error is seen in one specific computer, in one specific browser. Since Adobe Muse takes measures to prevent browser caching issues, this cause is rare. Clear your browser cache and reload your .muse file.
When you publish newer versions of some files, the server-side caching by Business Catalyst fails to clear the cache for these files. To resolve this issue, contact Adobe Support.
You may have added custom code or third-party widgets to your site. Custom code that is invalid or code that conflicts with the Adobe Muse code can cause this error. Remove the custom code in each page and isolate the issue. If the issue persists in many or all the pages, check the master page for faulty custom code.
This error is also seen when you copy and paste code with missing closing tags, or when you add complicated code to the existing Adobe Muse code. Specifically check for faulty code in Page Properties <Head> section and check HTML objects that you have added using Object > Insert HTML.
When you upgraded to 2015.2, you experienced this error. Sites produced with Adobe Muse 2015.1 or earlier might have contained poorly written JavaScript within custom code or third-party widgets. However, these did not manifest as obvious errors. For example, the errors may have been the last thing to occur during the loading of the page and may not have been reported in an alert.
With the improved page loading performance in Adobe Muse 2015.2, third-party widgets and incompatible jQueries can cause various errors.
Upgrade to Adobe Muse 2015.2.1 as this version allows each third-party widget to load its own version of jQuery without interfering with the Muse copy of jQuery.
Your hosting provider does not serve all the files for a page in your site. When you use the Publish > Export as HTML option along with a third-party FTP solution, the application may fail to upload all the files that have changed. This happens when you upload only the files that you have changed. However, there may be other files that are impacted due to your changes. Delete all the existing Adobe Muse files on the server and re-upload all your files that you export from Adobe Muse.
You can also use the Publish > FTP Host option from Adobe Muse. If you choose the internal FTP client, Adobe Muse detects all the files that have been changed. Adobe Muse also uploads these files to the server.
Despite upgrading to Adobe Muse 2015.2 you encounter the missing files error. Muse 2015.2.0 and later now queue some JavaScript files to load and the order they load is dependent on the speed of your Internet connection. You may see the errors when a specific page loads, and not in all pages because the JavaScript is loading in a different order once things are cached or there’s simply a different order because the server requests are resolved in a different order.

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy