Wedge

Are you sure you're using the latest revision..?
This was fixed a few days ago.

I am absolutely 100% certain I am using the latest revision as I check in several times a day and always grab the latest. However...

if you post new revs which say (for example) "6 files changed" I only overwrite those 6 files (plus index.php in the root folder). Is this right or wrong? Should I overwrite *every* wedge file?

Then what's the date of your core/app/Class-CSS.php file?

The last (installed) file is dated 19 Feb.

Edit: Sorry for the delays when answering, I check in before work, during work breaks and after work.

Then it's not up to date...

Then I ask again... if you post new revs which say (for example) "6 files changed" I only overwrite those 6 files (plus index.php in the root folder). Is this right or wrong? Should I overwrite *every* wedge file?

That was the latest "reported" update to that file. Should I replace every file with every new rev - or just the revised files?

Edit: This was the last "reported" revision that I can see you posted - dated 19/2/14: http://wedge.org/pub/feats/6108/new-revs/msg294224/#msg294224

I just update the revised files by looking at the commit section of here: https://github.com/Wedge/wedge and don't bother with index.php (unless updated). Of course I download a new zip each time to get the latest files.

If you had been doing this then the file in question would have been updated because (as your link shows) it is listed as being updated.

I do the same Farjo, and did this on 19 Feb, but just days later Nao says my file is out of date - though I haven't seen a later revision of the same file :-/

No, it isn't...
I'm assuming that testers don't want to bother with file versions and just overwrite everything every time they update.
If you want to update files one by one, you should rely on the commit list, rather than my manual changelogs, because I don't always list all files. I only list them for *my* own convenience when I want to find thematic groupings, but not as an exhaustive listing of all files you should update. For that, you can also just click the '6 files changed' link, and indeed see which files were modified.

As for the rest... See Farjo's last post!

I don't want to overwrite every file with every commit because my forum is on hosted web space (not my local machine) and I'm thinking about bandwidth here. I'd prefer to only update the absolute minimum required files...Which is what I do (or at least what I try to do (I clearly missed that one) :huh:

Safest way to do that:
Install git on your machine... (Or even GitHub for Windows, if you're not planning to do a lot of heavy modifications).
Clone/fork the Wedge repo(s) onto your hard drive.
When you see changes were made, just pull again from the remote repo.
Only the changed files will get their last modified date, err... Modified. I know, I'm repeating myself.

This is how I'm (manually) updating wedge.org, by the way. :P My FTP client has a shortcut to look for modified files, and only upload those.

@Nao what is your FTP client?