[Neb]

Ok, great. And is the plugin compatible with PHP 7.2?

[Neb]

Thanks. Looking at it this is a global setting (along with the API key) to enable double opt-in for all membership levels across the board, which would work if ALL membership levels have their lists set to be double opt-in.

However, the way my modifications worked is that the double-opt-in was at a Membership level, along with the List name. This made more sense, and I think was more flexible, as the double opt-in at the MailChimp level is based on the List’s settings.

[Neb]

Sorry, new link: https://www.dropbox.com/sh/ab9dkzp7fwtogay/AAA_8MHgciQRVmGiDMwZLReia?dl=0

[Neb]

Sure thing. Here it is: https://www.dropbox.com/s/lz6w5jlx6qqhkn5/simple-membership-mailchimp-integration-nebrekab-edit.zip?dl=0

The files edited were:

• swpm-mailchimp-action.php
• swpm-mailchimp-signup.php
• readme.txt (notes added)

At present we are running this modified version. So if/when you update, if you could let me know that would be helpful.

Thanks

[Neb]

Hi,

I have updated the plugin code to allow for enabling/disabling of the Opt-in for MailChimp and this now works. It adds a Double opt-in checkbox below the list name for each Membership Level. Pretty simple to achieve.

Happy to contribute the code, but not sure how to go about this.

Thanks,

Ben

[Neb]

Thanks for the reply.

I have Double-opt in selected within the list settings. This does appear under Form Settings, so I am wondering if this only applies if you are using an MC generated form (which is not the case with SWPM).

The process is tested and works as follows:

1. user signs up and pays
2. user receives an email from SWPM
3. user follows the link and completes registration
4. with registration complete they are subscribed to the MC list by the add-on plugin.

However, what is required is that instead it uses double opt-in:

1. user signs up and pays
2. user receives an email from SWPM
3. user follows the link and completes registration
4. with registration complete they are sent an opt-=in email from MC
5. user click opt-in email link and is subscribed

I have used the MailChimp plugin for Contact Form 7 and you must select that it uses double opt-in. I would guess the MC add-on for SWPM would need to do the same?

This link suggests perhaps you need to set the subscribed state in the api call to “pending”, not subscribed.

With the current scenario, I believe this breaks the GDPR rules, making the plugin of no use to us here in the EU.

Any thoughts? I will follow this up with MailChimp and get their input.

Thanks

[Neb]

Thanks for the quick reply.

I’ve found their hosting and support to be excellent, and its benefits far outweigh a self-managed system.

I think to clarify your response, what I would say is that caching on WPEngine can cause issues with your plugin.

From the post that you sent this suggests it’s purely the login page that is affected. This has been excluded from the caching, as has any account pages and also any cookies set by SWPM.

What would be useful from the plugin authors is a list of specific urls that would be best to have caching disabled.

Perhaps you could reach out to WPEngine and get a test account setup to test your plugin in their system? As they are one of the largest WordPress hosting sites out there, and this would make your plugin offering even more attractive.

[Neb]

Sure, I realise that. That’s how WP handles plugin updates.

For our WP build we have had to disable plugin updates, so this is more to do with notifying the SWPM community that an update has shipped, so that people in that situation can go and investigate the implications of updating.

I take it you have no Twitter feed that you could post out when an update’s been rolled out?

[Neb]

I see so you have to go to Members and click EDIT on the user, then at the bottom you see the custom fields. Is there any way to export this data, along with all user data, as a CSV?

[Neb]

Thanks very much, that’s very helpful.

We will run tests based on this.

[Neb]

Hi,

Was there any update on if this will make the next update and when that might be?

[Neb]

For the record, it goes in:

wp-content/themes/<your-theme>/simple-membership/login.php

NOT in
wp-content/themes/<your-theme>/simple-membership/views/login.php

[Neb]

Ah! *facepalm* It doesn’t go in the views folder within the theme folder.

Sorted 🙂

[Neb]

Great!

Thank you so much for the swift response and confirmation that it is the fix.

The current Version is 3.5.6, will this make it to the next release?

[Author]

Posts