Problems with Token integration with Rules

I've been trying to figure this out too:

When you use the action 'load a status id', these are the only data selectors available:

SELECTOR LABEL DESCRIPTION
site:current-user:uid User ID The unique ID of the user account.
site:current-user:roles: User roles The roles of the user.
site:current-user:status Status Whether the user is active or blocked.

Not sure how to get the status ID.

There should be tokens for the comment being created, one of which should be the status ID. If tokens for the comment being created are not there, that is probably a bug. However, I can only respond to bug reports against the development build until there is a stable release.

Is it OK then for me to change this status to the development build? That is actually what I am using now and I am having the same problem.

No tokens for the status ID when trying to load a status from an event of saving a new comment.

Is it OK then for me to change this status to the development build?

Of course

Hard to tell since there's no version number in the .info file.

The only reason you wouldn't have a version number in the .info file is if you pulled the files from git. The drupal.org packaging script puts a block like this into every packaged release:

; Information added by drupal.org packaging script on 2012-07-17
version = "7.x-1.0-unstable4+73-dev"
core = "7.x"
project = "statuses"
datestamp = "1342486432"

The version should also appear at admin/modules.

The problem here seems to be that Statuses offers a "Load a status" action, but Rules now expects you to use its "Add a variable" action instead. Statuses aren't currently available as a type of variable to add, and the "Load a status" action doesn't have tokens available to it. It's not immediately obvious to me why there are no tokens available to the "Load a status" action, although there are some things wrong with the way the action is specified (untested patch attached).

Apologies -- to be clear, what does this patch do, if I apply it?

Might clear up some errors, but otherwise pretty much nothing right now :)

Renaming to more accurately reflect the root issue, since it is causing problems for several different Rule configurations.

I'm started on this :)

Ah Found out the problem.

Here also the problem is statuses is not an entity, however rules considers the statuses as entity. Rules module provided additional options to implement rules on non entity.

Attached a partial patch, still its need cleanup/fixes.

Note:
Actually the rules integration is broken, there is no problem with token integration :(

To identify this one point, explored lot resources and learned many things :)

Here is the complete patch.

Testers are welcome. Don't forget to monitor the log messages while testing.

Sample rule for sending mail to the sender of the status when someone commented on it,

{ "rules_user_commented_on_status" : {
    "LABEL" : "User commented on a status",
    "PLUGIN" : "reaction rule",
    "TAGS" : [ "Statuses" ],
    "REQUIRES" : [ "fbss_rules", "rules", "fbss_comments_rules" ],
    "ON" : [ "fbss_comments_save" ],
    "DO" : [
      { "fbss_rules_load_action" : {
          "USING" : { "sid" : [ "comment:sid" ] },
          "PROVIDE" : { "status_loaded" : { "status_loaded" : "Loaded status" } }
        }
      },
      { "mail" : {
          "to" : "[status-loaded:sender:mail]",
          "subject" : "[comment:commenter:name] commented on your status",
          "message" : "Hi [status-loaded:sender:name],\r\n\r\n[comment:commenter:name] commented on your status [status-loaded:message-formatted]\r\n\r\n\r\nRegards,\r\n[site:name]"
        }
      }
    ]
  }
}

Haven't tested, but looks good to me -- in any case it's better than what we have now. ;) If you think this issue is basically resolved, feel free to commit and address any followup problems in separate issue(s).

I thought waiting until someone test this and give a report.

Any volunteers?

By the way, Sorry for the very late replay, due to my health challenges unable to look into the issue queue for past 3 weeks.

Committed a fix to dev.

Hi mathankumark, you say that is commited but non updated dev version on the page. Where can we download the new dev ??

Thanks a lot and sorry for reopen the fixed issue.

Dev builds automatically regenerate every 12 hours. If you want it sooner than that, pull it down from git.

Just in case anybody is still interested in this topic, have a look at the Rules example included at the end of the answer to How to add missing data selector in "Create new entity" rules action?.

The rule shown there, was inspired by what's in comment #13 here. And instead of sending an eMail ("to" the "sender"-token), it does some extra Rules Actions to fetch a user entity (by property), and then uses that to target a message to that user (using the Message module ... which expects a REAL entity). A bit of Rules-hitech, but it works like a charm, starting from the status-loaded:sender as provided by the patch in #13.

I have tested the solution provided in #21

It works