- Oct 23, 2003
- 16,711
- 1,132
- 54
- Faith
- Non-Denom
- Marital Status
- Single
- Politics
- CA-Conservatives
What happens if we lost 100,000 blessings? And thanks for the updates Paul. What happened to Lee?
Upvote
0
Starting today August 7th, 2024, in order to post in the Married Couples, Courting Couples, or Singles forums, you will not be allowed to post if you have your Marital status designated as private. Announcements will be made in the respective forums as well but please note that if yours is currently listed as Private, you will need to submit a ticket in the Support Area to have yours changed.
There are still so many problems. Now this thread is showing a Page 9 but when I click it I go back to the top of Page 8. I can't get to Page 9.
The standard for upgrades in most large operations is to test the upgrades offline, with a copy of the database, to make sure it works, before going live with it. That obviously is not what is going on here.
Inevitably there will be bugs with upgrades. Anyone who uses any version of Windows knows that. The rule of Unintended Consequences always is a factor. Add in a hacker or hackers exploiting vulnerabilities which may have been opened up due to the upgrade just makes it worse. Testing is always done offline for safety reasons. It also helps if those who test are familiar with the product (vbulletin). Just because an upgrade is available, doesn't mean that it must be implemented. The principle should always be "if it ain't broke, don't try to fix it."
Other boards use vbulletin, but they don't have all the heavy modifications that have been done to the code for this board. Those modifications are most likely the source of much of these problems. Bells and whistles are nice, but if they compromise safety and security, they should go. I'd rather have a safe, secure, stable site, than a buggy, insecure, glitchy site that looks nice, but crashes regularly, is down for long periods of time, is subject to unknown vulnerabilities, and isn't backed up daily or even every 12 hours or more frequently. Dialing it back almost 2 weeks is not good, as can be seen from the number of complaints detailed just in this thread.
This isn't Facebook, it isn't MySpace, nor should it try to compete with them.
Brilliant post sir! Excellent advice that I hope is heeded.
Working as a systems administrator myself, if I went to my boss and told him I lost 2 weeks worth of data because of an upgrade, I would be fired on the spot.
I always, ALWAYS do a test upgrade in the test environment, taking notes along the way as to what little problems I run into. Then, when I'm ready, I take the production system offline with a very good estimate of how long the system will be unavailable and what problems I will encounter along the way. I then make a FULL backup of everything, set it aside, and begin the upgrade. At a predetermined time (usually sometime Saturday evening) if there are huge glitches with the upgrade that I don't feel I will be able to work out, then I revert to the snapshot so that they system can be up and running Monday morning (with no data loss or loss of data integrity), and go back to the test environment and iron out the kinks, and try again the next weekend.
I am sympathetic to the hacker issue, as I've been hacked a few times myself, but I am rather disappointed in the disaster recovery plan (or lack thereof), and I hope the techies in charge will learn from this and institute a comprehensive upgrade and disaster recovery plan.
![]()
Thank you for bringing all these points up, as someone working in the computer-field.Just because an upgrade is available, doesn't mean that it must be implemented. The principle should always be "if it ain't broke, don't try to fix it."
Other boards use vbulletin, but they don't have all the heavy modifications that have been done to the code for this board. Those modifications are most likely the source of much of these problems. Bells and whistles are nice, but
if they compromise safety and security, they should go. I'd rather have a safe, secure, stable site, than a buggy, insecure, glitchy site that looks nice, but crashes regularly, is down for long periods of time, is subject to unknown vulnerabilities, and isn't backed up daily or even every 12 hours, or more frequently. Dialing it back almost 2 weeks is not good, as can be seen from the number of complaints detailed just in this thread..
Just wanted to say...to everyone who thinks everything is just fine, that no, it's not.
I'm writing from my husband's account at the moment because mine is still so messed up, including the Paypal situation. My SS renewal was hacked and now I'm listed here as a Credit Card thief on every post I make. My husband thinks that may happen on this post as well, since it's the same i.p. address. I hope not, but won't be surprised.
I hope this personal stuff is fixed soon. I know that it's being worked on, but no, it's not all over yet.
??? How does the site list you as a Credit Card Thief ???
And shouldn't a Mod / Admin fix this asap ?
Ahh It was almost sounding like it was a Board hack doing thatIt was in my siggy.On every post!!!
But fortunately I was smart enough to marry a computer guywho figured out my siggy must have been changed/hacked. I was able to go to my user CP and delete the information.
![]()
Oh and I did write to Paul about it too, so yes, I am concerned about the Admin knowing about this.
Thanks, pgp.
btw, I lost my ASA buddy tshirt and my prolife ribbons from my siggy too.