Google Forms - Version 0.33

Version Description

No known upgrade issues.

Release Info

Developer	mpwalsh8
Plugin	Google Forms
Version	0.33
Comparing to
See all releases

Code changes from version 0.32 to 0.33

Files changed (2) hide show

index.php +2 -2
readme.txt +5 -2

index.php CHANGED Viewed

	@@ -4,8 +4,8 @@
4	* Plugin Name: WordPress Google Form
5	* Plugin URI: http://michaelwalsh.org/wordpress/wordpress-plugins/wpgform/
6	* Description: Add Google Forms to a WordPress web site. Display a Google Form directly into your posts, pages or sidebar. Style the Google Form to match your existing theme and display a custom confirmation page after form submission.
7	- * Version: 0.31
8	- * Build: 0.31.$WCREV$
9	* Last Modified: $WCDATE$
10	* Author: Mike Walsh
11	* Author URI: http://www.michaelwalsh.org


4	* Plugin Name: WordPress Google Form
5	* Plugin URI: http://michaelwalsh.org/wordpress/wordpress-plugins/wpgform/
6	* Description: Add Google Forms to a WordPress web site. Display a Google Form directly into your posts, pages or sidebar. Style the Google Form to match your existing theme and display a custom confirmation page after form submission.
7	+ * Version: 0.33
8	+ * Build: 0.33.$WCREV$
9	* Last Modified: $WCDATE$
10	* Author: Mike Walsh
11	* Author URI: http://www.michaelwalsh.org

readme.txt CHANGED Viewed

	@@ -4,7 +4,7 @@ Donate link: https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_i
4	Tags: Google Forms, Google Docs, Google, Spreadsheet, shortcode, forms
5	Requires at least: 3.0
6	Tested up to: 3.4.1
7	- Stable tag: 0.32
8
9	Embeds a published, public Google Form in a WordPress post, page, or widget.
10
	@@ -63,7 +63,7 @@ Google Forms include plenty of [CSS](http://en.wikipedia.org/wiki/Cascading_Styl
63
64	There a number of reasons to get a 403 error but by far the most common one encountered so far is due to ModSecurity being installed by your web hosting provider. Not all providers deploy ModSecurity but enough do that it comes up every once in a while. If your provider is running ModSecurity and your version of the plugin is v0.30 or lower, you will likely see odd behavior where when the form is submitted, the page is simply rendered again and the data is never actually sent to Google. There isn't any error message to indicate what might be wrong.
65
66	- Version 0.32 fixes this problem for most cases but there is still a chance that it could crop up. If your provider has enabled ModSecurity AND someone answers one of the questions on your form with a URL (e.g. http://www.example.com), then very likely ModSecurity will kick in an issue a 403 error. The plugin is now smart enough to detect when the error is issued and let you know what is wrong. Unfortunately there isn't currently a solution to allow URLs as responses when ModSecurity issues a 403 error.
67
68	= No matter what I do, I always get the "Unable to retrieve Google Form. Please try reloading this page." error message. Why is this? =
69
	@@ -192,6 +192,9 @@ No known upgrade issues.
192
193	== Changelog ==
194



195	= Version 0.32 =
196	* New option to control Bcc to blog admin when using email notification. By default this option is enabled to allow plugin to behave as it has in prior versions.
197	* Fixed bug in processing default plugin settings which are on by default. New options which are on by default were not recognized.


4	Tags: Google Forms, Google Docs, Google, Spreadsheet, shortcode, forms
5	Requires at least: 3.0
6	Tested up to: 3.4.1
7	+ Stable tag: 0.33
8
9	Embeds a published, public Google Form in a WordPress post, page, or widget.
10

63
64	There a number of reasons to get a 403 error but by far the most common one encountered so far is due to ModSecurity being installed by your web hosting provider. Not all providers deploy ModSecurity but enough do that it comes up every once in a while. If your provider is running ModSecurity and your version of the plugin is v0.30 or lower, you will likely see odd behavior where when the form is submitted, the page is simply rendered again and the data is never actually sent to Google. There isn't any error message to indicate what might be wrong.
65
66	+ Version 0.31 fixes this problem for most cases but there is still a chance that it could crop up. If your provider has enabled ModSecurity AND someone answers one of the questions on your form with a URL (e.g. http://www.example.com), then very likely ModSecurity will kick in an issue a 403 error. The plugin is now smart enough to detect when the error is issued and let you know what is wrong. Unfortunately there isn't currently a solution to allow URLs as responses when ModSecurity issues a 403 error.
67
68	= No matter what I do, I always get the "Unable to retrieve Google Form. Please try reloading this page." error message. Why is this? =
69

192
193	== Changelog ==
194
195	+ = Version 0.33 =
196	+ * Fixed inacuracies in ReadMe.txt file.
197	+
198	= Version 0.32 =
199	* New option to control Bcc to blog admin when using email notification. By default this option is enabled to allow plugin to behave as it has in prior versions.
200	* Fixed bug in processing default plugin settings which are on by default. New options which are on by default were not recognized.