Just applied the Protector v3.04 (which I love BTW) and it WHITE-SCREENED by development site.

PHP Version 4.3.9
MySQL Version 5.0.27
XOOPS Version 2.0.16

I traced the hangup on my system to 'postcheck.inc.php' @ 33 with the echo statement. I changed to die instead.

Suspect this may be a problem with my php.ini options; but not sure which one. Obviously we don't want exploit broadcast on a production. Any1 have idea on possible INI problem that isn't printing error to screen as designed; or is there a more graceful way of disclosing the error (e.g. in the Protector log).

TIA

Is it "White screen" instead of a message against phpmailer?

Anyway, Protector does not make your site white by the setting of php.ini

If you mean the message against phpmailer, just overwirte class/mail/phpmailer* by security patch from xoops.org

Yes it's White Screen instead of message against phpmailer.

I didn't think Protector would WHITE my site due to php.ini; but suspected that maybe I had some non-safe settings that might not allow the echo from within the function => a white screen.

BTW, I have patch for phpmailer already; but had setting in Preferences to use SendMail.

Anyway, you'd better display the error message by debug mode.

Check these settings in php.ini: display_errors and log_errors.

If display_errors is Off and log_errors is On, then PHP diagnostics will be output to the PHP log file but not displayed.

For a public site, it's recommended to set display_errors = Off.

Looks like it was my .INI debug.printing the errors.
Thanks all.