Make WordPress Core

Opened 12 years ago

Closed 12 years ago

#20510 closed defect (bug) (fixed)

Confusing unopened </strong> tag in _e() in setup_config.php

Reported by: jiehanzheng's profile jiehanzheng Owned by: azaozz's profile azaozz
Milestone: 3.4 Priority: normal
Severity: minor Version: 3.4
Component: I18N Keywords: has-patch commit
Focuses: Cc:


Here it looks confusing because translators would see this:

If for any reason this automatic file creation doesn't work, don't worry. All this does is fill in the database information to a configuration file. You may also simply open <code>wp-config-sample.php</code> in a text editor, fill in your information, and save it as <code>wp-config.php</code>. </strong></p>\n
<p>In all likelihood, these items were supplied to you by your Web Host. If you do not have this information, then you will need to contact them before you can continue. If you&#8217;re all ready&hellip;

Clearly the </strong> seems unopened to them.

I would be nice if we could split up this long string, and leave <strong /> tags outside of _e().

Attachments (1)

20510.diff (1.6 KB) - added by jiehanzheng 12 years ago.

Download all attachments as: .zip

Change History (4)

12 years ago

#1 @jiehanzheng
12 years ago

And by "setup_config.php" I mean "wp-admin/setup-config.php".

Last edited 12 years ago by jiehanzheng (previous) (diff)

#2 @SergeyBiryukov
12 years ago

  • Keywords commit added
  • Milestone changed from Awaiting Review to 3.4

Introduced in [19760].

#3 @azaozz
12 years ago

  • Owner set to azaozz
  • Resolution set to fixed
  • Status changed from new to closed

In [20564]:

Move closing HTML tag outside _e(), props jiehanzheng, fixes #20510

Note: See TracTickets for help on using tickets.