Compatible XF 2.x versions
  1. 2.1
Additional requirements
Purchasing this add-on entitles you to one installation on your live site and one installation on a password protected test site. This add-on can not be repackaged or redistributed in any form.
Visible branding
By purchasing this add-on you also agree that EAE Addons, and the author will not be held responsible for any lost/deleted conversations.

This add-on allows admins with the proper permission to view and delete user conversations and batch prune conversations within the administrator control panel. This add-on is useful in a number of ways: to better understand a reported conversation message as you can follow the flow of the conversation, find old in-active conversations that are just taking up space, or to find and remove spam conversations, to name a few.

See all updates for new added features, and screen shots.

Options->Admin control panel:
  • Change view attachment browser link
AdminCP->Content->EAE Conversation tools:
  • Find conversations
  • Prune conversations
Administrator permission:

- EAE Manage conversations

  • Can set the attachment browser to use the conversation browser when viewing an attachment with the content type conversation message. This setting is ignored if the viewing administrator does not have EAE Manage conversations permission
  • Paginated, set to fetch 20 conversations per page and 20 conversation messages per page
  • Find conversations by username or title. When by username you can select started by, or all conversations
  • From the find conversations page you can delete a conversation or selected conversations (a confirmation pop-up will appear). Click the conversation title to view the conversation
  • BBCode is supported when viewing conversations
  • When viewing conversations, attachments are served through the Admin CP. A lightbox is used to view images when applicable, otherwise viewing an image works the same as the attachment browser
  • You can also use the Conversation tools to prune conversations with no replies after x days, or when last reply was x days ago. Before you can actually prune conversations, a count is returned first to show the number of conversations you are about to permanently delete
  • You may include moderators and administrators conversations when pruning. The default is set to exclude their conversations. If you choose to include moderator conversations, administrators that are also moderators will be excluded
  • Pruning is handled by a job runner. You can hit cancel while pruning, but be warned that you may end up deleting a large amount of conversations if you decide to change your mind
When pruning conversations you may want to set the days to a high number and get the count before proceeding. The default is set to 365 days. Note that this add-on has the potential to delete all conversations depending on your settings. Deleted conversations can only be restored from a back-up, so back-up your database first.


- All begin with eae_cvstt_

Screen shots:

First release
Last update
5.00 star(s) 3 ratings

More resources from Lawrence

Latest updates

  1. Bug fixes, changes, and new features added.

    Bug fixes: trying to access array offset on value of type null (Listener), that was thrown on...
  2. Bug fix

    Re-worked the listener to prevent non-object errors from being thrown under certain...
  3. Bug fix

    Fixed a template bug that caused an 'Column xxxxxx is unknown' error when certain add-ons were...

Latest reviews

We needed to monitor conversations to provide support for our classifieds section and EAE has been absolutely great
Thank-you for the review, I am glad you find it useful, :)
This addon is perfect for our forum I believe it is important for large forum You can use this tools to prune old conversations.
Thank-you for the review, and I am happy you find this tool useful, :)
Great addon with great support!
i'm glad to see this addon porting to xf2 :)
please keep it updated, working absolutely perfect in xF 2.1.2
Thank-you for taking the time to write a review, and more importantly thank-you for reporting that bug as quick as you did, well appreciated, :)