Opened 8 years ago

Closed 8 years ago

Last modified 6 years ago

#1468 closed defect (bug) (fixed)

load_plugin_textdomain() should accept variable paths

Reported by: firas Owned by: skippy
Priority: normal Milestone:
Component: General Version: 1.5.2
Severity: normal Keywords: plugin path bg|has-patch bg|dev-feedback
Cc:

Description

Currently, the load_plugin_textdomain() function is hardcoded to look under [ABSPATH . "wp-content/plugins/"] for a plugin's translation file. It should take an optional argument specifying the location of this file, such as wp-content/plugins/plugin-name/translations/ and so on.

Attachments (1)

locale-patch.txt​ (471 bytes) - added by firas 8 years ago.
patch to take optional second argument for load_plugin_textdomain specifying path

Download all attachments as: .zip

Change History (9)

firas — 8 years ago

patch to take optional second argument for load_plugin_textdomain specifying path

comment:2   skippy — 8 years ago

  • Keywords bg|needs-patch added
  • Owner changed from anonymous to skippy
  • Status changed from new to assigned

comment:3   skippy — 8 years ago

  • Keywords bg|has-patch added; bg|needs-patch removed

comment:4   markjaquith — 8 years ago

  • Keywords bg|dev-feedback added

comment:5   skippy — 8 years ago

  • Milestone set to 1.5.2

comment:6   matt — 8 years ago

  • Milestone changed from 1.5.2 to 1.6

comment:7   ryan — 8 years ago

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

(In [2888]) Add variable path support to load_plugin_textdomain() in order to support subdir plugins. Props firas. fixes #1468

comment:8   anonymous — 6 years ago

  • Milestone 2.0 deleted

Milestone 2.0 deleted

Note: See TracTickets for help on using tickets.