Opened 9 years ago
Last modified 6 years ago
#35339 new defect (bug)
Settings > Reading > Front Page Displays > Front Page and Posts Page Select Length of Text
Reported by: | robertwhitis | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 4.4 |
Component: | Administration | Keywords: | |
Focuses: | ui | Cc: |
Description (last modified by )
When choosing the Front Page and Posts Page within Reading Settings, if you have really long post or page titles, these are not truncated, leading to a pretty bad looking Settings page.
Screenshot:
This is further implicated if moving a column based admin as is discussed as having potential here: #16413
Expected output would be a limitation on the number of characters, what that limit should be is open for debate.
Change History (6)
#2
@
9 years ago
Since wp_dropdown_pages is used to generate these select inputs, it may be appropriate to add an additional parameter to this function, something akin to 'title_limit'.
#3
@
9 years ago
Agree we should truncate at a certain width. The setting page inputs are limited to 25ems — maybe we should limit the select boxes to that width as well.
#4
@
9 years ago
Thanks @melchoyce - the class .regular-text which is currently used for text inputs would accomplish this, however, not sure we should tie the width of select items to this class since it's intention is for text inputs.
From wp-admin/css/forms.css:
input.regular-text { width: 25em; }
Is your feeling that we would be better served by limiting all select inputs to 25em, or that we should create a class, .regular-select as an example, and then apply that class to the two dropdown fields on the Reading Settings page?
#5
@
9 years ago
Is your feeling that we would be better served by limiting all select inputs to 25em, or that we should create a class, .regular-select as an example, and then apply that class to the two dropdown fields on the Reading Settings page?
As far as I can tell, this is the only set of selects within settings that has this issue. I'd be fine with applying it directly to these selects, rather than creating a new class, but I'm also interested in hearing how @michaelarestad or @helen would approach this.
If this is determined to be changed and a good-first-bug, feel free to assign it to me.