Gravity Wiz http://gravitywiz.com Magically enhanced tutorials, snippets and plugins for Gravity Forms! Tue, 21 May 2013 12:32:12 +0000 en-US hourly 1 http://wordpress.org/?v=3.5.1 GP Conditional Logic Dates, First Draft http://gravitywiz.com/gp-conditional-logic-dates-first-draft/?utm_source=rss&utm_medium=rss&utm_campaign=gp-conditional-logic-dates-first-draft http://gravitywiz.com/gp-conditional-logic-dates-first-draft/#comments Mon, 13 May 2013 06:58:38 +0000 David Smith http://gravitywiz.com/?p=1861 This new perk allows you show/hide fields based on the selected date in a Date field. It integrates with Gravity Forms’ default conditional logic UI. Select the date field and then enter the date you would like the condition to be based on. All perks require Gravity Perks. If you’d like to give this perk [...]

The post GP Conditional Logic Dates, First Draft appeared first on Gravity Wiz.

]]> This new perk allows you show/hide fields based on the selected date in a Date field. It integrates with Gravity Forms’ default conditional logic UI. Select the date field and then enter the date you would like the condition to be based on.

All perks require Gravity Perks. If you’d like to give this perk a shot, you will need a valid Gravity Perks license. Once Gravity Perks is installed, you will be able to download the GP Conditional Logic Dates v0.1 perk via the Manage Perks page.

Please note: This perk is a first draft. Do not use on a production site. Below is a list of limitations and some general information you should be aware of if you decide to take this perk for a spin.

  • Most importantly, this perk is possible via new hooks added in Gravity Forms 1.7.2.6. This version is not publicly available. Contact david[at]rocketgenius[dot]com with your Gravity Forms Support username to get the latest version of Gravity Forms. This perk will not work without GF v1.7.2.6 or greater.
  • Only Datepicker Date fields are currently supported.
  • Date value must be entered manually using the US date format: MM/DD/YYYY Example. Will add support for jQuery Datepicker for selecting the date value in future version.
  • Supported operators: “is”, “is not”, “greater than”, “less than”. These are the only operators which are intended to be supported. All other operators do not appear to be applicable to date-based conditional logic.
  • When using the “less than” operator, if the field should not be visible until a date is actually selected, you will need to add a second condition where the selected Date field is greater than 0. Example
  • Special conditional-logic-only merge tag supported: {today} Allows conditional logic to be applied to fields based on whether the selected date is, is not, is greater than or is less than the current date. Example

Upcoming Enhancements

  1. jQuery Datepicker support will be added for selected the conditional logic date value.
  2. Other Date field types (besides “Datepicker”) will be supported.
  3. More special conditional-logic-only merge tags to check if the current date is a weekend, weekday, or any specific day of the week.

Report any issues via the Support Form

The post GP Conditional Logic Dates, First Draft appeared first on Gravity Wiz.

]]> http://gravitywiz.com/gp-conditional-logic-dates-first-draft/feed/ 0 Subtotal Merge Tag (for Calculations) http://gravitywiz.com/subtotal-merge-tag-for-calculations/?utm_source=rss&utm_medium=rss&utm_campaign=subtotal-merge-tag-for-calculations http://gravitywiz.com/subtotal-merge-tag-for-calculations/#comments Thu, 18 Apr 2013 04:16:58 +0000 David Smith http://gravitywiz.com/?p=1800 Currently, there is no easy way to get the current total (let’s call it the subtotal) of the form for use in calculations. It’s possible but you’ll have to enter all of your product merge tags into a long and complicated formula to get the subtotal. This snippet helps you avoid that hassle by providing [...]

The post Subtotal Merge Tag (for Calculations) appeared first on Gravity Wiz.

]]> A simple (but hacky) way of getting the subtotal for your Gravity Form calculations.
view demo

Currently, there is no easy way to get the current total (let’s call it the subtotal) of the form for use in calculations. It’s possible but you’ll have to enter all of your product merge tags into a long and complicated formula to get the subtotal.

This snippet helps you avoid that hassle by providing a {subtotal} merge tag for use in your Gravity Form calculations.

Please note: The {subtotal} merge tag is only available in for fields that support calculations.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 
<?php
/**
* Calculation Subtotal Merge Tag 
* http://gravitywiz.com/
*/
class GWCalcSubtotal { 
    
    public static $merge_tag = '{subtotal}'; 
    
    function __construct() {
        
        // front-end
        add_filter( 'gform_pre_render', array( $this, 'maybe_replace_subtotal_merge_tag' ) );
        add_filter( 'gform_pre_submission_filter', array( $this, 'maybe_replace_subtotal_merge_tag' ) );
        
        // back-end
        add_filter( 'gform_admin_pre_render', array( $this, 'add_merge_tags' ) );
        
    }
    
    /**
    * Look for {subtotal} merge tag in form fields 'calculationFormula' property. If found, replace with the
    * aggregated subtotal merge tag string.
    * 
    * @param mixed $form
    */
    function maybe_replace_subtotal_merge_tag( $form ) {
        
        foreach( $form['fields'] as &$field ) {
            
            if( !self::has_subtotal_merge_tag( $field ) )
                continue;
            
            $subtotal_merge_tags = self::get_subtotal_merge_tag_string( $form, $field );
            $field['calculationFormula'] = str_replace( self::$merge_tag, $subtotal_merge_tags, $field['calculationFormula'] );
            
        }
        
        return $form;
    }
    
    /**
    * Get all the pricing fields on the form, get their corresponding merge tags and aggregate them into a formula that
    * will yeild the form's subtotal.
    * 
    * @param mixed $form
    */
    static function get_subtotal_merge_tag_string( $form, $current_field ) {
        
        $pricing_fields = self::get_pricing_fields( $form );
        $product_tag_groups = array();
        
        foreach( $pricing_fields['products'] as $product ) {
            
            $product_field = rgar( $product, 'product' );
            $option_fields = rgar( $product, 'options' );
            $quantity_field = rgar( $product, 'quantity' );
            
            // do not include current field in subtotal
            if( $product_field['id'] == $current_field['id'] )
                continue;
            
            $product_tags = GFCommon::get_field_merge_tags( $product_field );
            $quantity_tag = 1;
            
            // if a single product type, only get the "price" merge tag
            if( in_array( GFFormsModel::get_input_type( $product_field ), array( 'singleproduct', 'calculation' ) ) ) {
                
                // single products provide quantity merge tag
                if( empty( $quantity_field ) )
                    $quantity_tag = $product_tags[2]['tag'];
                
                $product_tags = array( $product_tags[1] );
            }
            
            // if quantity field is provided for product, get merge tag
            if( !empty( $quantity_field ) ) {
                $quantity_tag = GFCommon::get_field_merge_tags( $quantity_field );
                $quantity_tag = $quantity_tag[0]['tag'];
            }
            
            $product_tags = wp_list_pluck( $product_tags, 'tag' );
            $option_tags = array();
            
            foreach( $option_fields as $option_field ) {
                
                $new_options_tags = GFCommon::get_field_merge_tags( $option_field );
                if( !is_array( $new_options_tags ) )
                    continue;
                
                if( GFFormsModel::get_input_type( $option_field ) == 'checkbox' ) {
                    array_shift( $new_options_tags );    
                } else {
                    $new_options_tags = array( array_shift( $new_options_tags ) );
                }
                
                $option_tags = array_merge( $option_tags, $new_options_tags );
            }
            
            $option_tags = wp_list_pluck( $option_tags, 'tag' );
            
            $product_tag_groups[] = '( ( ' . implode( ' + ', array_merge( $product_tags, $option_tags ) ) . ' ) * ' . $quantity_tag . ' )';
            
        }
        
        $shipping_tag = 0;
        if( rgar( $pricing_fields, 'shipping' ) ) {
            $shipping_tag = GFCommon::get_field_merge_tags( rgars( $pricing_fields, 'shipping/0' ) );
            $shipping_tag = $shipping_tag[0]['tag'];
        }
        
        $pricing_tag_string = '( ( ' . implode( ' + ', $product_tag_groups ) . ' ) + ' . $shipping_tag . ' )';
        
        return $pricing_tag_string;
    }
    
