Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support Peter

    (@petersquirrly)

    👋Hi Rashida,

    Thank you for your question.

    It looks like this is something you need to check with CloudFront.

    Possibly set Invalidation to the cache, but CloudFront should make an image to the site on custom paths.

    Also, you can put in LiteSpeed ​​> CDN custom paths from WP Ghost, but it should work without this setting. Please check this screenshot.

    Thread Starter rashidavc18

    (@rashidavc18)

    i have put the custom paths already.But this didn’t worked.
    Please let me know what i should look at my cloud front or s3.
    Thank you

    Plugin Support Peter

    (@petersquirrly)

    CSS/JS and Images should be added by S3 with the new paths by the plugin that puts media on S3.

    Unfortunately, our hands are tied as we can’t do anything fromthe WP Ghost plugin.

    Check the plugin that puts media on Amazon S3 and ask the author for a solution.

    Thread Starter rashidavc18

    (@rashidavc18)

    Actually i am manually uploading statics files like css,js,media to the s3 bucket and uses cloudfront cdn url. .And the cdn mapping is done using lightspeed cache plugin.Every thing works fine until the cdn mapping in hide my ghost plugin is added.
    This should be working fine without any modification in cloudfront right or
    Since CloudFront doesn’t know about the path rewrites, i need to create a behavior in CloudFront that maps lib/ to wp-includes/
    I s this how it should be working right?Can you please suggest me.

    Plugin Support Peter

    (@petersquirrly)

    Unfortunately, it works in a different way. In our documentation in CDN Mapping it’s stated that we used to add custom domains (different from the one in Settings > General > Site URL) in the list to change the path name in the frontend.

    NO physical directory changes are made on the site, these are made by the CDN server. What you can do is test LiteSpeed ​​Cache with https://www.quic.cloud/ which works together and automatically adds the modified paths on the CDN.

    Solutions:

    1. Look how to rewrite paths in S3 or CloudFront from default WordPress Paths to Custom Paths.
    2. Do not customize in WP Ghost what is related to WordPress Core Security and use the other functions that are not related to modifying paths.

    Recommendations:

    1. Use LiteSpeed ​​Cache with Quick.cloud or KeyCDN
    2. Use a hosting with CDN included like Hostinger or BlueHost
Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘CDN mapping issue’ is closed to new replies.