Author 詩語

Increasing Your PHP Max Execution Time

Increasing Your PHP Max Execution Time

Modifying your max execution time in php.iniModifying your max execution time in .htaccess

If you are receiving errors due to PHP scripts timing out when manipulating large amounts of data, such as a large import or export, you may need to increase the max execution time in PHP. In this article, we will show you how to do so.
When following these steps, keep in mind that these are generic instructions, as we cannot possibly account for every change in your web hosting environment. If these steps are unable to resolve your issue, or if you have any concerns about them, your best and quickest solution is to contact your web host.
Note: Only one of the following steps should be necessary. If one of them resolves your issue, there is no need to do the other.
Modifying your max execution time in php.ini
Depending on your hosting provider, you may have a php.ini file within your home directory. If it is present, find the max_execution_time parameter and modify it to increase the number of seconds PHP scripts are allowed to run.
max_execution_time = 300

Modifying your max execution time in .htaccess
If you are unable to change your max execution time from within a php.ini file, you may be able to change it within your .htaccess file. This file is typically located within your home directory. If you don』t see it, be sure you are able to see hidden files.
Place the following in the top of your .htaccess file:
php_value max_execution_time 300

Setting Up the iContact Add-On

Setting Up the iContact Add-On

Pre-RequisitesSetupCreating an iContact Application IDAdd-on Framework Hooks

Pre-Requisites

Download and install the add-on
An iContact account

Setup

Log into your WordPress admin dashboard.
On the left side navigation menu, hover over Forms and click on Settings.
From this page, click the iContact tab.
Enter your Application ID, Account Email Address, API Password, and select the Client Folder. This is obtained from iContact. See below for instructions on how to create an application ID.
Click Update Settings. If you』ve entered your account information correctly, you will be notified by green check marks beside each box. If you do not see green check marks, please double check this information and try again.

Creating an iContact Application ID

Visit the iContact application registration page.
Set an application name and description for your application.
Choose to show information for API 2.0.
Copy the provided API-AppId into the Application ID settings field.
Click 「Enable this AppId for your account」.
Create a password for your application and click save.
Enter your API password, along with your iContact account username, into the settings fields.

Once you have entered your API information, you』re ready to begin creating a feed for the iContact Add-On.
Add-on Framework Hooks
Because the iContact Add-On is built using the Add-On Framework it also inherits any hooks available in the framework methods it uses such as:

gform_short_slug_field_value for changing a field value before it is passed to iContact.

Increasing Your PHP Memory Limits

Increasing Your PHP Memory Limits

Modifying WordPress』 memory limitModifying your server』s memory limitModifying your memory limit in php.iniModifying your memory limit in .htaccessFollow your web host』s instructions

Sometimes, you may come across issues such as errors when exporting a large number of entries, or even errors stating that your available memory has been exhausted. These errors are caused by PHP limits within the server and/or the WordPress installation being too low for the amount of data being processed.
In this article, we will show you how to fix errors related to your PHP memory limits.
Note: In most cases, you will need to modify the PHP memory limit within WordPress, as well as your server』s PHP memory limit. Increasing only one of these may cause your issue to persist due to the limit in the other.
Modifying WordPress』 memory limit
Note: Even after increasing your memory limit inside this file, you will still also need to increase it on the server side, usually in your php.ini file. If either of these is too low, you will still experience issues.
To modify the memory limit used by WordPress, place the following in your wp-config.php file. This file is located at the home directory of your WordPress installation.
1define( 'WP_MEMORY_LIMIT', '4086M' );
Of course, you can change this to anything you want to. In the above example, we have simply set PHP scripts to be able to use 4GB on memory which is far more than should be required.
Modifying your server』s memory limit
As stated in the previous section, you will need to change both the WordPress memory limit and the server memory limit. In addition to the steps in this section, be sure to follow the instructions in the above section to increase the memory limit available to WordPress.
Note: You do not need to (or may not even be able to) complete all of the below items. One of them is enough.
Modifying your memory limit in php.ini
If you have a php.ini file within your site』s home directory, locate the line containing memory_limit and edit it to the following:
1memory_limit = 4086M
Modifying your memory limit in .htaccess
If you don』t have a php.ini file available, you may be able to modify your memory limit from within your .htaccess file. This file is located within the home directory of your site. If you don』t see if, be sure that hidden files are visible.
Place the following in the top of your .htaccess file:
1php_value memory_limit 4086M
Follow your web host』s instructions
As we cannot entirely predict every variable within your web host』s configuration, these are generic, common settings and you may need to take further steps if the above settings do not work. A few popular hosts』 steps on changing your php memory limit can be found at the following:

