nathanielbessent

I am having issues after the update too. It seems as though any new CSS I am adding in the code editor is not showing up on my website. I can add or change elements within a class in the Simple Custom CSS editor in the back end and it will save, but when I load the site and view the front end, the changes are not there. When I inspect the element, the additions/edits to a class are not present.

@jeherve Yes, I suspected that it was a problem with my theme since it was working fine with other themes, but you know how theme providers can be. If they don’t have an answer then they just point you back to the plugin developer or just tell you to disable the plugin. I have had some other issues with my theme and JetPack compatibility, which is supposed to be resolved in an update, but who knows when.

I should have made it more clear, but I do realize that the JetPack CSS was supposed to integrate with the WP 4.7 CSS, allowing the extra features and letting the WP CSS input and output CSS. That was just my precursor to explain that something strange seemed to have happened in that process, on the database side, that duplicated a CSS file and stored it in a location I could not find, making that CSS file override other CSS, even when !important was used.

Another solution I found for that was to use a plugin that allows you to place CSS in the header or footer, allowing your custom CSS to be loaded first or last, but that solution didn’t play well with the particular theme I was using. It may work for other themes though if someone is experiencing a similar issue.

I really love JetPack and plan to use it with other themes that are compatible, so I didn’t mean to imply that JetPack should not be used if that was implied. Even if the CSS isn’t compatible with a particular theme, there are a lot of other useful tools that make JetPack worth having.

@kadushi-marketing I wasn’t able to get the issue resolved like I would have preffered. After the WP 4.7 update, my CSS was gone and the JetPack custom CSS was being overridden by the WP 4.7 custom CSS, making options such as the CSS history not even show up.

That wasn’t the only problem I was having. After the 4.7 update, something happened in my databases where the JetPack CSS was copied to the WP CSS, creating a rogue CSS file of sorts in the database. I had a backup of my CSS, but I also found my CSS in the JetPack history backups in the database. I disabled the JetPack CSS since it was interfering with the WP CSS and copied my CSS to the WP CSS editor. However, I found that some of my CSS was being overridden by CSS marked as !important that was being stored in the database. I deleted all of the CSS backups I could find in the database, but my CSS was still being overridden by the rogue CSS file I mentioned earlier.

Here is what I did to resolve this problem. I downloaded the plugin “Simple CSS Editor” and copied all of my CSS there. Then, I cleared out all CSS in the WP editor and inserted an open comment “/*”. I didn’t close the comment. I saved the CSS and this appeared to either override or comment out the CSS from the rogue CSS backup I couldn’t find in the database. Since then, I have been using the “Simple CSS Editor” without any problems or interference from JetPack CSS or the WP CSS and any backups pertaining to those editors in the database.

I know that is somewhat of a hack and doesn’t really fix the problem, but as of yet, the JetPack CSS/WP CSS conflict has not been fixed. Not sure if that is something my theme provider needs to fix, an issue with JetPack, or an issue with WordPress, but I was on a time crunch and didn’t have the time to go back and forth with them to resolve the issue correctly.

• This reply was modified 7 years, 8 months ago by nathanielbessent.

Just an update. I contacted my theme provider about this issue and they were able to replicate the conflict in Custom CSS editors on their end. It looks like they weren’t intentionally trying to override WP 4.7 Custom CSS with their own. I was told they would have it fixed in a coming update.

When I disable Jetpack’s custom CSS, the Appearance->Customize->Additional CSS tab goes away and the Custom CSS tab remains.

I checked to see if I could disable the theme’s custom CSS tab. I didn’t see an option anywhere for that. I did switch my theme to Twenty Sixteen and it looks like the JetPack options were integrated into WP 4.7 Custom CSS. It looked as it did in your gif with the history option and everything.

I checked for JavaScript errors on the customizer page. Here is a screenshot of the errors.

One difference from my custom theme (WPLMS) from the Twenty Sixteen theme is that there were two CSS tabs in the WPLMS theme as you can see in this screenshot. The Custom CSS tab shows this and the Additional tab shows this. In the Twenty Sixteen theme all of these options were shown under the Custom CSS tab. Its almost like somewhere in the conflict WordPress recognized that there was already a Custom CSS tab so it created an Additional CSS tab and put the remainder of the options there. However, the History button doesn’t appear under either tab and when I paste my nearly 500 lines of CSS into the editor, no scroll bar appears, so I literally have to scroll to the bottom of my code using the mouse wheel.

This may be something I need to take up with my theme provider. I’ve been checking their support forum for any threads on the issue, but there aren’t any yet.

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

I forgot to mention that I did not do a manual upgrade to WP 4.7.

Let me know if it would be best for me to create a new thread. I figured I would chime in here since I am experiencing some of the same issues.

The JetPack CSS editor did not successfully migrate for me and I do not see the history button shown in your gif. I was running JetPack 4.4.2 prior to updating to WordPress 4.7.

I believe the problem for me is that my theme had a custom CSS section built into it under Appearance->Customize->Custom CSS. I installed JetPack because I didn’t like the CSS editor that came with my theme. When I click Edit CSS under Appearance, like I used to prior to WordPress 4.7, I am taken to Appearance->Customize->Additional CSS, Which looks like this Screenshot 01. If I navigate to Appearance->Customize->Custom CSS, it looks like this Screenshot 02.

At this point, it seems like WordPress 4.7, my theme (WPLMS), and JetPack may be fighting for the same custom CSS access point under Appearance->Edit CSS. That’s just my hunch at the moment as I’m still trying to figure out exactly what is going on and what I should be seeing. My website seems to still be accessing the JetPack Custom CSS file from the server, but I do not see any of my custom CSS in wp-admin.