Constant Contact Forms

外掛說明

Please note: Version 2.0.0 of this plugin is a significant release, including both security and feature updates. After updating to version 2.0.0, you will be required to reconnect the plugin to your Constant Contact account & reselect the lists associated with your forms.

Work smarter, not harder. The Constant Contact Way

Create branded emails, build a website, sell online, and make it easy for people to find you—all from one place.

Constant Contact Forms is the easiest way to connect your WordPress website with your Constant Contact account.

  • Effortlessly create sign-up forms to convert your site visitors into mailing list contacts.
  • Customize data fields, so you can tailor the type of information you collect from your users.
  • Captured email addresses will be automatically added to the Constant Contact email lists of your choosing.

BONUS: If you have a Constant Contact account, all new email addresses that you capture will be automatically added to the Constant Contact email lists of your choosing. Not a Constant Contact customer? Sign up for a Free Trial right from the plugin.

How To Get Started.

  1. Signup for a Free Trial. ( Existing Constant Contact users can skip this step).
  2. Follow first-time setup instructions.
  3. Create your first form.
  4. Add a form anywhere on your website.
  5. Watch as your visitors turn into lifetime contacts!

螢幕擷圖

  • Adding a New form when connected to Constant Contact account.
  • Viewing All Forms
  • Lists Page
  • Settings page
  • Basic Form

適用於區塊編輯器

這個外掛提供 1 個可供 Gutenberg/區塊編輯器使用的區塊。

  • Constant Contact: Single Form

常見問題集

Installation and Setup

HELP: Install the Constant Contact Forms Plugin for WordPress to Gather Sign-Ups and Feedback

Constant Contact Forms Options

HELP: Add email opt-in to a WordPress Form created with the Constant Contact plugin

Frequently Asked Questions

HELP: Enable Logging in the Constant Contact Forms for WordPress Plugin

Constant Contact List Addition Issues

HELP: Troubleshooting List Addition Issues in the Constant Contact Forms Plugin for WordPress

cURL error 60: SSL certificate problem

HELP: WordPress cURL Error 60: SSL Certificate Problem

Add Google reCAPTCHA to Constant Contact Forms

HELP: Add Google reCAPTCHA to Your WordPress Sign-up Form to Prevent Spam Entries

How do I include which custom fields labels are which custom field values in my Constant Contact Account?

You can add this to your active theme or custom plugin: add_filter( 'constant_contact_include_custom_field_label', '__return_true' );. Note: custom fields have a max length of 50 characters. Including the labels will subtract from the 50 character total available.

Which account level access is needed to connect my WordPress account to Constant Contact?

You will need to make the connection to Constant Contact using the credentials of the account owner. Campaign manager credentials will not have enough access.

Error: Please select at least one list to subscribe to.

Some users are experiencing errors when upgrading from an older version of the plugin. If you are receiving an error “Please select at least one list to subscribe to” on your form submissions we recommend “Sync Lists with Constant Contact”, this can be found in your admin dashboard Contact Form > Lists. If problem still persists we recommend recreating the form from scratch.

使用者評論

2023 年 6 月 8 日 1 則留言
The 2.0.1 version lost all of our lists. They cannot be re-synced. And we cannot create new lists from within WordPress. Without connections to lists, this plugin is fatally broken. Reverting back to v1
2023 年 6 月 7 日 1 則留言
Alert! The Constant Contact Forms plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the constant_contact_optin_ajax_handler function in versions up to, and including, 1.14.0. This makes it possible for authenticated attackers, with subscriber-level access and above, to modify the plugin's opt-in settings. References patchstack.com

meh

