Kjell Iver Johansen Posted September 3, 2016 Share Posted September 3, 2016 I get the following error overflowing my logs. One every minute or more. #0 /home/xx.no/system/Dispatcher/Front.php(432): IPS\_Widget::load(Object(IPS\advancedtagsprefixes\Application), 'tagCloud', 't18svfbyi', Array, NULL, 'vertical') #1 /home/xx/init.php(442) : eval()'d code(32): IPS\Dispatcher\_Front->finish() #2 /home/xx/init.php(442) : eval()'d code(57): IPS\Dispatcher\tripreport_hook_embedMap->finish() #3 /home/xx/system/Dispatcher/Dispatcher.php(131): IPS\Dispatcher\chat_hook_tabNewWindow->finish() #4 /home/xx/index.php(13): IPS\_Dispatcher->run() #5 {main} I have uploaded the fix from the KB article https://invisionpower.com/4docs/knowledgebase/4114-outofrangeexceptions-in-system-error-logs-r362/ I have cleared cache. Any other suggestions? Does anyone else has this error? Link to comment Share on other sites More sharing options...
TSP Posted September 5, 2016 Share Posted September 5, 2016 Have you tried turning off or updating (if available) any of the applications / widgets mentioned. I'm thinking about the tag cloud widget from advanced tags and prefixes and the embedMap-hook that seems to be from something named tripreport If any of that is causing the issue, you should report it to the plugin/app author. Link to comment Share on other sites More sharing options...
Kjell Iver Johansen Posted September 5, 2016 Author Share Posted September 5, 2016 Thanks for pointing me in the right direction. I did not have Advanced tags and prefixes enabled - and the error kept coming with all applications turned off. I upgraded AT& prefixes and when I enabled it - I saw this block with Tag cloud on the forum index page. I took that away and now the error is gone... Link to comment Share on other sites More sharing options...
TSP Posted September 5, 2016 Share Posted September 5, 2016 Seems to maybe be an issue with widgets from applications not being disabled when the application it belongs to is then. Maybe report that as a bug to IPS. It could've been resolved already however (on app disablement), but it may have been resolved after the point at which you disabled the advanced tags application. Link to comment Share on other sites More sharing options...
newbie LAC Posted September 5, 2016 Share Posted September 5, 2016 Fixed in 4.1.15 Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.