I'm a bit perplexed.

I have a form I built using WFB 2.3.5217 and is working just fine. You can view it here: http://www.sammconsulting.com/Agency-Br … uyers.html

My client wanted it updated. So I opened up the file made some changes to the form and re-uploaded it to the server. The current form is built using WFB 2.5.5437. However now when I go to submit the form it gives me a 500 internal server error. The only thing I changed was by adding some new fields to the form and the notification email that the user gets. I cannot for the life of me figure out why the form wont work.

Link to newer page not working: http://www.sammconsulting.com/Agency-Br … yers2.html

I even paired down the form to a smaller basic form and its not working. Link here: http://www.sammconsulting.com/demoform.html

The current PHP version on server is 5.4.24 so I don't think that's the issue.

Any ideas as to why it might not be working?

A few things:

1. You are on a much older version of Form Builder. You should be on 2.4
2. You have PHP 5.2 installed, not 5.4:

http://www.sammconsulting.com/general-c … ertest.php

Hey Scott,

My current version of WBF is 2.5 build 5437. When I built the form originally, I was using an older version.

The older build is working fine using my current version of PHP (as you can see by the 1st link). Its the new build that is not. So are you saying I should move the PHP back to 5.2 and the current build should work?

Version 2.3 requires PHP 5.2, Version 2.5 requires PHP 5.3.

This form fails because you are running the wrong version of PHP.
http://www.sammconsulting.com/buyers-fo … ertest.php

Hey Scott,

That's strange as it says I'm using version 5.4.43 in Cpanel. I went into PHPconfig and chose version 5.4 to use.

I tried the simple demo (link#3) and it is still not working. Going to check with my host.

http://www.sammconsulting.com/buyers-fo … ertest.php

Still shows 5.2.17 for me. You might need to adjust your php.ini file.

Is the domain your having issues with an addon domain? They can have separate php.ini files.

Hey Eric,

No, it's not a subdomain but that is a good idea and will keep that in mind if I have a future issue.

As Scott mentioned, it was the php.ini file that didn't get updated. I had the correct php version but for some reason that file was messed up on the server. The host was able to fix it within less than a minute.