#1468 closed defect (bug) (fixed)
load_plugin_textdomain() should accept variable paths
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 1.5.2 |
Component: | General | Keywords: | plugin path bg|has-patch bg|dev-feedback |
Focuses: | 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)
Change History (9)
#1
@
20 years ago
Here be the relevant issues & discussion: http://comox.textdrive.com/pipermail/wp-hackers/2005-June/001497.html
#2
@
20 years ago
- Keywords bg|needs-patch added
- Owner changed from anonymous to skippy
- Status changed from new to assigned
Note: See
TracTickets for help on using
tickets.
patch to take optional second argument for load_plugin_textdomain specifying path