Forums

Hi

A bit difficult to explain. My site is www,dev303.pmhu3a.org.au. I am having to run PHP 5.3 since 5.4 or 5.5 crashes.
I am using Bob's email control but when using PHP 5.3 I end up with this warning.
[attachment=2]ChronoPHP5.3.png[/attachment]
If I switch off the email plug in then the error does not appear.

Some research suggest that this is related to an earlier version of PHP.

However, if I switch to PHP 5.4 or PHP 5.5, then I hit this error.
[attachment=1]ChronoPHP5.5.png[/attachment]

If you try membership book on online when I am using 5.4 or 5.5. That only occurs if I pick a Chronoform screen.

Have you any suggestions as to the cause and fix for these?

Regards

Nick
ps currently i am running wiht 5.3. I can provide access to amin amdse tt 5.5 if you need me to.

Hi Nick,

This isn't anything that I've seen before. I looked at the punycode file and it appears to be used in converting UTF-8 Emails and URLs to and from PunyCode (and I've never heard of PunyCode before either).

I'm pretty certain that neither ChronoForms nor my Email action use this directly. It's possible that the Joomla! mailer calls this library when it spots a UTF-8 email address???

The message is just a Warning so setting your site error reporting to System Default or None should hide it and might fix the problem.

Bob

Hi Bob
Yes - as you say, i can disable the warning. My bigger worry is what is causing that encode error that arises when I switch to PHP 5.5. I will need to do that sometime. I have switched to 5.5 now so that you can see the problem if you try Membership|apply on line.

Nick

Hi Nick,

There are some suggestions in this StackOverFlow answer that might give you a clue. I suspect that this is something to do with server set up rather than directly from ChronoForms - though I guess it is possible that one or more of the CF files has a BOM code left in ???

Bob

I will look and see - thanks.

BOM code?
Nick

Hi Bob

Found reference to BOM and the checker. I haven;t checked all of my files but no sign of that as a problem

Thanks for the help. Looks like gzip is the problem. Now the question is why?

Nick