Make WordPress Core

Opened 10 years ago

Closed 9 years ago

#29306 closed defect (bug) (fixed)

Missing i18n in wp-db.php

Reported by: sergeybiryukov's profile SergeyBiryukov Owned by: sergeybiryukov's profile SergeyBiryukov
Milestone: 4.4 Priority: normal
Severity: normal Version: 3.9
Component: Database Keywords: has-patch 4.1-early
Focuses: Cc:

Description

There's an "Error reconnecting to the database" string (introduced in [27075]).

Unlike the "Error establishing a database connection" string, it does not use the __() function.

This looks like an omission.

Attachments (2)

29306.patch (531 bytes) - added by SergeyBiryukov 10 years ago.
29306.2.patch (585 bytes) - added by SergeyBiryukov 10 years ago.

Download all attachments as: .zip

Change History (8)

#1 @nacin
10 years ago

I want to say this was by design as it's too early in the process for strings to be loaded. We would need wp_load_translations_early(), I believe.

It looks like it was also possibly not translated originally because it was possible it was going to change (and it was a huge string). Should we wait until 4.1 to toss this to translators?

#2 @nacin
10 years ago

  • Component changed from I18N to Database

#3 @SergeyBiryukov
10 years ago

  • Keywords 4.1-early added; i18n-change removed
  • Milestone changed from 4.0 to Future Release

29306.2.patch adds wp_load_translations_early().

This can wait for 4.1.

This ticket was mentioned in Slack in #core-i18n by sergey. View the logs.


9 years ago

#5 @SergeyBiryukov
9 years ago

  • Milestone changed from Future Release to 4.4

#6 @SergeyBiryukov
9 years ago

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

In 34943:

Add wp_load_translations_early() to wpdb::check_connection().

Fixes #29306. See #34216.

Note: See TracTickets for help on using tickets.