#17172 closed enhancement (wontfix)
SCRIPT_DEBUG should be documented and defined false in wp-config-sample.php
| Reported by: | jorbin | Owned by: | |
|---|---|---|---|
| Priority: | low | Milestone: | |
| Component: | Inline Docs | Version: | |
| Severity: | normal | Keywords: | 2nd-opinion has-patch |
| Cc: | Focuses: |
Description
We define and document WP_DEBUG in wp-config-sample.php . It will be easier for people to contribute cs/jss if we define it as false as well to get
Related: #12236
Attachments (1)
Change History (4)
#2
in reply to: ↑ 1
@
15 years ago
- Resolution → wontfix
- Status new → closed
Replying to nacin:
I don't think this is necessary. It's only used for core development, rather than extensions. Might increase core CSS hacking. Also, unnecessarily lengtens the config file, which can be intimating.
I agree it isn't necessary.
However, I would encourage plugins to support it for there CSS and JS files.
All the ones I write do now - that way you have readable, editable js/css and compressed versions too :)
Note:
See TracTickets
for help on using tickets.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
I don't think this is necessary. It's only used for core development, rather than extensions. Might increase core CSS hacking. Also, unnecessarily lengtens the config file, which can be intimating.