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
encode / decode problem with text area #736
Comments
The problem is the double encoding in the |
As discussed in Mumble on May 7th, we want to revert the changes from contao/core#8623 and add a Also, we want to add a comment so we do not forget to remove the |
@sebj54 Regarding your ticket contao/core#8623: You can use |
Description ----------- | Q | A | -----------------| --- | Fixed issues | Fixes #736 | Docs PR or issue | - <!-- Bugfixes should be based on the 4.4 or 4.9 branch and features on the master branch. Select the correct branch in the "base:" drop-down menu above. Replace this notice with a short README for your feature/bugfix. This will help people to understand your PR and can be used as a start for the documentation. --> Commits ------- 5eca151 Add a "rawValue" property to the TextArea class 69e5870 Also remove the str_replace() when returning the raw value
Versions
all
contao/core-bundle/src/Resources/contao/forms/FormTextArea.php
Line 144 in 326bbb6
Description
Textarea form widgets encodes "<" on first submission but double decodes it on second submission.
In the end, the widgets should not encode anything on their own but I know this is not to be changed before Contao 5 for bc sake.
However, I think the double encoding (see reproduction below) should be adressed.
How to reproduce
open: <, close: >, ampersand: &
into the textarea but leave the mandatory field empty.open: <, close: >, ampersand: &
open: <, close: >, ampersand: &
again.thx at @discordier to check this
The text was updated successfully, but these errors were encountered: