Bug in Migrate CSS

So, as many have noticed, there’s a bug in the routine to migrate to custom CSS. Turns out, it was a bone-headed oversight on my part: the directory structure of my development environment wasn’t the same as the directory structure I shipped. So, a straightforward file copy that worked at home actually moved your file to the wrong place.

The next release will ship with a fix to the migration routine and also an option to re-migrate your files from the incorrect location to the correct custom directory.

If you’ve already fixed the issue, you’ll be able to ignore it.

My apologies for this!