Conversation Essentials

Conversation Essentials [Paid] 2.8.5

No permission to buy ($45.00)
Good point, I had downloaded 2.3.16 but forgot to updatre....

However just updated and get same:
Code:
    Error: Call to a member function isIgnoring() on null src/addons/SV/ConversationEssentials/XF/Repository/Conversation.php:370

    Generated by: Pete Thomas Jun 6, 2020 at 9:29 PM

Stack trace

#0 src/addons/SV/WarningImprovements/XF/Repository/Conversation.php(24): SV\ConversationEssentials\XF\Repository\Conversation->insertRecipients(Object(SV\ConversationEssentials\XF\Entity\ConversationMaster), Array, Object(SV\ConversationEssentials\XF\Entity\User))
#1 src/XF/Service/Conversation/Inviter.php(115): SV\WarningImprovements\XF\Repository\Conversation->insertRecipients(Object(SV\ConversationEssentials\XF\Entity\ConversationMaster), Array, Object(SV\ConversationEssentials\XF\Entity\User))
#2 src/addons/SV/ConversationEssentials/XF/Service/Conversation/Inviter.php(15): XF\Service\Conversation\Inviter->_save()
#3 src/XF/Service/ValidateAndSavableTrait.php(40): SV\ConversationEssentials\XF\Service\Conversation\Inviter->_save()
#4 src/XF/Pub/Controller/Conversation.php(814): XF\Service\Conversation\Inviter->save()
#5 src/XF/Mvc/Dispatcher.php(350): XF\Pub\Controller\Conversation->actionInvite(Object(XF\Mvc\ParameterBag))
#6 src/XF/Mvc/Dispatcher.php(257): XF\Mvc\Dispatcher->dispatchClass('XF:Conversation', 'Invite', Object(XF\Mvc\RouteMatch), Object(SV\ConversationEssentials\XF\Pub\Controller\Conversation), NULL)
#7 src/XF/Mvc/Dispatcher.php(113): XF\Mvc\Dispatcher->dispatchFromMatch(Object(XF\Mvc\RouteMatch), Object(SV\ConversationEssentials\XF\Pub\Controller\Conversation), NULL)
#8 src/XF/Mvc/Dispatcher.php(55): XF\Mvc\Dispatcher->dispatchLoop(Object(XF\Mvc\RouteMatch))
#9 src/XF/App.php(2190): XF\Mvc\Dispatcher->run()
#10 src/XF.php(391): XF\App->run()
#11 index.php(20): XF::runApp('XF\\Pub\\App')
#12 {main}

Request state

array(4) {
  ["url"] => string(52) "/conversations/welcome-to-cafesaxophone.20751/invite"
  ["referrer"] => string(71) "https://cafesaxophone.com/conversations/welcome-to-cafesaxophone.20751/"
  ["_GET"] => array(0) {
  }
  ["_POST"] => array(6) {
    ["tokens_select"] => string(7) "BUMNOTE"
    ["recipients"] => string(7) "BUMNOTE"
    ["_xfToken"] => string(8) "********"
    ["_xfRequestUri"] => string(46) "/conversations/welcome-to-cafesaxophone.20751/"
    ["_xfWithData"] => string(1) "1"
    ["_xfResponseType"] => string(4) "json"
  }
}
 
But is there a way to kick the deleted user from the conversation?

They don’t appear in the kick list, so it seems there is no way to delete the conversation. Even if the participants leave, it seems that conversation stays in the database.

I’m not saying it’s an issue with the add on as I presume it’s expected in XenForo, but just that being able to kick the deleted userwould solve this?
 
This is an XF1.x add-on, it isn't supported.

The XF2 version of Conversation Essentials has that feature

Sorry, I thought I was replying to XF2's version. Can you point out where that feature is? I have the add on activated, but I can't seem to find it. Thanks
 
Sorry, I thought I was replying to XF2's version. Can you point out where that feature is? I have the add on activated, but I can't seem to find it. Thanks
The Edit Conversation dialog.

It shows up as the option "Prevent conversation starter from unlocking the conversation." if you are a moderator or administrator. If you have Conversation Improvements installed, then it uses the "Manage Conversations" permission instead
 
Edit: I also would like to suggest a feature: an option for administrators and moderators to bypass the inbox size limit. I would like to be able to message an user even if he is over the quota.

Hello @Xon, I would like to bring this suggestion up again. Your addon is great I've been able to configure it exactly as I need. But my community has been online for almost 20 years, that means there are certain members with over 4000 conversations in their inboxes.

I decided to limit the inbox size and offer a paid upgrade to increase my member's inbox sizes and they are happily contributing to the site.

The problem comes when, even after they got the paid upgrade, they still can't get in touch with other members because their inboxes are full.

I think my suggestion of a new usergroup permission to bypass the inbox size limit would be beneficial both to users and admins. Right now, me as an Administrator can't get in touch privately with some members because of this and I'm OK with that, but it would make this addon perfect and a must have for me and I bet many other forums.

Thank you for reading!
 
Hello @Xon, I would like to bring this suggestion up again. Your addon is great I've been able to configure it exactly as I need. But my community has been online for almost 20 years, that means there are certain members with over 4000 conversations in their inboxes.

I decided to limit the inbox size and offer a paid upgrade to increase my member's inbox sizes and they are happily contributing to the site.

The problem comes when, even after they got the paid upgrade, they still can't get in touch with other members because their inboxes are full.

