XF 2.0 Macro public:PAGE_CONTAINER :: visitortabs() error: (solved)

[Gael56]

Hi,

After upgrading to 2.06 and merging my styles, I get this error message:

LogicException: Macro public: PAGE_CONTAINER :: visitortabs() error: Macro argument searchConstraints is required and no value was providedsrc/XF/Template/Templater.php:768

#0 internal_data/code_cache/templates/l3/s8/public/PAGE_CONTAINER.php(371): XF\Template\Templater->mergeMacroArguments(Array, Array, Array)
#1 src/XF/Template/Templater.php(662): XF\Template\Templater->{closure}(Object(XF\Template\Templater), Array, Array)
#2 internal_data/code_cache/templates/l3/s8/public/PAGE_CONTAINER.php(989): XF\Template\Templater->callMacro('PAGE_CONTAINER', 'visitortabs', Array, Array)
#3 src/XF/Template/Templater.php(1249): XF\Template\Templater->{closure}(Object(XF\Template\Templater), Array)
#4 src/XF/Pub/App.php(449): XF\Template\Templater->renderTemplate('PAGE_CONTAINER', Array)
#5 src/XF/App.php(1766): XF\Pub\App->renderPageHtml('\n\n\n\n\n\n\n\n\n\t\n\t\n\t\n...', Array, Object(XF\Mvc\Reply\View), Object(XF\Mvc\Renderer\Html))
#6 src/XF/Mvc/Dispatcher.php(310): XF\App->renderPage('\n\n\n\n\n\n\n\n\n\t\n\t\n\t\n...', Object(XF\Mvc\Reply\View), Object(XF\Mvc\Renderer\Html))
#7 src/XF/Mvc/Dispatcher.php(44): XF\Mvc\Dispatcher->render(Object(XF\Mvc\Reply\View), 'html')
#8 src/XF/App.php(1931): XF\Mvc\Dispatcher->run()
#9 src/XF.php(328): XF\App->run()
#10 index.php(13): XF::runApp('XF\\Pub\\App')
#11 {main}

array(4) {
  ["url"] => string(48) "/forum/t/lettre-de-motivation-poste-datsem.1732/"
  ["referrer"] => bool(false)
  ["_GET"] => array(0) {
  }
  ["_POST"] => array(0) {
  }
}

I had to delete something

Can you help me

Thanks

 

[Gael56]

I found

replace

<xf:macro name="visitortabs" />

with

<xf:macro name="visitortabs" arg-searchConstraints="{$searchConstraints}" arg-navTree="{$navTree}" />

 

[Brad Padgett]

Not sure what's causing this but I automatically merged my templates and didn't receive the error. I have not tried merging any manually yet but just wanted to point out that's a way to get it to work. I just upgraded a few hours ago.

Anyway I'll let a developer handle this just wanted to mention I have not received any errors after installing 2.0.6