    /**
    * Get all pricing fields from a given form object grouped by product and shipping with options nested under their 
    * respective products.
    * 
    * @param mixed $form
    */
    static function get_pricing_fields( $form ) {
    
        $product_fields = array();
 
        foreach( $form["fields"] as $field ) {
        
            if( $field["type"] != 'product' )
                continue;
                
            $option_fields = GFCommon::get_product_fields_by_type($form, array("option"), $field['id'] );
            
            // can only have 1 quantity field
            $quantity_field = GFCommon::get_product_fields_by_type( $form, array("quantity"), $field['id'] );
            $quantity_field = rgar( $quantity_field, 0 );
            
            $product_fields[] = array(
                'product' => $field,
                'options' => $option_fields,
                'quantity' => $quantity_field
                );
            
        }
 
        $shipping_field = GFCommon::get_fields_by_type($form, array("shipping"));
 
        return array( "products" => $product_fields, "shipping" => $shipping_field );
    }
    
    function add_merge_tags( $form ) {
        
        $label = __('Subtotal', 'gravityforms');
        
        ?>
        
        <script type="text/javascript">
            
            // for the future (not yet supported for calc field)
            gform.addFilter("gform_merge_tags", "gwcs_add_merge_tags");
            function gwcs_add_merge_tags( mergeTags, elementId, hideAllFields, excludeFieldTypes, isPrepop, option ) {
                console.log( elementId );
                mergeTags["pricing"].tags.push({ tag: '<?php echo self::$merge_tag; ?>', label: '<?php echo $label; ?>' });
                return mergeTags;
            }
            
            // hacky, but only temporary
            jQuery(document).ready(function($){
                
                var calcMergeTagSelect = $('#field_calculation_formula_variable_select');
                calcMergeTagSelect.find('optgroup').eq(0).append( '<option value="<?php echo self::$merge_tag; ?>"><?php echo $label; ?></option>' );
                
            });
            
        </script>
        
        <?php
        //return the form object from the php hook    
        return $form;
    }
    
    static function has_subtotal_merge_tag( $field ) {
        
        // check if form is passed
        if( isset( $field['fields'] ) ) {
            
            $form = $field;
            foreach( $form['fields'] as $field ) {
                if( self::has_subtotal_merge_tag( $field ) )
                    return true;
            }
            
        } else {
            
            if( isset( $field['calculationFormula'] ) && strpos( $field['calculationFormula'], self::$merge_tag ) !== false )
                return true;
                
        }
        
        return false;
    }
    
}
 
new GWCalcSubtotal();
view raw gistfile1.php This Gist brought to you by GitHub.

How do I install this snippet?

Easy peasy. Just copy and paste the code above into your theme's functions.php file.

How do I use this functionality?

This snippet will add a new “Subtotal” merge tag to the merge tag select available for the “Formula” setting on Calculation fields. Selecting this option will insert the {subtotal} merge tag into your “Formula” setting. You can then use all available mathematical operations available to this field to manipulate this subtotal as needed.

formula-subtotal-merge-tagFormula Setting: Subtotal Merge Tag
formula-subtotal-taxFormula Setting: Subtotal Used to Calculate Tax

The post Subtotal Merge Tag (for Calculations) appeared first on Gravity Wiz.

]]> http://gravitywiz.com/subtotal-merge-tag-for-calculations/feed/ 2 Use Gravity Forms Conditional Logic with Dates http://gravitywiz.com/use-gravity-forms-conditional-logic-with-dates/?utm_source=rss&utm_medium=rss&utm_campaign=use-gravity-forms-conditional-logic-with-dates http://gravitywiz.com/use-gravity-forms-conditional-logic-with-dates/#comments Fri, 01 Mar 2013 16:52:31 +0000 David Smith http://gravitywiz.com/?p=1466 You’re probably familiar with Gravity Forms conditional logic. That awesome feature that allows you to show or hide fields depending a set of custom conditions. One feature that isn’t yet support is date-based conditions. Or is it? This method will allow you to show or hide any field based on a date. You can configure [...]

The post Use Gravity Forms Conditional Logic with Dates appeared first on Gravity Wiz.

]]> A simple method for showing and hiding Gravity Form fields based on the current date.

You’re probably familiar with Gravity Forms conditional logic. That awesome feature that allows you to show or hide fields depending a set of custom conditions. One feature that isn’t yet support is date-based conditions. Or is it?

This method will allow you to show or hide any field based on a date. You can configure it to show/hide if that date has passed, has not passed or if you are currently on that date.

This tutorial is based on the following example. You are selling tickets to a conference. Tickets sold a week before the conference are $10. Tickets sold within a week of the conference are $15. Let’s dig in!

  1. The Code
  2. Setting Up Timestamp Field
  3. Setting Up Conditional Field

1. The Code

1 2 3 4 5 6 7 8 9 
<?php
/**
 * Use Gravity Forms Conditional Logic with Dates
 * http://gravitywiz.com/use-gravity-forms-conditional-logic-with-dates/
 */
add_filter("gform_field_value_timestamp", "gwiz_populate_timestamp");
function gwiz_populate_timestamp( $value ){
    return time();
}
view raw gistfile1.php This Gist brought to you by GitHub.

Copy and paste the above snippet into your theme’s functions.php file. This code enables you to populate a field on your form with the current date and time in the form of a UNIX timestamp.

It isn’t super important that you know what a UNIX timestamp is (the number of seconds since January 1, 1970) but it is important to understand that a timestamp is an integer. No weird date formatting just a really big number. For example, this post was published on March 1, 2013. The time stamp for this date is 1362117600.

Gravity Forms conditional logic can’t work with formatted dates but by converting the date into a number we can let Gravity Forms handle the rest.

2. Setting Up Time Stamp Field

Our timestamp snippet doesn’t do much on it’s own. We need to tell it which field to populate with the timestamp. Go ahead and open any form to which you would like to add this functionality and follow these steps:

  1. Add a new Hidden field and label it “Timestamp”
  2. Click on the “Advanced” tab to view the field’s advanced settings.
  3. Check the checkbox labeled “Allow Field to be Populated Dynamically”.
  4. Enabling the “Allow Field to be Populated Dynamically” option will reveal the “Parameter Name” input. Add this value timestamp.

Awesome! Now this field is configured to be dynamically populated with the current timestamp any time the form is viewed.

timestampTimestamp Field

3. Setting Up Conditional Field

Now it’s time for the fun part!

  1. Create another field that you would like to which you would like to apply the date-based conditional logic.
  2. Click on the “Advanced” tab to access the field’s advanced settings.
  3. Check the “Enable Conditional Logic” checkbox.
  4. Select the “Timestamp” field from the first drop down.
  5. Select “less than” or “greater than” from the operator drop down depending on your intent (more details below).
  6. Enter the timestamp for the date this condition is based on (more details below).

For our working example, we will have two product fields. One with the early bird pricing (any time a week before the event) and another for regular pricing (any time within a week of the event).

The event is on March 18, 2013. We want the pricing to be dependent on a date one week before the event, so March 8, 2013 is our “conditional date”. The timestamp for this date (set to midnight) is 1362700800. Based on that conditional date, here is how each field’s conditional logic would be configured:

early-bird-settingsEarly Bird Product Field
regular-settingsRegular Pricing Field

Should I use “less than”, “greater than”, or “is”?

If the field should show/hide if the current date is before the conditional date, you will want to use the “less than” operator.

If the field should show/hide if the current date is after the conditional date, you will want to use the “greater than” operator. You’ll note in the example, the regular pricing has an extra “is” clause. Without this, there would be one second at midnight on the conditional date that neither pricing field would display.

If the field should show/hide between two dates, you will need to create two conditions and use the “greater than” for the starting date condition and “less than” for the ending date condition.

How do I get a timestamp for my conditional date?

