Comet Cache overwriting CSS

[jcpacelli]

I've been trying for hours to get this to work. I'm using Content Views Pro and am trying to hide the .dropdown_script class underneath an HTML dropdown. I finally found where that code was located by importing into dreamweaver and searching for the code. No CSS will override the cached "display:block!important;" no matter where I put it. Tried uninstalling comet cache and my CSS will still not apply.

the link is communityfirstmc.com/wallpapers

I want to HIDE just the script below the dropdown but i can't due to some sort of cached file. HELP??

[raamdev]

Tried uninstalling comet cache and my CSS will still not apply.

If this problem occurs even with Comet Cache uninstalled, how is this is a Comet Cache issue?

[jcpacelli]

Because the ONLY code that is preventing me to do so is this:

#pt-cv-view-229fa8a6bh .pt-cv-content, #pt-cv-view-229fa8a6bh .pt-cv-content *:not(.pt-cv-readmore){display:block!important;}

Using DreamWeaver, I narrowed down where exactly that code was located. It was located in wp-content/cache/comet-cache/..../wallpapers.html

I uninstalled/deleted comet cache (with selecting the option to yes, delete within comet cache) and my problem still persists. The only place that code was located in was that cache folder. I tried deleting that folder and then installing a different plugin to purge the cache after uninstalling but that doesn't work either. I also tried before and after installing & uninstalling that other plugin.

Inspecting the code, if I uncheck that display:block!important;, the grayed out script{display:none;} is the class it defers to. If I try to manually change the display:block!important; to display:contents!important; for example, that !important tag does NOT override the script{display:none;}

[raamdev]

Have you deleted the wp-content/cache/comet-cache/ directory?

[jcpacelli]

Yes, tried that too.

[raamdev]

@jcpacelli If you delete wp-content/cache/comet-cache/ and uninstall Comet Cache, there's simply no way for Comet Cache to serve a cached version of anything.

Have you checked if you have some other server-side caching that might have been installed by your web hosting company that could be serving cached versions of the CSS files? Have you tried clearing your browser cache?