Terrible for an official plugin
-
The plugin used to work ok, but often crashed loading the backend due to a huge amount of stats data. There is no way to store stats for xx amount of time then delete older than a set date or amount of days.
The plugin was effectively dead for pretty much 1 whole year as the code-base contained vulnetabilities, so much so that www.ads-software.com prevented download of the plugin.
Now finally an update has been released that addresses the code vulnerabilities, however when connecting to my Keap CRM, I found that it will only authorize using the legacy API key (not a server key or personal access key). The problem here is that Keap will retire legacy API keys in October 2024 (for existing keys), which is only a few months away. Therefore the plugin will no longer work after this date without a further update to the plugin.
Overall when it works, it works. It’s a little inflexible in the data that can be catptured, only the name and email are options.
As the plugin stopped working due to vulnerabilities for a long time, I have already replaced the functionality and updated my keap CRM automations; and improved upon the fields that are captured with an alternative.
I cannot see myself using this plugin any further and trying the recent update is my last attempt to revive it.
-
I decided to re-try this plugin again as I receieved a notification it was updated (possibly triggered by my review). I installed the update and now notice the developers have fixed the issue with it using the legacy API which is no longer available to use with Keap CRM. The plugin can now correctly use either PAK (personal access keys) and SAK (service access keys) for the API integration. So, this is a great start.
I decided to use the ‘lock’ type optin form and a ‘popup’ type optin form (when the plugin works it works well).
Unfortunately I noticed that the forms randomly stop working. That is to say when populating a form as a visitor, the spinner icon is shown on submit and the form never completes submission. For the lock type optin this means it never reveals the content behind the lock or sends the contact info to the keap CRM, so doesn’t create the contact, etc.
For the popup type optin, the same the thing happens, and the form doesn’t send the contact to the CRM or redirect to the completion url (in my case it redirects to the shopping cart of woocommerce with a free product automatically added based on the url I set).
Workaround – To fix the issue I have to revisit the settings for the plugin and use the ‘reauth and save’ button. Some minutes later (between 2 – 5 mins) the forms start to work as normal again.
The problem – I cannot work out why the forms randomly stop working – the API seems disconnected. At times it seems this can occur because a page has been updated on my site (saved, updated, etc.), other times it seems to randomly occur. I have checked my server logs (cant see any obvious issues here) and my WAF (website application firewall) logs to see if my WAF is preventing response headers from servers hosting the keap API. Unfortunately as keap do not use an offical list or range of IP addresses for their API I cannot figure out if my WAF might possibly be blocking anything.
When the plugin works, it’s great, but unfortunately it fails randomly. I need a solution from the developers or an explaination why the API seems to disconnect itself – This happens daily, sometimes multiple times!!!
I am using php 8.1 and have the cURL extension installed, I have no issues with other API’s I am using. The plugin states it works with php version 8 and upwards, I have a suspicion php version could be the issue, but have not had time to test and monitor if using php 7.4 (or 8.0) would remove the disconnect issue though I recall the plugin will not even install if using php7.x.
As a side note: When upgrading from the previous version it rendered the old forms unusable and I had to recreate forms. When I recreated them, the forms work. I suspect this is because of different (new) settings possibly; and I also notice in the export for the config there are now more json values, which may explain why old forms break after upgrading. I also would not attempt to export then import from the old version to new version as it will likely break the forms too.
- You must be logged in to reply to this review.