The conditional date will also need to be in the UNIX timestamp format. Use this online UNIX timestamp converter to convert the date you want to base your show/hide condition on to a timestamp. Once you have your timestamp, enter it into the last input on the condition row.

The post Use Gravity Forms Conditional Logic with Dates appeared first on Gravity Wiz.

]]> http://gravitywiz.com/use-gravity-forms-conditional-logic-with-dates/feed/ 9 Calculate Number of Days Between Two Dates http://gravitywiz.com/calculate-number-of-days-between-two-dates/?utm_source=rss&utm_medium=rss&utm_campaign=calculate-number-of-days-between-two-dates http://gravitywiz.com/calculate-number-of-days-between-two-dates/#comments Sat, 23 Feb 2013 03:11:30 +0000 David Smith http://gravitywiz.com/?p=1285 Have you ever needed to calculate the number of days between two given date fields? Here’s a scenario for consideration. Let’s say you have a Gravity Form set up to register users for a multi-day event. The user is able to select a start date and end date that they will be attending the event. [...]

The post Calculate Number of Days Between Two Dates appeared first on Gravity Wiz.

]]> Calculate the number of days between two given date fields and populate this number into a field on the form.
view demo

  • March 3, 2013: Updated to fix issue where "include_end_date" option was not working and added better support for different date formats.

  • March 2, 2013: Updated to support applying to multiple sets of date fields on the same form. Also updated to fix issue where functionality did not run when form was returned due to validation error.

  • March 15, 2013: Updated to fix issue when conditional logic was used on the form.

Have you ever needed to calculate the number of days between two given date fields? Here’s a scenario for consideration.

Let’s say you have a Gravity Form set up to register users for a multi-day event. The user is able to select a start date and end date that they will be attending the event. For each day of attendance they must pay an attendance fee of $10. How can we calculate the total price they should pay for registration?

This snippet will allow to calculate the number of days between two date fields and then populate the calculated number of days into another field. This is beneficial because with this calculated number of days now available as a field value, we can use Gravity Forms’ Calculation Product to correctly calculate the registration fee based on the selected dates.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 
<?php
/**
 * Calculate Number of Days via Two Date Fields
 * http://gravitywiz.com/calculate-number-of-days-between-two-dates/
 */
class GWDayCount {
 
    private static $script_output;
 
    function __construct( $args ) {
 
        extract( wp_parse_args( $args, array(
            'form_id'          => false,
            'start_field_id'   => false,
            'end_field_id'     => false,
            'count_field_id'   => false,
            'include_end_date' => true,
            ) ) );
 
        $this->form_id        = $form_id;
        $this->start_field_id = $start_field_id;
        $this->end_field_id   = $end_field_id;
        $this->count_field_id = $count_field_id;
        $this->count_adjust   = $include_end_date ? 1 : 0;
 
        add_filter( "gform_pre_render_{$form_id}", array( &$this, 'load_form_script') );
        add_action( "gform_pre_submission_{$form_id}", array( &$this, 'override_submitted_value') );
 
    }
 
    function load_form_script( $form ) {
        
        // workaround to make this work for < 1.7
        $this->form = $form;
        add_filter( 'gform_init_scripts_footer', array( &$this, 'add_init_script' ) );
        
        if( self::$script_output )
            return $form;
 
        ?>
 
        <script type="text/javascript">
 
        (function($){
 
            window.gwdc = function( options ) {
 
                this.options = options;
                this.startDateInput = $( '#input_' + this.options.formId + '_' + this.options.startFieldId );
                this.endDateInput = $( '#input_' + this.options.formId + '_' + this.options.endFieldId );
                this.countInput = $( '#input_' + this.options.formId + '_' + this.options.countFieldId );
 
                this.init = function() {
 
                    var gwdc = this;
 
                    // add data for "format" for parsing date
                    gwdc.startDateInput.data( 'format', this.options.startDateFormat );
                    gwdc.endDateInput.data( 'format', this.options.endDateFormat );
 
                    gwdc.populateDayCount();
 
                    $(document).on( 'change', '#' + this.startDateInput.attr('id') + ', #' + this.endDateInput.attr('id'), function(){
                        gwdc.populateDayCount();
                    });
 
                }
 
                this.getDayCount = function() {
 
                    var startDate = this.parseDate( this.startDateInput.val(), this.startDateInput.data('format') )
                    var endDate = this.parseDate( this.endDateInput.val(), this.endDateInput.data('format') );
                    var dayCount = 0;
 
                    if( !this.isValidDate( startDate ) || !this.isValidDate( endDate ) )
                        return '';
 
                    if( startDate > endDate ) {
                        return 0;
                    } else {
 
                        var diff = endDate - startDate;
                        dayCount = diff / ( 60 * 60 * 24 * 1000 ); // secs * mins * hours * milliseconds
                        dayCount = Math.round( dayCount ) + this.options.countAdjust;
 
                        return dayCount;
                    }
 
                }
 
                this.parseDate = function( value, format ) {
 
                    if( !value )
                        return false;
 
                    format = format.split('_');
                    var dateFormat = format[0];
                    var separators = { slash: '/', dash: '-', dot: '.' };
                    var separator = format.length > 1 ? separators[format[1]] : separators.slash;
                    var dateArr = value.split(separator);
 
                    switch( dateFormat ) {
                    case 'mdy':
                        return new Date( dateArr[2], dateArr[0] - 1, dateArr[1] );
                    case 'dmy':
                        return new Date( dateArr[2], dateArr[1] - 1, dateArr[0] );
                    case 'ymd':
                        return new Date( dateArr[0], dateArr[1] - 1, dateArr[2] );
                    }
 
                    return false;
                }
 
                this.populateDayCount = function() {
                    this.countInput.val( this.getDayCount() ).change();
                }
 
                this.isValidDate = function( date ) {
                    return !isNaN( Date.parse( date ) );
                }
 
                this.init();
 
            }
 
        })(jQuery);
 
        </script>
 
        <?php
        self::$script_output = true;
        return $form;
    }
    
    function add_init_script( $return ) {
        
        $start_field_format = false;
        $end_field_format = false;
 
        foreach( $this->form['fields'] as &$field ) {
 
            if( $field['id'] == $this->start_field_id )
                $start_field_format = $field['dateFormat'] ? $field['dateFormat'] : 'mdy';
 
            if( $field['id'] == $this->end_field_id )
                $end_field_format = $field['dateFormat'] ? $field['dateFormat'] : 'mdy';
 
        }
        
        $script = "new gwdc({
                formId:             {$this->form['id']},
                startFieldId:       {$this->start_field_id},
                startDateFormat:    '$start_field_format',
                endFieldId:         {$this->end_field_id},
                endDateFormat:      '$end_field_format',
                countFieldId:       {$this->count_field_id},
                countAdjust:        {$this->count_adjust}
            });";
        
        GFFormDisplay::add_init_script( $this->form['id'], 'gw_display_count_' . $this->count_field_id, GFFormDisplay::ON_PAGE_RENDER, $script );
        
        // remove filter so init script is not output on subsequent forms
        remove_filter( 'gform_init_scripts_footer', array( &$this, 'add_init_script' ) );
        
        return $return;
    }
 
    function override_submitted_value( $form ) {
 
        $start_date = false;
        $end_date = false;
 
        foreach( $form['fields'] as &$field ) {
 
            if( $field['id'] == $this->start_field_id )
                $start_date = self::parse_field_date( $field );
 
            if( $field['id'] == $this->end_field_id )
                $end_date = self::parse_field_date( $field );
 
        }
 
        if( $start_date > $end_date ) {
 
            $day_count = 0;
 
        } else {
 
            $diff = $end_date - $start_date;
            $day_count = $diff / ( 60 * 60 * 24 ); // secs * mins * hours
            $day_count = round( $day_count ) + $this->count_adjust;
 
        }
 
        $_POST["input_{$this->count_field_id}"] = $day_count;
 
    }
 
    static function parse_field_date( $field ) {
 
        $date_value = rgpost("input_{$field['id']}");
        $date_format = empty( $field['dateFormat'] ) ? 'mdy' : esc_attr( $field['dateFormat'] );
        $date_info = GFCommon::parse_date( $date_value, $date_format );
 
        return strtotime( "{$date_info['year']}-{$date_info['month']}-{$date_info['day']}" );
    }
 
}
 
