Failed to load content css: uploads/swift- magic/editor-styles.css

Forums Forums SwiftThemes Bug report and suggestions. Failed to load content css: uploads/swift- magic/editor-styles.css

This topic contains 3 replies, has 3 voices, and was last updated by  James B 3 years, 1 month ago.

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
  • #34898

    James B

    After a recent upgrade to WordPress 4.8 I’m receiving the following warning message within the content editor when creating or editing a post or other content.

    Failed to load content css:

    I’m currently using Swift 7.3.1 even though it is in Legacy status until I decide on another theme for this site. This site is running Swift Premium with Woocommerce with some minor changes made via a child theme.

    The site is also set up with Cloud Flare’s flexible SSL. Things have been running fine this way since 2015. No issues until after a recent WordPress upgrade to version 4.8.

    I now receive the error message above.

    I’m assuming this has something to do with WordPress and/or Swift attempting to load the unsecure http:// version of editor-styles.css instead of loading it from https:// like it should. I’m unsure how to fix this and could use some help.

    This appears to be a common issue for many users after upgrading to WordPress 4.8. The following post has some insight but didn’t help me.

    Since I’ve read it can be an issue with using @import within a child theme style.css file I’ve tried changing the way I handle parent style sheet import in my child theme’s style.css but it doesn’t seem to help. Attempting to hard code an absolute file path, enqueuing parent styles all seemed to fail. My brain’s fried after a day of fixing woocommerce issues so I can’t think through this at the moment. Hoping you have a quick and easy fix!


    Puneet Bangera

    I am facing the exact same issue
    Failed to load content css uploads/swift- magic/editor-styles.css

    attached screenshot


    Satish Gandham

    Will release a fix in 24hours.


    James B

    Yesterday the affected site updated to WordPress 4.8.1 and now the issue appears to have been resolved.

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.