Localhost – Custom CSS Does Not save all CSS Entries

Update:
I tested JetPack Custom CSS with a default theme, same problem, both on the live and localhost sites.

Thanks for the report. Does this happen with specific CSS code? Could you paste the code you’re trying to save in a pastebin, and share it here so I can try to reproduce?

Thanks!

I think I used pastebin correctly, the URL works.

CSS in pastebin: https://pastebin.com/CmKxiA7q

Of course, the CSS is to modify a paid theme.

Was thinking, I should let you know that each time I saved the custom CSS, it cuts off the rest of the CSS at the same place, which is at Line 309 (see the pastebin link). At Line 309, all it has is the property “content:” and the value is blank (removed) and that is where it ends each time.

Another test.

Since I was thinking in terms of the PHP or script not accepting anything after line 309, I went and pasted the CSS up to line 304 (inclusive – pastebin example), which completes the selector “.payment, .service”. I saved the CSS and it did Not cut anything off. It was complete to that selector set. So if my CSS was only to line 304 (as per pastebin example), all would be fine. Go beyond line 309 and it gets removed.

Does that help?

• This reply was modified 7 years, 11 months ago by mwarbinek. Reason: Added information

Thanks for the extra details!

I should let you know that each time I saved the custom CSS, it cuts off the rest of the CSS at the same place, which is at Line 309 (see the pastebin link).

You appear to be missing a ' on that line. Could you try to replace it with the following:

.confit-address a::after {
    position: relative;
    left: 5px;
    content: url('/wp-content/uploads/2016/11/map-pointer-icon.png');
}

That should solve the issue.

I believe it worked, yet I also uninstalled Jetpack and reinstalled it before I made the syntax changes.
:O

I checked the syntax at the W3C CSS validator, without the single quotes it was valid, yet I know the single quotes are also valid.

Tell me why the single quotes would make a difference in JetPack? They never did before.

Any other good info about JetPack CSS that would cause errors, would hate to hit smack into another one and not even see it coming.

• This reply was modified 7 years, 11 months ago by mwarbinek.

Both syntaxes are valid, but you need to choose one and stick with it; you had originally added a closing double quote, but didn’t add any opening double quote. That’s not valid CSS I’m afraid.

Any other good info about JetPack CSS that would cause errors, would hate to hit smack into another one and not even see it coming.

Jetpack’s CSS editor will validate your CSS before to save it, so if some of your CSS disappears upon save, it means it wasn’t valid.

I hope this helps.

That information is really nice to know, thanks.

Sometimes I miss those little things (leaving out the end quotes usually or the “dot” for a class selector or the “:” to separate property names and values and the misery list goes on :/ ). Normally I see that and correct it.

Is it easier for Jetpack to remove the syntax instead of returning an alert saying the syntax is invalid?

For example, JetPack validates CSS like contact forms and pops up a modal box saying “Na Na Na, you tripped up on your syntax (with an image of a waving finger)”, kind of thing?

Reason for me asking this is when things just suddenly disappear, that normally gets attributed to a glitch, or software screw up, or the famous one ” *%$# ” windows again!!

Could the JetPack guys and gals give us some alert that our syntax is the wrong language?

• This reply was modified 7 years, 11 months ago by mwarbinek. Reason: grammer correction
• This reply was modified 7 years, 11 months ago by mwarbinek. Reason: Added more

Could the JetPack guys and gals give us some alert that our syntax is the wrong language?

The Custom CSS option is now part of WordPress itself, and it’s still a work in progress, but alerts are already available. Here is how they look like:
https://i.wpne.ws/iNJm

I’d suggest installing Jetpack 4.4.2 and WordPress 4.7 to give that a try!