Gravity Forms + Custom Post Types - Version 3.1.21

Version Description

  • Fixed a compatibility issue with Gravity Forms 2.5 and Enhanced UI.
Download this release

Release Info

Developer claygriffiths
Plugin Icon wp plugin Gravity Forms + Custom Post Types
Version 3.1.21
Comparing to
See all releases

Code changes from version 3.1.20 to 3.1.21

Files changed (4) hide show
  1. gfcptaddon.php +2 -2
  2. gfcptaddonbase.php +6 -4
  3. js/tag-it.init.js +14 -21
  4. readme.txt +261 -257
gfcptaddon.php CHANGED
@@ -3,7 +3,7 @@
3
  Plugin Name: Gravity Forms + Custom Post Types
4
  Plugin URI: https://gravitywiz.com/
5
  Description: Map your Gravity-Forms-generated posts to a custom post type and/or custom taxonomies.
6
- Version: 3.1.20
7
  Author: Gravity Wiz
8
  Author URI: https://gravitywiz.com/
9
  License: GPL2
@@ -16,7 +16,7 @@ class GFCPTAddon {
16
 
17
  private static $name = 'Gravity Forms + Custom Post Types';
18
  private static $slug = 'GFCPTAddon';
19
- private static $version = '3.1.20';
20
  private static $min_gravityforms_version = '1.9.3';
21
 
22
  //Plugin starting point. Will load appropriate files
3
  Plugin Name: Gravity Forms + Custom Post Types
4
  Plugin URI: https://gravitywiz.com/
5
  Description: Map your Gravity-Forms-generated posts to a custom post type and/or custom taxonomies.
6
+ Version: 3.1.21
7
  Author: Gravity Wiz
8
  Author URI: https://gravitywiz.com/
9
  License: GPL2
16
 
17
  private static $name = 'Gravity Forms + Custom Post Types';
18
  private static $slug = 'GFCPTAddon';
19
+ private static $version = '3.1.21';
20
  private static $min_gravityforms_version = '1.9.3';
21
 
22
  //Plugin starting point. Will load appropriate files
gfcptaddonbase.php CHANGED
@@ -137,15 +137,17 @@ if ( ! class_exists( 'GFCPTAddonBase' ) ) {
137
  var gfcptCurrentInputs = ' . json_encode( $inputs ) . ';
138
  for ( input in gfcptCurrentInputs ) {
139
  if( gfcptCurrentInputs.hasOwnProperty( input ) ) {
140
- gfcpt_tag_inputs.tag_inputs.push( gfcptCurrentInputs[ input ] );
141
  }
142
  }
143
  var gfcptCurrentTaxonomies = ' . json_encode( $taxonomies ) . ';
144
  for ( taxonomy in gfcptCurrentTaxonomies ) {
145
  if( gfcptCurrentTaxonomies.hasOwnProperty( taxonomy ) ) {
146
- gfcpt_tag_taxonomies[ taxonomy ] = gfcptCurrentTaxonomies[ taxonomy ];
147
  }
148
- }';
 
 
149
 
150
 
151
  GFFormDisplay::add_init_script( $form['id'], 'gfcpt_tagit', GFFormDisplay::ON_PAGE_RENDER, $script );
@@ -619,4 +621,4 @@ if ( ! class_exists( 'GFCPTAddonBase' ) ) {
619
  }
620
 
621
  }
622
- }
137
  var gfcptCurrentInputs = ' . json_encode( $inputs ) . ';
138
  for ( input in gfcptCurrentInputs ) {
139
  if( gfcptCurrentInputs.hasOwnProperty( input ) ) {
140
+ gfcpt_tag_inputs.tag_inputs.push( gfcptCurrentInputs[ input ] );
141
  }
142
  }
143
  var gfcptCurrentTaxonomies = ' . json_encode( $taxonomies ) . ';
144
  for ( taxonomy in gfcptCurrentTaxonomies ) {
145
  if( gfcptCurrentTaxonomies.hasOwnProperty( taxonomy ) ) {
146
+ gfcpt_tag_taxonomies[ taxonomy ] = gfcptCurrentTaxonomies[ taxonomy ];
147
  }
148
+ }
149
+ init_tagit_script();
150
+ ';
151
 
