Fix: Remove line breaks from REDCap HTML fields in LINST output #10256
+1
−1
Conversation
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
Fixes aces#10238 The redcap2linst.php script was generating malformed LINST files when REDCap fields contained HTML with line breaks. LINST format requires exactly one line per field. Previously, newline characters were being converted to <br /><br /> tags, but actual newline characters still remained in the output, breaking the LINST format. This change removes all line break characters (\r\n, \r, \n) from field labels when generating LINST output, ensuring each field stays on a single line as required by the LINST specification.
github-actions
bot
added
Language: PHP
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Brief summary of changes
Remove line breaks from REDCap HTML fields when generating LINST output. The toLINST() method now strips all newline characters (
\r\n,\r,\n) from field labels to ensure each LINST field stays on a single line as required by the LINST specification.Link(s) to related issue(s)