WordPress.org
Get WordPress

Make WordPress Core

Opened 20 years ago

Closed 19 years ago

#2033 closed defect (bug) (fixed)

Recommend removal of "rich_editing" global option

Reported by: markjaquith's profile markjaquith Owned by: markjaquith's profile markjaquith
Milestone: 2.1 Priority: normal
Severity: trivial Version: 2.0
Component: Administration Keywords: bg|has-patch
Focuses: Cc:

Description

The rich_editing global option is redundant, as it can already be set per-user. I don't see any great benefit from being able to set a default... at least not anything that justifies having an option dedicated to it.

Attachments (1)

remove-rich_editing-global-option.diff​ (4.2 KB) - added by markjaquith 20 years ago.
Patch for WP 2.0 SVN

Download all attachments as: .zip

Change History (6)

@markjaquith
20 years ago

Patch for WP 2.0 SVN

#1 @markjaquith
20 years ago

  • Keywords bg|has-patch added; bg|needs-patch removed
  • Owner changed from anonymous to markjaquith
  • Status changed from new to assigned

The patch removes the option, so I incremented the database version to enforce its removal. At the time that I made this patch, the current database version was 3243, and I incremented to 3244. I just want to point this out in case there are other increments before this patch gets considered... wouldn't want there to be a database decrement!

#2 @masquerade
20 years ago

+1 on the removal of this option.

#4 @matt
20 years ago

  • Milestone changed from 2.0 to 2.1

#5 @matt
19 years ago

  • Resolution set to fixed
  • Status changed from assigned to closed

(In [4574]) Remove the global rich_editing option, now it's just personal, fixes #2033

Note: See TracTickets for help on using tickets.