2022 年 10 月 2 日
I would like to see more rich form design, such as embedding field labels in the field, placement of the submit button, inline with text instead of always on a new line. I would like to be able to use a single line form in my website footer, but you don't seem to have one and your smallest form expands the footer unacceptably. I understand the need for your disclaimer, but perhaps it could be minimized. Your depiction of my lists in the dashboard is incomplete. Fortunately the list of lists for a subscription form is sufficiently complete.
2022 年 8 月 25 日 3 則留言
The forms feature that purportedly integrates with WP does only one thing well: capture an email address and put it in whatever CC email list you'd like. What it does not do well is capturing other information (i.e., a custom text field for comments, or a custom text field that may be requesting specific information like "how many adults" for an RSVP-style form). CC support told me I was not using the "official WP CC plugin," which I am! The issue I saw had to do with the opt in check off box that shows at the bottom of the fields. There are now 3 scenarios that I have noticed through testing: 1. If I remove the opt in check off box (as a feature at the bottom of the form) created in the Constant Contact plug in, I receive the email with all the form entries. 2. If I leave the opt in check off box on the form, fill out the form but do not click the check off box, I get nothing (no email with the entries, and of course no opt in for the subscriber). 3. If I leave the opt in check off box on the form, fill out the form and also click the opt in check off box, I get no email with the entries, but I do get an opt in for the subscriber. I am removed the optional check off box because it fouls up the whole purpose of my RSVP form (to gather entered info). What I asked CC but get not get a response, was if the entry data is stored somewhere either within WP or CC. I ask about the possibility of stored data (stored entries) because now I fear that site visitors have been entering data into the form that I have never received. If you know if form entries are stored anywhere, let me know. They do not show anywhere in the CC contact record.
2022 年 7 月 25 日
Constant Contact inline forms look primitive and are complicated to embed. This plugin makes the process even more complicated. I don't suggest this plugin or Constant Contact to anyone.
閱讀全部 81 則使用者評論

參與者及開發者

以下人員參與了開源軟體〈Constant Contact Forms〉的開發相關工作。

參與者

將〈Constant Contact Forms〉外掛本地化為台灣繁體中文版

對開發相關資訊感興趣?

任何人均可瀏覽程式碼、查看 SVN 存放庫,或透過 RSS 訂閱開發記錄

變更記錄

2.0.2

  • Updated: Rate limits on API requests. Should help address list sync issues.
  • Added: Notifications of issues with list fetching with API version 3. Shorter transient cache time.
  • Added: More conditions to show “APIv3 upgrade needed” notice while needed.

2.0.1

  • Fixed: Fatal error regarding objects and arrays upon update to 2.0.0

2.0.0

  • Updated: Plugin has been migrated to use Constant Contact API version 3.0. This will require new authentication workflow.
  • Updated: Addressed security issues with regards to opt-in notification.
  • Updated: Added support to check for DISABLE_WP_CRON constant usage and bypass cron scheduling if true.
  • Fixed: moved “Edit form” link to outside the <form> markup.
  • Fixed: Custom color choices were not applying to all parts of form text output.

1.14.1

  • Fixed: Backport of security issue originally fixed in 2.0.0 release.

1.14.0

  • Fixed: Issues around email submissions with “some+value@email.com” based addresses.
  • Fixed: Compatibility with Elementor Widget registration
  • Added: Notice regarding upcoming API changes in a later major plugin version.
  • Added: Compatibility with Cleantalk Spam Protect
  • Added: Extra compatibility with Akismet Spam protection
  • Updated: CMB2 internal library to 2.10.1

1.13.0

  • Fixed: get_optin_list_options() defaults to an empty array instead of an empty string
  • Fixed: Prevent “CTCT has experienced issues” notifications for “503 Service Not Available” errors
  • Fixed: Fixes plugin sometimes causing errors due to trailing commas
  • Changed: Move styles inline for honeypot field to ensure field is hidden when option to disable CSS output is used
  • Updated: Mask API keys in error logs
  • Updated: Mask phone numbers in logs
  • Updated: Add noopener noreferrer to blank links
  • Updated: Refactor multiple translated strings
  • Updated: Added error messages on form submissions upon API faliures