UPDATE: Bethesda has since informed IGN that the error that caused this situation was entirely unintentional and they're working on a way to quickly fix the problem ...