Hey folks, We seem to be having major issues with one of the servers that runs the backend of the discussion board. There are several different probable causes, but unfortunately, the problem is very intermittent, and not easy to track down... but we are working on the issues. In the meantime, I've run another maintenance on the database which seemed to clean up the corruption that was causing the immediate problems. We also completed the last steps in preparation to move degreeinfo to a new server, which will host both the database and the HTML portion of the site (with backups and mirroring and so forth in other data centers to protect against DOS attacks and so forth) So as soon as Nate, our tech guru, has time to finish configuring the new server, we'll move it there and the problems should go away. No, we're not losing interest in degreeinfo, no, it's not dying, and no, we're not getting ready to sell it to somebody. I'm just on deadline on some other projects and so not having as much time to hang here as I usually do. (I do often check in, just don't post that much these days...) So... hopefully that will calm feelings. And as far as comments on the various other boards operated by the degree mill apologists... I really don't care. They've been looking to find reasons to denigrate degreeinfo for ages, and no matter what we do, they'll find reason to dislike it... so it really doesn't matter. Hope that answers any questions.
One try for me also this morning. I did, however, have major problems logging on last week. I got around this by pulling up an old thread. I figured it was a bug or something. Thanks for all the hard work that goes into this forum. I have picked up tons of info that has really been helpful to me as I pursue my degree. Thanks and Merry Christmas! mona
Yeah, Bill, but you can't get decent tuica and them little sausages here. Thanks, Chip, yet again. I'm not always sure that even we veteran posters understand the amount of tsuris you guys have to deal with. Best wishes for any relevant holidays. Janko
Chip, I know you've been swamped; and I've been hounding you 'til you're no doubt sick to death of me (you and my ex-wife, I dare say... and by the way, for all her faults, that puts you in pretty good company, all things considered); but I think I speak for many -- probably most, around here -- when I say that we share the vision you originally had in creating this place in the first place... ...and now, like it or not, we share the love of it, too. So maybe we worry too much... er... well... or maybe just I do... who knows. Anyway, thanks for this place, Chip; and for keeping it alive and well... and soon-to-be-improved! It (and you) is (are) appreciated more than I suspect you realize. As always, I reiterate my willingness to help in any way I can.
When it was slow to respond, you clicked-on the "Submit Reply" button twice, there, did ya' Ult? Chip, if I may suggest, insert the following Javascript code in the <HEAD> area of all your .PHP form input pages: Code: <script language="javascript"> <!-- BLOCK JAVASCRIPT ERRORS --> <!-- Begin function blockError(){return true;} window.onerror = blockError; // End --> <!-- FORM BUTTON DISABLE AFTER CLICK --> <!-- REQUIRES <form onsubmit="return dis(this)"> --> <!-- Begin function dis(obj) { for(i=0;i<obj.length;i++) if(obj.elements[i].type == "submit" || obj.elements[i].type == "reset") obj.elements[i].disabled = true; } // End --> </script> And then, down in the BODY area of all such pages, as the last object in the <FORM> tag, include the following javascript call: Code: onsubmit="return dis(this)" as in, for example: Code: <FORM ACTION="replyform.php" METHOD="POST" onsubmit="return dis(this)"> Do this, and whenever anyone with a version 4+ browser (which has its Javascript turned on) clicks on either the "Submit Reply" or "Preview Reply" buttons, said clicked-upon button will immediately "gray out" so that it cannot be clicked-upon a second (or successive) time(s) while the post takes however long it's going to take to happen. Just tryin' to help.
maybe....... ........maybe................ Ok I did it! I admit it!!! For a second I thought of padding my post total, but It was my impatience. Darn, guilty as charged.
Re: maybe....... It's okay. I've done it, too... plenty of times. But there's a reason no one around here has seen any duplicate posts from me. Some vBulletin owner/operators, for whatever reason, don't turn on the "Delete" capability in the post's "Edit" area. Chip, et al, to their credit, did. After accidentally double-posting, simply click on the duplicate post's "Edit" button; then put a checkmark next to "Delete?" right at the very top of the page, then click on the "Delete Now" button over to the right. But you have to do it within ten minutes after posting. Chip has set the timeout for editing to 10 minutes (a little short, in my estimation, but it is what it is).
