script in Auto generation causes server error

Here is my problem:

After completing create form table, I can not save/edit the configuration of my form unless I remove </script> from the auto generation code. If i leave </script> in the auto generation settings it causes internal server error when saving. Is there anything else I can do apart from removing the tag </script>?


Great program I am testing at the moment and will purchase if can fix this problem.

hi,

Could you please post your autogenerated code ? the script tag isn't even so necessary, it will only popup an error if the insertion of data failed!!

Max

<?php
global $database;
$database->setQuery( "INSERT INTO #__chronoforms_1 VALUES (
'' , '". date('Y-m-d')." - ".date("H:i:s")."' , '".$_POST['name']."' , '".$_POST['email']."' , '".$_POST['postcode']."' , '".$_POST['telephone']."' , '".$_POST['weddingdate']."' , '".$_POST['weddinglocation']."' , '".$_POST['weddingservices']."');" );
if (!$database->query()) {
echo "<script> alert('".$database->getErrorMsg()."'); window.history.go(-1); </script>";
}
?>

I have removed the </script> to get it to work which is fine, script I understand is used to dispaly error message only. Any amendments/suggestions appreciated.

This never happened before so I will check it again, but as you said its almost useless and you can go without it, in case the error shows, it will show to the frontend user, so its good now I think!

Max

I think it must be server conflict/permission with code. Ive tried entering in <script></script> in another form and same thing happens - internal 500 error. I know server provider have very strict rules and firewalls and that php is running under safe mode if that helps solve it. Interestingly, when your program first created the database table it accepted the <script></script> tag. I can remove the </script> as you say for now anyway. Ive tried both versions v2 and latest beta. Thanks anyway.

Hi Stephen,

I had a little Google and this looks a like a fairly common error with scripts that is quite hard to diagnose. Doesn't look like it is anything directly to do with ChronoForms. The most likely cause seems to be a faulty .htaccess directive . . .

Bob