Bluehost
GoDaddy
Hostgator
InMotion Hosting
Kinsta
SiteGround

iContact Change Log

iContact Change Log

1.5 | 2020-09-081.4 | 2020-03-241.3 | 2018-03-301.2 | 2016-08-311.1 | 2015-12-161.0 | 2015-05-20

1.5 | 2020-09-08

Added support for Gravity Forms 2.5.
Fixed a PHP fatal error which occurs when accessing an existing feed which was created by a different iContact account.

1.4 | 2020-03-24

Added translations for Hebrew, Hindi, Japanese, and Turkish.
Updated account username setting label.
Updated stylesheets to use minified versions.
Fixed PHP 7.4 notices which occur when the API is initializing and the settings are empty.
Fixed a PHP 7.4 notice which occurs on the feed configuration page when saving a new feed.
Fixed the width of the Feed Name setting on the feed configuration page.

1.3 | 2018-03-30

Added security enhancements.
Added GPL to plugin header.
Added the gform_icontact_request_args hook allowing customers to modify the options array before sending requests to iContact.
Updated Plugin URI and Author URI to use https.
Fixed PHP notice on the add-on settings page.
Fixed strings for translations.
Increased limit for number of client folders retrieved from iContact.

1.2 | 2016-08-31

Added feed duplication support.
Added support for delaying feed processing until payment by PayPal Standard is successfully completed.
Fixed an issue with the request failed message.

1.1 | 2015-12-16

Added auto-mapping of first name and last name fields if only one name field exists.
Added client folder option to plugin settings.
Added default name for new feeds.
Added gf_icontact() for easily getting an iContact instance.
Fixed PHP warning during feed processing.
Updated feed processing to abort if value of mapped Email Address field is invalid.
Updated feed processing to use add_feed_error().
Updated feed field mapping styling.
Updated feed settings to support more than 20 iContact lists.

1.0 | 2015-05-20

It's all new!

Highrise Change Log

Highrise Change Log

1.3 | 2019-02-191.2 | 2017-04-281.1.3 | 2017-01-251.1.2 | 2016-11-301.1.1 | 2016-11-281.1 | 2016-08-311.0 | 2015-07-29

The Highrise CRM service is no longer in development, and no new accounts can be created. As of November 2019, we have deprecated the official Gravity Forms plug-in which is no longer available for download.

1.3 | 2019-02-19

Added security enhancements.
Added GPL to plugin header.
Added user agent to API requests.
Updated Plugin URI and Author URI to use https.
Fixed a PHP notice which would occur when sending a request to Highrise.

1.2 | 2017-04-28

Added security enhancements.
Added translations.

1.1.3 | 2017-01-25

Updated the description string on the Settings page.

1.1.2 | 2016-11-30

Fixed strings for translations.

1.1.1 | 2016-11-28

Fixed PHP notice.

1.1 | 2016-08-31

Added exception handling to API calls.
Added feed duplication support.
Added support for delaying feed processing until payment by PayPal Standard is successfully completed.
Fixed thrown exception when using a mapped phone number field.

1.0 | 2015-07-29

It's all new!

How To Report a Security Issue

How To Report a Security Issue

Steps to take before reportingEnsure Gravity Forms is fully updated to the latest versionEnsure all Gravity Forms addons are updatedSubmitting a security report

Note: this article is not intended for security researchers. If you』re a researcher see information for security researchers.
We take security issues very seriously and want to ensure that you always feel safe when using Gravity Forms. Here are a few steps you should take if you believe you have a security issue with Gravity Forms.
Steps to take before reporting
Ensure Gravity Forms is fully updated to the latest version
First, be sure that you have the latest version of Gravity Forms. If not, you may be running an older version in which we have already patched the issue in a newer version. We strive to keep newer versions compatible with any existing implementation you have, so you should see minimal, if any issues at all, from updates.
Ensure all Gravity Forms addons are updated
Whether you are using official or third party addons, be sure that they are all fully updated. Just as keeping Gravity Forms updated is important to your site』s health, keeping your addons up to date are just as important.
Submitting a security report
If you have ensured that the security issue is indeed a current one, we want to know as soon as possible.

First, be sure to gather all information possible. This includes what has been affected, as well as the potential exploit. Providing thorough information will help us release a patch much quicker.
Open a ticket using our Contact Us form as soon as possible, selecting the 「I Am Reporting a Security Vulnerability」 choice. We have individuals in various locations across the world, that will be able to review your concern quickly.
We will confirm receipt of your security concern as soon as possible.

