text above the header

[wclune]

This morning I had 2 websites i work on begin showing “code” above the header.

marsclub.org and mdrocketry.org

I have disabled ALL the plugins on both site and the code remains…

 

/* CSS+ Rules */ /*-=:m_primary_hover_bgcolor_css:=-*/.menu-primary .wvrx-menu li:hover > a {text-decoration:underline;}/*-:m_primary_hover_bgcolor_css:-*/ /*-=:m_secondary_hover_bgcolor_css:=-*/.menu-secondary .wvrx-menu li:hover > a {text-decoration:underline;}/*-:m_secondary_hover_bgcolor_css:-*/ /*-=:m_secondary_sub_hover_bgcolor_css:=-*/.menu-secondary .wvrx-menu ul li a:hover {text-decoration:underline;}/*-:m_secondary_sub_hover_bgcolor_css:-*/

[wclune]

Should mention both site are on 2 different server both running different flavors of .php

[scrambler]

Please do not double post, and follow up in your other thread

[alanwbaker]

Hello Scrambler,

A user of https://sirinc.org reported the same thing to me. A PDF of the screen shot is at https://sirinc.org/wp-content/uploads/sirinc.orgChrome.pdf. This appears to have happened following update https://downloads.wordpress.org/theme/weaver-xtreme.6.2.1.zip.

I don’t see the error on Windows Firefox 112.02, but I do see it on Edge 113.0.1774.35 and Chrome 112.0.5615.138 and on Android Firefox 112.2.0 and Chrome 113.0.5672.76. 😵

I see the same on https://sirinc2.org/branch99. HOWEVER, I do not see this error on site https://sirinc2.org/branch46 or https://sirinc2.org/branch20a, which were updated about the same time. 😵

Alan

 

[Weaver]

It is a bug, but will take me a day or so to track it down. Probalby an introduced issue with Weaver Xtreme Plus version compatibility.

[alanwbaker]

I rolled back the theme to https://downloads.wordpress.org/theme/weaver-xtreme.6.2.0.1.zip on site https://sirinc.org and the problem went away.

Alan

[alanwbaker]

I updated site https://sirinc.org to 6.2.1.1 and it returned the same results as with 6.2.1 on Chrome and Firefox (but worked correctly on Edge), so I rolled it back to 6.2.0.1 and things look OK again.

I updated site https://sirinc2.org/branch99 to 6.2.1.1 and it returned the same results as with 6.2.1 on Firefox (but worked correctly on Chrome and Edge). I left this site on 6.2.1.1 for your review.

Alan

[Weaver]

If you have it working correctly on some browsers, then that behavior is almost certainly a caching artifact.

WordPress and Weaver Xtreme don’t adjust anything based on browsers.

[Weaver]

I looked at your branch99 site, and see the stray CSS at the top.

But when I look at the page source, it is not what I would expect to see. All of the theme’s CSS output is not compressed, which may have been the case in some of the quick test versions I’d posted recently.

It seems to me that perhaps you are not using the version from the WordPress repository? If you really are using that version, then I think I will need admin access to some site – perhaps the broken branch99 site to see what is going on because that issues seems to be solved in the WP released 6.2.1.1.

 

[sbarnessckls]

I have seen this crop up on several sites we host (all running 6.2.1.1).  So far, the CSS text above the header seems to be visible only when logged out – which of course, would be most site users.

I went into the Weaver Xtreme Admin (not the Customizer) > Main Options > Menus, and found a few places where CSS had the – sign instead of the + sign (but no custom CSS code entered).  I clicked to change it back to the +, and that fixed the display problem!  Then on one site, I saw only /* CSS */ above the header, but found no instances of the ‘CSS – ‘ in the menu or any other settings.  I clicked the + twice for each of those options on the menu settings page, saved it, and the text went away.

I have so far been unable to recreate the problem – I have tried clicking CSS + to expand it to CSS – and saving without adding any code, but nothing happens. So I’m nut sure where this comes from, but for me at least, it has been an easy fix when I run across it!

[alanwbaker]

This reply has been marked as private.

[alanwbaker]

As sbarnessckls said above, the CSS at the top appears when logged out and disappears when logged in. I’ve sent you admin credentials on one of the problem sites.

Alan

[alanwbaker]

https://sirinc2.org/branch99 has 6.2.1.2 now, but still shows CSS at the top.

Alan

[Weaver]

I logged in, and as part of the login, I got the new 6.2.1.2 message that the CSS cache had been updated. And sure enough, the issue is gone. Confirms that the issue as been the CSS Cache with the bad CSS from the faulty CSS minifier.

So I see that branch99 has the plugin: Easy Updates Manager. That explains how the theme was updated without updating the CSS cache.

I don’t know how to get around that issue. Those Update Managers have some kind of “magic” access to your side that can update files without actually being an admin. I never figured out how they do that. But the auto-update does not trigger the CSS cache update. It is probably the same issue if a site was using the built-in WordPress theme updater. It is a pain to manage a lot of sites, so that is a useful tool.

I will add a post about auto updating the theme.

Thanks for your help and persistence.

[alanwbaker]

Thank you, Weaver.

Alan

[Author]

Posts