Home › Forums › General XMetaL Discussion › Avoid / clean temporary folders for remote document customisation › Reply To: Avoid / clean temporary folders for remote document customisation
Reply to: Avoid / clean temporary folders for remote document customisationMarch 2, 2015 at 10:58 pm
If the schema is being hosted on a server and referenced using HTTP or HTTPS it needs to be downloaded to your local machine's drive by XMetaL Author before it is loaded. XMetaL Author functions similarly to a web browser in this case (and it actually uses Windows APIs that are similar) and it places all the downloaded files into your %temp% directory.
There are two options I can think of if you are having issues.
1. Use the standard Windows disk cleanup tool to clean up the temp folder (for all applications) from time to time: http://windows.microsoft.com/en-us/windows/delete-files-using-disk-cleanup
2. Distribute your customizations (XSD + CSS + CTM + MCR and any other files) locally to avoid the need for XMetaL Author to download them from your server each time a document that references them is edited. See the following for details on how XMetaL Author locates schemas and associated customizations: http://www.slideshare.net/XMetaL/deploying-schemas-and-xmetal-customization-files
If a CMS system is being used (as gcrews suggests) and it is designed to work with XMetaL Author Enterprise (through what we call a “connector” and what some CMS vendors refer to as a “bridge”) then the CMS will either be designed to distribute the files XMetaL Author Enterprise requires for a particular XML document type to a location XMetaL can find it on your local machine's drive, or the CMS will expect those files to already be in place on the local drive (and essentially do nothing to aid with their deployment). If you are using a CMS check with the vendor for instructions and a description of the expected behaviour.