Looks like it is fixed, @Baron, at least in this section. Edit, not fixed, must have been a cache issue.