WordPress.org
Get WordPress

Make WordPress Core

Opened 17 years ago

Closed 16 years ago

Last modified 16 years ago

#6795 closed enhancement (wontfix)

Byte Order Mark

Reported by: denis-de-bernardy's profile Denis-de-Bernardy Owned by: matt's profile matt
Milestone: Priority: normal
Severity: normal Version: 2.5
Component: Plugins Keywords: dev-feedback
Focuses: 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)

#1 @DD32
17 years ago

  • Milestone set to 2.7

#2 @matt
17 years ago

  • Milestone changed from 2.7 to 2.9

#3 @Denis-de-Bernardy
16 years ago

  • Component changed from General to WordPress.org
  • Keywords dev-feedback added
  • Owner changed from anonymous to matt

Unless I'm mistaking, SVN could do this automatically, using some kind of pre-commit hook.

#5 @Denis-de-Bernardy
16 years ago

  • Milestone changed from 2.9 to Unassigned
  • Type changed from defect (bug) to task (blessed)

#6 @DD32
16 years ago

  • 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.

#7 @Denis-de-Bernardy
16 years ago

  • Milestone Unassigned deleted
Note: See TracTickets for help on using tickets.