Cliff Notes
The release of the new version of 6GC failed miserably due to bad errors that could not be solved by tonight. I'll be taking a much-needed break tonight and then I'll be working feverishly to find out what went wrong, and fix the problem. Once the problem is fixed, I'll schedule a new release that should take about four hours in the middle of the night. I'll let you guys know in advance before 6GC goes down again for upgrades.

The Long Version

Everything in the release went reasonably well in the beginning. There were some hiccups, but nothing too serious. Then I swapped domains and it all broke.

It's important to note how the release works. Friday during the day, while 6GC was still up, the new version of 6GC was installed on a new hosted server. This server was initially set up to run a different temporary domain name. This gave me the ability to test everything. Then, when everything worked, the plan was to swap IP addresses, which would point the 6gc.net domain to this new server with the new version of 6GC. Everything worked with a small test dataset on the temporary domain just fine, so we were go for release early Saturday morning.

Around 3am Saturday morning, the live site was turned off so that the database and all photos could be copied to the new server. This only took an hour or so.

At this point, the new 6GC was running flawlessly on the new server, which was running with a temporary domain name but all of the posts, information, and photos from 6gc.net. Tests passed and all was well. The last thing to do was swap the 6gc.net domain over, do some last tests of critical components, and then flip my switch to allow everyone else to see the site and not the Twizzlers-promoting maintenance page.

So I swapped the domain over, and then major problems started happening. Most of the problems were configuration issues and were sorted out within a couple hours.

The main problem though, was that file uploads stopped working as soon as the domain was switched over to 6gc.net. Every file upload problem I've had before was pretty easy to solve, but this was not. In fact, I still cannot figure it out, and this is the most stumped I've been in thirteen years of building websites. More technical details can be found on my cry for help at Stack Overflow. If you can help or might know a web dev who knows nginx and HTTP really well (specifically, ask them if they "know how to troubleshoot a HTTP 422 error"), if you could point them to http://stackoverflow.com/questions/4234574...progress-module I'd greatly appreciate it. I'm completely stumped and am about to start digging into the nginx source code (read: painful and slow) to try to figure this out.

Once I can figure out this issue, I think everything else will go well. And then I'll schedule another release. I'm hoping I can get it done before I leave Wednesday for a couple days in Yakima. But it's all dependent on solving that problem. So yeah, I'll post when I know more.

Good luck Christian.

Good luck man! Take your time with it all

we have been fine with the forum like this, we can wait for the update, take your time buddy and make it all it can be. best of luck

heh, I guess I need another part my car... so i have to wait for that now... so we can get this figured out!

Good Luck man!
Kevin

Good luck man! Thanks for it all!!

best of luck!

ya man dont kill your self over it. we are more then willing to give this update time. that your time and get it to the way you want it and do work son! lol we have faith

coomer you know im your support via facebook! lol.

Thanks guys. I'm gonna get some good rest and hit it hard tomorrow. I've got a good feeling about getting this fixed tomorrow once I'm not running on fumes.

cool. thanks for letting us know what happened. I just asked one of my friends if he knows anything about it. I have yet to get a respond to him since it is 12 am here in so cal. I'll let you know if I get any answer from him. I do appreciate your effort best of luck.

Coomer--


There's toooo much love & info to swap all at once!!

A failed release of a new 6gc is still a new 6gc.

i came across this
The 422 (Unprocessable Entity) status code means the server
understands the content type of the request entity (hence a
415(Unsupported Media Type) status code is inappropriate), and the
syntax of the request entity is correct (thus a 400 (Bad Request)
status code is inappropriate) but was unable to process the contained
instructions. For example, this error condition may occur if an XML
request body contains well-formed (i.e., syntactically correct), but
semantically erroneous XML instructions.

here is the website for documentation http://www.ruby-forum.com/topic/98002

There's nothing in your code that immediately jumps out at me as wrong. The 422 error means that the account object could not be saved because it was invalid. But typically, there's a body with the response that details the errors. You might try setting the content type to "application/xml" for your request -- I think the server could be trying to interpret your XML as URL encoded form data since it is not specified. The "Accept" header only tells the server what format to output the response -- it says nothing about the request type.

http://support.recurly.com/discussions/sup...unt-create-post

No worries mate, All i want is to embed you tube videos

Any potential for a mobile friendly version of the site?

Perhaps...I'll have to see what's involved in getting the forums to be more mobile-friendly.

And on the topic of releases, I still cannot figure out what's wrong. It's killing me. I'm going to look into alternatives to the previously-working functionality today.

With the site as it is right now, it works perfectly on my dad's htc droid, but on my phone I can access everything except for the text fields

there is the 'lo-fi version' at the bottom of the page.

I understand that your trying to get the new site up and running, and I'm very grateful that you put up the old/current site back up for now. Just wondering is there any chance of fixing a couple of menus/tabs such as the dropdown menu next to peoples names on the left and the 'options' on the far right (which changes the forum format). However if this slows down the new 6gc site from being completed, dont worry about it.

We'll the lo-fi doesn't show the text fields either

So, its been a minute.............not that I'm pushing for it or anything, but has there been any positive info regarding the updated site?

I have a droid, from what I know the android software can view websites without needing a special mobile version. This is different from most other smart phones, hence why android rules.

Not just droids, android as a platform can view everything in a non mobile format... And that's why android rules.

I can view any website in its non-mobile version on my iPhone as well... Lol

and i can view the entire full version of this site on winmo 6.5... i think any modern day phone should be able to? I wouldn't see the point in a mobile version unless the new site is gonna be a lot more "heavy" than this one.

i just have a regular cell phone, i can view the whole site fine, but i can't reply to messages or reply on threads because there is no place to enter any text

Its not about not being able to view the site. I have an android too!
Its about the site formating to the smaller screen on a mobile device so that you can basically view everything without having to scroll around.
Many modern websites have mobile versions of their sites just for this reason.

deff would be nice^

I'll address the mobile stuff at a later time. For now, I'm still 100% stuck with the errors, but I'm going to try releasing again. More details here.