XF 2.3 Server Error Log - Need help

[mrdoitnyce]

This started popping up recently. Any help is appreciated.

• InvalidArgumentException: Template public:alert_resource_purchase_insert error: Container key 'prefixes.resources' was not found
• src/XF/Container.php:48

• Generated by: Superchunes
• Aug 26, 2024 at 3:42 PM

Stack trace​

#0 src/XF/App.php(3870): XF\Container->offsetGet('prefixes.resour...')
#1 src/addons/XenGenTr/XGTOnekSistemi/XF/Template/Templater.php(24): XF\App->container('prefixes.resour...')
#2 src/XF/Template/Templater.php(1220): XenGenTr\XGTOnekSistemi\XF\Template\Templater->fnPrefix(Object(XenGenTr\XGTOnekSistemi\XF\Template\Templater), true, 'resources', 39)
#3 internal_data/code_cache/templates/l1/s117/public/alert_resource_purchase_insert.php(9): XF\Template\Templater->func('prefix', Array, true)
#4 src/XF/Template/Templater.php(1792): XF\Template\Templater->{closure}(Object(XenGenTr\XGTOnekSistemi\XF\Template\Templater), Array, NULL)
#5 src/addons/MaZ/AUN/XF/Template/Templater.php(39): XF\Template\Templater->renderTemplate('alert_resource_...', Array, true, NULL)
#6 src/XF/Alert/AbstractHandler.php(80): MaZ\AUN\XF\Template\Templater->renderTemplate('public:alert_re...', Array)
#7 src/XF/Entity/UserAlert.php(73): XF\Alert\AbstractHandler->render(Object(XF\Entity\UserAlert))
#8 src/XF/Template/Templater.php(1283): XF\Entity\UserAlert->render()
#9 internal_data/code_cache/templates/l1/s117/public/alert_macros.php(19): XF\Template\Templater->method(Object(XF\Entity\UserAlert), 'render', Array)
#10 src/XF/Template/Templater.php(922): XF\Template\Templater->{closure}(Object(XenGenTr\XGTOnekSistemi\XF\Template\Templater), Array, NULL)
#11 internal_data/code_cache/templates/l1/s117/public/account_alerts.php(42): XF\Template\Templater->callMacro('alert_macros', 'row', Array, Array)
#12 src/XF/Template/Templater.php(1792): XF\Template\Templater->{closure}(Object(XenGenTr\XGTOnekSistemi\XF\Template\Templater), Array, NULL)
#13 src/addons/MaZ/AUN/XF/Template/Templater.php(39): XF\Template\Templater->renderTemplate('account_alerts', Array, true, NULL)
#14 src/XF/Template/Template.php(24): MaZ\AUN\XF\Template\Templater->renderTemplate('public:account_...', Array)
#15 src/XF/Mvc/Renderer/Html.php(50): XF\Template\Template->render()
#16 src/XF/Mvc/Dispatcher.php(471): XF\Mvc\Renderer\Html->renderView('XF:Account\\Aler...', 'public:account_...', Array)
#17 src/XF/Mvc/Dispatcher.php(453): XF\Mvc\Dispatcher->renderView(Object(XF\Mvc\Renderer\Html), Object(XF\Mvc\Reply\View))
#18 src/XF/Mvc/Dispatcher.php(412): XF\Mvc\Dispatcher->renderReply(Object(XF\Mvc\Renderer\Html), Object(XF\Mvc\Reply\View))
#19 src/XF/Mvc/Dispatcher.php(66): XF\Mvc\Dispatcher->render(Object(XF\Mvc\Reply\View), 'html')
#20 src/XF/App.php(2813): XF\Mvc\Dispatcher->run()
#21 src/XF.php(802): XF\App->run()
#22 index.php(23): XF::runApp('XF\\Pub\\App')
#23 {main}

Request state​

array(4) {
["url"] => string(15) "/account/alerts"
["referrer"] => string(28) "https://www.superchunes.com/"
["_GET"] => array(0) {
}
["_POST"] => array(0) {
}
}

 

[Old Nick]

#1 src/addons/XenGenTr/XGTOnekSistemi/XF/Template/Templater.php(24): XF\App->container('prefixes.resour...')

Maybe you should contact @eTiKeT™ ?

 

[mrdoitnyce]

Maybe you should contact @eTiKeT™ ?

yeah, at first i thought it was an addon because the earlier error showed another addon. it showed my xen-soluce prefix & banner addon, to which i disabled, but then it errored with another addon, disabled, now errors with this, So i'm a bit confused.

it all started when a purchased was made on one of my resource.

Maybe you should contact @eTiKeT™ ?

It has nothing to do with them. It would happen at various times during the day. Wasn't sure what was triggering it. After looking over the errors multiple times, I've finally realized what was triggering the error. " ["url"] => string(15) "/account/alerts" "....Apparently, every time I would get a notification/Alert it was causing the error. It all started when users started purchasing items on my site. I use " Ozzmodz Purchasable resource ". After disabling that add-on and doing some alert testing, NO errors, lol.

I've reached out to them. The add-on needs an update. I'm on 2.3.2, maybe that's why.