|
dirk.tussing
|
June 3, 2023 at 10:06 am
Hi ee4 support,
After upgrading the php version to 8.1, the importer tool issue seems to be fixed, but we found it’s conflicting with the eea-wpuser-integration-2.0.16.p plugin.
link to previous ticket: https://eventespresso.com/topic/importer-tool-not-able-to-count-csv-items-and-therefore-importing-0-rows/
with the user integration addon turned off, the imported registrations looks good.
with the user integration addon turned on, the names of all registration are changed to the last record in the import csv, and the email are all changed to current logged-in user.
screenshot: https://ibb.co/fYBTCwy
|
|
Tony
|
June 7, 2023 at 7:57 am
Hi there,
Is that the correct version number?
The WP User integration add-on version 2.0.16 was released November 7th 2018:
https://eventespresso.com/wiki/2018-changelog-archive/#wpuser-2.0.16
We’ve pushed more updates for that add-on since then and the current version is 2.1.1.p
Testing this on my local sites with the latest versions works as expected so if the above version number is correct I’d recommend first updating to 2.1.1 and checking if you have the same issue.
|
|
dirk.tussing
|
June 7, 2023 at 9:22 am
I tried to upgrade/install the latest version, but it was not compatible with our current ee4 Version 4.10.46.p.
Error message when trying to activate Event Espresso – WordPress Users Integration (EE4.6+) Version 2.1.1.p :
IMPORTANT!
The Event Espresso “EE_WPUsers” addon requires Event Espresso Core version “4.11.0.rc.001” or higher in order to run.
Your version of Event Espresso Core is currently at “4.10.46.p.000”. Please upgrade Event Espresso Core first and then re-activate “EE_WPUsers”.
|
|
dirk.tussing
|
June 7, 2023 at 9:26 am
We don’t want to upgrade the core to ee5 yet, and I couldn’t find 4.11.0 tag in your repo.
|
|
Tony
|
June 7, 2023 at 10:56 am
Ok, so I’ve just dug into this a little deeper.
On a site with:
Event Espresso core – v4.10.46.p
WP user integration – 2.0.16.p
Importer add-on – 1.0.3.p
If I import registrations the imported registrations all work as expected so there has to be something else going on here.
Any custom functions hooking into maybe_sync_existing_attendee?
Or FHEE_EE_Single_Page_Checkout__save_registration_items__find_existing_attendee?
|
|
dirk.tussing
|
June 7, 2023 at 1:50 pm
No, I don’t think so.
|
|
dirk.tussing
|
June 7, 2023 at 1:59 pm
This reply has been marked as private.
|
|
Tony
|
June 7, 2023 at 2:20 pm
What hook are those using?
|
|
dirk.tussing
|
June 7, 2023 at 2:42 pm
it’s not using any hooks. it’s just checking if current registering wp user has EE_Attendee_ID attached to it. if not, it will try to add to the user meta using update_user_option()
|
|
Tony
|
June 7, 2023 at 3:10 pm
Hmm, ok, so what is calling those functions?
|
|
dirk.tussing
|
June 7, 2023 at 4:00 pm
our headless front end passes registration data to wordpress backend with graphql mutation to process the registration and trys to attach the registration with a wp user.
but it shouldn’t have been be called when using importer tool.
|
|
Tony
|
June 8, 2023 at 5:11 pm
Hmm, then right now I’m stumped as to why you would be getting the above.
Is this on the staging or live site? Can you test this in Troubleshooting mode?
I recommend using a plugin like Health Check & Troubleshooting:
https://wordpress.org/plugins/health-check/
Enable it and go to Tools -> Site Health -> Troubleshooting, enable troubleshooting.
That switches you to a default theme and no active plugins, but only for you the current logged in admin.
Then in the admin bar you can enable specific plugins
Admin Bar -> Troubleshooting Mode -> Manage active plugins.
Enable Event Espresso core, WP user integration & the Importer add-on and retest, same result?
(The reason I recommend using the above plugin is its easy to forget about a snippet in a plugin or theme somewhere. Troubleshooting mode basically disables everything until you enable it individually)
|
|
dirk.tussing
|
June 9, 2023 at 3:19 pm
This reply has been marked as private.
|
|
dirk.tussing
|
June 9, 2023 at 4:13 pm
This reply has been marked as private.
|
|
Tony
|
June 13, 2023 at 6:07 am
Can you send me a copy of the CSV you are using for the import?
I haven’t been able to reproduce this and asked another team member to test the same versions, again they had no issue so I’d like to test using the same file you ar using if possible.
If so just send it to support[at]eventespresso.com
|
|
dirk.tussing
|
June 13, 2023 at 11:32 am
This reply has been marked as private.
|
|
Rio
|
June 13, 2023 at 4:32 pm
We did try to import the CSV you sent, and everything is fine.
https://app.screencast.com/GIRdhngYWp2e8
We also try different use cases such as not mapping other fields, importing it on simple event and importing it on event with different tickets.
You did mention about this code “The closest thing came up to search was in graphql mutation customization.” Can you Comment any customization code you made in EE, then try to import again.
If it still didn’t work, can you shoot video for us, the whole process you’re doing. You can use loom to do that.https://www.loom.com/
Please send us also some more details, such as all the plugin installed and their version.
Thanks
|
|
dirk.tussing
|
June 14, 2023 at 9:29 am
I did more testing:
– deleted all plugins except these three ee4 plugins
– delete all custom themes and activate a default wp theme
– try importer tool ==> bad result with duplication
– then installed a plugin: WP Database Reset
– reset all tables
– create a new test event
– try importer tool ==> no duplication this time
So I wonder if there any place in the user integration addon depends on database data.
|
|
dirk.tussing
|
June 14, 2023 at 11:35 am
Another finding on was that the current logged in admin’s attendee info was changed to Sarah Williams in this case.
https://share.cleanshot.com/ZRjhZ7Xw
|
|
dirk.tussing
|
June 14, 2023 at 12:57 pm
This reply has been marked as private.
|
|
Rio
|
June 15, 2023 at 2:19 am
ok, In the video I noticed your version for wp user is
event espresso – wp users: 2.0.17.p and not 2.0.16 I will check if that is the one causing the issue. AS we have identical setup but we get different result. We may also need to access your site.
https://eventespresso.com/send-login-details/
Thanks
|
|
dirk.tussing
|
June 15, 2023 at 10:18 am
This reply has been marked as private.
|
|
dirk.tussing
|
June 21, 2023 at 4:50 pm
Do we have any updates on this issue?
|
|
Rio
|
June 21, 2023 at 7:17 pm
Thank you for your help that we’re able to replicate the issue.
I did submit issue to our Dev and they will check it for further review.
For now, we suggest to have specific admin account you will use for import. Anyway, thanks again for submitting this.
Thanks,
Rio
|
|
Rio
|
June 22, 2023 at 4:42 pm
By the way, this bug is not existing in the current version. Tested this scenario in 5.0.7+
Thanks
|
|
dirk.tussing
|
June 22, 2023 at 5:38 pm
yes. We are not confident that upgrading ee4 to ee5 will be smooth.
I think we had problem when we tried to upgrade/migrate it on our sandbox.
In the meantime, we will have to stick with ee4.
Under the circumstance, what would be your suggestions for the bug fix?
|