152
 
153
  GFFormDisplay::add_init_script( $form['id'], 'gfcpt_tagit', GFFormDisplay::ON_PAGE_RENDER, $script );
621
  }
622
 
623
  }
624
+ }
js/tag-it.init.js CHANGED
@@ -1,23 +1,16 @@
1
 
2
- var sampleTags = ['c++', 'java', 'php', 'coldfusion', 'javascript', 'asp', 'ruby', 'python', 'c', 'scala', 'groovy', 'haskell', 'perl', 'erlang', 'apl', 'cobol', 'go', 'lua'];
3
-
4
- ( function( $ ) {
5
-
6
- $( document ).bind( 'gform_post_render', function() {
7
-
8
- /* Temporary fix due to jQuery version issue */
9
- jQuery.curCSS = jQuery.css;
10
-
11
- $.each( gfcpt_tag_inputs.tag_inputs, function() {
12
- $( this.input ).tagit( {
13
- availableTags: gfcpt_tag_taxonomies[ this.taxonomy ],
14
- removeConfirmation: true,
15
- allowSpaces: true,
16
- animate: false
17
- } );
18
- } );
19
-
20
- } );
21
-
22
- } )( jQuery );
23
 
1
 
2
+ var init_tagit_script = function() {
3
+ /* Temporary fix due to jQuery version issue */
4
+ jQuery.curCSS = jQuery.css;
5
+
6
+ jQuery.each( gfcpt_tag_inputs.tag_inputs, function() {
7
+ jQuery( this.input ).tagit( {
8
+ availableTags: gfcpt_tag_taxonomies[ this.taxonomy ],
9
+ removeConfirmation: true,
10
+ allowSpaces: true,
11
+ animate: false
12
+ } );
13
+ } );
14
+
15
+ };
 
 
 
 
 
 
 
16
 
