Synchronization is Screwey

Question

I believe the synchronization information that DW-CS3 stores
has become corrupt. I have a site with local, test and remote
servers setup that I have been working with for months. When I
tried to do a full-synch yesterday, DW labeled all of the files
within one of the directories as "changed on both local and remote,
need to resolve". After checking every file in a diff program,
there were no changes - so I chose to mark as synched. That didnt
work, so I chose to GET all. That didnt work (the log just lists
all of the files with a note of "same - not transferred". Same with
choosing PUT.
Next I was grasping, so I deleted the folder from the local,
re-cached and then did a GET of that folder. Nothing happened and I
still get the log file stating "same - not transferred" for all of
the files in the directory.
Long story short, I believe the Synchronization Information
that DW stores is corrupt. Is there a way to delete that and start
from scratch with a fresh Synch?
Thanks in advance....

Answer 1

Are you sharing a local site? If so, then your
checkin/checkout scheme will
never work.
For that approach to be viable, you must never share a local
site. Instead
you would each have your own local site and share access to a
staging
server. The staging server will become your primary resource
for files, and
your local site will only be for local scratch storage while
you are editing
files. To start an edit session, you CHECKOUT from the
staging server, and
when done you CHECKIN to the staging server. Any other method
will fail.
Did that cover it?
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"larryvoyer" <[email protected]> wrote in
message
news:g3bhp6$fj5$[email protected]..
> Yes, One other user.
>
> However, we don't tromp on each others files. It's
pretty mine and his.
> But we
> strictly conform to check-in/check-out procedures as
good sw design
> practice...DW is the best tool for our site
development...unfortunately,
> not so
> good in this area..
>
> Example...I had to modify a library asset which occurs
on a copy thousand
> pages that I had previously check out last week. (I had
to go and
> re-check-out
> all the files before I could perform the operation.
Otherwise, I would get
> a
> "file is checked out by ?, Do you want to override ?s
checkout" or "File
> needs
> to be checked out before the operation..." Then it
laboriously goes
> through the
> files.
>
> From experience, it's easier to go throgh and re-check
everything out
> again...pain in the a#$
>
>
>