![]() |
Quote:
|
Yes, and if you add a couple of display echos, you will see that all the numeric valiables are passed, and all the string ones are not. Why? I haven't the faintest idea.
|
hi,
yes true.I haven't got an idea either but it's obvious variables of type TYPE_INT are passed and TYPE_STR aren't PHP Code:
maybe that got something todo with it just guessing here through there is a problem with it if you call GettType() of those TYPE_STR variables it just returns the plain function call while TYPE_INT is properly returned PHP Code:
|
John,
Look at the attached screenshot... :banana: :ermm: if you output those variables with $_GET[name] (no quotes) it does work verry strange i'm thinking about a vbulletin bug here ? |
I spend the best part of this morning, trying to figure that out. I compared the code, where the completeremove and the remove are called from. Same thing. I compared the GPC cleaning thing, I even copied parts of the code from the remove to the completeremove. Nothing!
This afternoon, I tried something, below the section of code that should affect this. Guess what? It fixed something, wname and uname are now passed, but not the parameter which shows if that warning has caused a ban. Darn vB 3.5!! :( |
I have to agree with you. Have a look at the attached admin_warn.php. The code for the remove and for the complete remove is the same. What I added to have the first variables shown (the ones which didn't show before), was the clean_array_gpc BELOW the form. How on earth can the code below the form, affect the code which is above the form, is totally beyond my understanding. Still, there is no way I can make the "N" (for No ban) pass!
Other members, please do not use this file. It contains debug code, which will mess up your system. |
The automatic warning seemed to work fine when I used the default userID(1), but when i used the one for my bot(47), it diddnt work anymore.
|
Quote:
|
well,
The ban parameter is indeed not passed.A quick n dirty solution would be changing "caused_ban" to a bool and use "TYPE_BOOL" this is either true or false (0 or 1 ) and that should work i know this is a "dirty" solution but the cause of this parameter not being passed can be anywhere.admin_warn.php are 3260 rules of code so ..... again the problem is the same it works fine in remove and doesn't in completeremove |
That's the worst possible solution, it will require people to alter their existing tables. Neah, I'll give it some more thought when I get some more time. In the mean time, nobody is telling me if the Automatic Warnings are working OK now.
|
All times are GMT. The time now is 03:57 AM. |
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:
|