I want the link appear above the PM-section.

(DUH) my bad! lol....:D

Awesome mod!!!!! I love it!

Lea,

this is a really good hack...thank you for your work...:)

The only thing I can tell you is that the "edit post" action (#20) is not working for me.

I have emptied the relevant field in the options in order to log EVERY action. ;)

Have you tested all the actions?

Thanks again...hack of the month for me...;)

I discovered a bug with action #20, about an hour ago. It notifies the thread starter instead of the post poster.
Unfortunately, this means that I'll have to rewrite a great portion of the code, due to vB's crappy moderator logging on post edits :mad: (In fact I reported that as a bug to vbulletin.com, it does not store the postid in the moderatorlog on post edit).
I thought I had got over that bug in my code, but it seems I've missed something.

So, I'm currently rewritting the queries in order to overcome that problem.
Support will be temporarily not provided, so that I can focus on fixing the problem.
You'll have to wait a little bit.
I expect to release a fixed version later today or tomorrow at most.
Sorry and thanks for your patience and kind words :)

PS: Of course all the other actions are working fine, the problem is with post edits (action 20)

very nice and useful, thanks :)

More screens please?

How does a user start a conversation with the staff member who moderated his/her post?

After installing is there supposed to be a link to show the actions from within the USERCP, or do actions only show when they have been made? I don't see a link anywhere in my USERCP.

@COBRAws:
There is nothing else in the hack that can be displayed in a screenshot.
As for the conversation, he can go to his/her profile (if the moderator column is selected to be displayed) and start a PM one, the old fashioned way. :p

@Junkie:The table shows only if there are any actions for it to show, and it shows in the usercp home. Ensure there is something for it to show.

Hey Michelle,

cheers for updating so fast. Unfortunatly, I still get the same error. I guess my server doesn't support such a large query - I even set it down to 5 days max, no positive results...

I'll wait and see, maybe you'll come up with something :)

Cheers