I think my suggestion of a new usergroup permission to bypass the inbox size limit would be beneficial both to users and admins. Right now, me as an Administrator can't get in touch privately with some members because of this and I'm OK with that, but it would make this addon perfect and a must have for me and I bet many other forums.

Thank you for reading!
But you can do that already.
Me, as admin can message to members even if they box is full. You have permission or option for that in ACP (for this addon).
 
But you can do that already.
Me, as admin can message to members even if they box is full. You have permission or option for that in ACP (for this addon).

I couldn't get a moderator to be able to send a private message to another user with a full inbox. Am I missing something?
 
i have this error

Code:
LogicException: Unexpected value disabled encountered. src/addons/SV/ConversationEssentials/XF/Entity/ConversationMaster.php:245
Generado por: Chan y Chao 12 Jun 2020 a las 13:16
Seguimiento
#0 src/XF/InlineMod/SimpleAction.php(57): SV\ConversationEssentials\XF\Entity\ConversationMaster->canSuppressAlert()
#1 src/XF/InlineMod/AbstractAction.php(68): XF\InlineMod\SimpleAction->canApplyToEntity()
#2 src/XF/InlineMod/AbstractAction.php(57): XF\InlineMod\AbstractAction->canApplyInternal()
#3 src/XF/Pub/Controller/InlineMod.php(42): XF\InlineMod\AbstractAction->canApply()
#4 src/XF/Mvc/Dispatcher.php(350): XF\Pub\Controller\InlineMod->actionShowActions()
#5 src/XF/Mvc/Dispatcher.php(257): XF\Mvc\Dispatcher->dispatchClass()
#6 src/XF/Mvc/Dispatcher.php(113): XF\Mvc\Dispatcher->dispatchFromMatch()
#7 src/XF/Mvc/Dispatcher.php(55): XF\Mvc\Dispatcher->dispatchLoop()
#8 src/XF/App.php(2184): XF\Mvc\Dispatcher->run()
#9 src/XF.php(391): XF\App->run()
#10 index.php(20): XF::runApp()
#11 {main}

Estado de la solicitud
array(4) {
["url"] => string(212) "/foro/index.php?inline-mod/&type=conversation&_xfRequestUri=%2Fforo%2Findex.php%3Fconversations%2Flabeled%26label_id%3D248&_xfWithData=1&_xfToken=1591960565%2C995a28f843c4a8156b5d240e47d4b623&_xfResponseType=json"
["referrer"] => string(69) "https://cloudbit.es/foro/index.php?conversations/labeled&label_id=248"
["_GET"] => array(6) {
["inline-mod/"] => string(0) ""
["type"] => string(12) "conversation"
["_xfRequestUri"] => string(50) "/foro/index.php?conversations/labeled&label_id=248"
["_xfWithData"] => string(1) "1"
["_xfToken"] => string(43) "1591960565,995a28f843c4a8156b5d240e47d4b623"
["_xfResponseType"] => string(4) "json"
}
["_POST"] => array(0) {
}
 
@Xon Hi I've just bought this, please can you tell me how to disable the prefix field in the messages?

Is it also possible to make kicks permanent, like when a member leaves? So it will stay if the addon is disabled or uninstalled.
 
@Xon Hi I've just bought this, please can you tell me how to disable the prefix field in the messages?
The prefix field should only show up if the user can create prefixes or has them.

Is it also possible to make kicks permanent, like when a member leaves? So it will stay if the addon is disabled or uninstalled.
Kick does this via default, they can't rejoin if kicked unless re-invited. And they are put into a 'deleted, ignored' state so it should stay the same.
 
Hello @Xon, I would like to bring this suggestion up again. Your addon is great I've been able to configure it exactly as I need. But my community has been online for almost 20 years, that means there are certain members with over 4000 conversations in their inboxes.

I decided to limit the inbox size and offer a paid upgrade to increase my member's inbox sizes and they are happily contributing to the site.

The problem comes when, even after they got the paid upgrade, they still can't get in touch with other members because their inboxes are full.

I think my suggestion of a new usergroup permission to bypass the inbox size limit would be beneficial both to users and admins. Right now, me as an Administrator can't get in touch privately with some members because of this and I'm OK with that, but it would make this addon perfect and a must have for me and I bet many other forums.

Thank you for reading!
If you have Conversation Improvements installed, you need to grant the " Manage any conversation" moderator permission, otherwise if that add-on isn't installed; the user needs to be a moderator or administrator.
 
The prefix field should only show up if the user can create prefixes or has them.
I have no prefixes added Screen Shot 2020-06-21 at 12.00.36 pm.png

I cannot find the permission to remove this. It will not let me set max number of prefixes below 1. Can this be updated so 0 setting would remove the field?

Kick does this via default, they can't rejoin if kicked unless re-invited
If I disable Conversation Essentials however they are able to view the chat again, which could create a problem.
 
If you have Conversation Improvements installed, you need to grant the " Manage any conversation" moderator permission, otherwise if that add-on isn't installed; the user needs to be a moderator or administrator.
Is it possible to let the conversation starter have a delete button which would kick all the participants and delete the conversation? I know they can reduce their box by leaving the conversation but this is confusing for direct messages, delete makes it much clearer.
 
I'm an admin on a site that has this add-on installed, and it appears that when a conversation reaches the maximum number of allowed participants, both the kick and invite link disappear. Shouldn't just the invite link disappear?
 
Back
Top Bottom