Skip to:
Content

Opened 8 years ago

Closed 8 years ago

Last modified 3 years ago

#3165 closed enhancement (fixed)

No feedback when posting to activity stream frequently

Reported by: DJPaul Owned by: DJPaul
Milestone: 1.5 Priority: normal
Severity: normal Version:
Component: Templates Keywords: needs-ui
Cc:

Description

When posting activity stream items (via AJAX) from the "what's new, user?" form, there is an eight second delay built in to throttle posting. However, there is no user feedback that they need to wait until they can post again, potentially leading people to think that something's broken.

We should display a "hey, slow down" message somewhere.

Attachments (1)

screen-capture-2.png (27.8 KB) - added by DJPaul 8 years ago.
mockup

Download all attachments as: .zip

Change History (12)

@DJPaul
8 years ago

mockup

#1 @DJPaul
8 years ago

I've attached a quick mockup of the sort of thing I have in mind. Thoughts?

#2 @boonebgorges
8 years ago

Nice idea. I like the idea for formatting and behavior. As for language, "Slow down." sounds a bit unfriendly. How about "You're posting updates too quickly! Try again in a few seconds."

#3 @DJPaul
8 years ago

  • Milestone changed from Awaiting Review to 1.3
  • Type changed from defect to enhancement

#4 @boonebgorges
8 years ago

How do you think this should be done? The current method (setting the button to 'disabled') means that jQuery no longer registers a click event. So there'll have to be a different way of keeping track of when the last post was left. Maybe a cookie that expires after 8 seconds?

#5 @cnorris23
8 years ago

We could use the cookie and then using javascript, disable the post button, and add a countdown timer as text in place of "Post." What I just wrote is about as far as my thought process has gone. Feel free to shoot it down ;)

#6 @DJPaul
8 years ago

The current method is easy to bypass (reload the page). What about moving the throttle to PHP rather than client site

#7 @DJPaul
8 years ago

  • Keywords needs-ui added
  • Milestone changed from 1.3 to Future Release
  • Priority changed from minor to normal

Bumping to a future release unless someone wants to work on designs and a patch.

#8 @Dennissmolek
8 years ago

  • Owner set to Dennissmolek
  • Status changed from new to accepted

I am willing to work on this, but I think its not needed to add another request via PHP.

I think if we put in a notifier about the limit it will explain why its not working.

If users start complaining about tons of repeat comments then we can work on a PHP solution.

#9 @DJPaul
8 years ago

  • Milestone changed from Future Release to 1.3
  • Owner changed from Dennissmolek to DJPaul
  • Severity set to normal
  • Status changed from accepted to assigned

#10 @djpaul
8 years ago

  • Resolution set to fixed
  • Status changed from assigned to closed

(In [4814]) Remove hidden delay from posting to the activity stream, and tweak behaviour of the "what's up" form when posting. Fixes #3165. See also #3360

#11 @DJPaul
3 years ago

  • Component changed from Appearance - Template Parts to Templates
Note: See TracTickets for help on using tickets.