They should reduce in frequency as we tighten things up :)

The wardrobe item removal page should be working now~!

We're working on the category issues, but it's looking like we might not have a solution until tomorrow. Something was wrong with the table and we need our previous vendor to make sense of it.

I'm working on the blurry images right now, as well as some of the other issues, including trades.

Is it on specific pages for you?

Just pushed up a rebuild of our PHP/web servers that includes changes for what we've seen since launching the new database. I had one of our web-servers running these changes for the past few hours and it had the best performance, so I've pushed the changes to the rest of them.

This should reduce those 504/502 errors ?

Today has been ?, but we're working on it!

In addition I'm aware of the problems with the wardrobe "all items" view.

I was just coming to post here :) We just got a hold of the data now, and we're going to write a script to apply it to the current database.

Unfortunately we can't just pop these in because the table has something called an auto_increment, which means that every new row gets an id+1 from the last thing inserted.

When the database moved happened, the table started at 1 again, so anything that you've had in your shop assigned to an ID could be assigned to someone elses category (although it wouldn't show up in their shop because they are assigned to both a shopid and a category).

Long story short we have to write a little script to manage that conflict, and should happen sometime in the day tomorrow. I'll update here (as will most likely) once it happens.

Where are they still showing up as question marks? One of the big improvements of this database is much greater support for unicode characters, but we have to undo some of the hacks that we built in for the last one.