Viewing 10 replies - 16 through 25 (of 25 total)
  • vSential

    (@vsential)

    Also it seems that the plugins aren’t being synced. I am getting around this by using the Sync Specific Directory option.

    vSential

    (@vsential)

    Another thing I noticed is that if I use something else to upload my static content to the CDN it now displays properly. It seems that there is something happening during the sync that is either not being set properly or causing some type of other issue with files being transferred.

    Chris Knights

    (@chrisknights)

    I has the same issue as Pete_PT.

    Looks like there is a problem with the new plugin or Amazon as CSS files are being sent to S3 as standard text files. Browser interprets these as wrong format and thus does not load the style sheet.

    Solution:

    Apply the following to all .css files.

    Log in to S3 and find the file > Properties > MetaData > Key: Content-Type > Change this to text/css. (Will be set to text/plain).

    Let me know if this helps.

    Pete_PT

    (@pete_pt)

    Mine were all set to text/x-c but changing them all manually to text/css did the trick.

    Thank you.

    Also, on Multisite support the following is happening.

    ALL image uploads including entire blogs.dir folder was uploaded to Main site.

    Images not syncing at all from child sites.

    The upload is not rewriting as /files but /blogs.dir/2/files so all I had to do was create a new folder in child bucket, and copy and paste the image files.

    CLunky but it works.

    Ammalgam

    (@ammalgam)

    This is all nice and good but I have a site that’s 3 years old, PR5 with over 1650 posts.

    I am taking NO chances with this upgrade.

    Plugin Author Ollie Armstrong

    (@olliea95)

    Thank you for pointing out this issue. It will be fixed as soon as possible.

    The incorrect mime types bug comes from the underlying S3 code. I’ve fixed the issue in the S3 library and submitted a pull request to the author.

    Those looking to fix this directly can replace the code in S3.php with the code in my fork.

    I’ve checked back from time to time and I still can’t get the new version to sync with my Amazon S3 buckets on either of two blogs. I keep going back to the previous version because I don’t have time to troubleshoot. There’s no error message, it claims it’s synced, and there’s nothing in the website error log, but the files never arrive at Amazon.

    Is there something I should be looking for? Some trick I should be using?

    I too dropped back to an old version of this plugin to keep my cdn working.

    Plugin Author Ollie Armstrong

    (@olliea95)

    S3 MIME issues have been fixed. Multisite issues due to be fixed this week.

Viewing 10 replies - 16 through 25 (of 25 total)
  • The topic ‘[Plugin: CDN Sync Tool] CDN Sync Breaks after upgrade’ is closed to new replies.