Opened 14 years ago
Closed 11 years ago
#3250 closed defect (bug) (no action required)
Limit Username, First, Last, Length
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | |
Component: | Activity | Keywords: | close |
Cc: | dennissmolek |
Description
Right now I can have a long username, firstname, and last name. When displaying activity by default it shows my first name, last name, and then whatever I did.
This creates instances where the content is being pushed down and leaves orphans or creates odd display behavior.
Currently the groups component stops showing the group name after 114 characters which I think is long as well, not to mention forum topics.
I noticed this issue when testing for #3234
Attachments (3)
Change History (7)
#1
@
14 years ago
- Component changed from Core to Activity
- Keywords needs-patch added; username activity removed
- Milestone changed from Awaiting Review to Future Release
This goes back to bp_core_get_user_displayname(). Not sure that running it through bp_create_excerpt(), or otherwise limiting the length of the name, is the best way. I think we need to fix the CSS so that this field doesn't clip behind something else.
#2
@
13 years ago
- Severity set to normal
quick fix: add [ maxlength="9" ] to the username field in register.php to limit username length.
And; here's a small css snippet that will help with the issue...
#3
@
13 years ago
- Keywords close added; needs-patch removed
I just had a look at the way this works in the BP 1.5.x bp-default theme, and I don't really see a lot of room for improvement. We're no longer positioning the Reply and Favorite buttons absolutely, so we don't get the same overlap issues. And the suggestion that chrisclayton makes doesn't seem to me to be warranted - super-long names *already* spill off the screen in what I would call an appropriate way. See long-username.png
.
Can I close this, or am I missing something?
#4
@
11 years ago
- Milestone Future Release deleted
- Resolution set to invalid
- Status changed from new to closed
Just did another check in latest bp-legacy templates. I do not think this is a problem anymore with our current layouts. If you find specific places where there are still overlap issues, please open a ticket with details.
Box with long (not limited) username