Constant Contact Gravity Forms Integration

### Steps to Integrate Constant Contact with Gravity Forms:
1. **Install and Activate Gravity Forms:**
– Ensure you have the **Gravity Forms** plugin installed and activated in your WordPress site.

2. **Install and Activate Constant Contact for Gravity Forms:**
– Go to the **Gravity Forms Add-Ons** page.
– Search for **Constant Contact** and install the add-on.
– Activate the add-on once installed.

3. **Connect Your Constant Contact Account:**
– Navigate to **Forms** > **Settings** > **Constant Contact**.
– Enter your **API Key** and **Access Token**. You'll need to get these from your Constant Contact account:
– Log in to **Constant Contact**.
– Go to **Account Settings** > **API Keys**.
– Create a new key if needed and grab the credentials.

4. **Create a Form with Gravity Forms:**
– Create a new form using Gravity Forms or edit an existing one.
– Add the necessary fields for the form, such as name, email, etc.

5. **Map Gravity Form Fields to Constant Contact:**
– Go to the **Form Settings** of the form you want to connect to Constant Contact.
– Click on the **Constant Contact** tab.
– Map your form fields to the corresponding fields in Constant Contact (e.g., map the email field to the Constant Contact email field).

6. **Enable Subscription:**
– In the **Constant Contact Settings** for the form, choose the **email list** in Constant Contact that users will be added to when they submit the form.

7. **Test the Integration:**
– After everything is set up, test the form to ensure that when a user submits it, their details are added to the specified Constant Contact list.

### Tips:
– You may need a Constant Contact API key if you haven’t already created one.
– You can create multiple lists in Constant Contact and choose which one to add subscribers to from Gravity Forms.

If you don't have the add-on, there are third-party plugins and Zapier automations that can also connect Gravity Forms to Constant Contact, but the official add-on is typically the easiest way to go.

### Steps to Install Constant Contact for Gravity Forms in Bedrock via Composer:

