Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
It is no longer used..well since drupal 7 actually
It is used in drupal 6 in decode_entities but in 7 we switched to html_entity_decode
Comment | File | Size | Author |
---|---|---|---|
#1 | drupal-remove_unicode_entities-1981190-1.patch | 5.82 KB | ParisLiakos |
Comments
Comment #1
ParisLiakos CreditAttribution: ParisLiakos commentedComment #2
alexpottTagging :)
Comment #4
ParisLiakos CreditAttribution: ParisLiakos commented#1: drupal-remove_unicode_entities-1981190-1.patch queued for re-testing.
Comment #5
RobLoachI grepped through and couldn't find any use of
$html_entities
.Comment #6
webchickOh, nice.
Tagging D8MI just to let those folks chime in here and confirm/deny.
Comment #7
alexpottCommitted 105ce44 and pushed to 8.x. Thanks!
I think the patch will apply to D7...
Comment #8
alexpottCommitted 105ce44 and pushed to 8.x. Thanks!
I think the patch will apply to D7...
Comment #9
alexpott#1: drupal-remove_unicode_entities-1981190-1.patch queued for re-testing.
Comment #11
ParisLiakos CreditAttribution: ParisLiakos commentedd7 has no core/ yet:P
Comment #12
alexpottdoh :) updating status then
Comment #13
David_Rothstein CreditAttribution: David_Rothstein commentedHm, it looks like the patch in #878408: Replace decode_entities() with built-in html_entity_decode() removed it but the file was never deleted when the patch was committed...
At this point, is it really worth removing from Drupal 7? It's not causing any harm in the filesystem, and you never know if someone out there is using it for some reason.
Comment #14
alexpottAgree with #13... it's just not worth it. And you never know... :)
Comment #15.0
(not verified) CreditAttribution: commentedAdd more info