On Fri, Jun 28, 2013 at 10:00 PM, Juan Pablo Lorier
I don't know if it's not better just to start over, because I'm
your time and it's not even a production environment. Maybe it's
just to cleanup everything and start over.
Other idea I had is to cleanup the database and then import the backup
that the upgrade made before rolling back. I don't know if that can
to an inconsistent database or not.
That could work.
Regarding your initial problem - it was fixed in later version, and
should be working now.
In any case - I would recommend reinstalling with 3.2, as it is indeed
a better chance to have less issues.