thats a bug in the litestep core, that should be fixed very soon... there is a post about it on the litestep installer forum... sticky even