Posted December 14, 20213 yr Community Expert This morning I started getting this error, no changes have been made to the site. [[Template core/front/global/announcementContentTop is throwing an error. This theme may be out of date. Run the support tool in the AdminCP to restore the default theme.]] I cannot access the ACP. How can I correct this? Thank you
December 14, 20213 yr Community Expert Solution Im working on your ticket at the moment This has now been escalated for you so that we can see whats going on
December 14, 20213 yr @Marc Stridgen 7 hours ago, Square Wheels said: [[Template core/front/global/announcementContentTop is throwing an error. This theme may be out of date. Run the support tool in the AdminCP to restore the default theme.]] I also get the same template error since upgrading to 4.6.8. The error is fired by Guests (I guess some bots) on non-existent attachments urls (eg. already deleted from a database). No error if urls point to existing attachments. The same error occurs on the default and custom theme. Recreating the default theme from scratch does not help. Of course, caches were cleared many times. I was preparing to upgrade to 4.6.9 hoping that the error will be fixed. But I would like to know how to fix that before upgrading.
December 15, 20213 yr Community Expert 9 hours ago, Luuuk said: @Marc Stridgen I also get the same template error since upgrading to 4.6.8. The error is fired by Guests (I guess some bots) on non-existent attachments urls (eg. already deleted from a database). No error if urls point to existing attachments. The same error occurs on the default and custom theme. Recreating the default theme from scratch does not help. Of course, caches were cleared many times. I was preparing to upgrade to 4.6.9 hoping that the error will be fixed. But I would like to know how to fix that before upgrading. This was an issue with Redis in this case. Please disable this if you have it running, and see if that resolves your issue
December 15, 20213 yr 2 hours ago, Marc Stridgen said: This was an issue with Redis in this case. Please disable this if you have it running, and see if that resolves your issue Thanks. Then I have a different culprit since I do not use Redis... In this case I will upgrade to 4.6.9 and seewhat will happen.
December 15, 20213 yr Community Expert Just now, Luuuk said: Thanks. Then I have a different culprit since I do not use Redis... In this case I will upgrade to 4.6.9 and seewhat will happen. Upgrading to the latest release would always be the first thing to do
