Mke Stoltz Posted Monday at 11:12 PM Posted Monday at 11:12 PM (edited) We have not made any recent administration or configuration changes on the site. When the accessing the home url www.cpica.ca, we get a blank page. When looking at the source, after the <head> tag, there is a body tag with classes "ipsApp ipsApp_front psJS_none ipsClearfix" The html appears to be building the main menu but doesn't display it. I can certainly provide the html source that I'm seeing if it would help. At 5:29 ET today, I did receive a notification of a new content summary that had been posted. At 5:49 ET I received the first member message that the site was down. At 6:02 ET I confirmed that the community site was down Edited Monday at 11:15 PM by Mke Stoltz
Mke Stoltz Posted Tuesday at 12:21 AM Author Posted Tuesday at 12:21 AM BTW, I can access the Admin portal without issue.
Gary Posted Tuesday at 12:26 AM Posted Tuesday at 12:26 AM Hi @Mke Stoltz, Just throwing an idea out there until someone from the team can assist you. Have you cleared your system caches in the AdminCP? AdminCP -> System -> Support -> Get Support -> Tools & Diagnostics -> Clear System Caches
Mke Stoltz Posted Tuesday at 12:57 AM Author Posted Tuesday at 12:57 AM Thanks for the tip Gary... I tried clearing the system caches but still the same result. BTW, there are no errors in the system logs Invision manages the DNS records.
Solution Ryan Ashbrook Posted Tuesday at 07:38 AM Solution Posted Tuesday at 07:38 AM This should be fixed now. A couple days ago, Google Tag Manager was enabled, however the the GTM Body Snippet simply had <noscript> in it, which was causing the issue. I've adjusted that to <noscript></noscript>, which resolved the issue. Note, this isn't likely correct - if you are using Google Tag Manager, then there is additional code that needs to be added there. Unfortunately, that code is unique, so I cannot add it myself. Only the administrator of the site, with access to GTM, can do that. SeNioR- 1
Mke Stoltz Posted Tuesday at 01:27 PM Author Posted Tuesday at 01:27 PM 12 hours ago, Mke Stoltz said: Thanks for finding what caused this error. I'll further investigate the GTM.
Mke Stoltz Posted Wednesday at 12:19 AM Author Posted Wednesday at 12:19 AM 23 hours ago, Mke Stoltz said: Was just thinking... could you add the "</noscript>" tag to your default, initial configuration. I enabled the GTM a few days ago thinking that I could come back and configure later, not noticing that the "<noscript>" tag without the close was going to cause problems. The other oddity, was that even though the plugin was enabled a few days ago, the site wasn't down until about 5:45pm yesterday (as far as I know). Thanks again for your support.
Jim M Posted Wednesday at 04:56 PM Posted Wednesday at 04:56 PM 16 hours ago, Mke Stoltz said: Was just thinking... could you add the "</noscript>" tag to your default, initial configuration. I enabled the GTM a few days ago thinking that I could come back and configure later, not noticing that the "<noscript>" tag without the close was going to cause problems. The other oddity, was that even though the plugin was enabled a few days ago, the site wasn't down until about 5:45pm yesterday (as far as I know). Thanks again for your support. As Ryan mentioned, the <noscript> is part of the overall GTM inclusion script so not something which we can add.
Recommended Posts