new GWDayCount( array(
    'form_id'        => 16,
    'start_field_id' => 1,
    'end_field_id'   => 2,
    'count_field_id' => 4
    ) );
view raw gistfile1.php This Gist brought to you by GitHub.

How do I install this snippet?

Easy peasy. Just copy and paste the code above into your theme's functions.php file.

How do I use this functionality?

To use this snippet’s functionality just go directly below the snippet and instantiate the GWDayCount() class. Instantiate is a big word but all it means is that you’ll be creating a new “instance” of the GWDayCount() class with a set of parameters (aka options) for that specific instance.

Standard Usage

7 8 9 10 11 12 
new GWDayCount( array(
	'form_id'        => 9,
	'start_field_id' => 1,
	'end_field_id'   => 2,
	'count_field_id' => 3
	) );
view raw gistfile1.php This Gist brought to you by GitHub.

Count “Nights” Only
End date is not included in the day count so you are essentially counting the number of “nights” between the two dates.

14 15 16 17 18 19 20 
new GWDayCount( array(
	'form_id'          => 9,
	'start_field_id'   => 1,
	'end_field_id'     => 2,
	'count_field_id'   => 3,
	'include_end_date' => false
	) );
view raw gistfile1.php This Gist brought to you by GitHub.

Once you instantiated the class you are finished! If you would like to have this functionality on multiple forms then just create a new instance of the class and fill in the parameters for the new form. That’s it!

Parameter Details

  • form_id: The form ID of the form you would like to apply this functionality to.
  • start_field_id: The ID of the date field that will contain the start date. This field must be a date field and the parameter only holds a single field.
  • end_field_id: This parameter holds the ID of the date field that will contain the forms end date. This field, like the start_field_id field, must be a date field and only holds a single field ID.
  • count_field_id: This parameter holds the ID of the field that will be populated with the calculated number of days between the start date and end date.
  • include_end_date: Defaults to true. Set to this false if you would like to count only “nights” where the start date would be the check-in date and the end date would be the check-out date.

Points of Note

  • This is currently only setup to work with “Date Picker” date fields. Let me know if you need this with other types of date fields in the comments.

The post Calculate Number of Days Between Two Dates appeared first on Gravity Wiz.

]]> http://gravitywiz.com/calculate-number-of-days-between-two-dates/feed/ 18 Customizing Gravity Forms User Registration Activation Page http://gravitywiz.com/customizing-gravity-forms-user-registration-activation-page/?utm_source=rss&utm_medium=rss&utm_campaign=customizing-gravity-forms-user-registration-activation-page http://gravitywiz.com/customizing-gravity-forms-user-registration-activation-page/#comments Tue, 19 Feb 2013 15:00:21 +0000 David Smith http://gravitywiz.com/?p=1154 If you’ve checked out the latest beta for the Gravity Forms User Registration add-on, you might have noticed one of the awesome new features is “Pending Activations”. Here’s how they work. When the user signs up, instead of automatically being registered as a user on your WordPress site, an activation email is sent to the [...]

The post Customizing Gravity Forms User Registration Activation Page appeared first on Gravity Wiz.

]]> If you’ve checked out the latest beta for the Gravity Forms User Registration add-on, you might have noticed one of the awesome new features is “Pending Activations”. Here’s how they work.

When the user signs up, instead of automatically being registered as a user on your WordPress site, an activation email is sent to the email address they signed up with. The activation email contains an activation link. When the user clicks this link and visits the activation page, they are “activated” and their user account is registered.

One of the first things you’re probably going to want to do with this new feature is customize the activation page. This is the page where users land after clicking the activation link in the activation email. This walk-through aims to demonstrate how this activation page can be completely customized.

This process can be broken down into two simple steps:

  1. Create a custom activate.php template
  2. Override default activate.php template

1. Create a Custom activate.php Template

At the most basic level, all you need to do here is find the activate.php file in the GF User Registration plugin folder and place a copy of this file in your theme folder.

  • Path to GF User Registration activate.php file
    <root>/wp-content/plugins/gravityformsuserregistration/includes/activate.php
  • Sample path to your theme folder
    <root>/wp-content/themes/<your_theme>/

The issue with this is that the activate.php template really isn’t easy to customize. There are a lot of nested conditionals and special variables that you probably won’t understand without really digging in.

GW Activate Template

To alleviate some of this burden, I’ve created a special version of the activate.php which you can download and include in your theme which is much simpler to customize. The primary benefit is that it takes 99% of the HTML output that lives in the activate.php template and moves it out to easy-to-edit template parts.

GW Activate Template on GitHub

Just click the “zip” button to download all the template files. Once downloaded, unzip the gfur-activate-template-master.zip file. Inside you will find a gfur-activate-template-master folder. Rename this to “gfur-activate-template” and move this folder into your theme folder.

github-download-zipDownload GW Activate Template Files

The Different Views of Activation

There are several different “views” or “parts” of the activation page.

activate-success
Success
This is the default view that a user will see after clicking the activation link in the activation email. This view is handled by the activate-success.php template part.
activate-error-already-active
Error: Already Active
Occurs when a user attempts to activate an activation key which has already been activated. This view is handled by the activate-error.php template part.
activate-error
Error
If anything goes wrong during the activation (i.e. bad activation key, username already registered, etc), this view will handling displaying the error. This view is handled by the activate-error.php template part.
activate-no-key
No Key
It’s quite unlikely that users will see this view since the activation key is passed in the activation link; however, for the sake of completeness, this view is what the user will see if no activation key is passed in the activation link. This view is handled in the activate-no-key.php template part.

2. Overriding the Default Activation Template

With the template files in place, you’re ready to override the default activate template files to point to your custom files. Doing this is actually pretty simple. Just add this code to your theme’s functions.php file:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 
<?php
 
/**
* Custom Activation Template
* http://gravitywiz.com/2013/02/13/customizing-gravity-forms-user-registration-activation-page
*/
add_action('wp', 'custom_maybe_activate_user', 9);
function custom_maybe_activate_user() {
 
    $template_path = STYLESHEETPATH . '/gfur-activate-template/activate.php';
    
    if( !file_exists($template_path) || rgget('page') != 'gf_activation' )
        return;
    
    require_once( $template_path );
    
    exit();
}
view raw gistfile1.php This Gist brought to you by GitHub.

In plain speak, this code says: “Here is a path to the template file I’d like to use for my activation page. If this file exists and we’re on the GF User Registration activation page, go ahead and load my custom activation page file.”

If you’re using the GW Activate Template files and followed the instructions above, you won’t need to change this snippet at all. It’ll just work. Otherwise, you will need to change the $template_path variable to point to the location of your own custom activate.php file.

Anything else?

That’s it for now. Give it a go and let me know how it works out of you. I’m eager for any feedback you have!

The post Customizing Gravity Forms User Registration Activation Page appeared first on Gravity Wiz.

]]> http://gravitywiz.com/customizing-gravity-forms-user-registration-activation-page/feed/ 0 Multi-page Form Navigation http://gravitywiz.com/multi-page-navigation/?utm_source=rss&utm_medium=rss&utm_campaign=multi-page-navigation http://gravitywiz.com/multi-page-navigation/#comments Sat, 02 Feb 2013 17:10:47 +0000 David Smith http://gravitywiz.com/?p=1083 This snippet can add the multi-page form navigation functionality to any form with multiple pages. Only forms using the “Steps” progress indicator will have the page steps converted into page links. For forms using the “Progess Bar” or no progress indicator at all can still make use of this functionality by creating custom links using [...]

The post Multi-page Form Navigation appeared first on Gravity Wiz.

]]> Adds support for navigating between form pages by converting the page steps into page links or creating your own custom page links.
view demo