readme.txt CHANGED
@@ -1,257 +1,261 @@
1
- === Gravity Forms + Custom Post Types ===
2
- Contributors: spivurno,claygriffiths,bradvin,wpsmith
3
- Donate link: http://gravitywiz.com/
4
- Tags: form,forms,gravity,gravity form,gravity forms,CPT,custom post types,custom post type,taxonomy,taxonomies
5
- Requires at least: 3.0.1
6
- Tested up to: 5.7
7
- Stable tag: 3.1.16
8
-
9
- Map your Gravity-Forms-generated posts to a custom post type and/or custom taxonomies.
10
-
11
- = Introduction =
12
-
13
- This plugin is an add-on for [Gravity Forms](http://gravityforms.com). Make sure you visit [GravityWiz.com](http://gravitywiz.com/blog/) for more **free** Gravity Forms resources. And if you're looking to the largest collection of Gravity Forms plugins, check out [Gravity Perks](http://gravityperks.com).
14
-
15
- = Description =
16
-
17
- Gravity Forms allows you to create posts from a form submission using special Post Fields. By default, the submitted form will be created as a standard WordPress post. This plugin allows you to change the post type of the generated post. **No code required!** This plugin also provides the ability to assign the generated post to a custom taxonomy.
18
-
19
- Need to update posts? Learn [how to update posts with Gravity Forms](https://gravitywiz.com/how-to-update-posts-with-gravity-forms/).
20
-
21
- = Features =
22
-
23
- - Map posts to a custom post type
24
- - Map posts to a custom taxonomy (via Drop Down, Multi-select, Radio Button or Checkbox field)
25
- - Map posts to multiple taxonomies
26
- - Visual hierarchy support for hierarchical taxonomies (Drop Down field only)
27
- - Populate a Drop Down with posts
28
- - Assign parent post for generated post (Drop Down field only)
29
- - Single Line Text field support for taxonomies (enter as a comma-delimited list: term a, term b, term c)
30
- - Enhanced UI support for Single Line Text fields (see screenshots)
31
-
32
- = How to map a form to a custom post type =
33
-
34
- 1. Add a Post Title field to your form and click on it to open the field settings.
35
- 2. Below the "Description" field setting, you will find the "Post Type" setting.
36
- 3. Select the desired post type from the drop down (default is "Posts").
37
-
38
- = How to link a field to a custom taxonomy =
39
-
40
- 1. Add the desired field to which the custom taxonomy should be mapped. Drop Down, Multi Select, Radio Buttons and Checkboxes fields are current supported.
41
- 2. Open the field settings by clicking on the field and click on the "Advanced" tab.
42
- 3. Check the "Populate with a Taxonomy" checkbox.
43
- 4. Select the desired taxonomy from the drop down that appears.
44
-
45
- = How to link the saved post to taxonomies using a single line text field =
46
-
47
- Single Line Text fields are a great way to allow users to select existing taxonomy terms and to also add new terms.
48
-
49
- 1. Add a Single Line Text field to your form.
50
- 2. Open the field settings by clicking on the field and click on the "Advanced" tab.
51
- 3. Check the "Save to Taxonomy" checkbox.
52
- 4. Select the desired taxonomy from the drop down that appears.
53
- 5. (optional) Check the "Enable Enhanced UI" checkbox to enable an awesome tag-input style UI (see screenshots).
54
-
55
- Note: If the user inputs exising term names, the generated post will be assigned these terms. If the user inputs term names that do not exist, these terms will be added to the selected taxonomy and the generated post will also be assigned these terms.
56
-
57
- = How to set a parent post with the drop down field =
58
-
59
- When populating a Drop Down field with a post type, you may wish to set the selected post as the parent post for the generated post.
60
-
61
- 1. Add A Drop Down field to your form.
62
- 2. Click on the field to open the field settings. Then click on the "Advanced" tab.
63
- 3. Check the "Populate with Post Type" checkbox.
64
- 4. Select the desired post type from the drop down that appears. Be sure to select the **same post type** for which the post is being generated.
65
-
66
- == Installation ==
67
-
68
- 1. Upload the plugin folder 'gravity-forms-custom-post-types' to your `/wp-content/plugins/` folder
69
- 2. Activate the plugin through the 'Plugins' menu in WordPress
70
- 3. Make sure you also have Gravity Forms activated.
71
-
72
- == Screenshots ==
73
-
74
- 1. Frontend: Example of mapping to a custom post type and multiple taxonomies
75
- 2. Frontend: Example of hierarchical taxonomy support
76
- 3. Setting: Mapping to a custom post type
77
- 4. Setting: Mapping a field to a custom taxonomy
78
- 5. Setting: Assigning generated post to selected parent post
79
- 6. Frontend: Example of Single Line Text field with Enhanced UI enabled
80
- 7. Setting: Mapping a Single Line Text field to a taxonomy (and enabling Enhanced UI)
81
-
82
- == Changelog ==
83
-
84
- = 3.1.20 =
85
-
86
- * Fixed PHP notice on Gravity Forms Coupons Add-On page.
87
- * Fixed PHP warning when populating taxonomies.
88
- * Updated formatting of PHP files in plugin to better conform to the WordPress Coding Standards.
89
-
90
- = 3.1.19 =
91
-
92
- * Bumped plugin version.
93
-
94
- = 3.1.18 =
95
-
96
- * Fixed issue with "Save To Taxonomy" setting not properly saving the entered taxonomy.
97
-
98
- = 3.1.17 =
99
-
100
- * Readme updates.
101
-
102
- = 3.1.16 =
103
-
104
- * Readme updates.
105
-
106
- = 3.1.15 =
107
-
108
- * Fixed issue when exporting taxonomy-and-post-type-populated Checkbox fields.
109
- * Updated how scripts are enqueued.
110
- * Tested with 5.5.1.
111
-
112
- = 3.1.14 =
113
-
114
- * Updated how taxonomy enhanced UI script and data were loaded.
115
-
116
- = 3.1.13 =
117
-
118
- * Added 'gfcpt_hierarchical_display' filter to allow filtering whether to display choices hierarchically.
119
-
120
- = 3.1.12 =
121
-
122
- * Fixed issue with GF 2.3 where taxonomies were not correctly saved on submission.
123
-
124
- = 3.1.11 =
125
-
126
- * Fixed issue where dynamic placeholder was duplicated in some instances.
127
-
128
- = 3.1.10 =
129
-
130
- * Fixed issue where dynamic placeholder was added even when default placeholder was specified.
131
-
132
- = 3.1.9 =
133
-
134
- * Added support for displaying Post Title on entry list, detail and export for fields populated with a post type.
135
- * Updated default sort order for pages to "menu_order".
136
-
137
- = 3.1.8 =
138
-
139
- * Fixed issue mapping taxonomies for Single Line Text fiela and Multi Select fields. Thanks, Cameron!
140
-
141
- = 3.1.7 =
142
-
143
- * Added support for displaying term label on Entry List and Export views (rather than term ID; does not work with Checkbox and Multi-select on Entry List).
144
-
145
- = 3.1.6 =
146
-
147
- * Added support for displaying term label on Entry Detail view (rather than term ID)
148
-
149
- = 3.1.5 =
150
-
151
- * Fixed issue with populating Drop Down & Multi Selects
152
- * Fixed issue when saving Multi Select taxonomies
153
-
154
- = 3.1.4 =
155
-
156
- * Updated plugin header information.
157
-
158
- = 3.1.3 =
159
-
160
- * Fixed compatibility issue with Gravity Forms: Post Updates plugin; custom taxonomies were not being saved.
161
-
162
- = 3.1.2 =
163
-
164
- * Fixed issue where setting first option was not possible due to typo in property name
165
- * Updated how GFCPTAddon::get_base_path() method retrieves the base path
166
-
167
- = 3.1.1 =
168
- * Updated all calls to get_post_types() to use plugin-specific version which applies the 'gfcpt_post_type_args' filter. Props: mgratch
169
- * Updated all calls to get_taxonomies() to use plugin-specific version which applies the 'gfcpt_tax_args' filter. Props: mgratch
170
- * Fixed issue where missing script dependency caused tag-style entry of terms was not working. Props: mgratch
171
- * Fixed issue where plugin's registration of GF preview styles was overwriting all other preview styles
172
- * Fixed issue where taxonomies were not saved for delayed payment entries
173
- * Updated Tag init JS to be bound to the 'gform_post_render' JS event which better supports other plugin integrations
174
- * Updated Tag init JS file to be loaded in the footer
175
- * Added 'gfcpt_get_posts_args' filter to allow modifying the posts that are populated into a field
176
-
177
- = 3.1 =
178
- * Added "gfcpt_taxonomy_args" filter to allow modifying the arguments used to retrieve taxonomy terms
179
- * Added "gfcpt_post_type_args" filter to allow modifying the arguments used to retrive post types for selection in field settings
180
- * Updated verbiage throughout plugin and readme.txt file
181
- * Updated minimum required version of Gravity Forms to 1.9.3
182
- * Updated "Save As Post Type" to be "Post Type" and moved location to standard settings tab
183
- * Updated jQuery UI enqueue to use version from WP core
184
- * Updated GFCPTAddonBase::load_taxonomy_hierarchical() method to support only displaying children of a parent term (requires "gfcpt_taxonomy_args" filter)
185
- * Fixed styling issues with Enhanced-UI-enabled Single Line Text fields
186
- * Fixed notice where get_base_path() was called statically by changing function to be static
187
- * Fixed issue where taxonomy select on Drop Down field settings would not populate the selected taxonomy correctly
188
- * Fixed issue with GF 1.9 where indirect modfiication of $field['inputs'] property had no effect; resolves issues using custom taxonomies with Checkbox fields
189
-
190
- = 3.0.1 =
191
- * Fixed minor bug causing a PHP warning (_FILE_)
192
- * removed the restriction of not including scripts when a call is ajax
193
-
194
- = 3.0 =
195
- * Removed support for Gravity Forms v1.4.5. Now supports v1.5 and up (including 1.6)
196
- * Added support for single line text fields
197
- * Added ability to populate a dropdown with posts
198
- * Added ability to set a parent post when saving a post form
199
- * Multiselect control now supports "populate with taxonomy" too
200
- * "first value" default overriden when populating with a taxonomy
201
- * Shows taxonomy selections when designing the form
202
- * Fixed support for conditional logic
203
- * Previews now load taxonomy terms
204
- * Previews can show enhanced UI (only in V1.6 and above)
205
-
206
- = 2.0 =
207
- * Added support for both Gravity Forms v1.5 beta and v.1.4.5
208
- * Now supports linking taxonomies to Drop Downs, Multiple Choice or Checkboxes
209
- * Integrated with GF v1.5 hooks for easier configuration (thanks to Alex and Carl from RocketGenius)
210
- * Support linking more than 1 taxonomy to a form
211
- * To keep in line with the GF standards, mapping a form to a CPT in GF v1.4.5 can now be done via the 'post title' field
212
-
213
- = 1.0 =
214
- * Initial Relase. First version.
215
-
216
- == Frequently Asked Questions ==
217
-
218
- = Does this plugin rely on anything? =
219
- Yes, you need to install the [Gravity Forms plugin](http://gwiz.io/gravityforms) for this plugin to work.
220
-
221
- = How do I map a form to a custom post type? =
222
-
223
- 1. Add a Post Title field to your form and click on it to open the field settings.
224
- 2. Below the "Description" field setting, you will find the "Post Type" setting.
225
- 3. Select the desired post type from the drop down (default is "Posts").
226
-
227
- = How do I link a field to a custom taxonomy? =
228
-
229
- 1. Add the desired field to which the custom taxonomy should be mapped. Drop Down, Multi Select, Radio Buttons and Checkboxes fields are current supported.
230
- 2. Open the field settings by clicking on the field and click on the "Advanced" tab.
231
- 3. Check the "Populate with a Taxonomy" checkbox.
232
- 4. Select the desired taxonomy from the drop down that appears.
233
-
234
- = How do I link the saved post to taxonomies using a single line text field? =
235
-
236
- Single Line Text fields are a great way to allow users to select existing taxonomy terms and to also add new terms.
237
-
238
- 1. Add a Single Line Text field to your form.
239
- 2. Open the field settings by clicking on the field and click on the "Advanced" tab.
240
- 3. Check the "Save to Taxonomy" checkbox.
241
- 4. Select the desired taxonomy from the drop down that appears.
242
- 5. (optional) Check the "Enable Enhanced UI" checkbox to enable an awesome tag-input style UI (see screenshots).
243
-
244
- Note: If the user inputs exising term names, the generated post will be assigned these terms. If the user inputs term names that do not exist, these terms will be added to the selected taxonomy and the generated post will also be assigned these terms.
245
-
246
- = How do I set a parent post with the drop down field? =
247
-
248
- When populating a Drop Down field with a post type, you may wish to set the selected post as the parent post for the generated post.
249
-
250
- 1. Add A Drop Down field to your form.
251
- 2. Click on the field to open the field settings. Then click on the "Advanced" tab.
252
- 3. Check the "Populate with Post Type" checkbox.
253
- 4. Select the desired post type from the drop down that appears. Be sure to select the **same post type** for which the post is being generated.
254
-
255
- == Upgrade Notice ==
256
-
257
- Please note, Gravity Forms 1.9.3 is now required.
 
 
 
 
1
+ === Gravity Forms + Custom Post Types ===
2
+ Contributors: spivurno,claygriffiths,bradvin,wpsmith
3
+ Donate link: http://gravitywiz.com/
4
+ Tags: form,forms,gravity,gravity form,gravity forms,CPT,custom post types,custom post type,taxonomy,taxonomies
5
+ Requires at least: 3.0.1
6
+ Tested up to: 5.7
7
+ Stable tag: 3.1.16
8
+
9
+ Map your Gravity-Forms-generated posts to a custom post type and/or custom taxonomies.
10
+
11
+ = Introduction =
12
+
13
+ This plugin is an add-on for [Gravity Forms](http://gravityforms.com). Make sure you visit [GravityWiz.com](http://gravitywiz.com/blog/) for more **free** Gravity Forms resources. And if you're looking to the largest collection of Gravity Forms plugins, check out [Gravity Perks](http://gravityperks.com).
14
+
15
+ = Description =
16
+
17
+ Gravity Forms allows you to create posts from a form submission using special Post Fields. By default, the submitted form will be created as a standard WordPress post. This plugin allows you to change the post type of the generated post. **No code required!** This plugin also provides the ability to assign the generated post to a custom taxonomy.
18
+
19
+ Need to update posts? Learn [how to update posts with Gravity Forms](https://gravitywiz.com/how-to-update-posts-with-gravity-forms/).
20
+
21
+ = Features =
22
+
23
+ - Map posts to a custom post type
24
+ - Map posts to a custom taxonomy (via Drop Down, Multi-select, Radio Button or Checkbox field)
25
+ - Map posts to multiple taxonomies
26
+ - Visual hierarchy support for hierarchical taxonomies (Drop Down field only)
27
+ - Populate a Drop Down with posts
28
+ - Assign parent post for generated post (Drop Down field only)
29
+ - Single Line Text field support for taxonomies (enter as a comma-delimited list: term a, term b, term c)
30
+ - Enhanced UI support for Single Line Text fields (see screenshots)
31
+
32
+ = How to map a form to a custom post type =
33
+
34
+ 1. Add a Post Title field to your form and click on it to open the field settings.
35
+ 2. Below the "Description" field setting, you will find the "Post Type" setting.
36
+ 3. Select the desired post type from the drop down (default is "Posts").
37
+
38
+ = How to link a field to a custom taxonomy =
39
+
40
+ 1. Add the desired field to which the custom taxonomy should be mapped. Drop Down, Multi Select, Radio Buttons and Checkboxes fields are current supported.
41
+ 2. Open the field settings by clicking on the field and click on the "Advanced" tab.
42
+ 3. Check the "Populate with a Taxonomy" checkbox.
43
+ 4. Select the desired taxonomy from the drop down that appears.
44
+
45
+ = How to link the saved post to taxonomies using a single line text field =
46
+
47
+ Single Line Text fields are a great way to allow users to select existing taxonomy terms and to also add new terms.
48
+
49
+ 1. Add a Single Line Text field to your form.
50
+ 2. Open the field settings by clicking on the field and click on the "Advanced" tab.
51
+ 3. Check the "Save to Taxonomy" checkbox.
52
+ 4. Select the desired taxonomy from the drop down that appears.
53
+ 5. (optional) Check the "Enable Enhanced UI" checkbox to enable an awesome tag-input style UI (see screenshots).
54
+
55
+ Note: If the user inputs exising term names, the generated post will be assigned these terms. If the user inputs term names that do not exist, these terms will be added to the selected taxonomy and the generated post will also be assigned these terms.
56
+
57
+ = How to set a parent post with the drop down field =
58
+
59
+ When populating a Drop Down field with a post type, you may wish to set the selected post as the parent post for the generated post.
60
+
61
+ 1. Add A Drop Down field to your form.
62
+ 2. Click on the field to open the field settings. Then click on the "Advanced" tab.
63
+ 3. Check the "Populate with Post Type" checkbox.
64
+ 4. Select the desired post type from the drop down that appears. Be sure to select the **same post type** for which the post is being generated.
65
+
66
+ == Installation ==
67
+
68
+ 1. Upload the plugin folder 'gravity-forms-custom-post-types' to your `/wp-content/plugins/` folder
69
+ 2. Activate the plugin through the 'Plugins' menu in WordPress
70
+ 3. Make sure you also have Gravity Forms activated.
71
+
72
+ == Screenshots ==
73
+
74
+ 1. Frontend: Example of mapping to a custom post type and multiple taxonomies
75
+ 2. Frontend: Example of hierarchical taxonomy support
76
+ 3. Setting: Mapping to a custom post type
77
+ 4. Setting: Mapping a field to a custom taxonomy
78
+ 5. Setting: Assigning generated post to selected parent post
79
+ 6. Frontend: Example of Single Line Text field with Enhanced UI enabled
80
+ 7. Setting: Mapping a Single Line Text field to a taxonomy (and enabling Enhanced UI)
81
+
82
+ == Changelog ==
83
+
84
+ = 3.1.21 =
85
+
86
+ * Fixed a compatibility issue with Gravity Forms 2.5 and Enhanced UI.
87
+
88
+ = 3.1.20 =
89
+
90
+ * Fixed PHP notice on Gravity Forms Coupons Add-On page.
91
+ * Fixed PHP warning when populating taxonomies.
92
+ * Updated formatting of PHP files in plugin to better conform to the WordPress Coding Standards.
93
+
94
+ = 3.1.19 =
95
+
96
+ * Bumped plugin version.
97
+
98
+ = 3.1.18 =
99
+
100
+ * Fixed issue with "Save To Taxonomy" setting not properly saving the entered taxonomy.
101
+
102
+ = 3.1.17 =
103
+
104
+ * Readme updates.
105
+
106
+ = 3.1.16 =
107
+
108
+ * Readme updates.
109
+
110
+ = 3.1.15 =
111
+
112
+ * Fixed issue when exporting taxonomy-and-post-type-populated Checkbox fields.
113
+ * Updated how scripts are enqueued.
114
+ * Tested with 5.5.1.
115
+
116
+ = 3.1.14 =
117
+
118
+ * Updated how taxonomy enhanced UI script and data were loaded.
119
+
120
+ = 3.1.13 =
121
+
122
+ * Added 'gfcpt_hierarchical_display' filter to allow filtering whether to display choices hierarchically.
123
+
124
+ = 3.1.12 =
125
+
126
+ * Fixed issue with GF 2.3 where taxonomies were not correctly saved on submission.
127
+
128
+ = 3.1.11 =
129
+
130
+ * Fixed issue where dynamic placeholder was duplicated in some instances.
131
+
132
+ = 3.1.10 =
133
+
134
+ * Fixed issue where dynamic placeholder was added even when default placeholder was specified.
135
+
136
+ = 3.1.9 =
137
+
138
+ * Added support for displaying Post Title on entry list, detail and export for fields populated with a post type.
139
+ * Updated default sort order for pages to "menu_order".
140
+
141
+ = 3.1.8 =
142
+
143
+ * Fixed issue mapping taxonomies for Single Line Text fiela and Multi Select fields. Thanks, Cameron!
144
+
145
+ = 3.1.7 =
146
+
147
+ * Added support for displaying term label on Entry List and Export views (rather than term ID; does not work with Checkbox and Multi-select on Entry List).
148
+
149
+ = 3.1.6 =
150
+
151
+ * Added support for displaying term label on Entry Detail view (rather than term ID)
152
+
153
+ = 3.1.5 =
154
+
155
+ * Fixed issue with populating Drop Down & Multi Selects
156
+ * Fixed issue when saving Multi Select taxonomies
157
+
158
+ = 3.1.4 =
159
+
160
+ * Updated plugin header information.
161
+
162
+ = 3.1.3 =
163
+
164
+ * Fixed compatibility issue with Gravity Forms: Post Updates plugin; custom taxonomies were not being saved.
165
+
166
+ = 3.1.2 =
167
+
168
+ * Fixed issue where setting first option was not possible due to typo in property name
169
+ * Updated how GFCPTAddon::get_base_path() method retrieves the base path
170
+
171
+ = 3.1.1 =
172
+ * Updated all calls to get_post_types() to use plugin-specific version which applies the 'gfcpt_post_type_args' filter. Props: mgratch
173
+ * Updated all calls to get_taxonomies() to use plugin-specific version which applies the 'gfcpt_tax_args' filter. Props: mgratch
174
+ * Fixed issue where missing script dependency caused tag-style entry of terms was not working. Props: mgratch
175
+ * Fixed issue where plugin's registration of GF preview styles was overwriting all other preview styles
176
+ * Fixed issue where taxonomies were not saved for delayed payment entries
177
+ * Updated Tag init JS to be bound to the 'gform_post_render' JS event which better supports other plugin integrations
178
+ * Updated Tag init JS file to be loaded in the footer
179
+ * Added 'gfcpt_get_posts_args' filter to allow modifying the posts that are populated into a field
180
+
181
+ = 3.1 =
182
+ * Added "gfcpt_taxonomy_args" filter to allow modifying the arguments used to retrieve taxonomy terms
183
+ * Added "gfcpt_post_type_args" filter to allow modifying the arguments used to retrive post types for selection in field settings
184
+ * Updated verbiage throughout plugin and readme.txt file
185
+ * Updated minimum required version of Gravity Forms to 1.9.3
186
+ * Updated "Save As Post Type" to be "Post Type" and moved location to standard settings tab
187
+ * Updated jQuery UI enqueue to use version from WP core
188
+ * Updated GFCPTAddonBase::load_taxonomy_hierarchical() method to support only displaying children of a parent term (requires "gfcpt_taxonomy_args" filter)
189
+ * Fixed styling issues with Enhanced-UI-enabled Single Line Text fields
190
+ * Fixed notice where get_base_path() was called statically by changing function to be static
191
+ * Fixed issue where taxonomy select on Drop Down field settings would not populate the selected taxonomy correctly
192
+ * Fixed issue with GF 1.9 where indirect modfiication of $field['inputs'] property had no effect; resolves issues using custom taxonomies with Checkbox fields
193
+
194
+ = 3.0.1 =
195
+ * Fixed minor bug causing a PHP warning (_FILE_)
196
+ * removed the restriction of not including scripts when a call is ajax
197
+
198
+ = 3.0 =
199
+ * Removed support for Gravity Forms v1.4.5. Now supports v1.5 and up (including 1.6)
200
+ * Added support for single line text fields
201
+ * Added ability to populate a dropdown with posts
202
+ * Added ability to set a parent post when saving a post form
203
+ * Multiselect control now supports "populate with taxonomy" too
204
+ * "first value" default overriden when populating with a taxonomy
205
+ * Shows taxonomy selections when designing the form
206
+ * Fixed support for conditional logic
207
+ * Previews now load taxonomy terms
208
+ * Previews can show enhanced UI (only in V1.6 and above)
209
+
210
+ = 2.0 =
211
+ * Added support for both Gravity Forms v1.5 beta and v.1.4.5
212
+ * Now supports linking taxonomies to Drop Downs, Multiple Choice or Checkboxes
213
+ * Integrated with GF v1.5 hooks for easier configuration (thanks to Alex and Carl from RocketGenius)
214
+ * Support linking more than 1 taxonomy to a form
215
+ * To keep in line with the GF standards, mapping a form to a CPT in GF v1.4.5 can now be done via the 'post title' field
216
+
217
+ = 1.0 =
218
+ * Initial Relase. First version.
219
+
220
+ == Frequently Asked Questions ==
221
+
222
+ = Does this plugin rely on anything? =
223
+ Yes, you need to install the [Gravity Forms plugin](http://gwiz.io/gravityforms) for this plugin to work.
224
+
225
+ = How do I map a form to a custom post type? =
226
+
227
+ 1. Add a Post Title field to your form and click on it to open the field settings.
228
+ 2. Below the "Description" field setting, you will find the "Post Type" setting.
229
+ 3. Select the desired post type from the drop down (default is "Posts").
230
+
231
+ = How do I link a field to a custom taxonomy? =
232
+
233
+ 1. Add the desired field to which the custom taxonomy should be mapped. Drop Down, Multi Select, Radio Buttons and Checkboxes fields are current supported.
234
+ 2. Open the field settings by clicking on the field and click on the "Advanced" tab.
235
+ 3. Check the "Populate with a Taxonomy" checkbox.
236
+ 4. Select the desired taxonomy from the drop down that appears.
237
+
238
+ = How do I link the saved post to taxonomies using a single line text field? =
239
+
240
+ Single Line Text fields are a great way to allow users to select existing taxonomy terms and to also add new terms.
241
+
242
+ 1. Add a Single Line Text field to your form.
243
+ 2. Open the field settings by clicking on the field and click on the "Advanced" tab.
244
+ 3. Check the "Save to Taxonomy" checkbox.
245
+ 4. Select the desired taxonomy from the drop down that appears.
246
+ 5. (optional) Check the "Enable Enhanced UI" checkbox to enable an awesome tag-input style UI (see screenshots).
247
+
248
+ Note: If the user inputs exising term names, the generated post will be assigned these terms. If the user inputs term names that do not exist, these terms will be added to the selected taxonomy and the generated post will also be assigned these terms.
249
+
250
+ = How do I set a parent post with the drop down field? =
251
+
252
+ When populating a Drop Down field with a post type, you may wish to set the selected post as the parent post for the generated post.
253
+
254
+ 1. Add A Drop Down field to your form.
255
+ 2. Click on the field to open the field settings. Then click on the "Advanced" tab.
256
+ 3. Check the "Populate with Post Type" checkbox.
257
+ 4. Select the desired post type from the drop down that appears. Be sure to select the **same post type** for which the post is being generated.
258
+
259
+ == Upgrade Notice ==
260
+
261
+ Please note, Gravity Forms 1.9.3 is now required.