XF 1.5 Server error log instances

KevRog

Member
We've encountered the following server error log, "
Cannot insert a message in the middle of a discussion. - library/XenForo/DataWriter/DiscussionMessage.php:449". We're wondering what this could mean, if we need to be concerned about anything, and how would we be able to fix it if needed.
 
It's always worth searching on here for similar reports of any errors or issues as they can often give suggestions for help.

https://xenforo.com/community/searc...age+in+the+middle+of+a+discussion&o=relevance

If the error has happened only once then it probably isn't anything to be concerned about.

It's worth checking that your server time is correct.
Also worth checking that the user who caused the error isn't discouraged.

Beyond that, if you have further issues you should post the full stack trace as well as the error message.
 
Thank you @Martok. I'm wondering what time the server should be following? There have actually been several instances for the year. Here's the trace:

#0 /home/memberscopychief/public_html/library/XenForo/DataWriter/DiscussionMessage.php(354): XenForo_DataWriter_DiscussionMessage->_setPosition()
#1 /home/memberscopychief/public_html/library/XenForo/DataWriter.php(1460): XenForo_DataWriter_DiscussionMessage->_preSave()
#2 /home/memberscopychief/public_html/library/XenForo/ControllerPublic/Thread.php(571): XenForo_DataWriter->preSave()
#3 /home/memberscopychief/public_html/library/XenForo/FrontController.php(351): XenForo_ControllerPublic_Thread->actionAddReply()
#4 /home/memberscopychief/public_html/library/XenForo/FrontController.php(134): XenForo_FrontController->dispatch(Object(XenForo_RouteMatch))
#5 /home/memberscopychief/public_html/index.php(13): XenForo_FrontController->run()
#6 {main}


Full error message:
Cannot insert a message in the middle of a discussion. - library/XenForo/DataWriter/DiscussionMessage.php:449
 
The server time needs to be accurate (and set to the timezone where the server is located). Usually this is done by synchronising with an NTP clock. If you don't manage the server yourself, then contact your host and ask them to check this and sort it.
 
Worth noting that having accurate server time is crucial if you're looking to enable two step verification/2FA. I noted from your other thread you're interested in implementing that. The wrong server time can cause verification codes to be considered out of date before they actually are.
 
Top Bottom