Make WordPress Core

Opened 15 years ago

Closed 14 years ago

Last modified 13 years ago

#2403 closed defect (bug) (invalid)

Rich editor setting in Site Admin->Options->Writing Options is unclear

Reported by: aylwin Owned by: davidhouse
Milestone: Priority: normal
Severity: minor Version: 2.0
Component: Administration Keywords:
Focuses: Cc:


From a discussion on the wp-testers mailing list, it became evident that the purpose to the visual rich editor formatting setting under Site Admin->Options->Writing Options is not entirely clear: http://comox.textdrive.com/pipermail/wp-testers/2006-February/002150.html

Currently the description of the setting is as follows:
"Users should use the visual rich editor by default"

This is not very accurate since the setting only affects new users. Therefore, I would like to propose a clearer description, like:
"Enable the visual rich editor as default for newly created users"

Of course, if anyone has a better suggestion then that would be welcome too.

Attachments (1)

2403.diff (3.8 KB) - added by davidhouse 14 years ago.

Download all attachments as: .zip

Change History (8)

#1 @markjaquith
15 years ago

  • Owner changed from anonymous to markjaquith
  • Status changed from new to assigned

Recommend that we axe the setting altogether.

#3 @davidhouse
14 years ago

  • Owner changed from markjaquith to davidhouse
  • Status changed from assigned to new

It's been over a month and Mark hasn't produced a patch, so I'm stealing this one :)

#4 @davidhouse
14 years ago

  • Status changed from new to assigned

Err, I don't know why that set the status to "new".

#5 @davidhouse
14 years ago

Option seemed to be broken anyway: I set it to false and created a new user, promoted them to an author and they had RTE. (verification of this would be appreciated)

Patch attached to remove it. I added 'rich_editing' to the list of deleted options in upgrade-schema.php, so if the committor could bump the DB version to make sure it gets removed, that'd be great.

14 years ago

#6 @markjaquith
14 years ago

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

The option is gone, so this is no longer relevant.

#7 @Nazgul
13 years ago

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