[Martin A]

This seems to be related to having the open minichats info stored in the cookies and then switching between multiple users. The plugin is showing a chat which the current user has no access to but the previous user had it opene in the same browser. This is my guess on why it’s happening. I’m also seeing this but only when using the Switch users plugin.

[Martin A]

Great, thanks! I’ll be waiting 🙂

[Martin A]

Hey,

What i’m trying to achieve is that there is a button in my template (which knows the current logged in user id and also the other user’s id who they want to chat to). Clicking this button should open the minichat. If there is an existing thread between these two users, then i can use BBPMOpenMiniChat(thread_id, open) because i also know the thread_id already in my templated. But if there isn’t an existing thread, then i can’t open it right now. I want to enable that as well.

So to recap – a button in the template that opens an existing thread between users in a minichat or if there isn’t an existing thread, creates a thread and opens it in a minichat.

I created three screenshots illustrating this idea. You can see them here: https://www.dropbox.com/sh/c9a2tt4z5n7e1ex/AACCQPcFv5HC9RSxVIHWOsuLa?dl=0

[Martin A]

Hey, thanks! This works great for opening an existing chat.

But before i can launch this new chat to my users i also need to be able to directly open a mini chat between two users who don’t have an existing thead. How can i solve this?

If i understand correctly Buddypress requires a message to be sent before a new thread id can be created in the database. An option to get around this would be to create an empty message programmatically and thus get the thread id. However this would trigger the email notifications as well right? And that would be a problem for an empty message. And i don’t want to create empty messages between all of the users on my site just in case, that would create a lot of trash data in the database.

Ideally an empty message would be create only once i initialize the open of the minichat. Then an empty message can be created, a thread id can be generated and a mini chat can be opened. And somehow the email notification would need to be suppressed.

Do you have any suggestions on how to solve this? It’s still a show-stopper at the moment. But your plugin is so good i want to release it to my users as soon as possible 🙂

[Martin A]

Yes, i did it with css for now. Thanks!

[Martin A]

Thanks! I will be waiting for it.

[Martin A]

Hey, any updates or estimations on this feature? We’re waiting to launch the improved messages to our users and want to launch with this feature.

Thanks!

[Martin A]

OK, sounds great. Any time estimation when this would be available?

Just to clarify, this would enable to open with a link in template an existing thread between users in minichat or create a new chat if necessary and then open it in minichat?

Thanks!

[Martin A]

No. Can i create it using one of the standard BP classes and then open it with jQuery in a mini-chat?

[Martin A]

Thanks, i will take a look.

[Martin A]

One question still remains regarding the email notifications. When i activated the plugin on an existing site where there were already private messages exchanged between users, bp better messages sent out email notifications for all past conversations as well. I know this because i had mailtrap.io set as our smtp service provider on our staging site and it captured all the emails that were sent out.

How can i prevent this once i enable the plugin on our live environment?

[Martin A]

Ok thanks for the quick response!

[Martin A]

Alright, thank you!

[Martin A]

Alright, but is there a way to edit the template myself to remove the starring features? Without modifying the files in the plugin directory?

[Author]

Posts