# Old Roots theme breaks wp-admin in WordPress 5.3 **URL:** https://discourse.roots.io/t/old-roots-theme-breaks-wp-admin-in-wordpress-5-3/17083 **Category:** sage **Created:** 2019-11-15T10:08:45Z **Posts:** 19 ## Post 1 by @pirod — 2019-11-15T10:08:45Z We use roots theme in Wordpress and it now has a broken admin in Wordpress 5.3. Any urgent fix available? ![image](https://discourse.roots.io/uploads/default/original/2X/5/55483a78f6f1dc0011d77586373074e25f070295.png) --- ## Post 2 by @blu — 2019-11-15T13:06:49Z I don’t know if this is the correct solution to the reported error (net::ERR\_HTTP2\_PROTOCOL\_ERROR) but as a temporary fix I added the following line to config/environments/production.php in the sage theme folder… define( ‘CONCATENATE\_SCRIPTS’, false ); --- ## Post 3 by @pirod — 2019-11-15T17:38:35Z > [@blu](#): > > (net::ERR\_HTTP2\_PROTOCOL\_ERROR why do you say this error? Are you on the right topic? --- ## Post 4 by @blu — 2019-11-15T19:09:16Z That’s the error that Chrome reported when I ran into the same issue. Have you checked to see what error is being reported in your case? --- ## Post 5 by @pirod — 2019-11-16T06:11:04Z thanks. I have to try again. I revert back from backup to previous WP version in the meantime. --- ## Post 6 by @sewmyheadon — 2019-11-22T18:38:28Z I’ve had this happen on three older Sage/Roots sites so far. In all cases, upgrading WP to 5.3 broke the WP Editor by making it impossible for WP to load all of the relevant CSS. The fix is to go into: `/lib/cleanup.php` and comment out the line that hooks the cleanup function `roots_clean_style_tag` into the `style_loader_tag` filter like so: `//add_filter('style_loader_tag', 'roots_clean_style_tag');` **Before** : [![](https://dl.dropboxusercontent.com/s/8s7rpiz99quhlqd/Screenshot%202019-11-22%2012.35.28.png?dl=0) ](https://dl.dropboxusercontent.com/s/8s7rpiz99quhlqd/Screenshot%202019-11-22%2012.35.28.png?dl=0) **After** : [![](https://dl.dropboxusercontent.com/s/r4dg7i2z0a72h98/Screenshot%202019-11-22%2012.34.16.png?dl=0) ](https://dl.dropboxusercontent.com/s/r4dg7i2z0a72h98/Screenshot%202019-11-22%2012.34.16.png?dl=0) I hope that helps someone! --- ## Post 7 by @Kezzak — 2019-11-26T05:00:34Z Thanks for that fix, helped in on a couple of old sites today. Much appreciated --- ## Post 8 by @fabriceleven — 2019-12-05T19:40:42Z In the newer but still old Soil theme you have to go to /lib/config.php and comment out `add_theme_support('soil-clean-up');` This is actually a pretty big issues, cause what happens is none of the plugin’s admin css files are loaded. --- ## Post 9 by @ben — 2019-12-07T21:55:10Z As of Soil 3.7.2, nothing should be running from Soil in the wp-admin --- ## Post 10 by @pirod — 2019-12-08T13:51:49Z Hi, So how one can update the WP theme based on roots? Should it not provide an update to fix old themes? --- ## Post 11 by @pirod — 2019-12-14T16:31:29Z I do not have that line ![image](https://discourse.roots.io/uploads/default/original/2X/4/4303c5e1dc60a069228042a3638cc8aa52b99078.png) --- ## Post 12 by @pirod — 2019-12-14T16:35:04Z [sewmyheadon] gave the right solution --- ## Post 13 by @pirod — 2019-12-14T16:39:14Z Hi, How to upgrade roots theme then? I don’t know what soil is. I have roots 6.5.1 ![image](https://discourse.roots.io/uploads/default/original/2X/1/136a89019e3318285fccd1d3ebf84f2e56fb9961.png) --- ## Post 14 by @ben — 2019-12-14T16:49:32Z You don’t need to upgrade your Roots theme (it’s a starter theme, doing so would wipe your theme and you’d need to restart from scratch). Older versions of the Roots theme just need the applicable code removed per the solution selected on this topic. Users running Soil, which contains some features used in the older versions of Roots, will need to upgrade to the latest version. That can be done via GitHub or from [https://roots.io/product-links/](https://roots.io/product-links/) --- ## Post 15 by @katierc — 2019-12-16T15:25:52Z I’m having the exact same issue (before pic looks like by back-end), but I can’t even get to my CSS to load to implement the fix. When I open my Theme Editor it shows the CSS for a split second and then it completely disappears. ![27%20AM](https://discourse.roots.io/uploads/default/original/2X/a/a9cfec1ed71bdf962001bbf8b0c597a06d7dbfad.png) Disclaimer: I don’t have a web dev background and just admin the site, so maybe I’m missing something simple here. --- ## Post 16 by @sewmyheadon — 2019-12-16T18:56:27Z Hey @katierc - can you connect to the site via FTP or use the hosting File Manager to access these files instead? That’s the way to go, I think. --- ## Post 17 by @katierc — 2019-12-16T19:17:16Z Thank you! I had shared your original solution post with a colleague who has more web dev knowledge, and he was able to fix it. I’ll ask him to show me how he accessed it so I’ll know for other fixes in the future. Thanks SO much for sharing the original post. It took me a while to diagnose the cause of all the different issues we had after the 5.3 update, so this was incredibly helpful. --- ## Post 18 by @sewmyheadon — 2019-12-16T19:46:28Z My pleasure, @katierc. I’m glad you got it sorted. It took me a bit to figure out what was happening and I was pretty sure it would happen to others too so I’m really glad it helped. --- ## Post 19 by @system — 2019-12-27T10:08:48Z This topic was automatically closed after 42 days. New replies are no longer allowed.