WordPress.org

Make WordPress Core

Opened 10 years ago

Closed 5 years ago

#3752 closed defect (bug) (duplicate)

Long Page Titles in Page Parent

Reported by: andymatic Owned by:
Milestone: Priority: low
Severity: normal Version: 2.7
Component: UI Keywords:
Focuses: Cc:

Description

When using long titles for Pages and with many Pages in the system, the Page Parent drop-down (Manage/Write > Pages) goes off the edge of the browser window and the scroll-bar to scroll up and down to select the parent is also not visible to the user. Not sure if this can be fixed via CSS for the menu or having WP truncate the Title or having the Title broken up into multiple lines.

Attachments (2)

3752.diff (980 bytes) - added by rob1n 10 years ago.
Cut it off at 80 characters (modifiable by a filter) and add a ... to the end (in HTML entities).
3752.2.diff (1.0 KB) - added by rob1n 10 years ago.

Download all attachments as: .zip

Change History (24)

#1 @rob1n
10 years ago

  • Milestone changed from 2.0.eventually to 2.2
  • Owner changed from anonymous to rob1n
  • Status changed from new to assigned
  • Type changed from defect to enhancement

I don't know what can be done about this, though truncating the titles seems like a good option.

andymatic: How long is "long titles"?

#2 @rob1n
10 years ago

  • Keywords reporter-feedback 2nd-opinion dev-feedback added

@rob1n
10 years ago

Cut it off at 80 characters (modifiable by a filter) and add a ... to the end (in HTML entities).

#3 @rob1n
10 years ago

  • Keywords has-patch added; reporter-feedback 2nd-opinion removed

It's a bit hacky (to me, at least), and I have no idea if 80 characters is "long."

#4 @ryan
10 years ago

substr could mangle multi-byte character sets.

@rob1n
10 years ago

#5 @rob1n
10 years ago

I added in a check for mb_substr() and used it if it's there, but I don't know what we could do apart from that...

#6 @foolswisdom
10 years ago

  • Milestone changed from 2.2 to 2.3

#7 @rob1n
9 years ago

  • Status changed from assigned to new

#8 @foolswisdom
9 years ago

  • Milestone changed from 2.3 to 2.5 (future)

#9 @rob1n
9 years ago

  • Owner rob1n deleted

#10 @mrmist
8 years ago

  • Keywords needs-patch added; has-patch removed
  • Version set to 2.7

It has to be a really, really, really long name before this actually becomes a breaking issue (depending on screen resolution). With just a long name it's a UI annoyance, as you can get around it with careful screen positioning in IE (Opera seems to manage the boxes more sensibly).

Could do with a patch refresh.

#11 @FFEMTcJ
8 years ago

  • Milestone changed from 2.9 to 2.8

#12 @ryan
7 years ago

  • Component changed from Administration to UI

#13 @janeforshort
7 years ago

  • Milestone changed from 2.8 to Future Release

Punting due to impending release. Will reconsider in upcoming release cycle.

#14 @Denis-de-Bernardy
7 years ago

  • Keywords dev-feedback removed

#15 @johnbillion
6 years ago

  • Keywords has-patch added; needs-patch removed

#16 @mrmist
6 years ago

Still an issue at 3.0.

#17 @johnbillion
6 years ago

  • Keywords needs-refresh added; has-patch removed
  • Severity changed from minor to normal
  • Type changed from enhancement to defect (bug)
  • Version changed from 2.7 to 3.0

#18 @mrmist
6 years ago

  • Version changed from 3.0 to 2.7

Version should reflect when it was found, I believe.

#19 @solarissmoke
5 years ago

  • Keywords needs-refresh removed
  • Resolution set to duplicate
  • Status changed from new to closed

#17043 has a patch ready for commit

#20 @scribu
5 years ago

  • Milestone Future Release deleted

#21 @jtsternberg
5 years ago

  • Cc justin@… added
  • Keywords has-patch added
  • Resolution duplicate deleted
  • Status changed from closed to reopened
  • Version changed from 2.7 to 3.2.1

Why hasn't this been addressed? It only needs a simple css patch. see http://core.trac.wordpress.org/ticket/18168

#22 @nacin
5 years ago

  • Keywords has-patch removed
  • Resolution set to duplicate
  • Status changed from reopened to closed
  • Version changed from 3.2.1 to 2.7

No need to resurrect old tickets.

Also, the version field is for the earliest reported version that this bug affects.

Note: See TracTickets for help on using tickets.