Make WordPress Core

Opened 7 years ago

Closed 7 years ago

#3600 closed defect (bug) (wontfix)

No means to select content type from admin interface

Reported by: nickshanks Owned by:
Milestone: Priority: normal
Severity: normal Version: 2.0.7
Component: Administration Keywords: has-patch
Focuses: Cc:


A means should be available through the administrative interface for setting the html_type option. I provide a patch for options-misc to do this, though it could easily be moved to a different pane of needs be.

Attachments (1)

content-type.diff (1.4 KB) - added by nickshanks 7 years ago.
Patch to options-misc supporting content-type selection

Download all attachments as: .zip

Change History (9)

nickshanks7 years ago

Patch to options-misc supporting content-type selection

comment:1 Viper007Bond7 years ago

Your patch is missing a usage of the option. ;)

comment:2 markjaquith7 years ago

I recommend keeping the option under wraps until the wp-admin is able to use it (without XML parse errors).

comment:3 nickshanks7 years ago

To Mark: that's what my other bugs are for!
The well-formedness ones have been fixed in trunk already. The safari-needs-NCRs one I have a patch for.
The only thing that didn't work in xml mode were those quicktags. I just commented out that function, but there is a bug logged against it, and it would be easy to wrap in an if statement (i should just do that patch now…)

These can all be in for 2.2 easily, and if you put this one in 3 (three) good things™ will happen:

1) People will start using XHTML more for their blogs, causing readers to switch away from IE to FireFox/Opera/Whatever.

2) Microsoft might get off their arses and support it, as a larger and larger section of the internet becomes unavaioable to their customers.

3) The XHTML in WordPress will get a lot better tested and maintained. It will fend off detractors who think it's broken to the core and will never do XHTML properly.

comment:4 foolswisdom7 years ago

  • Milestone changed from 2.2 to 2.3

comment:5 rob1n7 years ago

I disagree with #2. People aren't going to make their websites unavailable to, what, 80% of the browsing population (1) just to promote standards. The world out there is a practical one, and the standards-hugging developers are a very small fraction of it. To effect change in such a Draconian method is, to say the least, not going to work.

comment:6 rob1n7 years ago

Oh, and (1): I just pulled that figure from nowhere, but the point is IE is a huge majority.

comment:7 follow-up: Otto427 years ago

I'm for this patch, simply because it will make it easier to start making WordPress output be more well-formed, for the day when IE finally will actually support the application/xhtml+xml Content Type.

Whether anybody uses it or not, at present, is rather beside the point. It would be extremely handy to be able to switch back and forth between the two during development.

comment:8 in reply to: ↑ 7 markjaquith7 years ago

  • Milestone 2.3 (trunk) deleted
  • Resolution set to wontfix
  • Status changed from new to closed

Replying to Otto42:

Whether anybody uses it or not, at present, is rather beside the point. It would be extremely handy to be able to switch back and forth between the two during development.

We shouldn't be focusing UI efforts on things that will only be used by developers. You can switch to application/xhtml+xml with a single line (check out the pre_option_OPTIONNAME filter), anyway.

Note: See TracTickets for help on using tickets.