Although WordPress by default will allow you to upload and attach Microsoft Office documents to your posts and pages, if you’ve ever tried to upload more unusual documents (for example Inspiration concept maps or SMART Notebook files), you’ve probably gotten a weird “File type does not meet security guidelines” error message.
Fortunately, all is not lost.. we’ve installed a ‘MIME Types’ plugin, which will allow you to add new file types to the default ones WordPress will allow you to upload. You can get to those settings from your Dashboard.. just look for the ‘Mime types’ label under the Settings menu:
You’ll need the ‘File Extension’ and ‘Associated mime-type’ for the document you want to upload. Here is a brief list of commonly-requested document mime types:
SMART Notebook Files
- File Extension: notebook
- Associated mime-type: application/x-smarttech-notebook
Inspiration Files
- File Extension: isf
- Associated mime-type: application/octet-stream
Kidspiration Files
- File Extension: kid
- Associated mime-type: application/octet-stream
iWork Files
- File Extension: pages
- Associated mime-type: application/x-iwork-pages-sffpages
- File Extension: key
- Associated mime-type: application/x-iwork-keynote-sffkey
Google Earth Files
- File Extension: kml
- Associated mime-type: application/vnd.google-earth.kml+xml
- File Extension: kmz
- Associated mime-type: application/vnd.google-earth.kmz
Classroom Performance Software (CPS) Database Files
- File Extension: cxm
- Associated mime-type: application/octet-stream

Hi Jesse
Thanks for this tip, this is just what I needed as I’m trying to upload SMART notebook files to my self-hosted WordPress. Could you tell me which plugin you’re using?
Andy
Found it (I think) – I presume it’s this one – http://wordpress.org/extend/plugins/pjw-mime-config/
Thanks for pointing out how to do this
Hi Andy,
Yep, that’s the plugin we’re using. It *should* work just fine for you.. we had a few problems with it briefly (it stopped working) around the time WordPress 3.0 came out, but those seem to have been resolved with newer versions of WordPress.