Data assist, CSS formbuilder 2 html editor Bug or problem with validations

Hello webassist comunity need some help here almost lost my last few hairs, the new css formbuilder seems to nice but so buggy, i have a new issue or bug to report that i need to know a way around it.

Ill start explaining with the steps i did:

1. I used the data assist wizard to create my pages for the admin panel.
   
2. to the insert and edit pages i added css form builder to those made with data assist.
   
3. with the form builder i added fields with html editor directly in the form builder.
   
4. Selected the html editor pressed edit and selected the initial value laso placed xhtml 1.0 transitional to the settings, no encode types and also tried with encoded both also selecting and deselecting Encode html entries and also selecting and des-selecting acsii.
   
5. Saved tested the validations made by the cssform builder
   
6. left empty some required fields but added some text on the editor and when it does server validation to a field, i get the edsitor text wraped with html code.
   
7. Selected html code button on the editor and it has a bunch of strange simbols.

Tested and retested changed all posible settings i dunno what else to do to avoid this, im sorry to say this but webassist still needs to improve to fix these bugs, i was suppose to have this site ready today and i can not give this with this bug.

Please send a copy of the page so i can examine the code.

after rechecking and comparing with older sites i found out what the problem is and its with the new css form builder 2 on the file that it generates called wavt_validatedform_php.php

it comes with

<?php
if (!session_id())  {
  session_start();
}
function ValidatedField($page,$field)  {
  $theFields= "";
  $retVal = "";
  if (isset($_SESSION["WAVT_".$page."_Errors"]))  {
    $theFields = "&".$_SESSION["WAVT_".$page."_Errors"];
  }
  if (strpos($theFields,"&WAVT_".$field."=") !== false)  {
    $retVal = substr($theFields,strpos($theFields,"&WAVT_".$field."=")+strlen("&WAVT_".$field."="));
  }
  if (strpos($retVal,"&WAVT_") !== false)  {
    $retVal = substr($retVal,0,strpos($retVal,"&WAVT_"));
  }
  if ($retVal == "" && $page == $field) {
    $retVal = ValidatedField($page,$field."_Errors");
  }
   return str_replace("<","&lt;",str_replace(">","&gt;",str_replace('"',"&quot;",$retVal)));
}

?>

On my other sites where this problem doesnt come in the same file that was created by css form builder 1 was

<?php
if (!session_id())  {
  session_start();
}
function ValidatedField($page,$field)  {
  $theFields= "";
  $retVal = "";
  if (isset($_SESSION["WAVT_".$page."_Errors"]))  {
    $theFields = "&".$_SESSION["WAVT_".$page."_Errors"];
  }
  if (strpos($theFields,"&WAVT_".$field."=") !== false)  {
    $retVal = substr($theFields,strpos($theFields,"&WAVT_".$field."=")+strlen("&WAVT_".$field."="));
  }
  if (strpos($retVal,"&WAVT_") !== false)  {
    $retVal = substr($retVal,0,strpos($retVal,"&WAVT_"));
  }
  if ($retVal == "" && $page == $field) {
    $retVal = ValidatedField($page,$field."_Errors");
  }
  return $retVal;
}

?>

Comparing both files i notice this line wich is the one that afects the html editor with css form builder or the new validation toolkit it comes with

return str_replace("<","&lt;",str_replace(">","&gt;",str_replace('"',"&quot;",$retVal)));

So i replaced the new file generated by css form builder 2 with the one generated with css form builder 1 and works, my suggestion is that i know it is to avoid exploits or code injections but im working internally with the manager of the site im building, when i use the old file every thing is marked on the server behavoir as invalid and cant do any change cause it will overwrite the file again, css form builder should come with a file asking wich type of validation file should it use or something to avoid this, it works ok when its for page update but not when its for page insert taking the initial value from the validation form fields, when this happens the html editor shows those tags or quot wich is a pain in the a....

ok, thanks for the input, I will log this as a bug so the engineers can look into the problem.

Originally Said By: Jason Byrnes

  ok, thanks for the input, I will log this as a bug so the engineers can look into the problem.  

Just ran smack dab into this same issue with Form Toolkit and HTML Editor - is there a fix yet?

No, there is not a fix for this issue at this time.

it has been logged to be investigated by the engineering team.

FYI - changing the same line of code also fixed the issue for me, not sure what else it has caused but it has fixed this issue. ;o)

I just spent another 20 minutes looking for the solution to this issue - can this PLEASE make it into a Known Issues chunk on the downloads page and be posted as a stickey until the Known Issue is fixed???

:)

i have added a sticky thread:
showthread.php?p=89936#post89936

Thanks Jason,

Is there any way that a policy can be set that these stickies get created anytime a Known Issue is found - at least until they are officially fixed?

Thanks.