Skip to:
Content

BuddyPress.org

Opened 14 years ago

Closed 12 years ago

#2101 closed enhancement (no action required)

User status can be very very long

Reported by: motomac's profile motomac Owned by:
Milestone: 1.6 Priority: minor
Severity: minor Version:
Component: Activity Keywords: needs-patch
Cc:

Description

User status can be very very long and can harm to view of main page. To my ming it will be better to limit it.

Change History (7)

#1 @r-a-y
14 years ago

Could be done with a plugin and some javascript.

#2 @motomac
14 years ago

But BP cuts long blog posts in activity stream on index... Why not statuses?

#3 @thecorkboard
14 years ago

  • Component set to Activity

Adding a limit option in the dashboard would be nice. do it by characters, add a character countdown.

#4 @boonebgorges
14 years ago

  • Milestone changed from 1.3 to Future Release

A character limit + character countdown would be nice, though as r-a-y says, it could be done with a plugin without too much trouble. Probably not going to happen for 1.3.

#5 @slaFFik
13 years ago

  • Keywords changed from status, long to status long
  • Severity set to minor

Boone (or Paul), this is rather interesting task.
Should be in the core?

#6 @boonebgorges
13 years ago

  • Keywords needs-patch added; status long removed
  • Milestone changed from Future Release to 1.6

I suppose it's a good idea. Perhaps we could use the same 'Read More' javascript and logic as we do for activity items in the stream (which was added after some of the earlier comments on this ticket). The default length should be such that statuses do not extend too far beyond the header avatar.

If someone works up a patch, we can get this early in the 1.6 cycle.

#7 @boonebgorges
12 years ago

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

It looks like this is no longer an issue. Activity items in the stream are truncated with the [Read More] ajax link. Activity updates in user headers are truncated, with a static "View" link. Unless someone wants to step forward with some fancy schmancy javascript, I think this is a good enough solution.

Note: See TracTickets for help on using tickets.