-
-
Notifications
You must be signed in to change notification settings - Fork 824
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Participant import fix - broken uniqueName fields, mapping saving, ev… #23733
Conversation
(Standard links)
|
038104a
to
011ab68
Compare
…ent_id This switches to using 'normal' field names for all participant fields.
011ab68
to
b4167b7
Compare
@@ -88,11 +94,13 @@ protected function importCSV(string $csv, array $fieldMappings, array $submitted | |||
$form = $this->getFormObject('CRM_Event_Import_Form_MapField', $submittedValues); | |||
$form->setUserJobID($this->userJobID); | |||
$form->buildForm(); | |||
$this->assertTrue($form->validate()); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@demeritcowboy I managed to add these after two of the buildForm
calls - the first one fails on the file upload rule which seems tricky
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool. Would need to look closer - there's that low-level php function move_uploaded_file or something that you used to have to use in the previous century to access the file for security reasons, so maybe there's an extra hurdle for those.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yep - but running validate will def help find stuff
Looks good. Ok to merge once tests pass. |
Overview
This addresses reviewer feedback by @aydun on the Participant import cleanup currently merged.
#23703 (comment)
It addresses
This also switches away from using unique names in the participant import - which simplifies the code a little
Contact matching
This is a pre-existing confusion that we would ideally come up with a good answer for it - I think this PR gets us to the pre-existing behaviour & we should pick up over here https://lab.civicrm.org/dev/core/-/issues/3180
Note to self - re-test :"update mapping" works - UPDATE - yep UI test worked to update a field in a mapping