After new disc and new Leopard on my Mac: questions concerning synchronizing

[gavagai]

Hi,
after a new disc and a new Leopard on my Mac: two questions concerning synchronizing.
1) Yummy doesn't have the starting folders for my 4 websites at the Mac anymore. It starts with the desktop and I have to choose the correct high level folder for the website which I am about to synchronize.
I selected a folder in "Preferences" but Yummy seems to ignore that. Besides: I had a different starting high level folder for each of my 4 websites (and it worked very well before my disc-change and change of the operating system). In the "Preferences" I can only choose one folder for all.
How can I tell Yummy: please use folder XY for website XY and folder ZA for website ZA and so on ?
2) I always had trouble with some of my webpages. Yummy always assumed (for a special page) it to be newer at the Mac although it wasn't changed at all. Now I synchronize (for the first time) up and down (i.e. both sides) and Yummy tells me:
index.htm this object is newer at the Mac
index.htm this object is newer at the Server
How can that be?

[gavagai]

Hi
I found the question for my first answer by myself. The shop which changed my disc and the operating system to Leopard although changed my highest level folder. And that I can change now for each website separately.

[JD]

Sorry I didn't get to answer your first question - I've been busy with non-Yummy stuff for a change.

As you have chosen a bi-directional synchronize, rather than the usual 'Update Server' upload changes method, Yummy performs two synch passes - 1 is local to remote, 2 is remote to local. If you have the 'Compare file size if dates match' option enabled then you can get the situation you've described because there is no way for Yummy to know which file is actually newer.... the remote file size can be different due to differing line endings at the server compared to your local copy, even though the content is actually identical. This can happen if the server is running Windows. for example. I suggest to un-check that option and try again.