I’m not able to test at the moment (am away for the next 7 days and am currently typing from my tablet). But it sounds like the ‘load more’ click is resulting in all activity item comments being revealed? As far as I’m aware, a load more click should load new activity items onto the page and should not have any impact on activity item comments being shown or hidden. It would make sense for the functionality which displays or hides activity item comments to be associated with a different event listener (i.e. not the load more button click)
Considering you’ve tested unsuccessfully on an unmodified Twenty Twelve – Thirteen – Fourteen, it might be worth making the core dev team aware of the problem by opening a Trac ticket:
It sure is possible but you’ll need to write a custom function to handle the behaviour. The hook you’ll need is messages_message_sent. It fires after a private message has been sent successfully.
@julia_b I just re-read your question. I’m now wondering what exactly you mean by tag someone? If you mean @-mention someone then email alert settings are available but if you meant hashtag someone #henrywright (which is what I originally thought you meant but am now not so sure) then that sort of functionality isn’t standard.
@danbp I completely missed the comment in bp-activity-functions.php you pointed out! I see there’s a @todo in the source, so I’m sure the core devs are dreaming up a solution as we speak 🙂
Regarding mentions, I’m not seeing how spaces in usernames can work. Say hypothetically my username is Henry Wright (note that’s my username and not my display name). How would you mention me in a public message?
@Henry Wright wouldn’t mention me. It’d mention someone with the username @Henry.
As @durkk mentioned, @-mentions work on username and not on display name. So going on what you have in the screenshot, sending a public message to @ Julia Buckley will actually send the message to a user with username @ Julia. This probably isn’t want you want.
@shanebp even if I provided some explanation of the priority requirement, I think my edit to change the hook to wp_enqueue_scripts may have introduced confusion to some people not as familiar with the priority param. I think it’s safer all round just to use wp_print_scripts, especially as the hook isn’t being deprecated as first thought.
