Versions

php-feedback-form.zip (2013-08-13) (Downloaded 255 times)

Contains:

  • PHP feedback form (item-action) - v. 2.4.7
  • PHP feedback form (page-action) - v. 2.4.7
  • PHP Feedback Form Recipients List (item-action) - v. 2.4.7

Compatible: Pro 3.5, Pro 4, Pro 5, Pro 5.5, Pro 6, Express 3.5, Express 4, Express 5, Express 5.5, and Express 6

php-feedback-form.zip (2013-01-10) (Downloaded 6 times)

Contains:

  • PHP feedback form (item-action) - v. 2.4.5
  • PHP feedback form (page-action) - v. 2.4.5
  • PHP Feedback Form Recipients List (item-action) - v. 2.4.5

Compatible: Pro 3.5, Pro 4, Pro 5, Pro 5.5, Pro 6, Express 3.5, Express 4, Express 5, Express 5.5, and Express 6

php-feedback-form.zip (2012-05-08) (Downloaded 2 times)

Contains:

  • PHP feedback form (item-action) - v. 2.4.4
  • PHP feedback form (page-action) - v. 2.4.4
  • PHP Feedback Form Recipients List (item-action) - v. 2.4.4

Compatible: Pro 3.5, Pro 4, Pro 5, Pro 5.5, Express 3.5, Express 4, Express 5, and Express 5.5

PHPFeedbackForm237.zip (2011-04-05) (Downloaded 2 times)

Contains:

  • PHP feedback form (item-action) - v. 2.3.7
  • PHP feedback form (page-action) - v. 2.3.7
  • PHP Feedback Form Recipients List (item-action) - v. 2.3.7

Compatible: Pro 4, Pro 5, Express 4, and Express 5

PHP Feedback Form (2009-12-21) (Downloaded 6 times)

Contains:

Compatible: Pro 3.5, Pro 4, Pro 5, Express 4, and Express 5

PHP Feedback Form (2009-04-09) (Downloaded 3 times)

Contains:

Compatible: Pro 3.5, Pro 4, Pro 5, Express 4, and Express 5

Author: Tim Plumb

The easiest way to create powerful, secure and flexible feedback forms for Freeway. You design it - the action will send it!

PHP feedback Form 2.x requires a server that runs PHP version 4.1.0 or higher.

Demo

Purchase

20 Comments

Tim, I don't see v 2.0 anywhere, the page is still downloading 1.9.6. - T.

Is there a posibility to adjust the action according to ones special requirements? e.g. i would like to ad a second bcc recipient.

how is working it??

ok is working good:)

Hi Sverker, Thanks for the comment. I've just replied to your email and suggested that you change the names of the name and email fields into English. At the moment the Action only looks for these special fields in English, however this is something I'm keen to change at a later date.

Version 2.3.7 adds a few bug fixes and a new recipients list Action allowing users to specify who gets the resulting email. For example; http://www.freewayactions.com/test/php-feedback-form-recipient-list/

Simply attach the "PHP Feedback Form Recipients List" action to a menu item that lists the department names and email addresses.

Release notes; 2.3.4 - Fixed an issue with the ini_smtp_server setting not getting set correctly 2.3.5 - Added support for targeting the form submission when defining the success or error links 2.3.6 - Fixed an issue where using the GoDaddy option didn't correctly set the form action 2.3.7 - Added support for adding recipients via a drop down menu using the "PHP Feedback Form Recipients List" action

Version 2.4.4 offers a number of bug fixes and improvements over the previous version of the Action including;

2.3.8: Added support for https checking in not in domain checks.

2.3.9: Changed the encoding type of the resulting email from ISO-8859-1 to UTF-8 to allow for accented characters. Removed slashed out quotes (o'clock for example) that were appearing in the resulting email

2.4.0: Added IP address blocking. Enter the IP addresses of the form users you want to block directly in the Action.

2.4.1: Added a fallback method to get the remote IP address if register globals is turned off.

2.4.2: Corrected a mistake where the IP address was incorrectly displayed in the resulting email.

2.4.3: Replaced eregi for preg_match in the header injection checking code as eregi is deprecated from PHP 5.3.0

2.4.4: Added a check to see if the item action is applied to an inflow item. There appears to be a bug in Freeway that causes the Action to create multiple copies of the -go.php file when attached to inflow items. Apply the Action to a parent item or the page.

I just updated from 2.3.3 to 2.4.4. Very pleased to see that the UTF-8 code page is working! (Great help for us scandinavians). HOWEVER - now the validation and error does not seem to work. The scrip even send empty messages!! WHY?

Version 2.4.5:

Added the ignore empty fields feature.

When checked this option will, as the name suggests, ignore all data fields that don't contain a value. If you've a large form with this option enabled your resulting email will only contain information filled out by the user and none of the empty fields.

Version 2.4.7:

Added support for two 'email' fields to verify the email address is correct. Redirects the user to the 'error' page if not.

The PHP code now checks for entity encoded comments and redirects the user to the spam trap (mock success page) if it finds them.

I'm getting an error message when the form is sent saying it didn't send. But it is actually sending to the recipient. Is this something that was fixed with the new version? I downloaded the latest version (2.4.7) but the old version (2.3.7) is still showing in my Freeway action window. I followed the instructions for installing but I think it didn't work. Any ideas?

Hi Diane, If you are seeing the old version still in Freeway then you'll need to manually locate the old Action and install the new version in its place; http://www.softpress.com/kb/questions/122/Installing+Actions+in+Freeway

Thanks. I got the updated software but it didn't solve the problem I'm having. When I submit the form an error message comes up in the browser (PHP Notice: Undefined index: name in \boswinfs02homeuserswebb1969ez.armandmfgadminrfpmedprod-go.php on line 104). I'm thinking that there might have been a change to the server since it just started happening. Any ideas of what I can do? (It's not a GoDaddy account)

I have solved the problem. I had originally named the files with a .php extension (I think that was the requirement when I built these a few years ago). I changed the extension to .html. I also recreated new contact fields (name, email) I left the rest of the form fields as they were. I also created a new submit button. Lastly, I changed the PHP feedback form setting to "no reply". I'm not exactly sure what fixed the problem but it's fixed. phew!

<img src=/"http://www.packos.de&quot;/>

<img src=&quot;http://www.packos.de&quot;/>

Hey Tim

I have noticed som spam email s coming in from one of my clients feedback form. Is there something I can do about this?? thx so much Carla

Hi Carla,

Switch on the Spam Trap and Track IP address features. If you are lucky the spammer will be using a static or limited range of IP addresses which you can then add back into the Action. These IP addresses are simply ignored if the spammer tries to use the form again.

The Spam Trap feature will insert a 'honey trap' into the form that should catch out most automated scripts that try and spam you as well.

Regards, Tim.

Thx so much Tim

I checked both options.. I know I am not able to test it from here so hopefully it will do the job thx! Carla

Tim,

Been using the form for a while now .. no known issues , however over the last few months it has been noticed that if the recipient address is a Google address there is a very high possibility that the email will never get to the recipient, and it is not in Spam. I have tried sending the email to an email address associated with the domain, which works but when i forward the email onto the client who has a gmail account the same thing happens… no email get through. According to the hosting company they have logs that confirm that the emails are being sent and also that Google servers accepted them.

It appears to me that Google is sensitive about the Domain name, but i have tried setting up search filters within Gmail of the recipients address so that all emails with the domain name are never sent to spam… but with no luck.

Have you heard of anything like this before please? if you need more info i can provide… thx

John

Sign In or Sign Up to comment.