p01: I've found the "bug" with encoding, and now I'm getting nicely encoded messages with special chars :]
Want to know solution ?
PLEASE INSERT COIN
hihii
Problem was caused by your tools functions.
I had no idea whatfor you are converting chars to entities, and encode utf-8 ... into utf8 using an array.
Solution
Get rid of function utf8_encode_r($array) and function htmlentities_r($array)
Or just don't call them at all in below variables
K, problem with encoding solved.
But I've been hit with big dose of procrastination, and solving captcha img problem is up to you
btw. 3 additional things for your "todo" list:
1.custom subject as a parameter - to let users know that e-mail came from their contact form
2. handler informing user that message has been successfully sent - I didn't get any "you were lucky to successfully send me an e-mail" info
3. try to secure the form from history_back, put a timer or do anything to prevent resending message in a given period of time
edit: ohhh oscim found out earlier, so I didn't see his reply
But "base64_encode" is a must, and I wouldn't get rid of it, if this whole thing should work correctly
oscim: fix captcha img if you're such php geeko
Want to know solution ?
PLEASE INSERT COIN
hihii
Problem was caused by your tools functions.
I had no idea whatfor you are converting chars to entities, and encode utf-8 ... into utf8 using an array.
Solution
Get rid of function utf8_encode_r($array) and function htmlentities_r($array)
Or just don't call them at all in below variables
Code:
$forms_data[$form_id]['fields'] = stripslashes_r($_POST['contact']);
$fields = $form_data['fields'];
K, problem with encoding solved.
But I've been hit with big dose of procrastination, and solving captcha img problem is up to you
btw. 3 additional things for your "todo" list:
1.custom subject as a parameter - to let users know that e-mail came from their contact form
2. handler informing user that message has been successfully sent - I didn't get any "you were lucky to successfully send me an e-mail" info
3. try to secure the form from history_back, put a timer or do anything to prevent resending message in a given period of time
edit: ohhh oscim found out earlier, so I didn't see his reply
But "base64_encode" is a must, and I wouldn't get rid of it, if this whole thing should work correctly
oscim: fix captcha img if you're such php geeko
Addons: blue business theme, Online Visitors, Notepad