Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter purge7

    (@purge7)

    Just an update on this as it seems our initial conclusion that we had this working was not the case. Changing the name of the origin domain name in Amazon CloudFront to match the one the W3 Total Cache requires (websites domain name) breaks the connection to the images.

    Our conclusion is if you have a pre existing AmazonS3 bucket, Cloud Front and CNAME it cant be used with W3 Total Cache as it always forces you to create a new origin.

    It would be great if there was an input for and existing Origin as well as the ability to create one

    Regards

    Ray

    Thread Starter purge7

    (@purge7)

    Hello Marko,

    Well we played around with it and we think we have moved forward by changing the Origin Domain in Amazon Cloud Front to match our domain as it was named with the s3.eu-west-2.amazonaws.com.

    Once we did this we tested the credentials in W3 Total Cache and it passed the test. However we have seen no change in the way images are uploaded, we did numerous uploads but they are not ending up in the AmazonS3 Bucket but on the local wordpress upload folders. Oddly our CNAME domain name works for the uploaded media but is not reflected in the File URL: in the media section of the worpress instance.

    We cant really see any other setting to use for CDN why things shouldn’t now be working since we passed the test.

    Regards

    Ray

    Thread Starter purge7

    (@purge7)

    Hello Marko,

    I do appreciate you getting back to me. The plugin we use, and have done so for many years, is a free version of Off Load Media by Delicious Brains. There is a newer version of this plugin but they ask for very unreasonable charges for uploads so we have never upgraded.

    For clarity by using this old plugin we have all the required credentials including Access Key, Secret key, Origin Distribution, cloudfront and CNAME all working perfectly.

    We have wanted to invest in W3 Total Cache for a while now but we have not been about to use it because it seems reluctant to accept already working credentials. We have now tried all the Amazon S3 options irrespective of push or pull but with no success.

    We believe the right one would be Amazon Cloud Front from the Pull/Mirror

    Once we have made this selection we then go to the CDN part to input our credentials

    Here we were expecting to simply enter our credentials but to start with the Origin is defaulted to the websites domain name and all you can do at that point is create about distribution with out anyway to simply input an existing one and this is where it where we get to.

    Is there any reason why existing credentials cant be used or are we simply using the wrong initial selection?

    Any help would be appreiciated

    Regards

    Ray

    Thread Starter purge7

    (@purge7)

    So as a heads up pretty much all of your documentation says it ‘does’ work with a free API key

    How can anyone test it to see if it’s worth it or it even works?

    Maybe change all the documentation to reflect the truth of the plugin.

    Thread Starter purge7

    (@purge7)

    I have

    I have tried this plugin many times but I never got it to work uploading your own contract, it just never does anything.

    I have all the correct API’s set and details and fill out what is needed and I am connected to Metamask with plenty of ETH and my token from the contract I want to upload but it just sits there and does nothing. Cant find any videos either about loading your own contract.

    Shame as it looks like it would be a great plugin if it worked.

    Regards

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