Opened 17 years ago
Closed 16 years ago
#3845 closed enhancement (wontfix)
WPCON next to WPINC
Reported by: | Nazgul | Owned by: | Nazgul |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 2.2 |
Component: | Optimization | Keywords: | has-patch |
Focuses: | Cc: |
Description
We have WPINC defined, which points to wp-includes. It seems logical to also define a WPCON that points to wp-content.
Attachments (4)
Change History (16)
#2
@
17 years ago
- Owner changed from anonymous to Nazgul
Indeed for ease of use and consistency.
(And it saves some effort if we do want to change the folder name in the future.)
#5
@
17 years ago
- Keywords needs-patch added; has-patch removed
- Milestone changed from 2.3 to 2.4 (next)
Patch needs a refresh. Punting.
#6
@
17 years ago
- Keywords has-patch added; needs-patch removed
- Status changed from new to assigned
Patch refreshed
#7
@
17 years ago
- Keywords needs-patch added; has-patch removed
Nazgul, rss.php:645 -- you can't use a constant here (nor a variable, nor a function -- only hardcoded values)
#8
@
17 years ago
- Keywords has-patch added; needs-patch removed
I learn something new every day. :) re-refreshed patch added.
#9
@
17 years ago
you can't use a constant here (nor a variable, nor a function -- only hardcoded values)
I guess thats because its a Default class variable?
If so, Nazgul, you should set the default base in the constructor rather than just hard coding it if your modifying them all.
#10
@
16 years ago
This will break the enhancement to change the location of wp-content. There really should be a decision on whether to allow for those folders to be moved and make every place handle it well.
I would say that this ticket should be closed to allow for that change or at least not as drastic in some areas as to prevent the ability to relocate the wp-content folder.
Just for ease of use, right? User-definable
wp-content
directory would be a bit more complicated.