#6795 closed enhancement (wontfix)
Byte Order Mark
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Plugins | Version: | 2.5 |
| Severity: | normal | Keywords: | dev-feedback |
| Cc: |
Description
On occasion, BOM issues will break scripts. Example:
http://wordpress.org/support/topic/165717?replies=11
Could we add this somewhere in WP to check for BOM issues before they turn into end user nightmare? For instance, we could run it on plugins when they're activated, as a sanity check.
http://dev.fckeditor.net/browser/FCKeditor/trunk/_dev/php_bom_finder.php?rev=924
And maybe even fix them automatically.
D.
Change History (7)
- Component changed from General to WordPress.org
- Keywords dev-feedback added
- Owner changed from anonymous to matt
see also: #6690
- Milestone changed from 2.9 to Unassigned
- Type changed from defect (bug) to task (blessed)
- Component changed from WordPress.org to Plugins
- Resolution set to wontfix
- Status changed from new to closed
- Type changed from task (blessed) to enhancement
I'm closing as wontfix due to the limited actual instances of this. IMO, Plugin authors should be correcting it themselves, Or if users cause it by certain race conditions, need to deal with it themselves.
- Milestone Unassigned deleted
Note: See
TracTickets for help on using
tickets.
Unless I'm mistaking, SVN could do this automatically, using some kind of pre-commit hook.