Coder Social home page Coder Social logo

wordpress-cf7-cleverreach-integration's Introduction

CleverReach Integration for Contact Form 7

Contributors: pixelarbeit Tags: contact form 7, cf7, cleverreach, contact form 7 addon, contact form 7 integration Tested up to: 6.0.1 Requires at least: 4.6 Requires PHP: 7.4 Stable tag: 2.4.9 License: GPLv3 or later License URI: https://www.gnu.org/licenses/gpl-3.0.html

Connect your Contact Form 7 forms with your CleverReach account.

Description

Add or update new recipients to CleverReach when your Contact Form 7 form is submitted.

Features

  • Quick setup with CleverReach
  • Map Contact Form 7 fields to CleverReach fields with ease
  • Invidual settings per form (e.g. group, form, mapping, ...)
  • Choose between Single Opt-In and Double Opt-In
  • Mark a field as "required" for CleverReach submission

Requires

  • PHP >= 7.4
  • PHP cURL Extension
  • Contact Form 7 Plugin >= 4.5
  • CleverReach Account

Support

If you find a bug please open an issue on GitHub. For additional feature request or paid support contact me via email

Links

Configuration

  1. Go to Settings > CF7 to CleverReach
  2. Click "Get CleverReach API token". You will be redirected to CleverReach.
  3. Authenticate against CleverReach and give access to the plugin. You will be redirected back to Wordpress and should see the generated API token.
  4. Configure your forms via Contact -> "Your form" > CleverReach tab

Installation

  1. Upload the plugin files to the /wp-content/plugins/cf7-cleverreach-integration directory, or install the plugin through the WordPress plugins screen directly.
  2. Activate the plugin through the 'Plugins' screen in WordPress

Screenshots

  1. Get CleverReach API Token via settings page
  2. Configure form

Changelog

2.4.9

  • Fix: Fallback if $_SERVER vars are missing inside Api::sendActivationEmail()

2.4.8

  • Fix: Missing vendor folder

2.4.7

  • Security: Update dependencies

2.4.6

  • Fix: Respect WP_PROXY_HOST and WP_PROXY_PORT

2.4.5

  • Fix: Add link to log file in error message.
  • Fix: Don't show CF7 panel when token is not set.
  • Fix: Make strings translatable.

2.4.4

  • Fix: Solved issue inside CF7 configuration panel introduced with 2.4.3.

2.4.3

  • Fix: Do not show refresh token warning on first install or when API token is empty

2.4.2

  • Fix: Send Double-Opt-In Mail for existing users if they are not activated yet.

2.4.1

  • Fix: Added note on token expiry

2.4.0

  • Feat: Automatic token renewal
  • Feat: Improved Notifications/Logging

2.3.4

  • Feat: Add not regarding access tokens on settings page

2.3.3

  • Fix: Downgrade monolog for compatibility with PHP 5.5

2.3.2

  • Fix: Patch autoloader files to prevent collision

2.3.1

  • Fix: A function still relied on the old http client

2.3

  • Refactor: Use guzzle as http client
  • Refactor: Use monolog as logger
  • Refactor: Use php-Scoper

2.2

  • Merge global and local attributes in one select
  • Fix: Disable checks when integration is not active
  • Fix: Enable SSL verification in JsonClient
  • Fix: Improve logs and notifications

2.1.2

  • Update name to comply with Contact Form 7 trademark policy
  • Move settings to Contact Form 7 submenu

2.1.1

  • Fix bug with static var access

2.1

  • Fix bug for new api token generation

2.0

  • No need for custom app anymore
  • Select fields, form, group from list instead of giving an id.
  • Added source, double opt-in and tags option

1.1.2

  • Fix for checkboxes and radio buttons as input

1.1.1

  • Transfer api token from old option field to new one

1.1

  • Added cleverreach api token generation on settings page
  • Fixed case-sensitivity of attributes

1.0

  • First version

wordpress-cf7-cleverreach-integration's People

Contributors

dependabot[bot] avatar pxlrbt avatar

Watchers

 avatar  avatar  avatar

Forkers

fitz-huxley

wordpress-cf7-cleverreach-integration's Issues

WordPress compatibility

This plugin is officially compatible with WordPress up to 5.0.7. Even though it still seems to be working fine, I suggest to ensure its compatibility with the current WordPress Version (5.3).

Readme Plugin description

I suggest to slightly change the Plugin description from

Send Contact Form 7 form data to Cleverreach

to

Send Contact Form 7 form data to CleveReach.

debug.log is beeing flooded [with unhelpful messages]

My debug.log is being filled with messages from this plugin which I think shouldn't be the case. Messages I encountered so far:

  1. CF7 to Cleverreach CF7 to Cleverreach:Forbidden: email not allowed
  2. CF7 to Cleverreach CF7 to Cleverreach:Forbidden: Client not found
  3. CF7 to Cleverreach CF7 to Cleverreach:Not Found: Version 2 is not supported
  4. CF7 to Cleverreach No valid JSON

These are not helpful at all.
If you must output an error, please format them correctly, this looks messy and is not working with my RegEx to Extract error messages

[19-Nov-2019 11:33:04 Europe/Berlin] [2019-11-19 11:33:04] ERROR CF7 to Cleverreach CF7 to Cleverreach:Forbidden: email not allowed

Additionally, I do not know which E-Mail is not allowed. I am getting hundreds of these errors a day and I have little clue how to counter it.

Parse error in Logger.php

After updating to the latest version (2.3.2), I get this error message

The plugin cannot be activated because it generates a fatal error.

Parse error: syntax error, unexpected 'const' (T_CONST), expecting variable (T_VARIABLE) in /var/www/vhosts/address-of-my-website/httpdocs/wp-content/plugins/cf7-cleverreach-integration/vendor-prefixed/monolog/monolog/src/Monolog/Logger.php on line 32

WordPress version is 5.4.1, and I am running the theme "The7" version 8.7.1

Rename to be consistent with other CF7 Plugins

I have multiple Contact Form 7 Plugins installed and they all seem to have the same naming Scheme:

Contact Form 7 The Plugin Name

I suggest to remove the - from the name to make it consistent with other CF7 Plugins.

Wordpress-Proxy-Settings not applied

When trying to get the API token, i get "cURL error 35". It is due to the plugin not using the proxy-settings configured in wordpress.
I fixed the problem by adding the following lines in cf7-cleverreach-integration/vendor-prefixed/guzzlehttp/guzzle/src/Client.php:

if (defined('WP_PROXY_HOST') && defined('WP_PROXY_PORT')) { curl_setopt($curl, CURLOPT_PROXY, WP_PROXY_HOST . ':' . WP_PROXY_PORT); }

Warning is showing even though option is disabled

On some Forms, I choose not to use this plugin. And thus I have left the "Active" Checkbox disabled. Still, after saving I get this message:

CF7 to Cleverreach Missing form configuration. Required: List Id, Form ID, Email Field.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.