Files not uploading via FTP

[mikelons]

I am having issues uploading my files at the moment. Files were uploading fine up until a few minutes ago (approx. 2014-10-27-20:00 GMT+0). I am on the xo1 server and my domain name if you need it is http://www.mikelonsdale.co.uk. I am using Filezilla v.3.9.0.5, there is an update for a new version, but after i updated that's when the issues started so I reverted back to this version thinking it was Filezilla but the files are still not uploading.

Please update me when you find the cause or need more information.

Thank you.

 

[Dead-i]

Hi mikelons,

Currently FTP uploads on xo1 appear to be functioning normally, and I can't see anything on your account that would prevent you from uploading. What is the exact error message that FileZilla is giving you?

Thank you,

 

[mikelons]

Filezilla isn't giving me an issue; all uploads are successful. When the webpage is refreshed (with or without cache) the new file isn't on the server. The latest file upload seems to be present on the server now, so maybe it's just taking a really long time to be updated on the server? If you get what I mean.

 

[mikelons]

Last uploaded file was /stylesheets/css-min.css at 02:34:24 and it is still not live on the server, 13 minutes after the upload.

 

[mikelons]

Upload now live after 16 minutes.

 

[essellar]

There is server-level caching in place now, so if you've changed files that are ordinarily static (HTML, JS, CSS, graphics) it's going to take a while to see updates. You can set the cache-control to get around that using an .htaccess file in the target directory (it'll take the files aging out at least once for the no-cache thing to register with the server), but once development is done, please revert back to the cached behaviour — it takes some load off of the server.

 

[caftpx10]

There is server-level caching in place now, so if you've changed files that are ordinarily static (HTML, JS, CSS, graphics) it's going to take a while to see updates. You can set the cache-control to get around that using an .htaccess file in the target directory (it'll take the files aging out at least once for the no-cache thing to register with the server), but once development is done, please revert back to the cached behaviour — it takes some load off of the server.

When I've looked at this thread, I had a feeling it was to do with cache, though it seemed odd for it not to update for a while. For me, I sometimes have to either turn off development mode on Cloudflare's settings or just refresh twice to get an update. (PHP was cached?)