Sometimes we need to create JSON in a text file with extension .json, however by default IIS 7 or any of the IIS are not configure to handle .json extension. So below is a very simple method to do that. You can apply the method on the root of IIS so .json can be handled by every site or virtual folder in the IIS or just to the specific site. Open IIS Manager Display properties for the IIS Server Click MIME Types and then add the JSON extension: File name extension: .json MIME type: application/json
As a follow up to this - we don't have this problem - but the file path that is returned by the RoxyfileMan does not include the virtual directory - so the images never show up in the TinyMCE editor - something you came across ?
ie we get: /content/images/uploaded/someimage.jpg
when we need
/shop/content/images/uploaded/someimage.jpg
There is an easy manual fix - add the /shop - but explaining that to a end user gets tricky :-)
Sometimes we need to create JSON in a text file with extension .json, however by default IIS 7 or any of the IIS are not configure to handle .json extension. So below is a very simple method to do that. You can apply the method on the root of IIS so .json can be handled by every site or virtual folder in the IIS or just to the specific site. Open IIS Manager Display properties for the IIS Server Click MIME Types and then add the JSON extension: File name extension: .json MIME type: application/json
However, I found that somehow after deploying to my hosting(Arvixe) the mimeMap file extension declaration was lost and so Roxyfileman was unable to properly configure itself on startup(i.e. on click to add picture from TinyMCE), and throws those errors. Roxyfileman uses a conf.json file to configure itself and if your server isn't handling .json's then Roxy craps out.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.