set_on ( hook, [object_id], [value] )

[Pebble]

EDIT: I've added my own submit button for the tree to set the key which works OK, but the below request would make things easier/cleaner.

Hi Everyone,

I'm currently writing a plugin and using the post set_on( hook, [object_id], [value] ) but I need ( would like ) this to work for when someone edits a post.

In the API it says:

set_on
( hook, [object_id], [value] )
Triggers a plugin key to be set when a specific action occurs.

Parameters

hook String
The name of the action. Right now this is limited to 'thread_new' and 'post_new'.

So I suppose this is a request for an extra hook, eg: post_edit  or does someone know something I don't about setting the post key on edit. I didn't want to get all hacky if some other easier way already exists.

Just in case it matters, though I don't think it does, it's a family tree plugin, entered from the posting page but I want to have the option of editing the tree from the edit page. Demo ( which may or may not be working depending on if I'm playing about with it at the time and I've broken something! ) is here: pebbleplugins.proboards.com/thread/72/family-tree-testing

Cheers,
Pebble.

------------------------------------------------------------------------------------
EDIT2:

While I'm here as the above I've made a work around for the moment....

Is it possible to set a post key using 'thread_new' ?
If someone is creating a new thread then I want to set the post key when they submit the new thread.

I've tried using pb.plugin.key('familytree').set_on('post_new', tree );  but it doesn't work for the new thread post....

------------------------------------------------------------------------------------

[Chris]

Aug 31, 2014 21:28:15 GMT -8 Chris said:

I took a look at the source to come up with the above hack for limiting the plugin to staff only and noticed that it used a set_on hook not listed in the API reference:
 key.set_on('thread_edit', fieldHash);

According to the API: "Right now this is limited to 'thread_new' and 'post_new'."

The All about Plugin Keys thread lists even more hooks:

Nov 23, 2012 15:25:58 GMT -8:

Plugin Key Events

We offer a few different event bindings that you can use to change plugin key data when certain actions happen. These events are:

• thread_new - When a thread is created
• post_new - When a post is made
• post_quick_reply - When a post is made using the quick reply
• conversation_new - When a conversation is created
• message_new - When a reply to a conversation is made

Using these events, you can set a plugin key's data only when the event listed has occurred.

Here is sample code on how to bind to a plugin key event:

<script>
pb.plugin.key('example_thread_key').set_on('thread_new', 'Hello world');
</script>


Sept 2, 2014 12:35:25 GMT -8 Tim said:

Hmm, not sure how the API got wrong, but yeah, there look to be plugin key hooks on creating conversations and messages, and creating/updating threads and posts. I'll add a task in to update the API, but honestly at this point it's likelier that that task will languish until the bigger task that will add far more comprehensive hooks for set_on.

The thread_new hook is especially useful since it allows setting a key for a thread at the same time the thread is created (thus alleviating the problem of object_id being unknown since not yet created -- the chicken or the egg scenario)

[Pebble]

It's late at night so I'll take another read in the morning!

From the above, logic would say there is a hidden post_edit hook already in there. ( which I'll try tomorrow )
The thread_new hook, I've tried to use but it returns the id of the thread. What I really need is the id of the post when creating a new thread.

Like I say, it's late and it might make more sense in the morning!

[Chris]

The thread_new hook automatically chooses the object_id during thread creation and that is determined by the key type being used in the call, so if your key is of type POST then the object_id chosen would be the id of the first post in the thread. On the other hand if the key type is type THREAD then the object_id chosen would be the id of the thread. Also the post_new hook only fires on a REPLY (not a create) if I am remembering correctly so it might make better sense if it was actually called reply_new instead to further solidify that distinction.

[Pebble]

Cheers Chris for the help with this 'stuff'( as usual ).

I assumed the thread_new was for thread keys and post_new being for posts. I've been told I assume a lot , and shouldn't. But who listens to that sort of advice!

Anyway, back to my jumbled up code that even I can't follow anymore!

[Wormopolis]

post_edit and thread_edit hooks work. I use them in quarantine

[Chris]

Feb 2, 2015 21:14:17 GMT -8 Wormopolis said:

post_edit and thread_edit hooks work. I use them in quarantine

But thread_edit works when editing first post and post_edit works when editing replies (i.e. all other posts except the first) or at least that is what my dog keeps barking at me since he wrote a plugin using those hooks. Is that correct?

[Wormopolis]

you quoted me before i corrected it. thread_edit is for the first post in a thread. post_edit was for all the others.