Closed (fixed)
Project:
Facebook-style Statuses (Microblog)
Version:
6.x-3.x-dev
Component:
Submodules
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
30 Apr 2010 at 10:50 UTC
Updated:
9 Jun 2011 at 16:41 UTC
Jump to comment: Most recent file
Comments
Comment #1
icecreamyou commentedFrom the project page:
In other words, it's planned. I usually don't really like it when issues are opened for something already mentioned on the project page, but I guess I wasn't specific, and there's no harm in leaving this open for now.
Comment #2
jrivelli commentedIs there any plan when this will be completed?
Comment #3
icecreamyou commentedNo plan. It will get completed when I have a sudden urge to do so in one of those rare moments when I actually have free development time... in other words I would like to get FBSSC in a solid stable state with all planned features by the end of August, but whether that will actually happen is kind of doubtful.
Comment #4
jrivelli commentedAlright sounds like a plan. I'm going to contact you to get some development going. I'm gonna fund all this I've finally decided.
Comment #5
momper commentedsubscribe
Comment #6
7sudos commentedHere's a module we wrote to add some limited rules integration for FBSSC. We used the fbss_after_save hook to provide a way to pass info about the comment into rules, as the site we were working on required user notification when other users commented on their statuses. This was very quick-and-dirty, but works (although we couldn't get the date type working, it wasn't necessary for our implementation).
Comment #7
capellicWow.. this is great! Thanks for this module -- exactly what I was looking for!
Comment #8
logickal commentedCapellic - Glad it helped you out!
I've put this module up in a sandbox repo in case anyone else needs it. Not sure how much more maintiaining I would actually do for this module, if I had time I would probably integrate the functionality into FBSSC itself.
Anyway, here's the link!
http://drupal.org/sandbox/logickal/1075186
Comment #9
logickal commentedIceCreamYou: I haven't yet had a chance to check out the new version of FBSC, which I assume will completely depricate my little rules integration module. Do you have any quick tips on what I could do to get this functionality ready for your next version or do you have that covered at this point?
Comment #10
icecreamyou commentedI think your module should be basically the same except that IIRC hook_fbssc_after_save() is now hook_fbss_comments_after_save (since the module was renamed from fbssc to fbss_comments).
Comment #11
logickal commentedI will pull your new versions down and update - if you aren't officially planning on rolling this functionality into the parent module, I'll clean this up and apply for full project status for it.
Comment #12
icecreamyou commentedI am planning to roll it into the parent. (Thanks for contributing.) Just need to find some time!
Comment #13
logickal commentedSounds great! Glad I could help!
Comment #15
icecreamyou commented...needs to be rolled into FBSS 3.x
Comment #16
icecreamyou commentedComment #17
liliplanet commentedsubscribe, thx!
Comment #18
mrwhizkid commentedHi --
I've been playing around with the submodule in #6. Seems to work quite well for alerting status authors when comments are posted to their status.
However, I have just spent the entire day trying to figure out how to alert all those who have commented to a status that the status they commented on has been updated.
I was looking at the Appbar helper function (which of course won't work with current versions of Appbar) to see if I could figure this out.
I found this:
I'm wondering if it's possible for me to do some sort of textual comparison in Rules based on this and then send a message out to all users who commented on the status?
Thanks for your help.
@IceCreamyou -- I realize you're very busy...I posted this here hoping that someone else might have a quick solution to this. Thanks.
Comment #19
icecreamyou commentedIf you have the status ID as $sid, you can get a list of everyone who commented on the same status like this:
I have not tested this. Also creating an interface for it is complicated because you can't create a token that represents an array. There would probably need to be a select box for the recipient with options like "commenter", "other commenters", "sender", "recipient (if applicable)", and "arbitrary user", and then there would need to be some JS to show and hide a textfield to enter tokens for the arbitrary user depending on whether that option is selected.
I appreciate you being considerate of my time. :) I expect to have much more time to work on FBSS over the next 3-4 months, starting in the next few days. (Unless I get distracted by Portal 2 or Crysis 2. :P)
Comment #20
mrwhizkid commentedThanks! I think this gets me going in the right direction.
I was trying to figure out how to make this work with rules. I think I can set up a rule (user comments on facebook status) and then add an action to execute some custom PHP code using the code you gave me to list the uid's that have commented on the status.
The only jump I can't seem to make here is how I could add a few more lines of code to send an appbar alert out to all of those UID's in the same code.
Based on what I saw above (I'm still trying to learn PHP), it would be something like:
appbar_set_message(t('$comment_user commented on a <a href="/statuses/$sid">status</a> on which you also commented.',But how do I tell appbar to send the alerts to the uids generated from the php code that you gave me?
Comment #21
icecreamyou commentedAppbar API: http://drupal.org/node/546536#api (this thread is not the best place to have that discussion)
If you are using an "execute custom PHP" action, just do
appbar_set_message(t('My message'), $account->uid)inside of all the if() statements instead of building an array of the UIDs.[The more generic solution would be to create a rules action in code that uses the code in #19 to select the recipients. However there's nothing FBSS itself can do to make it easier to do this in general because it's the action that has to know what to act on and actions are generally designed to deal with only one item (user) at a time.]
Comment #22
mrwhizkid commentedI am so close! I got the action to work correctly. It works beautifully except...
I can't get the variables to show up correctly. Username and sid are not working correctly.
***Update -- I added
and now the status id is working correctly. However, the username is showing up as anonymous.
Here is the code that I am using:
Comment #23
icecreamyou commentedCommitted Rules integration for the Comments submodule to dev