Yeah that's good to limit the number of replies per conversation.That's not currently a feature but it'd be possible to add it. The only thing is, it wouldn't work retrospectively. It'll only prevent new messages from sending a conversation over the limit.
This actually seems like a bug. It is supposed to be checking the size of each recipient's inbox before allowing the message to be created.Please try to add an option to limit the number of conversations user can have in his inbox too. He can receive conversations but he can not start new conversations if he has exceeded the limit of conversations he can have in his inbox.
That's actually a User Essentials feature.+Reminder: "Starred Conversations" need the conversation wrapper...![]()
Fixed in the next version.Found an inline style property in "convess_conversation_add_groups" template that is in an extra div around the "linkGroup convessPopupLocation" for conversation groups: style="position:block;". I am pretty sure this will not work. Somehow position and display got mixed. I recognized that the position of the participation group popup menu moved away after the last upgrade or so.
Fixed in the next version.Ah yeah but that we have turned off some time ago (and deleted and rebuilt the search index afterwards), so that doesn't explain it in our case... unless it's still doing something even though conversation indexing disabled...?
Because now that you say it, I do use the PMs a lot.
ok, testing...
CONFIRMED!
I just sent a PM, and the number of posts in "Postings" dropped by one.
I can reproduce this now.
@Daniel Hood your conversation indexing still seems to be doing something even though it's disabled for us.
OMG YES!Fixed in the next version.
What's New
- Fixed a bug that resulted in conversation messages being indexed regardless of the search option.
- Fixed a typo in a template that was invalid css.
Didn't fix for me.Daniel Hood updated Conversation Essentials with a new update entry:
1.11.3
Read the rest of this update entry...
How can I confirm that?That doesn't make any sense at all. Are you sure the search handler file uspdated?
BTW @Daniel HoodHow can I confirm that?
I upgraded the add-on as usual (unzip, upload the contents of the upload directory, overwriting previous stuff, then used the convess xml to upgrade the add-on; 1.11.3 it says I have in the "List Add-ons")
Yep! Works nowYeah, I realized the problem is my fault. The zip was messed up a little. I just swapped it out (since not many people have updated yet). Anyone that updated earlier and is affected by this bug should download the zip again and it's resolved. Thanks @markku for all your help.
Should run update or just upload files?nyone that updated earlier and is affected by this bug should download the zip again and it's resolved
If you installed the first 1.11.3 then just upload the files, otherwise do both.Should run update or just upload files?
We use essential cookies to make this site work, and optional cookies to enhance your experience.