I don't have this hack installed on 2.2.9 right now. I un-installed it when I couldn't get the time and date to show for the double post and haven't re-installed it yet. I clicked the install button just now, anyway, though. ;)

I know we went through this when I had 2.2.5 up and running, but I don't remember how we did it. I want to add an option in the Admin CP to turn it off if I need to do some testing on the site and be able to turn it back on again. maybe even have it be able to be disabled for Admins. Any ideas? ;)

hmm, if we already worked it out, maybe you can find it again in the thread ;)

Any way to get the date (if different from the original date) and time of each double post?

not without changing the table structure...

everything seems to be working without a hitch, just wanted to pitch in my 2 cents worth of affirmation :P

oh, just for everyone's edification, if you run into a 1064 mysql error number after doing the hack, make sure you didn't remove the line

$postid=$DB_site->insert_id();

that's at the very end of the text you're told to replace in the .txt file. I did that by accident and it caused errors until I realized my mistake. The line in question is directly one line after the end of the php-to-be-replaced, so just don't highlight too far :P

Ok....

I'm not sure where to post this....buuutt...I have a dilemma!

Alright, I've installed this hack double post prevention and the remove redirects hack...

but here's my problem!!

Let's say I post on page 3....once I submit, I am redirected back to page 1....

If I go back to page 3 (after posting) and double post, I am redirected back to page 3.

this has become quite a nuisance....having to go back...

so i'm wondering...is this the remove redirects

or

the double post prevention thats causin this ackward weird silly thing

!!!????

Anyhelp would be greatly appreciated :)

neither nor...

it's the normal procedure to be redirected to the posted post.
if it's not like that on your board, you've hacked it, and have to apply the same hack to the prevent doublepost hack :)

Decided to alter 3600 to 86400 * 30 ;)

24 hours x 60 minutes per hour x 60 seconds per minute yield 86,400 seconds in a day.

86,400 seconds in a day x 30 yield 30-day timeout.

Naturally you could write 2592000 as well.

[high]* Kriek spanks install[/high]

not bad, doubleposting timeout for 30 days ^^