Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
#61 2007-11-08 18:07:20
- kevinmcdougall
- Member
- Registered: 2007-02-08
- Posts: 55
Re: zem_contact_reborn 4.0.3.20
OK ruud, any chance you could enlighten me as to what does? Postmaster maybe? If so, then maybe the post should be moved over there instead.
Offline
Re: zem_contact_reborn 4.0.3.20
I have no idea what inserts it.
Offline
#63 2007-11-08 18:35:22
- kevinmcdougall
- Member
- Registered: 2007-02-08
- Posts: 55
Re: zem_contact_reborn 4.0.3.20
And there was me getting all hopeful… ;)
Offline
Re: zem_contact_reborn 4.0.3.20
What about sticking file with the mail? Or some js-framework wich will upload file to server, then send form with pre-inserted link to file? :)
P.S. OMG, what dumn errors through the post… fixed :)
Last edited by the_ghost (2007-11-14 20:46:56)
Providing help in hacking ATM! Come to courses and don’t forget to bring us notebook and hammer! What for notebook? What a kind of hacker you are without notebok?
Offline
Re: zem_contact_reborn 4.0.3.20
Hello, I’m installing this plugin for a friend but had some trouble. Details below. Any suggestions?
Fatal error: Call to undefined function: is_valid_email() in /nfs/cust/2/22/72/527222/web/textpattern/lib/txplib_misc.php(459) : eval()'d code on line 480
pap_contact_cleaner 0.1
zem_contact_lang 4.0.3.6
zem_contact_reborn 4.0.3.20
Textpattern · 4.0.3
Is zem_contact still compatible with TxP 4.0.3? I’m afraid they don’t have the skills or resources to upgrade at this time.
thanks…
Offline
Re: zem_contact_reborn 4.0.3.20
Edit the plugin and add this at the bottom, that should be enough to restore 4.0.3 compatibility (you’ll have to remove it again when upgrading):
function is_valid_email($address)
{
return preg_match('/^[a-z0-9](\.?[a-z0-9_+%-])*@([a-z0-9](-*[a-z0-9])*\.)+[a-z]{2,6}$/i', $address);
}
Having said that… people really should upgrade. TXP 4.0.4 was released more than a year ago. TXP 4.0.5 has been available for half a year. Both fix security bugs.
Offline
Re: zem_contact_reborn 4.0.3.20
I have a very simple form:
<txp:zem_contact to=“recipient@myclient.com” subject=“myclient.com website registration” thanks=“Thank-you: your registration has been sent.” redirect=“registered”>
<txp:zem_contact_email /><br />
<txp:zem_contact_text label=“First Name” /><br />
<txp:zem_contact_text label=“Surname” /><br />
<txp:zem_contact_text label=“Company” /><br />
<txp:zem_contact_submit label=“Send your registration info” />
</txp:zem_contact>
Problem is, whether I specify a from attribute or not, the “Reply-To” field of the resulting email is anonymous@myclient.com and not the sender’s email. This is causing myclient’s email system to reject the email – it “fails the sender verification check”.
Any idea of what might be happening? I tried editing the $reply variable in the plug-in code to my email address, but to no avail:
Still “Reply-To: anonymous@myclient.com
Thanks – this one is driving me crazy.
Offline
Re: zem_contact_reborn 4.0.3.20
If that anonymous email address was neither specified in the plugin code, nor in the ZCR tag attributes, nor in in the user input, then it’s the mailserver that adds the address => contact your webhost.
Offline
Re: zem_contact_reborn 4.0.3.20
Thanks, Ruud.
You’ve given me the ammunition I need… web-hosters, here I come!
Offline
Re: zem_contact_reborn 4.0.3.20
Is there any way to override zem_contact send_article so that it always sends the whole article and not an extract (if it exists?)
Doug.
Offline
Re: zem_contact_reborn 4.0.3.20
ruud wrote:
If that anonymous email address was neither specified in the plugin code, nor in the ZCR tag attributes, nor in in the user input, then it’s the mailserver that adds the address => contact your webhost.
update:
The web-host shot back that we need to specify a ‘Return-Path’. I spliced one into the plug-in and so far it appears to be working…
Offline
Re: zem_contact_reborn 4.0.3.20
That webhost should read the relevant RFCs that specify that the Return-Path must be inserted by the final recipient SMTP server, not by the sending client. But hey, if it works for you ;)
Offline