XF 2.1 Template error: Macro public:conversation_message_macros:message is unknown

[thomas1]

Since our upgrade to XF2.1.0, we have been receiving a lot of these error messages:

ErrorException: Template error: Macro public:conversation_message_macros:message is unknown src/XF/Template/Templater.php:582
Generated by: Maria_223 Feb 12, 2019 at 21:56
Stack trace
#0 [internal function]: XF\Template\Templater->handleTemplateError(512, 'Macro public:co...', '/home/xxx/p...', 582, Array)
#1 src/XF/Template/Templater.php(582): trigger_error('Macro public:co...', 512)
#2 src/XF/Template/Templater.php(693): XF\Template\Templater->getTemplateMacro('public', 'conversation_me...', 'message')
#3 internal_data/code_cache/templates/l1/s27/public/conversation_view.php(220): XF\Template\Templater->callMacro('conversation_me...', 'message', Array, Array)
#4 src/XF/Template/Templater.php(1294): XF\Template\Templater->{closure}(Object(SV\ContentRatings\XF\Template\Templater), Array)
#5 src/XF/Template/Template.php(24): XF\Template\Templater->renderTemplate('conversation_vi...', Array)
#6 src/XF/Mvc/Renderer/Html.php(48): XF\Template\Template->render()
#7 src/XF/Mvc/Dispatcher.php(418): XF\Mvc\Renderer\Html->renderView('XF:Conversation...', 'public:conversa...', Array)
#8 src/XF/Mvc/Dispatcher.php(400): XF\Mvc\Dispatcher->renderView(Object(XF\Mvc\Renderer\Html), Object(XF\Mvc\Reply\View))
#9 src/XF/Mvc/Dispatcher.php(360): XF\Mvc\Dispatcher->renderReply(Object(XF\Mvc\Renderer\Html), Object(XF\Mvc\Reply\View))
#10 src/XF/Mvc/Dispatcher.php(53): XF\Mvc\Dispatcher->render(Object(XF\Mvc\Reply\View), 'html')
#11 src/XF/App.php(2177): XF\Mvc\Dispatcher->run()
#12 src/XF.php(390): XF\App->run()
#13 index.php(20): XF::runApp('XF\\Pub\\App')
#14 {main}

Request state
array(4) {
  ["url"] => string(32) "/conversations/appreciate.74788/"
  ["referrer"] => string(31) "https://xxxx.com/conversations/"
  ["_GET"] => array(0) {
  }
  ["_POST"] => array(0) {
  }
}

I appreciate any pointer or suggestion.

 

[hqarrse]

We're also having this - did you managed to get it fixed?

 

[thomas1]

In our case disabling the Content Ratings add-on did the trick.

 

[hqarrse]

Thanks and that worked for us as well