This snippet can add the multi-page form navigation functionality to any form with multiple pages. Only forms using the “Steps” progress indicator will have the page steps converted into page links. For forms using the “Progess Bar” or no progress indicator at all can still make use of this functionality by creating custom links using the custom page link formatting instructions below.

Currently, this functionality is setup so that the page links are not activated until the user reaches the final page of the form. Users can then navigate freely to any page using the page step links (displayed above the form).

After reaching the last page, navigating back to any form page will display a link: “Back to Last Page”. Clicking this link will (you guessed it!) take the user back to the last page.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 
<?php
/**
 * Multi-page Navigation
 * http://gravitywiz.com/
 */
 
class GWMultipageNavigation {
 
    private $script_displayed;
 
    function __construct( $args = array() ) {
 
        $form_ids = false;
        if( isset( $args['form_id'] ) ) {
            $form_ids = is_array( $args['form_id'] ) ? $args['form_id'] : array( $args['form_id'] );
        }
 
        if( !empty($form_ids) ) {
            foreach( $form_ids as $form_id ) {
                add_filter("gform_pre_render_{$form_id}", array( &$this, 'output_navigation_script' ), 10, 2 );
                //add_filter('gform_register_init_scripts', array( &$this, 'register_script') );
            }
        } else {
            add_filter('gform_pre_render', array( &$this, 'output_navigation_script' ), 10, 2 );
        }
 
    }
 
    function output_navigation_script( $form, $is_ajax ) {
 
        // only apply this to multi-page forms
        if( count($form['pagination']['pages']) <= 1 )
            return $form;
 
        $this->register_script( $form );
 
        if( $this->is_last_page( $form ) || $this->is_last_page_reached() ) {
            $input = '<input id="gw_last_page_reached" name="gw_last_page_reached" value="1" type="hidden" />';
            add_filter( "gform_form_tag_{$form['id']}", create_function('$a', 'return $a . '' . $input . '';' ) );
        }
 
        // only output the gwmpn object once regardless of how many forms are being displayed
        // also do not output again on ajax submissions
        if( $this->script_displayed || ( $is_ajax && rgpost('gform_submit') ))
            return $form;
 
        ?>
 
        <script type="text/javascript">
 
            (function($){
 
                window.gwmpnObj = function( args ) {
 
                    this.formId = args.formId;
                    this.formElem = jQuery('form#gform_' + this.formId);
                    this.currentPage = args.currentPage;
                    this.lastPage = args.lastPage;
                    this.labels = args.labels;
 
                    this.init = function() {
 
                        // if this form is ajax-enabled, we'll need to get the current page via JS
                        if( this.isAjax() )
                            this.currentPage = this.getCurrentPage();
 
                        if( !this.isLastPage() && !this.isLastPageReached() )
                            return;
 
                        var gwmpn = this;
                        var steps = $('form#gform_' + this.formId + ' .gf_step');
 
                        steps.each(function(){
 
                            var stepNumber = parseInt( $(this).find('span.gf_step_number').text() );
 
                            if( stepNumber != gwmpn.currentPage ) {
                                $(this).html( gwmpn.createPageLink( stepNumber, $(this).html() ) )
                                    .addClass('gw-step-linked');
                            } else {
                                $(this).addClass('gw-step-current');
                            }
 
                        });
 
                        if( !this.isLastPage() )
                            this.addBackToLastPageButton();
 
                        $(document).on('click', '#gform_' + this.formId + ' a.gwmpn-page-link', function(event){
                            event.preventDefault();
 
                            var hrefArray = $(this).attr('href').split('#');
                            if( hrefArray.length >= 2 ) {
                                var pageNumber = hrefArray.pop();
                                gwmpn.postToPage( pageNumber );
                            }
 
                        });
 
                    }
 
                    this.createPageLink = function( stepNumber, HTML ) {
                        return '<a href="#' + stepNumber + '" class="gwmpn-page-link">' + HTML + '</a>';
                    }
 
                    this.postToPage = function(page) {
                        this.formElem.append('<input type="hidden" name="gw_page_change" value="1" />');
                        this.formElem.find('input[name="gform_target_page_number_' + this.formId + '"]').val(page);
                        this.formElem.submit();
                    }
 
                    this.addBackToLastPageButton = function() {
                        this.formElem.find('#gform_page_' + this.formId + '_' + this.currentPage + ' .gform_page_footer')
                            .append('<input type="button" onclick="gwmpn.postToPage(' + this.lastPage + ')" value="' + this.labels.lastPageButton + '" class="button gform_last_page_button">');
                    }
 
                    this.getCurrentPage = function() {
                        return this.formElem.find( 'input#gform_source_page_number_' + this.formId ).val();
                    }
 
                    this.isLastPage = function() {
                        return this.currentPage >= this.lastPage;
                    }
 
                    this.isLastPageReached = function() {
                        return this.formElem.find('input[name="gw_last_page_reached"]').val() == true;
                    }
 
                    this.isAjax = function() {
                        return this.formElem.attr('target') == 'gform_ajax_frame_' + this.formId;
                    }
 
                    this.init();
 
                }
 
            })(jQuery);
 
        </script>
 
        <?php
        $this->script_displayed = true;
        return $form;
    }
 
    function register_script( $form ) {
 
        $page_number = GFFormDisplay::get_current_page($form['id']);
        $last_page = count($form['pagination']['pages']);
 
        $args = array(
            'formId' => $form['id'],
            'currentPage' => $page_number,
            'lastPage' => $last_page,
            'labels' => array(
                'lastPageButton' => __('Back to Last Page')
                )
            );
 
        $script = "window.gwmpn = new gwmpnObj(" . json_encode( $args ) . ");";
        GFFormDisplay::add_init_script( $form['id'], 'gwmpn', GFFormDisplay::ON_PAGE_RENDER, $script );
 
    }
 
    function is_last_page( $form ) {
 
        $page_number = GFFormDisplay::get_current_page($form['id']);
        $last_page = count($form['pagination']['pages']);
 
        return $page_number >= $last_page;
    }
 
    function is_last_page_reached() {
        return rgpost('gw_last_page_reached');
    }
 
}
 
$gw_multipage_navigation = new GWMultipageNavigation();
view raw gistfile1.php This Gist brought to you by GitHub.

How do I install this snippet?

Easy peasy. Just copy and paste the code above into your theme's functions.php file.

How do I use this functionality?

If you want to apply this functionality to all forms and you are already using the “Steps” progress indicator for your forms, installing the snippet is all you’ll need to do. If you’re interested in limiting this functionality to a few specific forms, need some help setting your form’s progress indicator, or want to learn how to create your own custom page links, read on!

Limiting to a Specific Form

Limit to a Single Form

4 
$gw_multipage_navigation = new GWMultipageNavigation();
view raw gistfile1.php This Gist brought to you by GitHub.

Limit to Multiple Forms

10 
$gw_multipage_navigation = new GWMultipageNavigation( array( 'form_id' => array(2, 5, 11) ) );
view raw gistfile1.php This Gist brought to you by GitHub.

Setting Progress Indicator

If you’d like your form’s page steps (which display above the form), you’ll need to set your paging progress indicator to “Steps”. To do so, find the “Start Paging” field and open its settings. Under the “Properties” tab, find the “Progress Indicator” setting and select the “Steps” option. If you’d like to specify a name for each step, you can do so here.

paging-progress-indicatorPaging Progress Indicator: Steps

Creating Custom Page Links

If you’d like to create your own custom page links, you can do so using the following link format:

<a href="#{pageNumber}" class="gwmpn-page-link">My Link Text</a>

Just update {pageNumber} to the page number you would like to link to and update My Link Text to whatever text (or other HTML) you would like to display for your link. Note: The link must be output somewhere within the opening and closing GF <form> tags.

Small Disclaimer

One not-so-awesome thing about this snippet is that we’re outputting a decent bit of Javascript to the page. Ideally, this Javascript would be included in a separate file. For the sake of users new to WordPress and/or web development, I chose to go the simpler, less efficient route for ease of installation.

