[wp-trac] [WordPress Trac] #42613: Custom CSS with errors before 4.9 upgrade can't be corrected after upgrade

WordPress Trac noreply at wordpress.org
Sat Nov 18 04:40:01 UTC 2017


#42613: Custom CSS with errors before 4.9 upgrade can't be corrected after upgrade
-------------------------------+------------------------------
 Reporter:  hptccharge         |       Owner:
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Customize          |     Version:  4.9
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:  javascript
-------------------------------+------------------------------

Comment (by hptccharge):

 Replying to [comment:1 Clorith]:
 Hi, thanks for the response. I deactivated all plugins and still cannot
 get the custom CSS to save.  One critical note for replicating - that I
 didn't consider until I read your comments - is that the WP upgrades to
 4.9 were all done automatically by the hosting providers, so any warnings
 about errors weren't seen. At the point I realized the problem, the sites
 were already upgraded to 4.9 and I was dealing with bad code previously
 saved in the custom CSS code file.  I can cut out all of the code or only
 a portion - even when I've deleted all of the custom CSS, I cannot save
 the then-empty file.

 I've tried changing themes, and the custom CSS is still there and can't be
 modified.  I'm looking now for a theme that doesn't support custom CSS in
 hopes that that would cause what is there to be deleted.




 > Hi there and welcome to Trac!
 >
 > I'm afraid I'm not able to reproduce the problems you are experiencing,
 when starting out with invalid CSS I am presented with a warning stating
 there are errors, I can then fix the error and save, remove the erroneous
 piece and save, or tick a checkbox which lets me save even though there
 are errors, all three are currently functioning for me.
 >
 > Would you please try the default troubleshooting steps of disabling any
 plugins and see if the problem still occurs, alternatively try a different
 theme and see if you are allowed to save then, this will help identify if
 it's a plugin or your theme being the root cause.
 >
 > If the problem persists even with things disabled, would you please
 provide the original CSS you had when first experiencing the problems so
 that we can see if we can reproduce this?

--
Ticket URL: <https://core.trac.wordpress.org/ticket/42613#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list