Hmm...

I can't remember if I have that one installed:(

*damned script kiddies attacking my Hosts server:mad:*

I will test it out on DB when it gets back up:)

Satan

you'll like it chris :)

Hehe no doubt;) It will probably reduce my Forumhome queries considerably - At last check, I think I had 24 or 26:)

Satan

Don't have that one installed, but I do have a hack for Photo Post installed.

My counters were already updated like a billion times. Doing the orphan posts option didn't find anything either. :(

Xenon, it shouldn't work that way IMO.
It would be tons cleaner if it was only updated when a new mod is added.
Current version waits for a new post/new thread for being made and then updates the moderator db table.
Not so useful for busy boards. ;)

@Smoothie: Just test it out if it works :)

@fury: As i know the orphan post function just finds posts where threadid is 0.
but there can also be some posts where threadid > 0 but the thread they belong to is deleted.
my hack shows not the ammount of posts that are saved in the db, just the ammount of posts which can be viewed by at least the admin. So i'd say my method is better, normally the ammount should be the same, but if you've had a little problem some time ago you can have this difference :)

@nuno: It's an optimization of the loading time of the forumhome.
When you have a busy board the updated way is really enough, because you'll surely have a new post shortly after adding a new moderator.
just on not so busy boards the cache can be too old for you :)
For the hackinstructions i prefer the easier way, but of course you can add one query to the add moderator function to always update the cahce afterwards: [sql]DELETE FROM cache_forumhome[/sql]
As i say it's not needed, you have to modify other files, too, but you can do, without any negative aspects except of little more work ;)

It worked fine for some hours, then this:

Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 4081664 bytes) in .../index.php on line 408

Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 45 bytes) in .../admin/db_mysql.php on line 77

Any ideas?

hmm, you don't have the zlib installed on your host have you?
if you have not, the whole html is saved uncompressed in the db, which will blow the table very fast. especiall when there are much users online.

try to contact your host to install zlib and allow more memory :)

i think that's the problem....

I do! (Or I think I do - I'm obviously no expert. :D) This is what phpinfo tells me:

zlib:
ZLib Support - enabled
'zlib:' fopen wrapper - enabled
Compiled Version - 1.1.3
Linked Version - 1.1.3