Announcement

**Glenn Vergara** · Mon 10th Oct '16, 7:11am

What version did you upgrade from? Did you make any modifications to the header template before the upgrade? When you login to AdminCP, do you see a notification that says there are out of date templates? If yes, click the link provided and check if header template is one of them. You have to resolve the template merge conflicts.

**AcemanWolf** · Tue 11th Oct '16, 10:44am

Originally posted by Glenn Vergara View Post

What version did you upgrade from? Did you make any modifications to the header template before the upgrade? When you login to AdminCP, do you see a notification that says there are out of date templates? If yes, click the link provided and check if header template is one of them. You have to resolve the template merge conflicts.

Upgraded from 5.2.2. I have went to adminCP and reverted the templates. I am still getting that error on headings.

**Mark.B** · Tue 11th Oct '16, 10:48am

Originally posted by AcemanWolf View Post

Upgraded from 5.2.2. I have went to adminCP and reverted the templates. I am still getting that error on headings.

Can you please try disabling that Comodo graphic at the bottom?

**Glenn Vergara** · Tue 11th Oct '16, 11:47am

Did you really revert the header template? Looking at the HTML source, I'm seeing some old code. For example, I'm seeing a call to vBulletin.Responsive.Debounce.checkInitialBrowserSize() js function. But in 5.2.4, it has been changed to vBulletin.Responsive.Debounce.checkBrowserSize();

**Wayne Luke** · Tue 11th Oct '16, 11:50am

Please reupload your /core/install folder. Make sure that all themes are also uploaded in /core/install/themes. Then run /core/install/upgrade.php again. Clear your browser cache and reload the page.

**Glenn Vergara** · Tue 11th Oct '16, 12:02pm

I'm also seeing an inefficient Comodo script included in the head using document.write. It's causing a JS warning.

Code:

<script type="text/javascript"> //<![CDATA[
var tlJsHost = ((window.location.protocol == "https:") ? "https://secure.comodo.com/" : "http://www.trustlogo.com/");
document.write(unescape("%3Cscript src='" + tlJsHost + "trustlogo/javascript/trustlogo.js' type='text/javascript'%3E%3C/script%3E"));
//]]>
</script>

The warning I got in Chrome is "A Parser-blocking, cross-origin script, https://secure.comodo.com/trustlogo/...t/trustlogo.js, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity."

If your site is in https, just include the https URL directly

Code:

<script src="https://secure.comodo.com/trustlogo/javascript/trustlogo.js"></script>

I don't recommend it being included in the <head> tag. I recommend it to be included at the bottom of the body using template hook in footer_before_body_end hook location. And if possible (depends on the trustlogo.js), include it with "async" attribute in the <script> tag to include the script asyncronously without affecting page load performance.

**AcemanWolf** · Tue 11th Oct '16, 12:31pm

i will reinstall the upgrade. And go from there. I will remove the comodo script.

**Mark.B** · Tue 11th Oct '16, 1:02pm

Originally posted by AcemanWolf View Post

i will reinstall the upgrade. And go from there. I will remove the comodo script.

Bear in mind, removing it is just a diagnostic tool, to see if it fixes the problem. You can put it back afterwards. If it DOES fix the problem, then it's a matter of placing it somewhere more suitable (in the code, not on the screen).

Announcement

Heading Error on 5.2.4

Heading Error on 5.2.4

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Related Topics