- 🇳🇱Netherlands spadxiii
As the ticket responsible for postponing this has been merged and fixed (and released), I've re-rolled the latest patch against 2.x.
And putting it back to needs review
- 🇩🇪Germany Anybody Porta Westfalica
@SpadXIII thanks! Why are you adding
Markup::create()
? Doesn't that introduce security risks?
It wasn't there before, so I don't know yet, why it should be needed?BTW, Tests are failing, but that might be unrelated?
- 🇳🇱Netherlands spadxiii
I seem to have forgotten to add a use-statement. Fixed in new patch.
- First commit to issue fork.
- Status changed to Needs work
over 1 year ago 8:26am 25 March 2023 - 🇮🇳India rajeshreeputra Pune
Agree with @Anybody Markup::create() isn't required.
- First commit to issue fork.
- Status changed to Needs review
over 1 year ago 3:18pm 25 March 2023 - Status changed to Needs work
over 1 year ago 3:42pm 25 March 2023 - 🇳🇱Netherlands tess bakker
Could use a test to validate the case in comment #7 for double escaping.
- First commit to issue fork.
- 🇮🇳India kunal_sahu Karnataka
Please review the MR, I have tried to write some addition test cases as per @Tess Bakker requirement.
Thanks
- Status changed to Needs review
over 1 year ago 8:05pm 25 March 2023 - last update
11 months ago Patch Failed to Apply - 🇩🇪Germany stefan.korn Jossgrund
I am a bit confused about the status of this issue.
Imho patch from #14 was the best solution so far, maintainer just requesting to not use Markup::create.
Merge Request #40 seems a bit of a mess now, i. e. what is "commerce_product_ui_product_form" doing in there?
I am providing patch based on #14 without Markup::create to maybe get this going again.
Regarding tests: Not sure what should be tested and how and if additional test is really necessary.
- 🇩🇪Germany stefan.korn Jossgrund
@Anybody: Okay, I am not sure about the double escaping. So we would need the Markup::create still to resolve this?
And changing to 2.x branch as this is current.
- last update
11 months ago Patch Failed to Apply - last update
11 months ago Patch Failed to Apply - 🇩🇪Germany stefan.korn Jossgrund
So testing this, it seems without Markup::create special characters in the title will indeed be double escaped. This would mean #15 is still the way to go.
- last update
11 months ago 30 pass - 🇩🇪Germany stefan.korn Jossgrund
now this patch based on #15 but applying to 2.x branch.
- 🇩🇪Germany Anybody Porta Westfalica
@stefan.korn thanks, seems you're right. Guess that happens because of https://api.drupal.org/api/drupal/core%21lib%21Drupal%21Component%21Rend...
Perhaps we can find a pattern in core for this case? Otherwise we need to find out, if we introduce security risks here and if yes, which. Perhaps they can be mitigated by using a different method? (If needed). Sorry I'm unsure myself.
- 🇮🇳India rajeshreeputra Pune
Rajeshreeputra → changed the visibility of the branch 3097313-string-translation-for-cloned to hidden.
- last update
5 months ago 30 pass - 🇮🇳India rajeshreeputra Pune
Rajeshreeputra → changed the visibility of the branch 3097313-string-translation-for-cloned to hidden.
- Status changed to Needs work
5 months ago 3:47am 9 July 2024 - 🇮🇳India ankitv18
With MR!40 noticed lot of issues and moreover issue is with version 2.x-dev and MR is against 1.x
Base branch should be 2.x-dev so that we can check issues on the pipelines too. - 🇮🇳India rajeshreeputra Pune
Rajeshreeputra → changed the visibility of the branch 3097313-8.x-1.x to hidden.
- Status changed to Needs review
5 months ago 4:10am 9 July 2024 - Status changed to Needs work
5 months ago 11:33am 9 July 2024 - Status changed to Needs review
4 months ago 11:40am 17 July 2024 - 🇮🇳India rajeshreeputra Pune
@TessBakker - Updated prefix/suffix as per language direction, please review.