Opened 4 years ago
Closed 4 years ago
#9779 closed enhancement (wontfix)
Inconsistency between WP_PLUGIN_DIR and plugin_dir_path(), etc.
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Priority: | high | Milestone: | 2.8 |
| Component: | Plugins | Version: | 2.8 |
| Severity: | minor | Keywords: | has-patch tested commit dev-feedback |
| Cc: |
Description
It's rather minor, if it this is to get fixed, it's now or never.
The various path and url constants in WP don't add a trailing slash (except ABSPATH), and neither do the various content_url() et al functions. But plugin_dir_path() and plugin_dir_url() do.
Shouldn't it be consistent across the board?
Attachments (1)
Change History (8)
Denis-de-Bernardy — 4 years ago
- Keywords has-patch dev-feedback added
- Summary changed from Inconsistency between WP_PLUGIN_DIR and plugin_dir_path() to Inconsistency between WP_PLUGIN_DIR and plugin_dir_path(), etc.
- Component changed from General to Plugins
- Owner anonymous deleted
- Keywords tested commit added
- Priority changed from low to high
either way works for me, since it's documented. I merely meant to highlight the inconsistency with the other *_url() functions, which are not trailingslashed. once 2.8 is released, it'll be to late.
Note: See
TracTickets for help on using
tickets.
Leaving this for Mark.
I can see that they are inconsistent but they are well documented and the slashes make them easier to use so I am on the WONTFIX side of the fence.