Hi,

We appreciate your response on Twitter, and here is the support we'd love to have. First, a quick note on who we are: We run Young Writers Project, a small nonprofit in Vermont that encourages kids to write, use digital media and otherwise express themselves; we provide civil space, guidance, support, editing and many places to publish their best work. We've used Drupal since our inception 10 years ago, but much has changed.

We are creating a new D7 site to replace our present teen writing community, http://youngwritersproject.org (D4.7>>D5>>D6). D7 is a steep learning curve for us, particularly given all the changes in Drupal and in Web technology. We tested a beta version with teen users and believe that your wonderful module Statuses could be used in all interactive exchanges on the site -- comments, chat, shoutbox, idea formation, personal statuses, private messaging. We think having one widget for multiple functionalities makes more sense than having multiple modules to do the same. But we need some help. We can pay, though our budget is tight. And we also would be happy to be directed to some additional detailed case-use information, directions and documentation.

Here is the functionality we would love with this module:

  • AUTHOR AUTO REFRESH: A user posts a status update; the update is automatically refreshed. (We have posted to issue: https://www.drupal.org/node/1547864 but I suspect this is an odd, one-case problem; we've tried all the suggested solutions but still can't get it to work.)
    • READER AUTO REFRESH: A user posts a status update, another user on another screen but the same page, sees the status update refresh automatically to reveal the new status update. (Would mirror chat functionality.)
  • NON-CONTEXTUAL BLOCK: Block on front page that utilizes separate, single-use stream. (We want an "ideaboard" that has a block presence on front page)
  • SINGLE-USE STREAMS: Separate streams for separate functions. For instance, a stream that is for ideas or for six-word stories or for a random challenge of some sort.
  • Private statuses.
  • USERPOINTS: Integration with userpoints module (We are going to be giving user points for comments on specific nodes. Can we do the same if a user posts status to a specific node?)

Our aim in this is to make things more simple for the users. We think it would be fascinating to see how this functionality would promote creativity, writing, interaction and growth. Please let us know if this is something you can help us with.

Thanks in advance.

geoff

ggevalt@youngwritersproject.org
Young Writers Project
Burlington, VT

Comments

ggevalt’s picture

Title: Autorefresh for all users when status update is posted » Seeking some support for expanded use of statuses on site
Category: Feature request » Support request
Issue summary: View changes
ggevalt’s picture

Issue summary: View changes
ggevalt’s picture

Issue summary: View changes
IceCreamYou’s picture

Status: Active » Fixed

I'm not available for consulting/development services at this time but you can post issues in the queue for specific problems you are encountering. Please limit to one question per issue.

READER AUTO REFRESH: A user posts a status update, another user on another screen but the same page, sees the status update refresh automatically to reveal the new status update. (Would mirror chat functionality.)

This requires writing new code to achieve. Conceptually it's not that difficult but in general real-time updates are resource-intensive on the server side.

NON-CONTEXTUAL BLOCK: Block on front page that utilizes separate, single-use stream. (We want an "ideaboard" that has a block presence on front page)

You can use the General context for this or create your own.

SINGLE-USE STREAMS: Separate streams for separate functions. For instance, a stream that is for ideas or for six-word stories or for a random challenge of some sort.

Other than the number of characters, you can't limit what people put in a status without custom code - it's just a blob of text, so you couldn't require that people only submitted six-word stories. Most likely you could use the Node context to have different streams for different purposes, or create your own in custom code.

Private statuses.

There is a submodule for this. Private messages show up in normal user streams but they are only visible to the sender and recipient.

USERPOINTS: Integration with userpoints module (We are going to be giving user points for comments on specific nodes. Can we do the same if a user posts status to a specific node?)

There is a submodule for this.

ggevalt’s picture

Thanks so much for your responses.

Quite helpful.

And thanks for the great module. We see great opportunities to use this to help youths go deeper on their work.

cheers,

g

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.