Conversation Essentials

Conversation Essentials [Paid] 1.14.1

No permission to buy ($45.00)
  • Thread starter Thread starter Syndol
  • Start date Start date
@Xon After installing "Conversation Essential" and "Conversation Improvements" and "Post Rating Compatibility", should anything special be done to change LIKE to ratings in conversations? (can't find any option for it)

Thanks
 
@Dadparvar sadly this does not add Post Rating to conversations. What "Post Rating Compatibility" does is add some extra UI bits so Conversation Essentials fully works with Posting Ratings being installed.

It is basically a total rewrite of post ratings for it to support conversations.
 
is there any plan to add support of username placeholder for auto respond? (or is is already possible and I don't know?)

Thanks
 
It doesn't support any placeholders for the auto-respond, and I don't have plans to expand that due to XF2 being on the horizon and working to figure out how to migrate mt add-ons to it.
 
Xon updated Conversation Essentials with a new update entry:

1.12.12 - Bugfix update

  • Split bulk template modification code for Filters into the template convess_conversation_list_filter
    • fix filter links now showing up as expected.
  • Fix installer when upgrading from pre-1.12.8
Know compatibility issue:
  • UI.X & setting a conversation prefix results in the prefix appearing behind the popup.
    • Installing Multi Prefix "fixes" this by replacing the prefix...

Read the rest of this update entry...
 
@Jake B. fyi, there is a compatibility issue with UI.X & this addon's conversation prefix UI.

In uix.css;
Code:
.Menu { z-index: 9000;}

XenForo standard title_prefix_edit.css has:
Code:
.PrefixMenu
{
 z-index: 15000;
...
Due to CSS ordering, .Menu has preference over .PrefixMenu

Overlays gets a z-index of 10000, which is why .PrefixMenu is getting pushed the overlay.
 
@Xon Could you elaborate what exactly that means...
  • UI.X & setting a conversation prefix results in the prefix appearing behind the popup.
    • Installing Multi Prefix "fixes" this by replacing the prefix...

Because in the current previously installed version of ConvEss it is not a problem...
 
Last edited:
Getting this when trying to save options,

"You must select at least one exportable forum!"
In the "Copy to Thread Nodes" option, please select at least 1 forum for exported conversations to go to. It is permission and option based on if the option is enabled.

I'll relax this restriction on the next release.
 
Upgrading from 1.11.3, the last version from Daniel.

I was thinking of installing Conversation Improvements first, then upgrading Conversation Essentials, both using Install & Upgrade. Is there anything else I need to do, or anything I need to be aware of when upgrading from such an old version?
 
Nope, that process should work fine.

Please ensure Conversation Improvements fully installs. Re-running the installer if it times out should work, otherwise look at the FAQ for the manual SQL to run.
 
I got one error while upgrading, for 'Deleting old search index, please re-index conversation messages', but we have the search for conversation messages turned off, and I think maybe it did finish re-indexing them after the error happened.

The reason I have the conversation search turned off is that we have millions of conversation messages and I don't want to slow the site down. But would it really make any difference?

I'm having this issue with Enhanced Search, where Mike said that it could be affected by 'any add-ons that index additional content -- in particular, conversations'. Are there any settings I need to change or look at in either conversations add-on that would affect this?
 
If you don't have Conversation Improvements installed, conversations will not be indexed. When you upgrade, it tries to delete any old search content that might have been included. You can safely ignore that error. It also takes a few hours for Elastic Search to release the diskspace too, after doing deletes that way.

The reason I have the conversation search turned off is that we have millions of conversation messages and I don't want to slow the site down. But would it really make any difference?
Elastic Search is damn fast.

I've got ~36 million documents of which 5 million are conversation messages on SpaceBattles. I use Elastic Search Essentials which implements permission-based filtering for XF1 with Elastic Search Queries (XF2 also implements this ;) ), so you only get matches returned that you have a hope on seeing so the issue Mike talks about happens much less.

But all said; it does chew up a fair chunk of diskspace!
 
Back
Top Bottom