XF 1.3 A discussion insert was attempted without the required first message.

GeorgeS

Active member
Hello,


this error message shows up in the server under two situations:

a) an attempt to permanently delete a thread (in a section that has no prefixes defined)
a) an attempt to update a post (in a section that has different prefixes defined)

We do not use a multi-prefix addon, as there was a report ovn XF 1.2 where this was the reason for the error message:

The trace looks like this:

Code:
#0 /var/www/library/XenForo/DataWriter.php(1446): XenForo_DataWriter_Discussion->_preSave()
#1 /var/www/library/XenForo/DataWriter.php(1385): XenForo_DataWriter->preSave()
#2 /var/www/library/AVForums/ModCheckpoint/DataWriter/PostCheck.php(104): XenForo_DataWriter->save()
#3 /var/www/library/AVForums/ModCheckpoint/DataWriter/PostCheck.php(57): AVForums_ModCheckpoint_DataWriter_PostCheck->getThreadCheckedStatus(true)
#4 /var/www/library/XenForo/DataWriter.php(1779): AVForums_ModCheckpoint_DataWriter_PostCheck->_postDelete()
#5 /var/www/library/AVForums/ModCheckpoint/DataWriter/DiscussionMessage/Post.php(18): XenForo_DataWriter->delete()
#6 /var/www/library/XenForo/DataWriter/DiscussionMessage.php(590): AVForums_ModCheckpoint_DataWriter_DiscussionMessage_Post->_messagePostSave()
#7 /var/www/library/XenForo/DataWriter.php(1409): XenForo_DataWriter_DiscussionMessage->_postSave()
#8 /var/www/library/Dark/TaigaChat/DataWriter/DiscussionMessage/Post.php(7): XenForo_DataWriter->save()
#9 /var/www/library/XenForo/ControllerPublic/Post.php(243): Dark_TaigaChat_DataWriter_DiscussionMessage_Post->save()
#10 /var/www/library/XenForo/FrontController.php(347): XenForo_ControllerPublic_Post->actionSaveInline()
#11 /var/www/library/XenForo/FrontController.php(134): XenForo_FrontController->dispatch(Object(XenForo_RouteMatch))
#12 /var/www/index.php(13): XenForo_FrontController->run()
#13 {main}
 
Looks like it's related to the mod checkpoint system (or possibly Taigachat). You should disable the add-ons one by one until you can't reproduce it. The last one disabled is the likely cause.
 
There are some bugs in that version of Mod Checkpoint, but I do not believe this to be one of them. But as Mike says, disabling it ought to confirm.
 
Top Bottom