![]() |
WHole threads keep dissapearing
Do not know if anyone can help, I hope so.
Whole threads just keep dissapearing, I have no idea why, I just have one super mod who is not the cause, I have checked all permisions and have no idea whats going on? Has thi happened to anyone else/ If yes what can I do to stop it happening. Man thanks in advance graham |
H4x
|
Quote:
|
Hacked?
Someone hacked into your CP or DB? |
Another problem might be DB issues. If you are getting too many DB errors, some of these errors might damage to your threads/post table which might result in disapearing threads/posts/users
|
check your database, a good hack for such issues would be filburts self healing db
|
The self healing hack only runs a repair. If theres a problem with a thread it would be removed during that repair i believe.
I have lost a few threads myself due to corrupt threads. I got those from converting over from an ikonbored. (and all the crap that came from there) |
Provided that:
a) Threads disappeared because of DB problems b) Your are comfortable with DB structure and have a tool (PHPMyAdmin) to work on the DB. c) You know the disappearing threads ID It is possible to recover the threads by manually editing DB and modify the record of corrupted threads.. But if you don't know what you are doing, I suggest NOT to touch your DB. |
maybe his moderators are just deleting them.... or there over 30 days old and just "dissapearing" ?
|
:rofl: @ faranth
|
well no one eles thought to ask.......
i was only being half sarcastic ive had totaly newbs ask me thos questions about threads dissapering |
Yep, people usually overlook the fact that vBulletin at default hides threads over 30 days old in a forum, and that you must switch the value using that drop-down menu on the forum page. I get this question message to me quite a bit on my forum also.
I think you can change the "30 day" thing as default via options. I've just been too lazy to do so. /me shrugs |
Nope - I also get this problem. Always accompanied by an error 1030 "got error 127 from table handler" during a thread update.
If I run check or repair on the thread table it's always fine. All the post records are still there so provided you know the threadid (provided in the error msg) and the forumid (easy to guess - or just pick one and move it later) you can always reconstruct the thread record. I was doing this a couple of times a week with phpMyAdmin but then got bored and wrote a PHP script to automate the process. Takes a threadid and forumid as arguments and reconstructs the thread record. Still no idea what's causing the problem in the first place though :( Michael. |
All times are GMT. The time now is 09:46 PM. |
Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
![]() |
|
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|