Copyright Field Stripped In Helix Ultimate 2.2.7/2.2.8
Jeroen
Hi,
Helix Ultimate 2.2.8 fixed the stripping of custom code in Before Head, After Body, Before Body, Custom CSS and Custom JS.
But in Helix Ultimate 2.2.8: Basic > Footer > Copyright the HTML and links you enter there are also stripped. Try to enter and save for example: <a href="#">Test</a>
Can you please fix this?
Jeroen
Jeroen
Accepted AnswerIn addition: Also go to Advanced > SCSS > turn on 'Compile SCSS to CSS' > Save > turn off 'Compile SCSS to CSS' > Save. Result: The HTML has been removed from the copyright box.
Toufiq
Accepted AnswerHi there,
Thank you for reaching out, and I apologize for any inconvenience caused by this oversight. Added a patch. Please use this build until release next update.
https://drive.google.com/file/d/180nsdNh2e1Rrx80fV2cGIKO6-NUp3jDL/view
Best regards,
Toufiqur Rahman (Team Lead, Support)
David Forés
Accepted AnswerHi Toufiq,
The patch you shared seems to be based on version 2.2.7 rather than 2.2.8, which you released a few hours ago.
In version 2.2.8, besides fixing the existing bug, many third-party libraries (vendor) had also been updated. However, with this patched 2.2.8 (2) version, the libraries appear to have reverted to the ones used in 2.2.7.
Could you please check this so the update remains incremental and we are not moving back and forth between versions?
Toufiq
Accepted AnswerWe intentionally kept the version number as 2.2.8. If we had released it as 2.2.9, your site would receive another update notification, even though this release only contains a patched build of the same version.
David Forés
Accepted AnswerHi Toufiq,
Maybe I didn't express myself clearly.
What I meant was that the patch you shared on Drive (2.2.8 (2)) doesn't seem to be an update to version 2.2.8 itself, but rather an update to version 2.2.7.
As I said, if you run a diff on the changes between versions 2.2.7 and 2.2.8, you can see that many third-party libraries were updated to new versions.
However, when you run a diff between 2.2.8 and 2.2.8 (2), you’ll see that those versions have reverted back to the same versions that were in 2.2.7. That is where the inconsistency lies, and that is why I requested a review—so that for the upcoming version 2.2.9, you will take this into account to avoid reverting to previous versions of other libraries that had already been updated.
