[seehowtwo]

Yes, I have gone through the testing with a default theme and no other plugins – but I realize now that, at that time, I was thinking it was a display issue only. We still saw duplicates after reverting to a default WP theme AND turning off all other plugins.

However, now that we know it’s a duplicate database custom field entry issue, I need to go back and turn off all plugins and use a WP theme WHILE doing a manual incomplete registration process.

Will try to do that in the next day or two – we had used up all our incomplete registrations during testing, so I’ll need to create several fake incompletes first, so we can test with all plugins off, then, if the problem disappears, turn on each one, complete a registration, turn on the next, etc.

• This reply was modified 1 year, 2 months ago by seehowtwo.

[seehowtwo]

Doesn’t this suggest there’s an issue with the Custom Fields function?

Not that the function itself is problematic or you would have heard of more instances of this happening, but rather that some interaction with another plugin is causing the issue by interacting with the process of creating Custom Fields…??

On this site, the other plugins we’re using are:

WordPress 6.0.2

Admin Columns – Version 4.4.5
BackupBuddy – Version 8.7.5
Better Search Replace – Version 1.4.1
Caldera Forms – Version 1.9.7
Caldera Forms Anti Spam – Version 0.4
Contact Form 7 – Version 5.6.3
Disable Gutenberg – Version 2.7
eMember Email Broadcast – Version v2.4
eMember Member Bulk Import – Version v1.2
eMember Profile Extended – Version v3.3
Fluent Forms – Version 4.3.12
FooGallery – Version 2.2.16
GA Google Analytics – Version 20220517
Genesis Simple Edits – Version 2.3.1
Health Check & Troubleshooting – Version 1.5.0
Imsanity – Version 2.8.1
iThemes Sync – Version 2.1.10
Media Library Assistant – Version 3.04
Menu Icons – Version 0.13.0
Page Builder by SiteOrigin – Version 2.17.0
Really Simple SSL – Version 5.3.4
Responsive Lightbox & Gallery – Version 2.4.1
See How Support Theme Extras – Version 0.1.0
ShiftNav – Responsive Mobile Menu – Version 1.7.1
Simple 301 Redirects – Version 2.0.7
SiteOrigin Premium – Version 1.34.1
SiteOrigin Widgets Bundle – Version 1.42.1
The Events Calendar – Version 6.0.1
The Events Calendar Shortcode & Block – Version 2.5.5
The Post Grid – Version 4.2.3
UpdraftPlus – Backup/Restore – Version 1.22.22
Widgets for SiteOrigin – Version 1.4.7
WP Activity Log – Version 4.4.2.1
WP Crontrol – Version 1.14.0
WP eMember – Version v10.4.6
WP Help – Version 1.7.1
WP Mail Logging – Version 1.10.4
Yoast Duplicate Post – Version 4.5
Yoast SEO – Version 19.7.1

• This reply was modified 1 year, 2 months ago by seehowtwo.

[seehowtwo]

I’ve finally figured it out:

We have Custom Fields set up, and the people who are showing up as duplicates, have TWO separate Custom Field entries – each with exactly the same info.

When I delete one of the Custom Field rows – the duplicated entry disappears on the Members list.

So somehow, when we do a manual registration, it’s creating a duplicate set of Custom Fields.

umeta_id
user_id
meta_key
meta_value

