fix: CSV user import issue if attribute isn't the exact value - MEED-10196 - Meeds-io/meeds#4002#5621
Merged
akhanfir merged 1 commit intofeature/maintenancefrom Feb 23, 2026
Merged
Conversation
mkrout
previously approved these changes
Feb 23, 2026
ahamdi
reviewed
Feb 23, 2026
component/core/src/main/java/io/meeds/social/core/identity/service/UserImportService.java
Outdated
Show resolved
Hide resolved
component/core/src/main/java/io/meeds/social/core/identity/service/UserImportService.java
Show resolved
Hide resolved
component/core/src/main/java/io/meeds/social/core/identity/service/UserImportService.java
Outdated
Show resolved
Hide resolved
akhanfir
force-pushed
the
TASK-10196
branch
2 times, most recently
from
14f9440 to
e7a8670
Compare
…10196 - Meeds-io/meeds#4002 Before this change, create attribute filed which ID is Phone and import csv having telephone attribute, user attribute never displayed on user profile and the Telephone attribute can never be reimported again. To fix this problem, ensured that profile property validation is performed in a strictly case-sensitive way at the application level, independently of the database collation. Now, the system verifies that the imported field name exactly matches the attribute ID before allowing it. After this change, attribute will not be imported if it doesn't exactly match the attribute ID.
|
ahamdi
approved these changes
Feb 23, 2026
exo-swf
pushed a commit
that referenced
this pull request
Feb 24, 2026
…10196 - Meeds-io/meeds#4002 (#5621) Before this change, create attribute filed which ID is Phone and import csv having téléphone attribute, user attribute never displayed on user profile and the Téléphone attribute can never be reimported again. To fix this problem, ensured that profile property validation is performed in a strictly case-sensitive way at the application level, independently of the database collation. Now, the system verifies that the imported field name exactly matches the attribute ID before allowing it. After this change, attribute will not be imported if it doesn't exactly match the attribute ID.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Before this change, create attribute filed which ID is Phone and import csv having
téléphoneattribute, user attribute never displayed on user profile and theTéléphoneattribute can never be reimported again. To fix this problem, ensured that profile property validation is performed in a strictly case-sensitive way at the application level, independently of the database collation. Now, the system verifies that the imported field name exactly matches the attribute ID before allowing it. After this change, attribute will not be imported if it doesn't exactly match the attribute ID.