Make WordPress Core

Opened 7 years ago

Closed 7 years ago

#42639 closed enhancement (wontfix)

_e() function should be deprecated.

Reported by: rnaby's profile rnaby Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: I18N Keywords:
Focuses: Cc:

Description

Most of the time this _e() is being caught by PHPCS for escaping and validation. And I noticed all of the time this _e() function can be replaced by more secure esc_html_e or esc_attr_e. So it seems like this _e() creates a confusion with these esc_html_e and esc_attr_e. Therefore I propose to deprecate this _e().

Change History (1)

#1 @ocean90
7 years ago

  • Milestone Awaiting Review deleted
  • Resolution set to wontfix
  • Status changed from new to closed
  • Version trunk deleted

For core, translations are inherently trusted because of various checks, including a review process for translations. This has been mentioned before in https://core.trac.wordpress.org/ticket/30724#comment:8 so I'm going to close this as wontfix.

Note: See TracTickets for help on using tickets.