How do I upload files I changed in the last hour?
Put Recent to Server in FTP by Zaweba lists every local file changed in the time you pick, such as the last hour, and uploads them after you check the list.
Use Put Recent to Server in FTP by Zaweba. You choose how far back to look, such as the last hour, and the app lists every local file you changed in that time. Check the list, untick anything you don't want, and the rest go up to the server.
It's the quickest way to publish an afternoon's work when you've touched files in several folders and can't remember them all.
Why it is quick
Most "upload what changed" features compare your folder with the server first. That means listing the server, folder by folder, before anything can be decided, which on a big site or a slow host takes a while.
Put Recent doesn't scan the server at all. It looks only at your local files and picks out the ones changed within the period you set. On a site with thousands of files and a handful of edits, that's a short list found quickly.
The trade-off is that it doesn't know what's on the server. If someone else changed a file there in the meantime, Put Recent won't spot it by comparing the two sides. Keep that in mind on shared sites, and see the section on choosing the right tool below.
Uploading the last hour's work
Connect to the site. Choose Put Recent to Server, either for the whole site or from a folder's right-click menu if you only want to look in one part of it.
Pick the period. You can choose minutes, hours or days, so "the last hour" is one option among many. If you started work after lunch, pick a few hours. If you edited something yesterday and forgot to upload it, pick a day or two.
Read the list. Every file changed in that window is there, wherever it sits in the site. Untick anything that shouldn't go up yet, a page that's half finished or a test file you made along the way.
Confirm, and the uploads run. They go side by side on several connections (three by default, set in File > Options), and you can follow them in the transfer queue in the bottom panel.
Getting a good result
Set the period a little wider than you think. If you worked for about an hour, choose two. Extra files that haven't really changed simply go up again; a file that was missed stays out of date on the live site.
Watch for files that change on their own. Build tools, caches and log files can have fresh dates without you touching them. Add those to the site's Exclude box in Site Manager (node_modules, *.log and the like) and they'll never be transferred.
Anything Put overwrites on the server has its previous version kept first in local version history on your PC, so a bad upload can be put right from the history window.
Choosing between Put Recent, Put Newer and Upload on Save
Put Newer to Server is the careful cousin. It uploads only local files that are newer than the server copy or not there yet, leaving files that are newer on the server alone. It has to look at the server to do that, but it's the better choice on a site other people also edit.
Upload on Save sends each file as you save it in the editor, so there's nothing to catch up on later. It suits steady work in FTP by Zaweba's own editor, and conflict checks still apply.
Put Recent sits between them. Use it when you've been editing in other programs, or with Upload on Save switched off, and want a fast, reviewable catch-up of your own recent work.
