-
Notifications
You must be signed in to change notification settings - Fork 8
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
#!#protected_XXX#!# #3
Comments
Thanks for reporting, I will check this ASAP |
I am sorry, but I'm unable to reconstruct this issue. Tested in TYPO3 11 with PHP 8 and TYPO3 10 with PHP 7.4. Can you give me more info and dump your plugin.tx_min config? |
@a-r-m-i-n Thanks for checking. I've tested on Typo3 10.4.16 / PHP 7.4 and additional config like this:
|
Hello, we do have the same behavior. Textareas will be replaced with #!#protected_XXX#!#. The XXX is a hash and regenerates with every refresh. We use the latest T3 10 LTS with PHP 7.4 and the following configuration:
The static template of min 2.0.0 is not included. |
Okay thanks. Locally I'm still not able to reconstruct this issue, but on my own website's dev environment, I was able to reconstruct. I'm going to fix it as soon as possible. |
Okay, I see the problem. This was a major upgrade, which breaks old configurations, which is also well documented: |
I reopen this issue, because I want to fix this behaviour. The reason why this is happening: At the place where the protection applies, the body version of protectCode is defined as fallback, in case the root version is missing. But when restoring the protected code, this fallback is missing. I'm going to replace the fallback at all. In worst case, you will get no protected textareas, then. Also I want to improve documentation, when upgrading from v1. |
Thank you! |
Thank you. With changing the configuration, min works like a charm. |
Hi, after upgrade to 2.0 there is "protected" instead of loading .js:
![Zrzut ekranu 2022-03-4 o 14 28 46](https://user-images.githubusercontent.com/7590893/156771858-784ef69b-f4d0-4838-8057-eb39a8c9f70f.png)
The text was updated successfully, but these errors were encountered: