XFMG uses xfmg_media as it's main content type, but XFRM uses resource with no prefix, which seems inconsistent. Not really a bug, but wasn't sure where to put this
We're aware, but this isn't something that will be changed at this point. (In an ideal world, custom content types should be prefixed to prevent conflicts.)
