Skip to:
Content

BuddyPress.org

Opened 15 years ago

Closed 13 years ago

#845 closed defect (bug) (fixed)

bp_format_time outputs non-l10n date

Reported by: remi's profile remi Owned by:
Milestone: 1.5 Priority: minor
Severity: Version:
Component: Core Keywords: date i18n l10n has-patch
Cc:

Description

The bp_format_time function uses PHP's date function which doesn't care about WordPress WP_LANG constant.

Here's attached is a patch that replace its usage of date with WP's date_i18n function.

Attachments (2)

datei18n_20090711.diff​ (680 bytes) - added by remi 15 years ago.
845.patch​ (1.2 KB) - added by GIGALinux 15 years ago.

Download all attachments as: .zip

Change History (15)

@remi
15 years ago

#1 @remi
15 years ago

  • Summary changed from bp_format_time outpus non-l10n date to bp_format_time outputs non-l10n date

#2 @remi
15 years ago

  • Keywords date i18n l10n added

#3 follow-up: @apeatling
15 years ago

Thanks will look into adding this soon. Could you check for other uses of date() in BuddyPress? I'm sure there are more than just this one.

#4 in reply to: ↑ 3 @remi
15 years ago

Replying to apeatling:

Thanks will look into adding this soon. Could you check for other uses of date() in BuddyPress? I'm sure there are more than just this one.

Found 24 other occurrences — will submit a new ticket/patch soon!

#5 @apeatling
15 years ago

  • Milestone set to 1.0.4

#6 @GIGALinux
15 years ago

  • Keywords has-patch added

Added patch

@GIGALinux
15 years ago

#7 @apeatling
15 years ago

  • Milestone changed from 1.0.4 to 1.1

Milestone 1.0.4 deleted

#8 @apeatling
15 years ago

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

(In [1702]) Fixes #845

#9 @apeatling
15 years ago

  • Resolution fixed deleted
  • Status changed from closed to reopened

Previous commit fixed #854 not this bug.

#10 @apeatling
15 years ago

  • Resolution set to fixed
  • Status changed from reopened to closed

(In [1726]) Fixes #845 props remi, GIGALinux

#11 @DJPaul
13 years ago

  • Component set to Core
  • Milestone changed from 1.1 to 1.3
  • Priority changed from major to minor
  • Resolution fixed deleted
  • Status changed from closed to reopened

Apparently this one has popped up again according to reports on the support site.

#13 @djpaul
13 years ago

  • Resolution set to fixed
  • Status changed from reopened to closed

(In [3339]) Use date_i18n() instead of date() for output. Fixes #845 again.

Note: See TracTickets for help on using tickets.