Quote:
Originally Posted by sv1cec
Let us all know my friend and do post that file here, so I can have a look. I am almost sure I've screwed somewhere in the code, but don't say that to anyone. 
|
Well John I hate half work.When something doesn't work as it should (or as exspected)i want to know why.So i've look at the html source vb produces and you will see that for the normal warn remove method the form will be submitted with "do_delete".So what i've did is seperating the code that's responsible for displaying the form and add a method like this
PHP Code:
if($_POST['do'] == "do_delete")
{
//here we go
}
i used the same procedure for the complete warn remove
PHP Code:
if($_POST['do'] == "do_completedelete")
{
//here we go
}
i think the reason why it didn't work as we exspected because you would need multiple clean_array_gpc() calls by seperating both procedures (form display and the PHP to parse it) we tell vb what todo and when todo it.About screwing up well so did i in the first place.But here's a little tip.On your development board turn on vb's debug code.why ? well if you hover your mouse over the submit button row on forms vb will show you the parameters which are hidden along with there value this way you do not need special coding to track it.Enabling debug mode is easy in "/includes/config.php" add
PHP Code:
$config['Misc']['debug'] = true;
this has to bet set in the config.php but i believe there's a plugin here somewhere that allows you to switch it.
here's that plugin
that's how i did it now John don't shoot me if something i did is wrong

the file is attached