« BACK  |  PRINT

RS

MEMBER DIARY

Seriously…Can we bring back 2.0 till the bugs are fixed on 3.0

I know Neil is doing a thankless job and he’s doing the best he can…but can we bring back 2.0 temporarily so 3.0 can be debugged…It’s really getting old typing out a thread post only to have it disappear into space when you try to post it because of a 500 error. I can’t get to my Diary either!

Tags: , ,

COMMENTS

  • speciallist

    Remember the Bills?

  • NightTwister

    Most bugs are fixed. I don’t want to give up the state feature and am willing to put up with some inconvenience to get it (just put up my blog in response to Erick’s challenge).

    Most issues (multiple postings) are related to impatience, imo. Do you really need to see your comment three seconds after you hit “post comment”?

  • Neil_Stevens

    What happened just now used to happen under RS 2, too. MySQL needed a swift kick.

    Going back to RS 2 would not prevent that.

    • Neil_Stevens
      • speciallist

        n/p

        • aceintx

          I’ve advocated taking a collection to pay Neil for the hard work…but I’m getting frustrated…I’ve tried to make 3 posts and keep getting dumped and I can’t get into my diary. It’s damned near impossible to have a conversation on 3.0 either because everyone else is frustrated, or the new format get’s in the way…and it get’s really old having to re type comments because it’s disappeared into thin air!

          Sorry all…I’m venting…please don’t take it personally!

          • aceintx

            I’ve advocated taking a collection to pay Neil for the hard work…but I’m getting frustrated…I’ve tried to make 3 posts and keep getting dumped and I can’t get into my diary. It’s damned near impossible to have a conversation on 3.0 either because everyone else is frustrated, or the new format get’s in the way…and it get’s really old having to re type comments because it’s disappeared into thin air!

            Sorry all…I’m venting…please don’t take it personally!

          • aceintx

            Again…I’ve been advocating patience from the beginning…maybe today is a bad day for me, (wrong side of the bed and all that)…

            I’m just wondering if it can be a temporary thing till the bugs are worked out on 3.0…chalk the last six months up as a test run and bring it back when the bugs are gone!

          • aceintx

            Again…I’ve been advocating patience from the beginning…maybe today is a bad day for me, (wrong side of the bed and all that)…

            I’m just wondering if it can be a temporary thing till the bugs are worked out on 3.0…chalk the last six months up as a test run and bring it back when the bugs are gone!

          • aceintx

            and please understand…I’m not advocating scrapping 3.0 all together…I’m advocating a temporary return to 2.0 till the bugs can be fixed here.

            I’m not sure if you’d have to pay for the server space to do that or not…and if so I can understand not doing it…but if not, I’d think it’s worth considering.

            I’ve replied to each post here and I’m still not sure if they will post or not because they still haven’t shown up. Once I make the post, the page never reloads all the way and I have to go back to the main page, try to get back to my diary, go to my OP, and scroll back to the next post in the thread…and wonder if any of my replies will ever appear or slip off to the abyss!

            I really don’t mean to give you a hard time Neil…but I think what I’m advocating might take some of the pressure off you.

          • absentee

            I never, ever, EVER compose a blog within the interface of the site I’m posting to. I compose it in Notepad first, then paste into the interface.

            Any site you post a blog to, you have the chance of a dead submit. And then the whole thing is gone. I don’t risk it.

          • Neil_Stevens

            Right up to the time we turned RS 3 on, the Eagle people were regularly having to restart MySQL when it took the site offline.

            What happened today was exactly the same. Being on RS 2 would not have prevented it.

            And I know you’re not being mean or unfair in your criticisms. I’m not taking it personal or badly at all.

            I’m just pointing out that in this case, it wasn’t RS 3′s fault (and I’m not one to whitewash how badly we got burned in what software was delivered to us).

          • aceintx

            I don’t if it’s intended to be short….My problem is…I start out with a short reply in mind and get long winded!!!

            I know I need to be patient…but this is getting frustrating!!!

          • aceintx

            I don’t if it’s intended to be short….My problem is…I start out with a short reply in mind and get long winded!!!

            I know I need to be patient…but this is getting frustrating!!!

          • bs

            I never, ever, ever got a 500 error on RS2, in over a year of use. As ace says, it’s pretty darned frustrating to compose a posting, only to be presented with an error rather than a confirmation – how do you know if the thing got eaten or if it might actually appear someday? I recently wrote and submitted a post, and it didn’t appear for at least 15 mins, following the dreaded 500 error. I’m not saying that RS2 should return, as it would make it rather hard to debug problems that are load-induced… but it is frustrating, and since there’s no “sticky” for reporting issues, all we’re left with is to post diaries that sound like whines.

          • aceintx

            :>)

            ROFL

          • aceintx

            Waste of bandwidth and very disruptive in a thread!

          • SteveLA

            Open two browser threads.

            Post what ever you want, hit POST one time.

            Go to the other window and do something else, like look at Terrel Owens fan page or something. Come back to the browser window where you have RS going in a few minutes and RS will have done your bidding. You will be a happier camper, well if that’s possible.

          • Neil_Stevens

            It was the same problem though behind both. MySQL would get horked up.

            In fact sometimes MySQL still gets horked up on archive.redstate.com and the site becomes inaccessible until somebody kicks MySQL.

          • aceintx

            nt

          • rjd27

            your comments and diaries in another program, that way you have a back up.

  • Flagstaff

    One reason the delays are so frustrating is that things can be going along fine and then BOOM! (a little Madden lingo there) we’re all tied up for minutes waiting for something to re-appear. I know we should just expect it every time, but human nature is to expect technology to work right every time, not to prepare for bad stuff every time.

    All that aside, it takes a lot of the fun out of the site if there are frequent long delays traveling from screen to screen.

    At least we aren’t like NFL Field Pass. I bought a subscription, couldn’t access the game on Thursday, and it took about 2 hours (literally) on the phone Friday to them before I found a tech who knew there was a problem between Mac OS X and their software. “It’ll be fixed in a couple of days.”

    • aceintx

      waiting for this to work itself out.

      I’m over it now…and will shut up till the next time…

      :>)

  • streetwise

    When it functions!

    The longer 3.0 is live, the faster the bugs will be worked out.

    The RS team did all they could with an extensive beta testing to iron out the kinks. But nothing reveals the shortcomings like going live.

  • StephC

    Like yesterday on GC’s blog about the New Era Bill. When it takes 3 minutes to log on, then 10 minutes to post, and then when it does finally post, it’s double half the time, then it’s time to give up for the day.

    Seems to be working alright today.

  • speciallist

    and Saved….Then you can post it whenever you want…

    Tell you a little secret..If you’re thinking two steps ahead and Redstate is a little slow…have a couple posts waiting and ready to fire off…when the time is right