XF 1.4 Can't reply to conversation

Here is the error log.

Server Error Log
Error Info
XenForo_Exception: Non-recipients cannot reply to a conversation. - library\XenForo\DataWriter\ConversationMessage.php:119
Generated By: Alan Verbeke, 5 minutes ago
Stack Trace

#0 C:\inetpub\wwwroot\myreinspace.com\library\SV\ConversationImprovements\XenForo\DataWriter\ConversationMessage.php(73): XenForo_DataWriter_ConversationMessage->_preSave()
#1 C:\inetpub\wwwroot\myreinspace.com\library\XenForo\DataWriter.php(1446): SV_ConversationImprovements_XenForo_DataWriter_ConversationMessage->_PreSave()
#2 C:\inetpub\wwwroot\myreinspace.com\library\XenForo\ControllerPublic\Conversation.php(1106): XenForo_DataWriter->preSave()
#3 C:\inetpub\wwwroot\myreinspace.com\library\XenForo\FrontController.php(347): XenForo_ControllerPublic_Conversation->actionInsertReply()
#4 C:\inetpub\wwwroot\myreinspace.com\library\XenForo\FrontController.php(134): XenForo_FrontController->dispatch(Object(XenForo_RouteMatch))
#5 C:\inetpub\wwwroot\myreinspace.com\index.php(14): XenForo_FrontController->run()
#6 {main}

Request State

array(3) {
  ["url"] => string(71) "http://myreinspace.com/conversations/beginner-investor.498/insert-reply"
  ["_GET"] => array(0) {
  ["_POST"] => array(9) {
  ["message"] => string(4) "Test"
  ["_xfRelativeResolver"] => string(59) "http://myreinspace.com/conversations/beginner-investor.498/"
  ["attachment_hash"] => string(32) "02ef72a7dacb93cf3bc82f8fb7b8eb23"
  ["last_date"] => string(10) "1471273304"
  ["last_known_date"] => string(0) ""
  ["_xfToken"] => string(8) "********"
  ["_xfRequestUri"] => string(37) "/conversations/beginner-investor.498/"
  ["_xfNoRedirect"] => string(1) "1"
  ["_xfResponseType"] => string(4) "json"


XenForo moderator
Staff member
That looks like it may be related to the conversation improvements add-on.

You will need to post in the resource thread for support to determine if that is the case.


XenForo moderator
Staff member
The specific cause is this: 'Non-recipients cannot reply to a conversation'.

it suggests there is some corruption or data mismatch in the database with regards to this conversation.
We haven't seen any instances of that with regards to the core software, so it's possible an add-on has caused it.

It's likely going to mean manually editing the database to correct the records.