Help... Me... (I'm NOT using an illegal copy!)

[irbrian]

Nothing on my end was changed... the only thing I know of is that one of my webhost's staff members did *something* to attempt to recover a corrupt database table in one of the forums' databases (log_clicks). The recovery was successful, but thats when THIS problem started.

[Winnie]

Hi.

A php include path isn't related to mysql, so a mysql file or yabb script itself cannot corrupt that in a file.

Someonme must have changed the file, through ftp or cpanel. If you didn't change it, then someone has access to your account, like your co-staff Josep or someone and they must have logged in. Otherwise, check the "last login" log in cpanel and see who was the last person to login.


As for bringing Apache nearly 100% down like your site did a few days ago, I talked with Jeff and after he explained somethings about it for which I am thankful, from what I understood on how yabb was designed, the script itself apparently shouldn't cause apache to come down, since your site doesn't have that many postings either and we have other sites with 10 times much more users and posts like I showed you on msn, thus it maybe the corrupt mysql database or an error from your end.

As for php path, I don't think it is an error with yabb, but maybe I am wrong. Did you specify correct info during the install of yabb?

Also, no include path have been changed. Like you said above, other php scripts work fine, so it is only with this script, so that rules out the php include being changed option.

As for the test board, have you made sure files are there and with same upper/lowercase characters, and are not hidden or chmodded to a wrong setting if they need to be written opon, amongst a few suggestions?

Also, your mysql databases were corrected, you html or php files weren't. Meaning, no one touched your directories or anything related to your php files, so that rules out anything done by staff either.

What must have happened, is your mysql databases itself or something related to yabb on your account which caused the slowdown a few days ago. Was it corrupted from the server side? No, since it happened the night you upgraded and before that it was running fine.

Also, every other script works fine, but on your account yabb doesn't, which I can say might have happened by an error or wrong data entered during installation of yabb, so that means it is limited to only yabb script itself.

Here is my theory: The upgrade you made somehow hiccuped, and you or either yabb made some errand somewhere. Maybe you entered some wrong info during upgrade, or somehow did something to the mysql database through cpanel, and when you ran the index file of the script after you performed the upgrade, it kept opening connections and page wouldn't load. During that time something would have happened, most probably with mysql database which you are still facing today.

The "illegal" notice didn't come because of php include, it must have come because of removing or changing the template, which means you or one of your colleagues must have edited the file/related files and that could have resulted in those errors. Try asking your co-staff. If they didn't do a thing, then your password must have leaked and someone is playing with your account. Change your password.

Question after all this put-to-sleep post of mine:

Are you using the same mysql database or tables from your previous installation which was corrupted, for this testboard?

[David]

Is this the same board being discussed in the Chit Chat forum?

[Jeff Lewis]

Yes.  If you are still having issues today, email me your login info and phpmyadmin info and I'll go in and correct the issue

[irbrian]

The technical support contact I've working with from my webhost company suggested last night that I wait 72 hours for our new nameserver IPs to be resolved, and then we'll try creating a new account and see if that fixes the problem with the template.html file not being recognized. If for some reason that does not resolve the issue, they have offered a refund for the service. So with that, I am abandoning the issue until 72 hours has passed. I appreciate everyone's help on the matter.

Incidentally, the database table issue is no longer an issue. Regardless of how the table became corrupted, my host was thankfully able to recover it, with no data loss. It is the end result that matters, and it turns out that story had a happy ending.

[irbrian]

A final update on this issue, regarding the sudden and as-yet unexplained failure of all my forums...

I backed up the databases, deleted all the files, and installed 1.3.1 completely fresh, then imported the (Structure and Data) database dump files, and lastly ran the upgrade.php. The problem has vanished.

I just thought this info might help someone in the future.