Invision Community 4: SEO, prepare for v5 and dormant account notifications By Matt Monday at 02:04 PM
dal Posted September 22, 2023 Posted September 22, 2023 (edited) I've just migrated my Invision forum to a new host and everything is working fine except for one thing - the system error log is constantly filling up with this same error message over and over every time anyone views the forum at all: Quote OutOfRangeException #0 /home/files/public_html/forum/system/Dispatcher/Front.php(626): IPS\_Widget::load(Object(IPS\core\Application), 'announcements', 'announcements', Array, NULL, 'horizontal') #1 /home/files/public_html/forum/system/Dispatcher/Dispatcher.php(155): IPS\Dispatcher\_Front->finish() #2 /home/files/public_html/forum/index.php(17): IPS\_Dispatcher->run() #3 {main} Oddly, this doesn't seem to be having any impact on anything - there are no visible errors or problems when using the forum and the announcements system works fine - I can add/edit/remove announcements and they show up without issue. I've tried clearing the cache, clearing the datastore folder, I've disabled all third-party plugins/applications - nothing seems to make any difference. Any ideas ? Edited September 22, 2023 by dal
teraßyte Posted September 22, 2023 Posted September 22, 2023 What URL is triggering this error? The URL should be visible at the top of the page when you're viewing a System Log in ACP.
Marc Posted September 22, 2023 Posted September 22, 2023 We would need to look further into this for you, however the access details on file appear to be incorrect or missing. Could you please update these details by visiting your client area, selecting the relevant purchase, then clicking "Review/Update Access Information" under the "Stored Access Information" section. We look forward to further assisting you.
dal Posted October 14, 2023 Author Posted October 14, 2023 (edited) On 9/22/2023 at 2:53 PM, teraßyte said: What URL is triggering this error? The URL should be visible at the top of the page when you're viewing a System Log in ACP. The error is triggered every time anyone views any page anywhere on the forum, except the board index. On 9/22/2023 at 3:40 PM, Marc Stridgen said: We would need to look further into this for you, however the access details on file appear to be incorrect or missing. Could you please update these details by visiting your client area, selecting the relevant purchase, then clicking "Review/Update Access Information" under the "Stored Access Information" section. We look forward to further assisting you. Thank you, I've gone ahead and updated the access information. I'm running a test install of my live forum with the latest version and the default theme, no plugins or third party applications enabled - and the problem still persists. On my live forum, the system log fills up so quickly I have to keep manually emptying it. Edited October 14, 2023 by dal
Jim M Posted October 14, 2023 Posted October 14, 2023 We would only be able to analyze/support this on your production installation. Please ensure all credentials are up to date. Currently, the .htaccess credentials are invalid.
dal Posted October 14, 2023 Author Posted October 14, 2023 1 minute ago, Jim M said: We would only be able to analyze/support this on your production installation. The test installation is identical to the production installation but allows me to test different solutions without impacting the live site. Both are running on the same server. I'm looking to find a solution that works on the test install before carrying that across to the live site. 3 minutes ago, Jim M said: Currently, the .htaccess credentials are invalid. Fixed now - added the additional login details in the field at the bottom.
Jim M Posted October 14, 2023 Posted October 14, 2023 2 minutes ago, dal said: The test installation is identical to the production installation but allows me to test different solutions without impacting the live site. Both are running on the same server. I'm looking to find a solution that works on the test install before carrying that across to the live site. Fixed now - added the additional login details in the field at the bottom. I'm afraid, as per our support standards, we are unable to support test installations. If it is a software error, we would only apply this to your production installation. .htaccess credentials are invalid at this time.
Miss_B Posted October 14, 2023 Posted October 14, 2023 Have you installed any third party stuff that has to do with the Announcement System? If you disable all third party apps/plugins, does the error still happen? What is the php version at the new host?
dal Posted October 14, 2023 Author Posted October 14, 2023 8 minutes ago, Miss_B said: Have you installed any third party stuff that has to do with the Announcement System? If you disable all third party apps/plugins, does the error still happen? What is the php version at the new host? I have tried disabling all the third party plugins/extensions and it makes no difference. The new host is running PHP 8, but then so was the old host, so I don't think that's the issue. The error seems to have something to do with the announcements system, but as I say it doesn't seem to be impacting anything - I can create/view/edit announcements and it all works fine. Even with the announcements table empty the error keeps occurring. The main issue is that this error is filling up the system log table with huge numbers of entries. The minimum setting for purging the system log is insufficient, so one thing I could do is run a php script via cron to clear the system log table of these particular entries every day - that would prevent it from getting too large.
dal Posted October 17, 2023 Author Posted October 17, 2023 For anyone else experiencing this - I've finally found a fix. The issue was due to the 'bimchatbox' application not uninstalling properly - it left entries in the 'ibf_widget_areas' table labelled 'announcements' which stayed there after the application was removed. Upon every page view, the forum tried to load up the widget but couldn't because the application wasn't there any more, thus generating one error in the log for every view. Manually removing these entries from the database table solved the problem. Miss_B, angle4cor, Adriano Faria and 1 other 3 1
Recommended Posts