Interesting problem... I have some mAP2n's here I'm wanting to use for a project. This involves implementing a WebFig skin.
1) Taking a mAP2n with no configuration, clicking 'save' under WebFig skin designer does nothing. The skin is not saved.
2) If I FTP into the mAP2n and create a directory 'skins', clicking 'save' under WebFig skin designer does create a file in the new skins directory. However, this skin does not show in the list of skins available to apply to user groups. This skin also cannot be loaded back into WebFig for further editing.
3) If I FTP into the mAP2n, download the new skin from 'skins/newskin.json' and then upload it as 'flash/skins/newskin.json', then the skin appears in the list of skins available to apply to user groups. WebFig can also now load this skin in for further editing (although when it is saved, it's saved to the wrong place).
So, I can get it working, but this is clearly impractical...
In summary - WebFig is saving the skins to '/skins/' when it should be saving them to '/flash/skins/'.