1. **Install Gravity Forms via Composer** (if you haven't already):
First, make sure that Gravity Forms is installed via Composer. In Bedrock, plugins are usually managed in the `composer.json` file, so add Gravity Forms to it.

– Open the `composer.json` file and add Gravity Forms as a dependency. Under the `repositories` section, add the Gravity Forms package:

"repositories": [
     {
       "type": "vcs",
       "url": "https://github.com/gravityforms/gravityforms"
     }
   ],
   "require": {
     "gravityforms/gravityforms": "^2.5"
   }

Then run the following command to install Gravity Forms:

composer install

2. **Install the Constant Contact Add-On for Gravity Forms:**
Next, you’ll install the **Constant Contact for Gravity Forms** add-on. However, this add-on isn’t directly available via Composer by default, so you will need to install it manually.

– Download the **Constant Contact for Gravity Forms** plugin from the **Gravity Forms Add-Ons** section.
– Once downloaded, you will need to upload the add-on to your plugin directory (`/wp-content/plugins`), typically under the `web/app/plugins/` folder in a Bedrock setup.

Alternatively, if you're comfortable using GitHub and Composer, you can manually add it as a **GitHub package** to your `composer.json` file:

"repositories": [
     {
       "type": "vcs",
       "url": "https://github.com/gravityforms/constant-contact"
     }
   ],
   "require": {
     "gravityforms/constant-contact": "^1.0"
   }

Then run:

composer install

3. **Activate the Plugins:**
After installation, log in to the WordPress dashboard, go to **Plugins** > **Installed Plugins**, and activate both **Gravity Forms** and **Constant Contact for Gravity Forms**.

4. **Configure the Integration:**
– After activating the plugins, go to **Forms** > **Settings** > **Constant Contact** in the WordPress dashboard to connect your Constant Contact account.
– Follow the steps to obtain your **API Key** and **Access Token** from Constant Contact and connect the service.

5. **Set Up Form Settings:**
– Create or edit a Gravity Form and go to its **Settings**.
– Under the **Constant Contact** tab, map the Gravity Forms fields to Constant Contact fields as needed.

### Final Notes:
– Make sure you have Composer properly set up in your Bedrock project before proceeding.
– The **Constant Contact for Gravity Forms** add-on might need to be uploaded manually to the plugin directory unless it is added via a GitHub repository as explained.
– You can also use **Composer plugins** or **scripts** to handle dependencies more flexibly in your Bedrock environment if you need a more automated process.

This method should allow you to integrate Constant Contact with Gravity Forms in your **Bedrock**-based WordPress project.

### Using WPackagist to Install Plugins via Composer

To install plugins (like **Gravity Forms** or others) from the **WPackagist** repository using Composer, you need to configure your **composer.json** file to point to the WPackagist repository.

Here’s how you can set it up:

### 1. **Add WPackagist Repository to Composer**

First, you need to add the WPackagist repository to your `composer.json` file. If you’re using **Bedrock**, this is done in the `composer.json` file under the `repositories` section.

Add the following line under `"repositories"` in your `composer.json` file:

"repositories": [
  {
    "type": "composer",
    "url": "https://wpackagist.org"
  }
]

### 2. **Install Plugins Using Composer**

Once the WPackagist repository is added, you can install WordPress plugins directly from WPackagist using Composer.

For example, to install **Gravity Forms** or **Constant Contact for Gravity Forms**, you would run the following commands:

composer require wpackagist-plugin/gravityforms
composer require wpackagist-plugin/constant-contact

This will download and install the plugins from WPackagist into your project.

### 3. **Configure and Activate Plugins**

After installation, you’ll need to:

– Go to your WordPress **Plugins** page and activate both **Gravity Forms** and **Constant Contact for Gravity Forms**.
– Set up your Constant Contact integration (API keys and access tokens) from the **Gravity Forms Settings**.

### Example `composer.json` for Bedrock

Here’s an example of how your `composer.json` might look in a **Bedrock** setup when using WPackagist:

{
  "name": "your-project/bedrock",
  "type": "project",
  "repositories": [
    {
      "type": "composer",
      "url": "https://wpackagist.org"
    }
  ],
  "require": {
    "php": ">=7.4",
    "composer/installers": "^2.1",
    "wpackagist-plugin/gravityforms": "^2.5",
    "wpackagist-plugin/constant-contact": "^1.0",
    "roots/bedrock": "1.16.*"
  },
  "extra": {
    "installer-paths": {
      "web/app/plugins/{$name}/": ["type:wordpress-plugin"]
    }
  }
}

### 4. **Additional Notes**
– **WPackagist** essentially mirrors the WordPress Plugin Directory, so if a plugin exists on WordPress.org, it will be available through WPackagist.
– It is particularly useful for projects that need to manage WordPress dependencies in a **Composer-based workflow**, such as **Bedrock** or other Composer-managed WordPress sites.

### Advantages of Using WPackagist
– It allows you to easily manage WordPress plugin and theme versions with Composer.
– It simplifies deployment and environment setup, especially when using tools like **Bedrock**.
– You can define specific plugin versions for more predictable deployments across environments.

By using **WPackagist** with Composer, you can manage and version WordPress plugins just like any other dependency in your **Bedrock** project.

### Syntax:

composer remove <package-name>

### Example:
To remove a plugin or package, such as **Gravity Forms** or **Constant Contact for Gravity Forms**, you would run the following:

composer remove wpackagist-plugin/gravityforms
composer remove wpackagist-plugin/constant-contact

This command will:

1. Remove the specified package from your project.
2. Update the `composer.json` file to remove the package from the `require` section.
3. Update the `composer.lock` file to reflect the change.
4. Uninstall the package from the `vendor` directory.

### Removing Multiple Packages:
You can also remove multiple packages at once by listing them, separated by a space:

composer remove wpackagist-plugin/gravityforms wpackagist-plugin/constant-contact

### Optional Flags:
– **`–dev`**: If the package was installed as a development dependency (i.e., under the `require-dev` section), you can specify this flag to remove it from the dev dependencies:

composer remove --dev <package-name>

– **`–no-update`**: If you want to remove the package but **not** update the `composer.lock` or perform the update operation, you can add the `–no-update` flag:

composer remove <package-name> --no-update

After running the `remove` command, Composer will ensure that the package is uninstalled, and your project will be up to date without that dependency.