ughh I had to go through the database manually and fix all the incorrect URLs that were caused by that bug in 1.5.0rc1