Catching up on some old posts here...
Quote:
Originally Posted by Seiyaboy
(Post 1388709)
This looks very nice indeed, but I have a question about this before I install it. Do this modification require admins and mods to be logged into their admin/mod cps in order for the banning and thread/post deleting to take place? Or as long as the usergroup permission matches, no extra login is needed? Thanks in advance.
|
No, they do not have to be logged into the admincp/modcp first. It's a single-file .xml install, it would have actually been faster to try for yourself than type your question :)
Quote:
Originally Posted by weeno
(Post 1400713)
An issue that we've seen.
If you try to "one touch ban" from a user's name in the postbit, it tries to ban the 1st poster in the thread, not the user whose name you've clicked on.
Obviously, it's the wrong variable is being used.
arn
|
I haven't seen that before, nor had anyone else report this. Is this issue still current, if so please PM me with the details of your setup to see if I can figure out why that might happen.
Quote:
Originally Posted by DssCrazy
(Post 1400718)
something needs to be added!
Look at the pic! i pointed it out!
|
Well I looked at the pic you posted and could see nothing other than the fact you drew a box around the forum name used in the example. I'm afraid you'll have to be more specific about what you are trying to say, because I've no idea.
Quote:
Originally Posted by tekguru
(Post 1408540)
Any ideas why we are getting this message when trying to run?
PHP Code:
Database error in vBulletin 3.6.8:
Invalid SQL:
DELETE FROM vb_pm WHERE pmtextid IN (SELECT pmtextid FROM vb_pmtext WHERE fromuserid = 21443);
MySQL Error : Got error 134 from storage engine
Error Number : 1030
Date : Monday, December 24th 2007 @ 08:37:24 PM
Script : http://www.4winmobile.com/forums/misc.php
Referrer : http://www.4winmobile.com/forums/misc.php?do=spamcleanconfirm&u=21443
It's been running flawlessly for ages...
|
When I took that error message and put it into google I found people suggesting that this indicates possible problems with your tables, and suggesting running repair / optimise on them. This message has nothing to do with this mod.
Quote:
Originally Posted by telc
(Post 1413497)
Can you please fix the addon so it will work with MySQL > 4.0.16 the same as VBulletin requirements?
|
There is no requirement that mods must be compatible with the same versions of older software that the current version of vbulletin allows. That's why a system of minimum version numbers was built into the plugin system. In fact, starting from vbulletin 4.0 I'd be very surprised if they allow MySQL 4.0 to be used. See this
post.
This mod uses sub queries. Sub queries are not possible in 4.0. There are a whole host of things which are possible in 4.1 and not in 4.0, as well as performance issues. In fact, many times when I try to do something useful with mysql I find that it is not possible with 4.0. Very small numbers of people still use 4.0 (since the arguments to upgrade, at least from my perspective, are good ones), so I don't really see the sense in committing the additional time required to rewrite what is essentially a simple query into a larger chunk of code to avoid using sub queries.
If someone else wants to undertake the work to rewrite that code to work in mysql 4.0 then I will include it into a new version, but I have limited resources at the moment, so I didn't ever plan to undertake such work.
Since this question seems to come up over and over I'll add it to a FAQ at the start of this thread.
More Information