Home → General →

.dot files are not working

• Edit

ces55739

17 Nov, 2015 10:37 PM

Hello,

Our web content team has had issues with including .dot files (word document templates). The files appear as gibberish with random symbols when viewed from Cascade's internal view. Does Cascade have the functionality to handle uploading these types of files?

Let me know if you need any more information.
Thanks!

1. 1 Posted by Ryan Griffith on 18 Nov, 2015 04:45 PM

   

   Hi,

   This is a known issue in which Cascade will not recognize the file extension and isn't able to send the correct MIME type to the browser to render it properly. If it is truly a test-based file, you might be able to add it to both the Editable file extensions and Plain text file extension preference (**System Menu -> Preferences -> Content**) to see if you can attempt to render the raw content.

   If this does not work, you could attempt to add the new MIME type in the tomcat\webapps\ROOT\WEB-INF\classes\com\hannonhill\cascade\model\render\mime\mime-mappings.xml configuration file and restarting Cascade to see if you get a different result.

   Note: these mappings will need to be re-added after any upgrade because this file is replaced during the upgrade process.

   That being said, we are reworking file preview a bit in Cascade 8 to provide a better experience when Cascade attempts to render a file it does not recognize. Specifically, you will be presented with a friendly message stating the file could not be rendered by Cascade and a few links are provided to download or attempt to preview it in a new browser tab (to see if perhaps the browser can handle the file natively).

   Please let me know if you have any questions.

   Thanks!

   • Edit

2. 2 Posted by ces55739 on 23 Nov, 2015 02:40 PM

   

   Hi Ryan,

   Thanks for your response! I tried adding .dot to the Editable file extension and Plain text file extensions but that didn't seem to fix the issue even after a restart.

   I also tried to update the mime-mappings.xml file, but that also didn't work after restarting. The mapping I used is below. Any ideas on how to fix this issue?

   <mime-mappings>
   
   . . .
   
      <mapping>
            <extension>dot</extension>
           <value>application/msword</value>
       </mapping>
   </mime-mappings>
   

   • Edit

3. 3 Posted by Ryan Griffith on 24 Nov, 2015 09:15 PM

   

   Hi,

   Do you know if .dot files are XML based by chance? If so, you could try adjusting your <mapping> declaration to the following and restart Cascade to see if you are able to render the file:

   <mapping>
     <extension>dot</extension>
     <value>text/xml</value>
     <renderable>true</renderable>
   </mapping>
   

   If this does not work, I suspect the browser is simply unable to render the file and doesn't know what to do with it. As I mentioned, we are reworking file preview a bit in Cascade 8 to provide a better experience when Cascade attempts to render a file it does not recognize, but until then there isn't much we can do in terms of rendering the file natively within Cascade.

   Please let me know if you have any questions.

   Thanks!

   • Edit

4. Tim closed this discussion on 11 Dec, 2015 06:39 PM.