- This topic has 10 replies, 3 voices, and was last updated 1 year ago by
.
-
Posts
-
When a new member has not completed their registration, we use the Admin Function to generate a link to complete that registration.
We then use the link ourselves (rather than sending it to the member) to complete their registration.
But, after filling out the registration form, we then have TWO listings for the member.
I’ve checked in the database, and there is, in fact, only one listing.
On the Manage Member page, at the top left, the total for Active members is correct, while the pagination total includes the duplicated members.
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.
When a new member has not completed their registration, we use the Admin Function to generate a link to complete that registration.
We then use the link ourselves (rather than sending it to the member) to complete their registration.
When you use the link yourself; are you still logged in as the admin account? Can you try copying the link to an incognito window and try it?
Also, just to be sure, load a fresh copy of the plugin before doing the test in an incognito window:
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.
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_value274
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…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.1Not 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…??
Have you done this?
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.
- You must be logged in to reply to this topic.