[dev/core#412] Avoid truncated UTF-8 strings when using substr() #12935
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.
Overview
This fixes broken export forms when a custom group name contains a UTF-8 character at the 10th character position.
See dev/core#412.
Before
The export form can not be used due to a JavaScript error "Uncaught syntax error: Unexpected token ,".
The next column of options does not pop up.
After
The export form works correctly.
Technical Details
CRM_Core_BAO_Mapping::getCustomGroupName()
truncates custom group names when longer than 10 characters usingsubstr()
, which causes multibyte characters being cut in half when at the truncating position.This should use
CRM_Utils_String::ellipsify()
instead, which utilisesmb_substr()
.Comments
Maybe someone with more core code insight should inspect a
grep substr(
result for more places where that happens.