If you’d like to move the JS portion to a separate file, please do! The entire gwmpnObj JS object can be moved to any JS file; just make sure you include it on any page you display a form configured to use it.

Closing Notes

Gravity Perks is almost ready to launch and this snippet will be available as a perk. What does that mean for you? Have a centralized location to manage all your Gravity Forms functionality and an awesome repository of useful Gravity Form enhancements. Sign-up to be notified when Gravity Perks is released or view the currently available perks in beta and help test!

The post Multi-page Form Navigation appeared first on Gravity Wiz.

]]> http://gravitywiz.com/multi-page-navigation/feed/ 6 Fix Gravity Form Tabindex Conflicts http://gravitywiz.com/fix-gravity-form-tabindex-conflicts/?utm_source=rss&utm_medium=rss&utm_campaign=fix-gravity-form-tabindex-conflicts http://gravitywiz.com/fix-gravity-form-tabindex-conflicts/#comments Tue, 29 Jan 2013 03:16:18 +0000 David Smith http://gravitywiz.com/?p=1071 This is most common when loading a Gravity Form on a page which is loading a non-GF form (like the WordPress comment form). You’re typing away on your Gravity Form and tab to the next field. Awesome. Except the next field is a completely different form. This snippet sets the starting index of your Gravity [...]

The post Fix Gravity Form Tabindex Conflicts appeared first on Gravity Wiz.

]]> Avoid the annoying issue where tabbing from a field in one form tabs you to a field in another form. This is caused by conflicting tab indexes.

This is most common when loading a Gravity Form on a page which is loading a non-GF form (like the WordPress comment form). You’re typing away on your Gravity Form and tab to the next field. Awesome. Except the next field is a completely different form. This snippet sets the starting index of your Gravity Form inputs ridiculously high so such conflicts never happen again.

1 2 3 4 5 6 7 8 9 10 
<?php
/**
 * Fix Gravity Form Tabindex Conflicts
 * http://gravitywiz.com
 */
add_filter("gform_tabindex", "gform_tabindexer");
function gform_tabindexer() {
    $starting_index = 1000; // if you need a higher tabindex, update this number
    return GFCommon::$tab_index >= $starting_index ? GFCommon::$tab_index : $starting_index;
}
view raw gistfile1.php This Gist brought to you by GitHub.

How do I install this snippet?

Easy peasy. Just copy and paste the code above into your theme's functions.php file.

How to I use this functionality?

This snippet is plug-n-play. No changes needed (unless you’re still seeing tabindex conflicts which is highly unlikely). If you are, just update the 1000 in the snippet to a higher number until the conflict disappears.

The post Fix Gravity Form Tabindex Conflicts appeared first on Gravity Wiz.

]]> http://gravitywiz.com/fix-gravity-form-tabindex-conflicts/feed/ 1 Basic WordPress membership site with protected content using Gravity Forms http://gravitywiz.com/basic-wordpress-membership-site-with-protected-content-using-gravity-forms/?utm_source=rss&utm_medium=rss&utm_campaign=basic-wordpress-membership-site-with-protected-content-using-gravity-forms http://gravitywiz.com/basic-wordpress-membership-site-with-protected-content-using-gravity-forms/#comments Wed, 14 Nov 2012 17:00:26 +0000 stevehenty http://gravitywiz.com/?p=939 Level of difficulty: easy, really easy What you’ll need: Gravity Forms (Developer License) Gravity Forms User Registration Add-On Justin Tadlock’s Members Plugin About 15 minutes Introduction WordPress already has quite a lot of the functionality you need to create a basic membership site. The trouble is, you quickly realise that some parts of the functionality [...]

The post Basic WordPress membership site with protected content using Gravity Forms appeared first on Gravity Wiz.

]]> Level of difficulty: easy, really easy

What you’ll need:

  • Gravity Forms (Developer License)
  • Gravity Forms User Registration Add-On
  • Justin Tadlock’s Members Plugin
  • About 15 minutes

Introduction

WordPress already has quite a lot of the functionality you need to create a basic membership site. The trouble is, you quickly realise that some parts of the functionality can be improved. The nice thing about WordPress though is that you can nearly always find a plugin that will help you as your site grows.

In this tutorial, we’ll be using Gravity Forms and Justin Tadlock’s Members plugin to turn WordPress into a basic membership site and require visitors to register to be able to see protect posts and pages. Non-members will only see the titles of the posts.

Once you’ve got the plugins installed, the configuration only takes a few simple steps.

Step 1: Set up the registration form in Gravity Forms
Step 2: Configure the form to create user accounts
Step 3: Configure some members-only content
Step 4: Add a login box to a sidebar

Step 1: Setting up the registration form

WordPress, out of the box, is limited to a rather sparse registration form with just username and password fields in the middle of a virtually blank page. It’s all very zen but not much use if we need to collect more information about the users, sign them up to a mailing list or require that they accept terms and conditions. By using Gravity Forms to create the registration form we get the features you might expect for a membership site; we can put the registration form on any page or widget area, include any additional fields, make sure that users get signed up to an email list, require email verification and keep the account on hold until the administrator’s approval.

To create our basic registration form we need to create a new Gravity Form following the directions here. You’ll end up with a form that looks something like this:

The user won’t be logged in automatically so you may want to change the form’s confirmation message to display a link to the login page.

Now we’ve got the form set up we need to tell Gravity Forms that this form will be used for new user registrations.

Step 2: Configure the form to create user accounts

Once you’ve installed the User Registration Add-On you’ll need to set up a simple user registration feed. This will map each field on the registration form to a field in the WordPress user settings and will make sure that Gravity Forms creates the user account with the right information.

Don’t worry about the User Meta and Additional Options sections for the moment – you can add those options later if you like.

The registration form now knows it has to check the username field to make sure it’s not already taken. If there’s another account with that username then form will fail the validation and ask the user to choose a different username.

Now we have a Gravity Form configured to create user accounts for our members we need to protect some content.

Step 3: Protecting content

WordPress has a couple of options for protecting content but neither are particularly helpful for a membership site. The first requires the post author to assign a password to each post and the second requires the user to be an editor of the blog. We’ll need to make sure that all registered users can see our protected content so we’ll need finer control over who can see what.

There are lots of plugins that will do this for you to varying levels of complexity but our basic membership site just needs a simple plugin that will allow us to hide certain content from non-members. Justin Tadlock’s Members plugin has been around for a long time and continues to be developed and supported and it gives us plenty of control.

Once you’ve installed and activated the Members plugin you’ll find this box on the edit page below the content of each post and page:

The only thing we need to configure here is the role which will have access. Select the “subscriber” role for each of the posts and pages you’d like to protect. This will ensure that all registered users will have access to content and anonymous users will see something like this for protected posts and pages:

If you want to hide posts completely then you may want to try the WordPress Access Control plugin.

Step 4: Add a login form

The standard login form on WordPress is like the registration form. It works perfectly but it doesn’t give us any control over what the login page looks like. If we want to integrate the login form into one or all of the pages we’ll need to use a plugin. The Members plugin, in addition to controlling access, also has a login widget that you can activate in the settings and then add to a sidebar. By default it will look like this:

And once the user has logged it, it’ll look like this:

For further control over the login form, and the logged in content, try the Sidebar Login plugin.

That’s all there is to it – your WordPress site is now set up to provide protected content for members only.

Next Steps

As your membership site grows you’ll find you want to refine the set up further.

Remove the admin bar

One of the first things you’ll probably want to do is hide the admin bar that appears at the top for logged in users. Again, lots of plugins will do this for you for instance Admin Bar Disabler and Admin bar.

Auto-login after register

If you’d like to save your newly registered members the additional step of having to log in immediately after registering there’s a little snippet of code here that you can add to your theme’s functions.php file that do this for you. New members will be automatically logged in so you can send them directly to your member content.

The new Gravity Perks add-on provides this functionality as a perk: GP Auto Login. No need to get messy editing your functions.php. Just click, install, and activate.

Charge for access

