It’s an expensive operation to check all attachments for changes at any interval. Yes it’s a possibility, but for now if you update old attachments you have to manually do an another export.
Thread Starter
sqlwiz
(@sqlwiz)
There is another way of looking at this. I just noticed that a change in file size is picked up by w3tc, and the file is resent – nice!
Each file to be sent is checked on the remote server with ftp_size and if found and the size matches, the “File already exists” message is displayed, otherwise the file is resent.
It would be extremely helpful to add support for a date check with ftp_mtdm (if the remote server supports it).
If ftp_mtdm is not an option, because not all servers support it, a simple time stamp of the last transfer (includes, theme, custom, etc.) stored in the config could be used to check files on the way out.
Thread Starter
sqlwiz
(@sqlwiz)
Frederick – I’ve added a little code to our copy of http://Ftp.php that checks file dates (if available) before deciding that a file already exists. Works great.
I’ll send it or publish here if you want it.
Please contact my directly via linked in or my website.
Is it possible to not use FTP but instead use something else, like rsync, to keep files in sync? I think this would be better, less intensive, no?
We cannot assume that a given server (and PHP permissions) would have rsync installed and allow rsync to be used, nor that the system user running it has sufficient privileges even if it did work in every single case.
ok, thanks. I can handle the rsync. Perhaps all I need is a way to rewrite media URLs so the external server is used.
I am working on an auto-(re)upload feature, but the problem with it is that not every server supports all of the same functionality.
