[wp-trac] [WordPress Trac] #39127: Updating to 4.7 deletes existing Jetpack custom CSS

[WordPress Trac]

#39127: Updating to 4.7 deletes existing Jetpack custom CSS
--------------------------+-----------------------------
 Reporter:  pressupinc    |      Owner:
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:  trunk
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 Today I updated WPShout.com from 4.6.1 to 4.7, and lost all the custom CSS
 in my Jetpack "Appearance > Edit CSS" page.

 Have since restored the site, so it looks fine now. I've attached
 screenshots of:
 1) working.png: How it should look (including how the Jetpack styles make
 it onto the page), and
 2) after_update.png: How it looked immediately once I updated to 4.7.

 I created the screenshot for 2) by manually deleting all the Jetpack
 styles in Chrome dev tools, but it's *exactly* how the site looked when I
 updated to 4.7.


 A couple of other details:

 1. I tried the same process (update from 4.6.1 to 4.7 with the same custom
 CSS in "Appearance > Edit CSS") on a locally hosted site, and it properly
 loaded into the customizer. Clicking "Appearance > Edit CSS" now redirects
 to the "Additional CSS" view on the customizer, and the CSS is still
 properly there.


 2. On another locally hosted site, I tried the same process (update from
 4.6.1 to 4.7 with custom CSS in "Appearance > Edit CSS"), but with a
 single very simple CSS rule on the page: see simple_change.png.

 The single rule continued to function, but there's no edit window for the
 custom CSS in the customizer: see after_simple_change.png.


 So at this point I'm just seeing very inconsistent behavior in Jetpack's
 custom CSS feature during upgrades to 4.7.

 I'm worried that a lot of 4.7 updates will end scarily for Jetpack users,
 so please let me know if this is an understandable problem and if there's
 a fix in the works -- or if it's a problem only I will have, which seems
 unlikely but would be nice.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/39127>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform