We use cookies to improve your experience. No personal information is gathered and we don't serve ads. Cookies Policy.

ExpressionEngine Logo ExpressionEngine
Features Pricing Support Find A Developer
Partners Upgrades
Blog Add-Ons Learn
Docs Forums University
Log In or Sign Up
Log In Sign Up
ExpressionEngine Logo
Features Pro new Support Find A Developer
Partners Upgrades
Blog Add-Ons Learn
Docs Forums University Blog
  • Home
  • Forums

very strange behavior after upgrading to ee6

Development and Programming

captainahab's avatar
captainahab
22 posts
4 years ago
captainahab's avatar captainahab

After upgrading my staging environment to ee6 from 5.3.x, my production CP looks broken. Styles, according to color, seem to be ee6 styles, but it looks broken like a style sheet is missing. Staging and Prod are completely separate instances – dev.myclientsdomain.com / myclientsdomain.com. How is that possible, what am I missing here? Any suggestions and help very welcome! Thank you!

       
Rob Allen's avatar
Rob Allen
3,105 posts
4 years ago
Rob Allen's avatar Rob Allen

The first thing I’d do is clear your production site EE cache, and your browser cache, so you know you’re using up to date system files.

If that doesn’t work check URL and path settings are correct and all system files exist on the production site.

       
captainahab's avatar
captainahab
22 posts
4 years ago
captainahab's avatar captainahab

Unfortunately caching is not the problem. There are files and directories changed in the prod theme, looks like the auto-updater is noch limited to the current directory. Staging and prod are on the same hosting, different directories, not ideal, I know. Nasty bug.

       
Rob Allen's avatar
Rob Allen
3,105 posts
4 years ago
Rob Allen's avatar Rob Allen

On your production site have a look at the CP source to see if CSS files are being loaded, then check those CSS URL(s) to make sure the file(s) exist and where it’s pulling them from.

       
Neil Evans's avatar
Neil Evans
1,403 posts
4 years ago
Neil Evans's avatar Neil Evans

On production, open up your browsers Web Developer tools. Typically F12. Under network (after refreshing the control panel page, see what is in red, or not loading. That is the easiest way to carefully check.

My bet is a broken URL, http/https mishap, or theme files did not transfer correctly and file is missing.

       

Reply

Sign In To Reply

ExpressionEngine Home Features Pro Contact Version Support
Learn Docs University Forums
Resources Support Add-Ons Partners Blog
Privacy Terms Trademark Use License

Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.