How to add Gravity Forms Blocks

How to add Gravity Forms Blocks

IntroductionInsert using the Add Block buttonInsert using the quick select slash 「/」Insert using the content area 「recent blocks」 shortcut.Insert using the Shortcode blockTailoring Your Block

Introduction

WordPress 5 introduced the block based page/post editor, a replacement for the venerable classic editing environment. Gravity Forms includes its own blocks for use in the new editor. The following article gives instructions on how to add a block to your page or post.

Note that as of WordPress 5.8, the Gravity Forms Block will no longer work properly if you are on Gravity Forms 2.4.x or earlier. You will need to upgrade to the latest Gravity Forms release.

Insert using the Add Block button

Open the page or post you wish to add a block to.Click the plus sign button (+) to add a new block into the content area where your cursor focus is.

In the search bar, type enough text to identify the block you want. Alternatively, look under the Embeds area.Click the block to insert it.

This will place the block on your page/post, and you can now begin specifying the options and settings for the particular block you have selected.

Example: inserting the Poll block using the Add Block button. Click to view animation.

Insert using the quick select slash 「/」

Typing forward slash / anywhere within your content area will bring up an 「insert shortcode」 dialog, which then allows you to search and insert as per above.

Example: inserting the Poll block using the shortcode short cut. Click to view animation.

Insert using the content area 「recent blocks」 shortcut.

When you are in the content area, the appearing contextual controls will include shortcut icons to the right side that show recently used blocks. Check there to see if the Gravity Forms block you want is shown. Hover over the icon to see the block name. (Delelte This section?)

Insert using the Shortcode block

The WordPress 5 editor comes with a Shortcode block (under the Widgets category), which once added will accept a standard Gravity Forms shortcode. Insert that block using any of the methods above, and then you can manually tailor your Gravity Forms shortcode as needed.

Tailoring Your Block

Refer to the documents for each block type to see the types of settings and options specific to that block.

Form block (included with Gravity Forms core).Poll block (included with Poll add-on)Gutenberg Gravity Forms block (included with the Gutenberg Block experimental add-on)

Highrise Feed Meta

Highrise Feed Meta

IntroductionUsagePropertiesCustom Field Properties

Introduction
The Feed Object meta for the Highrise add-on is an associative array containing the properties which determine how the add-on should process the form submission.
$feed['meta'] = array(
'feed_name' => 'Highrise Feed 1',
'action' => 'contact',
'person_custom_fields' => array(),
'feed_condition_conditional_logic' => true,
'feed_condition_conditional_logic_object' => array(
'conditionalLogic' => array(),
),
);

Usage
We recommend accessing the $feed meta using the rgar() or rgars() functions, e.g.:
$conditional_logic_enabled = rgars( $feed, 'meta/feed_condition_conditional_logic' );

Properties

feed_name string
The feed name which appears on the add-ons feeds tab.

action string
The feed action. Default is contact.

contact_standard_fields_first_name string
The ID of the form field containing the contact』s first name.

contact_standard_fields_last_name string
The ID of the form field containing the contact』s last name.

contact_standard_fields_title string
The ID of the form field containing the contact』s title.

contact_standard_fields_company string
The ID of the form field containing the contact』s company.

contact_custom_fields array
A multidimensional array containing the Highrise custom fields. See Custom Field Properties.

contact_note string
The note to add to the contact. Merge tags supported.

contact_visible_to string
Who can see this contact. Possible values: Everyone, Owner or the Highrise Group ID.

feed_condition_conditional_logic boolean
Is the feed condition (conditional logic) setting enabled. Default is false.

feed_condition_conditional_logic_object array
An associative array containing the conditional logic rules. See the Conditional Logic Object for more details.

Custom Field Properties
array(
'key' => 'title',
'value' => '3',
)

Each custom field is an associative array containing the following properties:

key string
The Highrise custom field key.
The default keys are: background, linkedin, twitter, email_work, email_home, email_other, phone_work, phone_mobile, phone_fax, phone_pager, phone_home, phone_skype, phone_other, website_work, website_personal, website_other, address_work, address_home, address_other, im_aim, im_msn, im_icq, im_jabber, im_yahoo, im_skype, im_qq, im_sametime, im_gadu-gadu, im_gtalk, im_other.
Other custom fields all begin custom_ and then end with the Highrise field ID, e.g. custom_1007122.

value string
The ID of the form field or entry meta item containing the value for this custom field.