404 on resource assets

  • Enterprise Branding

    (@enterprisebranding)


    4 years, 11 months ago

    Hi!

    You can see the screenshot @ https://take.ms/aW5RQ

    I think the issue is just in the css, which refers to some image resources, etc.

    This method would be fine, except, when the css is combined into a cache or uploaded in the same manner to a cdn, then the path to the image referred in the css, returns a 403.

    I have the Pro version.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Max K

    (@kaminskym)

    4 years, 11 months ago

    Hi,

    Very strange, I saw this file in the folder.
    So the path was correct.
    Did you check via FTP if this file exists on your server?

    Max

    Thread Starter Enterprise Branding

    (@enterprisebranding)

    4 years, 11 months ago

    Hi!

    Yes, I checked.

    I’m a developer a bit, so I checked in VSCode and was going to change it.

    But not looking into it further, I use Litesped Cache @ https://wordpress.org/plugins/litespeed-cache/

    And so when the css is compress and “combined”, then the css file is something like /wp-content/litespeed/css/combined-file-name.css

    So then the image fails to load because the css file is different.

    That is just my initial thought. I haven’t really dealt with images referred to in css.

    So then I was initial thinking that the file needs to be pushed into the /uploads directory and referenced there where it should be more reliable to be found no matter the path.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘404 on resource assets’ is closed to new replies.