You can easily add a paywall to your membership site by using the Gravity Forms PayPal Add-On to require payment before the account is created. Both one-off payments and recurring subscriptions with automatic account cancellations are supported.

Add more membership levels

The Members looks very simple on the surface but it’s actually a very flexible and deceptively powerful plugin. With a bit of planning and care it can be used to create multiple membership levels which you can then assign to users, post and pages.

Protect downloads

If you have a special download like a pdf report or a product that only your members should have access to then that link needs to be protected to reduce the risk of unauthorised sharing. The PluginBuddy S3 URLs plugin will generate a link to your download that expires automatically after a specified number of seconds.

Configure admin approval for new accounts

By activating the “user activation” option in the current version of the Gravity Forms User Registration Add-On (1.5 beta1.2) the user will receive a mail with an activation link which will create the account immediately. If you’d like to make sure that only the administrator can approve the account you’ll need to add the following bit of code to the functions.php file in the current theme.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 
/**
* Configure Admin Approval for New Accounts
* http://gravitywiz.com/
*/
remove_filter('wpmu_signup_user_notification_email', array('GFUserSignups', 'modify_signup_user_notification_message'));
add_filter('wpmu_signup_user_notification_email', 'my_modify_signup_user_notification_message');
 
function my_modify_signup_user_notification_message() {        
    return false;
}
    
add_action('gform_user_registered', 'my_new_user_notification', 10, 4);
function my_new_user_notification($user_id, $config, $lead, $password) {
    $user = new WP_User($user_id);
 
    $user_login = stripslashes($user->user_login);
    $user_email = stripslashes($user->user_email);
 
    $blogname = wp_specialchars_decode(get_option('blogname'), ENT_QUOTES);
 
    $message = "Thanks for signing up. Your account has been approved and you can now log in.rn";
    $message .= sprintf(__('Username: %s'), $user_login) . "rn";
    $message .= "Password: the one you entered in the registration formrn";
    $message .= wp_login_url() . "rn";
 
    wp_mail($user_email, sprintf(__('[%s] Your account has been been approved'), $blogname), $message);
}
view raw gistfile1.php This Gist brought to you by GitHub.

 

Steve Henty is a developer at rocketgenius.

The post Basic WordPress membership site with protected content using Gravity Forms appeared first on Gravity Wiz.

]]> http://gravitywiz.com/basic-wordpress-membership-site-with-protected-content-using-gravity-forms/feed/ 17 Ban/Limit Email Domains for Gravity Form Email Fields http://gravitywiz.com/banlimit-email-domains-for-gravity-form-email-fields/?utm_source=rss&utm_medium=rss&utm_campaign=banlimit-email-domains-for-gravity-form-email-fields http://gravitywiz.com/banlimit-email-domains-for-gravity-form-email-fields/#comments Sun, 11 Nov 2012 15:31:59 +0000 David Smith http://gravitywiz.com/?p=961 Want to ban users from entering test@test.com and spamming your registration form? Want to only allow users with your companies email address to signup (i.e. jane@yourcompany.com). This snippet will let you do both! How do I use this functionality? All you need to do is create a new instance of the GWEmailDomainControl() class, populated with [...]

The post Ban/Limit Email Domains for Gravity Form Email Fields appeared first on Gravity Wiz.

]]> This snippet allows you to ban or limit any email domain(s) for your Gravity Form email fields.

Want to ban users from entering test@test.com and spamming your registration form? Want to only allow users with your companies email address to signup (i.e. jane@yourcompany.com). This snippet will let you do both!

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 
<?php
/**
* Ban/Limit Email Domains for Gravity Form Email Fields
* http://gravitywiz.com/2012/11/11/banlimit-email-domains-for-gravity-form-email-fields/
*/
class GWEmailDomainControl {
    
    private $_args;
    
    function __construct($args) {
        
        $this->_args = wp_parse_args($args, array(
            'form_id' => false,
            'field_id' => false,
            'domains' => false,
            'validation_message' => __('Sorry, <strong>%s</strong> email accounts are not eligible for this form.'),
            'mode' => 'ban' // also accepts "limit"
            ));
        
        // convert field ID to an array for consistency, it can be passed as an array or a single ID
        if($this->_args['field_id'] && !is_array($this->_args['field_id']))
            $this->_args['field_id'] = array($this->_args['field_id']);
        
        $form_filter = $this->_args['form_id'] ? "_{$this->_args['form_id']}" : '';
        
        add_filter("gform_validation{$form_filter}", array($this, 'validate'));
        
    }
    
    function validate($validation_result) {
        
        $form = $validation_result['form'];
        
        foreach($form['fields'] as &$field) {
            
            // if this is not an email field, skip
            if(RGFormsModel::get_input_type($field) != 'email')
                continue;
                
            // if field ID was passed and current field is not in that array, skip
            if($this->_args['field_id'] && !in_array($field['id'], $this->_args['field_id']))
                continue;
            
            $domain = $this->get_email_domain($field);
            
            // if domain is valid OR if the email field is empty, skip
            if($this->is_domain_valid($domain) || empty($domain))
                continue;
            
            $validation_result['is_valid'] = false;
            $field['failed_validation'] = true;
            $field['validation_message'] = sprintf($this->_args['validation_message'], $domain);
            
        }
        
        $validation_result['form'] = $form;
        return $validation_result;
    }
        
    function get_email_domain($field){
        $email = explode('@', rgpost("input_{$field['id']}"));
        return rgar($email, 1);
    }
    
    function is_domain_valid($domain) {
        if($this->_args['mode'] == 'ban') {
            return !in_array($domain, $this->_args['domains']);
        } 
        else {
            return in_array($domain, $this->_args['domains']);
        }
    }
    
}
 
new GWEmailDomainControl(array(
    'form_id' => 152,
    'field_id' => 9,
    'domains' => array('gmail.com', 'hotmail.com', 'test.com'),
    'validation_message' => __('Oh no! <strong>%s</strong> email accounts are not eligible for this form.'),
    'mode' => 'ban'
    ));
view raw gistfile1.php This Gist brought to you by GitHub.

How do I install this snippet?

Easy peasy. Just copy and paste the code above into your theme's functions.php file.

How do I use this functionality?

All you need to do is create a new instance of the GWEmailDomainControl() class, populated with your specific details, like so:

4 5 6 7 8 
new GWEmailDomainControl(array(
    'form_id' => 152,
    'field_id' => 9,
    'domains' => array('gmail.com', 'hotmail.com', 'test.com')
    ));
view raw gistfile1.php This Gist brought to you by GitHub.

By default, the form will “ban” the specified email domains; however, you can also limit by the specified domains by passing limit for the mode argument. The example below demonstrates this as well as how to apply the email domain control to two specific fields by passing an array of field IDs for the field_id argument:

20 21 22 23 24 25 
new GWEmailDomainControl(array(
    'form_id' => 152,
    'field_id' => 9,
    'domains' => array('gmail.com', 'hotmail.com', 'test.com'),
    'mode' => 'limit'
    ));
view raw gistfile1.php This Gist brought to you by GitHub.

To apply this functionality to ALL fields on a form, do not pass the field_id argument at all.

27 28 29 30 31 
// apply to all email fields on a form
new GWEmailDomainControl(array(
    'form_id' => 152,
    'domains' => array('gmail.com', 'hotmail.com', 'test.com')
    ));
view raw gistfile1.php This Gist brought to you by GitHub.

Here is a full list of available options:

11 12 13 14 15 16 17 
new GWEmailDomainControl(array(
    'form_id' => 152,
    'field_id' => 9, // multiple field IDs can be passed as an array: array(8,9)
    'domains' => array('gmail.com', 'hotmail.com', 'test.com'),
    'validation_message' => __('Oh no! <strong>%s</strong> email accounts are not eligible for this form.'),
    'mode' => 'ban' // also accepts "limit"
    ));