274
269
custom_field
a:5:{s:13:”Neighbourhood”;s:0:””;s:46:”High_School…

279
269
custom_field
a:5:{s:13:”Neighbourhood”;s:0:””;s:46:”High_School…

[seehowtwo]

I downloaded a fresh copy of the latest eMember – 10.4.6 – and re-installed it, but the duplicates continue to show.

I have not had a chance to test the idea of manually completing a registration through an incognito window where I’m not logged in as an admin. Will let you know, soon as.

[seehowtwo]

No caching plugins, and I’ve tried Troubleshooting mode, with only eMember turned on, and the problem persists. So it doesn’t seem to be any conflict with plugins or themes.

[seehowtwo]

Thanks so much for the quick and detailed response. (Literally heading into a meeting about this!)

So, this is a (relatively) complicated process.

Dear Tips and Tricks – no membership plugin I know of is addressing the VERY COMMON requirement of having a single renewal date for all members (whether Jan – Dec or some other calendar year).

If you were to solve this and create an easier to use method than the one described above by coabirder, you would have a very saleable feature to offer customers – e.g. just enter the start date for the membership level (say, January 1), and the system would automatically calculate the yearly end date (e.g. Dec 31) so there’d be no need to create new membership levels, etc.

Cheers!

[seehowtwo]

Hi coabirder!

We have the opposite issue – existing memberships are “1 year from joining” and we want to change them to Jan 1 – Dec 31.

I’m curious how you’re doing the Calendar Year system – I see in membership levels where you can set an expiry date. But how does that work when you reach the end of the calendar year? I’m assuming you have to go into the Membership Level settings and update the year? And it would need to be done first thing on Jan 1 (else everyone would be expired)?

[seehowtwo]

Thanks for clearing that up – that shortcode sounds handy, to at least make the cancellation process easier. You seem to have a shortcode for everything

And thanks for the prompt replies – I’ve found your customer support to be consistently excellent over the five or six years I’ve been using your products.

[seehowtwo]

What I need to be clear about is how WP eMember interacts with PayPal.

From what you say, it sounds like, in order to upgrade to Paid Level 2, a member would need to cancel their Paid Level 1 subscription first, and then subscribe to Paid Level 2.

Will WP eMember automatically be cancelling the PayPal profile that was originally created for Paid Level 1? And then automatically creating a new PayPal profile for Paid Level 2 when the member clicks the WP eMember button for Paid Level 2?

I don’t want my members to have to go into PayPal to stop their recurring payment for Level 1.

If they do have to do a manual PayPal cancellation, I’m thinking it would be more seamless for me to break up my membership into parts, which would be concurrent PayPal subscriptions. So, people would sign up for Level 1 membership with certain features and ADD ON Level 2 as a second membership level with additional features. If they subscribe to both, they would have two PayPal payments coming out each month…

[seehowtwo]

It would be very simple for you to add something like the following line on each applicable Email setting box:

PERSONALIZATION IS NOT AVAILABLE FOR THIS TYPE OF EMAIL

I’m using v8.5.7, which is long after this discussion, and it’s still not obvious that only some emails can use the shortcodes for things like first_name and last_name.

[seehowtwo]

Thanks for that link – I’m usually pretty good at searching for answers, but I see from this link that I missed a whole lot!!

Anyway, based on your checklist I went back to double-check the IPN settings in PayPal.

While the URL for the IPN was filled in, someone had Disabled “send messages” and I hadn’t noticed (I’ve now Enabled it).

They had also turned on Payment Data Transfer (PDT), which I’ve now turned off.

I think they had made those last two changes when they put in WooCommerce, despite the fact that WooCommerce does not require either of them.

So now I’m getting the debug messages, the account is getting created, and the email for registration is going out. Thanks so much!

[seehowtwo]

Sorry for the confusion, I’m actually the webmaster for the site – can you email me through my profile.

[seehowtwo]

Thanks for those suggestions.

I did have all of the WP User integration settings checked, except for “Automatically create an eMember account when another plugin creates a WP User account”, but just to clarify – WP eMember is creating new WP Users when you do new eMember registrations, and those users are integrating with WooCommerce no problem.

I’ve done the re-loading of the plugin.

But unfortunately I’m still getting this error:

Catchable fatal error: Object of class WP_Error could not be converted to string in /xxxxxx/xx/public_html/wp-content/plugins/wp-eMember/eMember_misc_functions.php on line 586

Weird that it’s one line less than the previous error…

And my apologies, I had forgotten that I have the Members plugin installed as well. I don’t think I actually need it now so I’m going to try uninstalling it.

Ok, got rid of Members, but the error still occurs.

[Author]

Posts