For better or for worse (at the moment anyway) we have just launched the new code for Partybody 2.0. I want to emphasize and I cannot stress this enough that although this code is live on the site it should still be considered to be developmental and pre-beta. You will encounter errors using the site initially until we can get up to speed with fixing and/or adding new functionality. This isn’t the path we had intended to take but unfortunately it’s the best of the situation we’ve been thrown into.

That said, you too can help us make Partybody better. I’ve added a bug/issue tracking system to the site that I urge everyone to use (login not required so guests can use this as well). How you can help is simple, if you come across something that you think is missing or doesn’t perform the way you think it should, simply tell us. You can provide feedback in our bug and issue tracking system.

That’s all for now. Drop us a comment here or open a bug/issue log if you have any questions.

P.S. I haven’t forgotten about the most recent set of pics, rest assured getting those up is high on my priority list.

First and foremost we apologize for the intermittent service interruptions over the past two weeks, most notably the outage experienced over the past 48-72 hours. We’ve never experienced such significant downtime (and don’t anticipate any such downtime again) and it is always our aim to make Partybody readily available 24/7/365. That said, I’d like to go ahead and explain what happened as it affects the way we move forward.

To put it in layman’s terms, roughly a few weeks ago we started some server transitioning with the goal of priming the site for the next version of Partybody. While we made the correct decision with respect to the next iteration of Partybody, our current environment as it stands couldn’t handle the masses of you trying to access the site simultaneously. The end result was a crashed server that took a few days to revive and a fight with our Web host (don’t worry, Rich is presently en route to California to punch them all), and that’s where we stand currently.

So now there is good news and bad news. Let’s start with the good news: we’ve been slowly building the next version of Partybody over the last few months. And now the bad news: it’s not done yet.

Well that’s just dandy, but what does it mean for you our beloved? Unfortunately it means that you’re going to have to stare at this blog post for a short time while we work our tushies off to get a working version of the new Partybody.

Again, we apologize for this inconvenience, but we think you’re really gonna like what we have in store for you.

Feel free to leave a comment below if you have any questions or requests (or if you just need some attention until the forum is back up).