Invalid "conditions" field "conditions" - not a string or array

[markalexandrov]

Does your script need php suexec or safe_mo off?

[russellr]

Hi,

FormMail doesn't need suexec enabled or safe_mode to be off.

Some advanced features might not work with safe_mode on, but that's not the issue here.

The issue is that a correct language structure doesn't work, namely:

foreach ($SomeArray as $value)
... 

FormMail uses this language structure in a lot of places, so just disabling an error message isn't a solution.

To assist you further, today we've downloaded and installed PHP 4.4.1 onto a test system.

We've run the bug.php script on this test system with PHP 4.4.1 and it works fine!

This explains why we haven't been able to find a report of this bug anywhere on the 'net.

This is not a bug in PHP 4.4.1. This is a bug in the PHP installed on your server!

I have no idea how your server can have a faulty PHP installation whereas 100's of thousands of other servers are fine.

But, that's what the evidence shows!

You need to contact your hosting provider and get them to fix the problem.

The work we've done for you makes it very easy for them to see the problem and to test the solution.

Whoever manages your server must fix the problem. Presumably you pay them many dollars per month, so it's reasonable for them to work on and fix the problem that we've identified for them.

Please let us know the outcome of your discussions with your hosting provider.

[markalexandrov]

I'm the hosting company.

And no, I do not agree with you that the php on my server is not OK.

Did you hear me, that I run more than 10 different huge php/mysql applicaitons on this server, including Lpanel, way more coplicated than your formmail WITH no error?

However, never mind that I liked your scpipt, I do not think it was made for higher that 4.3.1 verision of php, or there is another error therte. Don't really have the time to go thru your code, and that is why I paid you.

You missed as well, that I'm quite expericned, and I know exactly what is up :-)

Thanks for trying, obviusly is beyond your knowledge to fix this problem.

Regards,
Mark

Hi,

FormMail doesn't need suexec enabled or safe_mode to be off.

Some advanced features might not work with safe_mode on, but that's not the issue here.

The issue is that a correct language structure doesn't work, namely:

foreach ($SomeArray as $value)
... 

FormMail uses this language structure in a lot of places, so just disabling an error message isn't a solution.

To assist you further, today we've downloaded and installed PHP 4.4.1 onto a test system.

We've run the bug.php script on this test system with PHP 4.4.1 and it works fine!

This explains why we haven't been able to find a report of this bug anywhere on the 'net.

This is not a bug in PHP 4.4.1. This is a bug in the PHP installed on your server!

I have no idea how your server can have a faulty PHP installation whereas 100's of thousands of other servers are fine.

But, that's what the evidence shows!

You need to contact your hosting provider and get them to fix the problem.

The work we've done for you makes it very easy for them to see the problem and to test the solution.

Whoever manages your server must fix the problem. Presumably you pay them many dollars per month, so it's reasonable for them to work on and fix the problem that we've identified for them.

Please let us know the outcome of your discussions with your hosting provider.

[markalexandrov]

hey,

i think I fix it. there is no more condition error.

Unable to create check file "/tmp/fm911d43.txt": failed to open stream: Success.

The .txt file say - FormMail version check for identifier 'www.artesiagardens.com' at 09:28:22 21-Feb-2006.

This is I assume your vers check, but why do I get error? Any thoughts?

[russellr]

Hi,

How did you fix the conditions error? Did you re-install PHP? Maybe upgraded to 4.4.2?

Unable to create check file "/tmp/fm911d43.txt": failed to open stream: Success

Yes, it is the version check.

I've no idea why you're getting an error message for something that's succeeded. Other people have reported this occassionally and it's always a PHP problem of some sort (it's probably a bug in certain PHP versions). They usually just resort to switching off the version check.

Regarding your previous post, you don't have to go thru the code of FormMail.

Just go through the small bug.php script. It's very simple and it should work on every PHP installation.

When that works on your site, then the original problem will go away.

Your comments about FormMail are not true, BTW. One thing to realize is that FormMail is used on tens of thousands of servers: Windows, Linux, BSD, and Solaris and others, and on every version of PHP from 4.0.4 upwards.

Only your server has/had the problem with "foreach".

[markalexandrov]

How do I switch off the version check?

Hi,

How did you fix the conditions error? Did you re-install PHP? Maybe upgraded to 4.4.2?



Yes, it is the version check.

I've no idea why you're getting an error message for something that's succeeded. Other people have reported this occassionally and it's always a PHP problem of some sort (it's probably a bug in certain PHP versions). They usually just resort to switching off the version check.

Regarding your previous post, you don't have to go thru the code of FormMail.

Just go through the small bug.php script. It's very simple and it should work on every PHP installation.

When that works on your site, then the original problem will go away.

Your comments about FormMail are not true, BTW. One thing to realize is that FormMail is used on tens of thousands of servers: Windows, Linux, BSD, and Solaris and others, and on every version of PHP from 4.0.4 upwards.

Only your server has/had the problem with "foreach".

[russellr]

Hi,

How do I switch off the version check?

In the FormMail config section, change:

define("CHECK_FOR_NEW_VERSION",true); 

to

define("CHECK_FOR_NEW_VERSION",false); 

Are you going to tell us how you solve the "conditions error" problem?

[markalexandrov]

Sure it was the php, as we thought - 4.4.2 seem to fix it. Sorry for my premature judgement.

Do I miss something if I have the check_...",false? How often do you release updates? In other words, how often I should check back with you to make sure I have the latest versions.

I also, want to thank you for you time and support.

Mark

Hi,



In the FormMail config section, change:

define("CHECK_FOR_NEW_VERSION",true); 

to

define("CHECK_FOR_NEW_VERSION",false); 

Are you going to tell us how you solve the "conditions error" problem?

[russellr]

Hi,

Sure it was the php, as we thought - 4.4.2 seem to fix it. Sorry for my premature judgement.

That's interesting, thanks for letting us know. I'm just glad the problem is fixed!

Updates aren't regular - they are released when new features are added (and the occasional bug fix). It tends to be about 3 or 4 times a year.

BTW, I think the version check file you've got is old. I think what's happening is that you new version of PHP isn't allowing you to write to that file.

Can you remove all /tmp/fm*.txt files and re-enable the version check?

Then try submitting the form twice. If you get an error, tell me which occasion it happened. Also, post the output of this command:

ls -l /tmp/fm*.txt

[markalexandrov]

Thers is few (5 or 6) tmp files there... If I remove it - it giving me error, that the same file is missing ;-), otherwise OK!

I want to share something - someone is probing my server and along with other errors from the same I IP, I wanted to show you this
[client 71.247.63.30] Premature end of script headers: /home/arrowlm/public_html/sfm/sfm.php

:-) Thank you again!

PS. Can I ask a queston for the validation you provide?