Make WordPress Core

Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#4352 closed defect (bug) (wontfix)

Reinstate 'Write Post' heading under Write->Post for consistency

Reported by: johnbillion Owned by: rob1n
Milestone: Priority: normal
Severity: trivial Version: 2.2
Component: Administration Keywords: has-patch 2nd-opinion
Focuses: Cc:


Affects versions 2.1 and above.

Go to Write->Post and you'll notice there is no "Write Post" header above the post title input, unlike there is under Write->Page where it says "Write Page".

This has been lost from edit-form-advanced.php somewhere between 2.0 and 2.1. Patch attached to re-instate it for consistency across writing screens.

Happy bank holiday everyone!

Attachments (1)

4352.diff (356 bytes) - added by johnbillion 11 years ago.

Download all attachments as: .zip

Change History (7)

11 years ago

#1 @johnbillion
11 years ago

  • Keywords has-patch added

#2 @rob1n
11 years ago

  • Keywords 2nd-opinion added
  • Owner changed from anonymous to rob1n
  • Status changed from new to assigned

Thus leads to the debate of simplicity or consistency.

Simplicity in the fact that the Write Post screen is the default one, and for some the <h2> would add clutter, whereas on the Write Page it's not the post one, so better to alert the user to this.

Consistency in the fact that both should have the <h2>'s.

I would go to the latter (consistency) choice if I had to decide, but IMO it doesn't make much of a difference.

#3 @rob1n
11 years ago

  • Status changed from assigned to new
  • Version changed from 2.1 to 2.2

#4 @johnbillion
11 years ago

Drop this into 2.3? If not then may as well close as wontfix.

#5 @foolswisdom
11 years ago

  • Resolution set to wontfix
  • Status changed from new to closed

Closing as WONTFIX, b/c seems like a minor aesthetic detail (I actually prefer the "alerting" differentiation), but the happycog design work will see this significantly reworked for 2.4 .

#6 @foolswisdom
11 years ago

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