First let me apologize for the initial problems of last night and early this morning. Then for having to take down the site completely.
In trying to understand and then fix the problems that started last night, I found a whole rat's nest of bad logic and code. My code and my logic:slap::slap::slap: Then I found that the problems had caused a whole bunch of logical inconsistancies in the 2 of the database which had to be fixed. I couldn't come up with usual "quick & dirty" clean up the DB tricks. Some of the tables are now too large for that. I had to write and debug a program to straighten out the mess.:crybaby2:
At this point, I hope all is well but I won't really know for a while.
The fixes will have the site effect that the visits/week will no be more stable. That number is now only computed at 3:00 AM. The wild changes that some people have should now be better, especially after a few more weeks.
Some people may notice that their visits/week are now lower than before. The number showing now is actually correct.
Again, my apologies
In trying to understand and then fix the problems that started last night, I found a whole rat's nest of bad logic and code. My code and my logic:slap::slap::slap: Then I found that the problems had caused a whole bunch of logical inconsistancies in the 2 of the database which had to be fixed. I couldn't come up with usual "quick & dirty" clean up the DB tricks. Some of the tables are now too large for that. I had to write and debug a program to straighten out the mess.:crybaby2:
At this point, I hope all is well but I won't really know for a while.
The fixes will have the site effect that the visits/week will no be more stable. That number is now only computed at 3:00 AM. The wild changes that some people have should now be better, especially after a few more weeks.
Some people may notice that their visits/week are now lower than before. The number showing now is actually correct.
Again, my apologies