UPDATES EasyBlog 6.0.14 Released! Joomla 5.x and PHP 8.x compatible now!

Helpdesk

Your Time
Our Time
Response Time
24 — 48 hours
We strive to provide the fastest ever response possible. However, we are not super beings.

Allow at least 24 — 48 hours
  Support is offline
Our team is away during the weekend. Some answers may already be available on our documentation

Rest assured that we will get back to your posts as soon as the week starts!
  Support is offline

Conversation API Issues

dave parkhurst · ·
11:58 AM Wednesday, 01 May 2019
Urgent
I currently have 2 issues that I am looking for answers on and can't seem to find it in the developer documentation anywhere.

Issue 1: Creating a new group message
I was able to find the documentation for opening a popup to create a new message for a specific user. I am looking to open a popup that populates a list of specific users to create a new group message. The documentation on the developer site refers to the old Foundry way of calling the popup conversation scripts. That documentation didn't work as Foundry is apparently deprecated.

I did figure out how to initialize the popups and creating a new single user conversation to a specific user works with no issues.

Here is the link I am using to create a new conversation popup:



What I don't understand is how to utilize the data-es-conversations-listid attribute. The documentation says that is the attribute for sending messages to a group of friends, but it does not give any reference as to how to use it or the data type that is expected as a value.

Being able to set a title for a new conversation would be helpful as well.

Issue 2 Renaming of Conversations:

It appears that I can rename a conversation that only involved 2 users (myself and another user). Renaming a conversation with multiple users however fails. The conversation title never changes. There is no feedback and nothing in the console that would specify an error occurring. If there is a way to create the conversation name upon creating a new message that would pretty much alleviate this issue.

I like the extension so far, I am just having to muddle my way through it to implement it into my own component and figure out the new API since the old documentation is deprecated.
The replies under this section are restricted to logged in users or users with an active subscription with us