Version: , by Konqueror
Developer Last Online: Dec 2002
Version: 2.2.x
Rating:
Released: 12-20-2001
Last Update: Never
Installs: 4
Is in Beta Stage
No support by the author.
"Ultimate Ignore" v0.91 Beta
This hack was requested at https://vborg.vbsupport.ru/showthrea...threadid=33294
This hack allows admins to set a user to "ultimative ignore" mode. This means that no-one except
admins and the user himself can see any posts or threads posted by that user.
I lost the instructions, so if anyone still got them let me know please.
Show Your Support
This modification may not be copied, reproduced or published elsewhere without author's permission.
$uignore = $DB_site->query_first("SELECT uignore FROM user WHERE username='$post[username]'");
should be this:
Code:
$uignore = $DB_site->query_first("SELECT uignore FROM user WHERE userid='$post[userid]'");
Or you will get lots of mysql errors for users whose username includes '
I'm also unsure why you would need to run this query to begin with. You need to find a way to get the global ignored users and cache them, rather than running this extra query for every thread
maketableheader("Options");
and
receivepm='$receivepm',emailonpm='$emailonpm'
show twice.
Should this be replaced in both instances? (I did after I placed it in the first instance and it did not show in CP)
Also, I tried to use it. It does what i says but the last 10 posts did not reflect that. It is showing the link to the thread. When you click on it, there was no thread as it was meant. Is there a way to also ignore the last post?
this is a VERY resource thirsty hack. It adds an sql query to EVERY post!
What you want to do is forget about adding 'uignore' to the user table.
Instead, add it to the 'setting' table:
varname=uignore
vale = list of space-delimited userids
Same as IP banning.
This way, it won't add ANY queries AT ALL (because all the settings are loaded).
Instead, you'll need to add a 'checkuignore' function that explodes $uignore, and the bb admin will add the users via the Admin CP Options page -- again, exactly like ipban or emailban.
The other alternative is creating a usergroup "global ignore" and then usering the $userinfo[usergroupid] -- again, this is globally loaded so there won't be a need for additional queries.
Either way, your current method is highly unrecommended. On a thread with, say 40 or more posts, you are looking at adding 40 or more SQL queries!!! :stupid:
Sorry, had some problems with my server that needed urgent attention. (that is, Apache wasn't working)
I got it up again now, so I'll be able to fix all those problems with the hack.
Quote:
Either way, your current method is highly unrecommended. On a thread with, say 40 or more posts, you are looking at adding 40 or more SQL queries!!!
Well, what can I say... You got a point there! Guess that's one of the reasons I put it in beta hacks.
I've edited the hack to be more efficient, but I'll add some new things to it as well now, so it will be another day till the next version.
But I think you'll like the changes.