view raw gistfile1.php This Gist brought to you by GitHub.
  • form_id The form ID of the form you would like to apply this functionality to. If you want to apply the the same email domain control to all forms, simply do not pass the form_id argument at all.
  • field_id The field ID for which this email domain control should be applied. If you would like to apply the same control to multiple fields you can pass an array of field IDs: 'field_id' => array(8,12,15). If you want this to apply to all fields on a form, simply do not pass the field_id argument at all.
  • domains An array of email domains that should be banned or limited to depending on what mode you have set.
  • validation_message The message which will be displayed below the email field if the submitted email contains an invalid domain. You can use %s anywhere in the message to output the invalid domain.
  • mode By default, this is set to ban which will mark any of the specified domains as invalid if they are submitted in the email field. You can also pass a limit mode. In this mode, the specified domains are the only valid domains. All other domains will be marked as invalid.

The post Ban/Limit Email Domains for Gravity Form Email Fields appeared first on Gravity Wiz.

]]> http://gravitywiz.com/banlimit-email-domains-for-gravity-form-email-fields/feed/ 7 Better Limit Submission Per Time Period by User or IP http://gravitywiz.com/better-limit-submission-per-time-period-by-user-or-ip/?utm_source=rss&utm_medium=rss&utm_campaign=better-limit-submission-per-time-period-by-user-or-ip http://gravitywiz.com/better-limit-submission-per-time-period-by-user-or-ip/#comments Tue, 06 Nov 2012 13:19:38 +0000 David Smith http://gravitywiz.com/?p=928 This snippet replaces both the and the snippets. How to I use this functionality? All you need to do is create a new instance of the GWSubmissionLimit() class, populated with your specific details, like so: Want to apply the same submission limit to all forms? Want to apply multiple limitations? This example allows you to [...]

The post Better Limit Submission Per Time Period by User or IP appeared first on Gravity Wiz.

]]> This snippet allows you to limit submissions to any (or all) Gravity Forms per a time period (i.e. 30 minutes, 24 hours, 2 days, etc) by a WP User ID, by the submitting users IP adddress, or from a specific embed URL.

This snippet replaces both the Limit User to One Submission Per Time Period and the Limit IP to One Submission Per Time Period snippets.

This snippet was updated on January 15th, 2012 to provide support for limiting by the embed URL of the form and also specifying multiple “limit_by” parameters. Big thanks to Lee for funding this enhancement!
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 
<?php
 
/**
* Better Limit Submissions Per Time Period by User or IP
* http://gravitywiz.com/2012/05/12/limit-ip-to-one-submission-per-time-period
*/
 
class GWSubmissionLimit {
    
    private $_args;
    
    function __construct($args) {
        
        $this->_args = wp_parse_args($args, array(
            'form_id' => false,
            'limit' => 1,
            'time_period' => 60 * 60 * 24, // must be provided in seconds: 60 seconds in a minute, 60 minutes in an hour, 24 hours in a day
            'limit_message' => __('Sorry, you have reached the submission limit for this form.'),
            'limit_by' => 'ip' // also accepts "user_id"
            ));
        
        $form_filter = $this->_args['form_id'] ? "_{$this->_args['form_id']}" : '';
        
        add_filter("gform_pre_render{$form_filter}", array($this, 'pre_render'));
        add_filter("gform_validation{$form_filter}", array($this, 'validate'));
        
    }
    
    function pre_render($form) {
        
        if( !$this->is_limit_reached($form['id']) )
            return $form;
    
        $submission_info = rgar(GFFormDisplay::$submission, $form['id']);
    
        // if no submission, hide form
        // if submission and not valid, hide form
        if(!$submission_info || !rgar($submission_info, 'is_valid')) {
            add_filter('gform_get_form_filter', create_function('', "return '<div class="limit-message">{$this->_args['limit_message']}</div>';") );
            //add_filter('gform_get_form_filter', create_function('$form_string, $form', 'return $form["id"] == ' . $form['id'] . ' ? '<div class="limit-message">' . $this->_args['limit_message'] . '</div>' : $form_string;'), 10, 2 );
        }
         
        return $form;
        
    }
    
    function validate($validation_result) {
    
        if($this->is_limit_reached($validation_result['form']['id']))
            $validation_result['is_valid'] = false;
        
        return $validation_result;
    }
    
    public function is_limit_reached($form_id) {
        global $wpdb;
        
        $limit_by = is_array($this->_args['limit_by']) ? $this->_args['limit_by'] : array($this->_args['limit_by']);
        $where = array();
        
        foreach($limit_by as $limiter) {
            switch($limiter) {
            case 'user_id':
                $where[] = $wpdb->prepare('created_by = %s', get_current_user_id());
                break;
            case 'embed_url':
                $where[] = $wpdb->prepare('source_url = %s', RGFormsModel::get_current_page_url());
                break;
            default:
                $where[] = $wpdb->prepare('ip = %s', RGFormsModel::get_ip());
            }
        }
        
        $where[] = $wpdb->prepare('form_id = %d', $form_id);
        $where[] = $wpdb->prepare('date_created BETWEEN DATE_SUB(utc_timestamp(), INTERVAL %d SECOND) AND utc_timestamp()', $this->_args['time_period']);
        $where = implode(' AND ', $where);
        
        $sql = "SELECT count(id)
                FROM {$wpdb->prefix}rg_lead
                WHERE $where";
        
        $entry_count = $wpdb->get_var($sql);
        
        return $entry_count >= $this->_args['limit'];
    }
    
}
 
// standard usage
new GWSubmissionLimit(array(
    'form_id' => 86,
    'limit' => 2,
    'limit_message' => 'Aha! You have been limited.'
    ));
view raw gistfile1.php This Gist brought to you by GitHub.

How do I install this snippet?

Easy peasy. Just copy and paste the code above into your theme's functions.php file.

How to I use this functionality?

All you need to do is create a new instance of the GWSubmissionLimit() class, populated with your specific details, like so:

4 5 6 7 
new GWSubmissionLimit(array(
    'form_id' => 86,
    'limit' => 2,
    ));
view raw gistfile1.php This Gist brought to you by GitHub.

Want to apply the same submission limit to all forms?

19 20 21 
new GWSubmissionLimit(array(
    'limit' => 5
    ));
view raw gistfile1.php This Gist brought to you by GitHub.

Want to apply multiple limitations? This example allows you to limit the number of a submissions a logged in user can make to specific form from the same embed URL. This would allow you embed the same form on multiple pages and allow users to submit that form up to the submission limit on each page.

24 25 26 27 28 29 
new GWSubmissionLimit(array(
    'form_id' => 2,
    'limit' => 1,
    'limit_message' => 'Aha! You have been limited.',
    'limit_by' => array('embed_url', 'user_id')
    ));
view raw gistfile1.php This Gist brought to you by GitHub.

Here is a full list of available options:

10 11 12 13 14 15 16 
new GWSubmissionLimit(array(
    'form_id' => 2,
    'limit' => 5,
    'time_period' => 60 * 60 * 24 * 2, // two days in seconds
    'limit_message' => 'You are all maxed out! Try again in a couple days.',
    'limit_by' => 'ip', // default is 'ip', also supports 'user_id' and 'embed_url'; can alternately provide an array of limitations: array('ip', 'embed_url')
    ));
view raw gistfile1.php This Gist brought to you by GitHub.
  • form_id The form ID of the form you would like to limit. If you want to apply the the same submission limit to all forms, set the form_id as false or do not provide it at all.
  • limit The number of submissions allowed before the user will no longer be able to make additional submission.
  • time_period The period of time to which the limit applies. The default time period is one day. In any 24 hour period, if the user reaches the limit they will no longer be able to make new submissions.
  • limit_message The message which should be displayed to the user once they have reached the specified submission limit.
  • limit_by Specify which identifying data the user should be limited by. The default is ip. user_id is also supported which allows you to limit logged in WP users. embed_url is now supported to limit submissions of a form from a specific embed URL.

The post Better Limit Submission Per Time Period by User or IP appeared first on Gravity Wiz.

]]> http://gravitywiz.com/better-limit-submission-per-time-period-by-user-or-ip/feed/ 22