Conversation Improvements by Xon 1.3.15

[Mouth]

I can recall which one went to Stuart but for me User/moderator/conversation are my 3

Oh yeah, you are right, the essentials suite was 4 add-ons.
Tag Essentials went to Stuart.

 

[Floyd R Turbo]

5, elastisearch is Xon's too, right?

 

[Mouth]

5, elastisearch is Xon's too, right?

Snap! Do we hear 6?

 

[Xon]

Snap! Do we hear 6?

Prefix Essentials, Tag Essentials went to @Stuart Wright
I picked up Conversation Essentials, User Essentials, Elastic Search Essentials, Moderator Essentials. So that is 6.

I've then got an Xen Product Manager Essentials, which is in private beta atm. I want to add some better stats reporting before I release 1.0.0 but I use it myself.

So not quite yet 7

 

[Scoobie]

@Xon

Manage Conversations by anyone - does this selection only allow the moderator to edit a conversation are a part of - or does it allow them to go into any conversation and edit it, even if they are not a part of it?

Thanks!

 

[Xon]

Manage Conversations by anyone - does this selection only allow the moderator to edit a conversation are a part of - or does it allow them to go into any conversation and edit it, even if they are not a part of it?

It only allows a moderator to edit a conversation they are already a part of.

 

[Robert9]

I like this addon, but i dont want to allow the search. Can i switch it off?

 

[Xon]

I like this addon, but i dont want to allow the search. Can i switch it off?

There is a GUI option exposed via Conversation Essentials as it extends Conversation Improvements to support it. Otherwise you need to-do a fairly simple code edit (unsupported) to disable it.

 

[llk]

Based on the database schema modification statement under "Or just edit support:", I assumed this addon could run without the `_likes` and `like_users` columns being added to the xf_conversation_message table, as long as the likes feature isn't actually used. But I'm getting the error "Unknown column '_likes' in 'field list'" from code that tries to create a conversation message, so it looks like that's not correct.

What code changes would we need to make to disable conversation likes completely, so that those columns don't need to be added to the database? You might also want to put a warning about this next to the "Or just edit support" instructions in the overview.

 

[Xon]

@llk while it can support not having the Like columns when viewing or reading converstaions, XF's datawriter system isn't smart enough to handle missing columns when starting a conversation or replying to it.

I've updated the documentation to correctly state both are required.

 

[Xon]

Xon updated Conversation Improvements by Xon with a new update entry:

1.3.7 - Maintenance update

• Add "Display results as conversations" to quick search drop-down, as this option exists from the advanced conversation search.

Read the rest of this update entry...

 

[Freelancer]

Feature Request: "Merge" and "Split" conversations as Moderator Permission / Inline Mod Tool... pretty please

 

[Xon]

Xon updated Conversation Improvements by Xon with a new update entry:

1.3.8 - Maintenance release

• This release will unblock upgrading from XF1.x to XF2.x

Read the rest of this update entry...

 

[Xon]

Xon updated Conversation Improvements by Xon with a new update entry:

1.3.9 - Maintenance update

• Fix "Mysqli prepare error: Prepared statement contains too many placeholders" when indexing large numbers of conversations

Read the rest of this update entry...

 

[Xon]

Xon updated Conversation Improvements by Xon with a new update entry:

1.3.10 - Maintenance release

This add-on now requires php 5.4

• Dramatically reduce memory usage when bulk-indexing conversation messages
  • With a 512mb memory limit, went from being able to index ~1500 conversation messages per run, to being able to index ~150000 conversation messages per run

Read the rest of this update entry...

 

[Xon]

XF2 entity system may be a regression due to requiring so much to be loaded at once

So much nicer in other ways, but if you have a large number of entities loaded; you have to pay the memory cost of them. However, only loading them once may help compared to how 'wide' the XF1 queries are.

 

[Xon]

Xon updated Conversation Improvements by Xon with a new update entry:

1.3.11 - Bugfix update

• Fix breaking listing conversations due to too aggressive pruning fetched conversation data (it should only have applied during search indexing)

Read the rest of this update entry...

 

[Xon]

The version the resource manager called 2017-0-18, is just 1.3.11 without the verison id set correctly. Re-uploaded the same zip to give it the right version number

 

[Xon]

Xon updated Conversation Improvements by Xon with a new update entry:

1.3.12 - Bugfix release

• Fix "Undefined index: recipient_state"

Read the rest of this update entry...

 

[Xon]

Xon updated Conversation Improvements by Xon with a new update entry:

1.3.13 - Compatibility update

• Fix "Undefined index: recipient_state" when interacting with other add-ons

Read the rest of this update entry...