Getting JavaScript Error With SecurityAssist Email Encrypted Password Dialogue Box

Hello Jason,

I am getting javascript error when I try to save changes in Email Encrypted Password Dialogue box. This only started yesterday and am at a lost as to why its happening. I even unistalled DB DE eCart and Freetool and re-installed to see if that resolves the problem but to no avail. I have deleted the WinCache.dat file and restarted Dreamweaver and that did not solve the problem. Would I need to re-install Dreamweaver again if some of the configuration settings are corrupted?

The Error message reads: Error applying: TypeError: defn has no properties

Please see attached image for visual confirmation.

What do I do?

I am also getting an error when testing out the forgot password page. I have seen similar posts on the issue and tried suggested solutions but to no avail. Upon clicking send I get this error message:

Warning: Cannot modify header information - headers already sent by (output started at /home3/username/public_html/client-access/forgotpassword.php:136) in /home3/username/public_html/webassist/security_assist/helper_php.php on line 289

See attached image.

Please help!

This is a bug that I have logged in our system, we will have it corrected in the next update, I will let you know when that becomes available.


the headers already sent error means there is out put to the page before the code to redirect.


the error says the problem is at line 136:
output started at /home3/username/public_html/client-access/forgotpassword.php:136

send a copy of the page please.

Thanks Jason, please find attached a copy of the the forgotpassword page.

line 135 has a blank space at the end:

"?> "

i include the quotes to illustrate the space. Delete the blank space at the end of line 135

I have deleted the blank space and it works fine now.

In respect of the other issue, I will wait for the next update of DB.

Thanks Jason.

you're welcome.

Im also getting this error is the update out already? or a way to get it fix in the mean time?

we hope to release an update this week to address this problem. I don't have a work around in the mean time though.