Can’t get custom CSS to work

Hi, it all appears to be working to me, the CSS has loaded otherwise your page would not have much formatting at all.

But there is something odd. I can’t see the SpeakOut! version number in the page source code, also the source code is not formatting properly.

My suggestion is to have a look at the source code, which is jammed into 10 lines. Then try a different theme and see if that sorts it out.

Also you should see a comment something like <!-- SpeakOut! Email Petitions 1.16.4 --> at the top of the SpeakOut! code. There is a bunch of code missing so I am not sure what has happened.

My suggestion is to remove the plugin and reinstall it, see if that helps. If not, switch themes and see if that helps. There is certainly something odd happening and I am pretty sure it is not directly related to the plugin, have never seen this before.

Ahh…sorry, didn’t mean to mark this resolved and I can’t undo that now ??

Sorry, seems like I left it with the basic theme option instead of the no theme-option, as I was testing different approaches yesterday. So that’s the CSS you saw.

In the source code the petition.css file seems to be loaded, but it doesn’t take effect.

This is probably an issue with my theme, which has several issues, but I can’t just switch themes on a live site. If there was an easy fix for this or a known issue, I was hoping to fix it.

Though, a workaround seems to be to add the what I want in the custom theme style.css instead. Then it loads.

Have you tested your plugin with W3 Total Cache minification? I guess that explains why you can’t see all the code you expect to see.

Seems like this is a weird cache issue.

• This reply was modified 5 years, 3 months ago by audunmb.

Glad I fixed it :o)

Sorry, it wasn’t fixed. Sometimes it loads the petition.css, sometimes it doesn’t.

Seems like using the css from the theme-default.css-file doesn’t work at all, while minor edits work.

I disabled my caching plugin for now, as that partly seems to be the issue.

Now I got css from theme-default.css to work. Not sure exactly why it does’nt work sometimes.

• This reply was modified 5 years, 3 months ago by audunmb. Reason: clarity

Seems like my browser cache was the main culprit, though I never had issues with this before. Now I can edit it and it works properly.

Sorry, it was W3 Total Cache which was the culprit. Updates to the petition.css file wasn’t included in the minification of css. Purging cache for each update seems to do the trick.

Normally the cache should know that a file is updated, you should probably check with the W3 Total Cache developers why it isn’t. My guess is that it would affect all cache plugins equally.