• This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.

XF 2.0 MySQL query error and Template error

ALMUSA

Active member
#1
Getting these errors

XF\Db\Exception: MySQL query error [1364]: Field 'first_react_users' doesn't have a default value in src/XF/Db/AbstractStatement.php at line 183

  1. XF\Db\AbstractStatement->getException() in src/XF/Db/Mysqli/Statement.php at line 66
  2. XF\Db\Mysqli\Statement->execute() in src/XF/Db/AbstractAdapter.php at line 67
  3. XF\Db\AbstractAdapter->query() in src/XF/Db/AbstractAdapter.php at line 144
  4. XF\Db\AbstractAdapter->insert() in src/XF/Mvc/Entity/Entity.php at line 1343
  5. XF\Mvc\Entity\Entity->_saveToSource() in src/XF/Mvc/Entity/Entity.php at line 1085
  6. XF\Mvc\Entity\Entity->save() in src/XF/Service/Thread/Creator.php at line 285
  7. XF\Service\Thread\Creator->_save() in src/XF/Service/ValidateAndSavableTrait.php at line 40
  8. XF\Service\Thread\Creator->save() in src/XF/Pub/Controller/Forum.php at line 704
  9. XF\Pub\Controller\Forum->actionPostThread() in src/XF/Mvc/Dispatcher.php at line 249
  10. XF\Mvc\Dispatcher->dispatchClass() in src/XF/Mvc/Dispatcher.php at line 89
  11. XF\Mvc\Dispatcher->dispatchLoop() in src/XF/Mvc/Dispatcher.php at line 41
  12. XF\Mvc\Dispatcher->run() in src/XF/App.php at line 1831
  13. XF\App->run() in src/XF.php at line 328
  14. XF::runApp() in index.php at line 13




  • ErrorException: Template error: Function reaction is unknown
  • src/XF/Template/Templater.php:780
  • Oct 15, 2017 at 10:48 PM
Stack trace
#0 [internal function]: XF\Template\Templater->handleTemplateError(512, 'Function reacti...', '/home/p...', 780, Array)
#1 src/XF/Template/Templater.php(780): trigger_error('Function reacti...', 512)
#2 internal_data/code_cache/templates/l1/s7/public/alert_post_react.php(9): XF\Template\Templater->fn('reaction', Array, true)
#3 src/XF/Template/Templater.php(1152): XF\Template\Templater->{closure}(Object(XF\Template\Templater), Array)
#4 src/XF/Alert/AbstractHandler.php(67): XF\Template\Templater->renderTemplate('public:alert_po...', Array)
#5 src/XF/Entity/UserAlert.php(47): XF\Alert\AbstractHandler->render(Object(XF\Entity\UserAlert))
#6 [internal function]: XF\Entity\UserAlert->render()
#7 src/XF/Template/Templater.php(860): call_user_func_array(Array, Array)
#8 internal_data/code_cache/templates/l1/s7/public/alert_macros.php(18): XF\Template\Templater->method(Object(XF\Entity\UserAlert), 'render', Array)
#9 src/XF/Template/Templater.php(583): XF\Template\Templater->{closure}(Object(XF\Template\Templater), Array, Array)
#10 internal_data/code_cache/templates/l1/s7/public/account_alerts_popup.php(18): XF\Template\Templater->callMacro('alert_macros', 'row', Array, Array)
#11 src/XF/Template/Templater.php(1152): XF\Template\Templater->{closure}(Object(XF\Template\Templater), Array)
#12 src/XF/Template/Template.php(24): XF\Template\Templater->renderTemplate('public:account_...', Array)
#13 src/XF/Mvc/Renderer/Json.php(81): XF\Template\Template->render()
#14 src/XF/Mvc/Renderer/Json.php(65): XF\Mvc\Renderer\Json->renderHtmlFallback('XF:Account\\Aler...', 'public:account_...', Array)
#15 src/XF/Mvc/Dispatcher.php(332): XF\Mvc\Renderer\Json->renderView('XF:Account\\Aler...', 'public:account_...', Array)
#16 src/XF/Mvc/Dispatcher.php(303): XF\Mvc\Dispatcher->renderView(Object(XF\Mvc\Renderer\Json), Object(XF\Mvc\Reply\View))
#17 src/XF/Mvc/Dispatcher.php(44): XF\Mvc\Dispatcher->render(Object(XF\Mvc\Reply\View), 'json')
#18 src/XF/App.php(1831): XF\Mvc\Dispatcher->run()
#19 src/XF.php(328): XF\App->run()
#20 index.php(13): XF::runApp('XF\\Pub\\App')
 

Mike

XenForo developer
Staff member
#4
The first one is because they haven't defined their schema correctly.

The second might be a race condition with what happens while the add-on is being disabled.
 

Mike

XenForo developer
Staff member
#6
You should report this to the add-on developer (particularly the first one, as it's something they're doing wrong explicitly).

Actually, I see what happened with the second one. You should report that to them as well.
 

ALMUSA

Active member
#7
You should report this to the add-on developer (particularly the first one, as it's something they're doing wrong explicitly).

Actually, I see what happened with the second one. You should report that to them as well.
Will sure do. Thanks a bunch mate.