Re: crash with library items

Murray:

Several working at the same time?

Yes, on different machines

Are you using checkin/checkout?

Not at the moment. Although I have thought about this before.

Is your local site actually on a network shared drive?

yes on a single machine hosted here on the network.

Dion.

Cheers for that Murray,

you've got our boss in a bit of a worry now.
After a short discussion we are about to swap all our stuff over to the way
you suggested.

How do Library items work when you check things in / out?
say someone has a page checked out and I change a library item that appears
on that page.
hows that work?

Dion

"Murray *TMM*" <forums (AT) HAHAgreat-web-sights (DOT) com> wrote

Dion:

Your setup is a recipe for disaster.

1. If you have multiple people working on the same site, you really
should
use checkin/checkout to avoid file versioning problems.
2. Having a local site that is on a network shared drive is very
dangerous
and is no doubt what is responsible for your corrupted site cache.

I recommend you do the following -

1. Copy the 'local' site to each hard drive (yes, this means that each
developer needs to have a local - really local - copy of the site).
2. Define a new site for each developer that has the local site for
LOCAL,
and the shared network drive as a staging server for the remote.

Now - the workflow would be like this. Each developer would check out the
files they want to work on from the staging server. When completed, the
files would be checked back in to the staging server. In this way, the
staging server becomes the 'gold' resource for the development team, but
you
would have to all become accustomed to the checkin/checkout methodology to
make it work. Using this methodology, the local site loses its central
position in the workflow, and the staging server assumes that role.

When the site/files is/are completed then ONE of the developers would have
a
second site defined with the staging server as local and the production
server as remote. This person would then connect to this site, and upload
(only upload) files to the production server.

Using this scheme, I can nearly guarantee you that your cache corruption
issues will disappear.

--
Murray --- ICQ 71997575
Team Macromedia Volunteer for Dreamweaver MX
(If you *MUST* email me, don't LAUGH when you do so!)
==================
news://forums.macromedia.com/macromedia.dreamweaver - THE BEST WAY TO GET
ANSWERS
==================
http://www.dreamweavermx-templates.com - Template Triage!
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.DreamweaverFAQ.com - DW FAQs, Tutorials & Resources
http://www.macromedia.com/support/search/ - Macromedia (MM) Technotes
==================

"Dion Jones" <monkey (AT) deadcatdesigns (DOT) co.uk> wrote in message
news:beehov$mp8$1 (AT) forums (DOT) macromedia.com...
Murray:

Several working at the same time?

Yes, on different machines

Are you using checkin/checkout?

Not at the moment. Although I have thought about this before.

Is your local site actually on a network shared drive?

yes on a single machine hosted here on the network.

Dion.

Dion:

Well, that's an excellent question, and it's very tricky. Here's how you
would have to do it.

1. Broadcast a message to all developers that you will need to make changes
to a library/template on the site in one hour (adjust timeframe as needed),
and that they should immediately save and checkin all working files.
2. At the zero hour, synch yout site with the staging server by checking
out EVERYTHING.
3. Make the changes to the Library Item/Template file, and allow those
changes to propagate.
4. Check your files back in to the staging site.
5. Broadcast an all clear message.

You may want to consider moving from the use of Template/Library Items to
server-side includes. This scenario would be much simpler when using SSI.

--
Murray --- ICQ 71997575
Team Macromedia Volunteer for Dreamweaver MX
(If you *MUST* email me, don't LAUGH when you do so!)
==================
news://forums.macromedia.com/macromedia.dreamweaver - THE BEST WAY TO GET
ANSWERS
==================
http://www.dreamweavermx-templates.com - Template Triage!
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.DreamweaverFAQ.com - DW FAQs, Tutorials & Resources
http://www.macromedia.com/support/search/ - Macromedia (MM) Technotes
==================

"Dion Jones" <monkey (AT) deadcatdesigns (DOT) co.uk> wrote

Cheers for that Murray,

you've got our boss in a bit of a worry now.
After a short discussion we are about to swap all our stuff over to the
way
you suggested.

How do Library items work when you check things in / out?
say someone has a page checked out and I change a library item that
appears
on that page.
hows that work?

Dion

"Murray *TMM*" <forums (AT) HAHAgreat-web-sights (DOT) com> wrote in message
news:beei9v$nva$1 (AT) forums (DOT) macromedia.com...
Dion:

Your setup is a recipe for disaster.

1. If you have multiple people working on the same site, you really
should
use checkin/checkout to avoid file versioning problems.
2. Having a local site that is on a network shared drive is very
dangerous
and is no doubt what is responsible for your corrupted site cache.

I recommend you do the following -

1. Copy the 'local' site to each hard drive (yes, this means that each
developer needs to have a local - really local - copy of the site).
2. Define a new site for each developer that has the local site for
LOCAL,
and the shared network drive as a staging server for the remote.

Now - the workflow would be like this. Each developer would check out
the
files they want to work on from the staging server. When completed, the
files would be checked back in to the staging server. In this way, the
staging server becomes the 'gold' resource for the development team, but
you
would have to all become accustomed to the checkin/checkout methodology
to
make it work. Using this methodology, the local site loses its central
position in the workflow, and the staging server assumes that role.

When the site/files is/are completed then ONE of the developers would
have
a
second site defined with the staging server as local and the production
server as remote. This person would then connect to this site, and
upload
(only upload) files to the production server.

Using this scheme, I can nearly guarantee you that your cache corruption
issues will disappear.

--
Murray --- ICQ 71997575
Team Macromedia Volunteer for Dreamweaver MX
(If you *MUST* email me, don't LAUGH when you do so!)
==================
news://forums.macromedia.com/macromedia.dreamweaver - THE BEST WAY TO
GET
ANSWERS
==================
http://www.dreamweavermx-templates.com - Template Triage!
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.DreamweaverFAQ.com - DW FAQs, Tutorials & Resources
http://www.macromedia.com/support/search/ - Macromedia (MM) Technotes
==================

"Dion Jones" <monkey (AT) deadcatdesigns (DOT) co.uk> wrote in message
news:beehov$mp8$1 (AT) forums (DOT) macromedia.com...
Murray:

Several working at the same time?

Yes, on different machines

Are you using checkin/checkout?

Not at the moment. Although I have thought about this before.

Is your local site actually on a network shared drive?

yes on a single machine hosted here on the network.

Dion.

Dreamweaver will display a notice that "fileblahblah is checked out by
fred", and it won't update that page.

if you are all in one workspace-- pass the word to people that you will do
a sitewide update in 5 minutes, and pls checkin all files.

you can then open either the master site- (with local on the network drive)
or preferable- open the site with the local defined to inside your
workstation.
Refresh the remove view in Site manage window- and scan for checked out
files- they'll show a green or red notice.

update the library item or template- click okay to it checking out all files
as needed.

then- when done- click in local side of Site manager window.
use dw menu-->Site-->Site Files View-->Select checked out files
And checkin all the selected files to the network drive.
Then change to the site def that's network drive and the real remote, and
sync or upload all the changed files.

Something you may want to consider- is changing to SSI instead of library
items. With many pages, and many designers with their fingers in the site-
it would make for much less checkin/checkout delays and uploading of files.

How do Library items work when you check things in / out?
say someone has a page checked out and I change a library item that appears
on that page.
hows that work?

--
Team Macromedia Volunteer for Dreamweaver
Certified Dreamweaver MX Developer

Dion:

But think how much nicer it'll be without all that cache corruption and DMX
crashing.

--
Murray --- ICQ 71997575
Team Macromedia Volunteer for Dreamweaver MX
(If you *MUST* email me, don't LAUGH when you do so!)
==================
news://forums.macromedia.com/macromedia.dreamweaver - THE BEST WAY TO GET
ANSWERS
==================
http://www.dreamweavermx-templates.com - Template Triage!
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.DreamweaverFAQ.com - DW FAQs, Tutorials & Resources
http://www.macromedia.com/support/search/ - Macromedia (MM) Technotes
==================

"Dion Jones" <monkey (AT) deadcatdesigns (DOT) co.uk> wrote

Thanks both Alan & Murray.
Now all I have to do is implement it.
Turns out it's my new task on my worksheet.
me and my big mouth

"Alan Ames" <blu (AT) formdude (DOT) com> wrote in message
news:BB304D69.13ACEE%blu (AT) formdude (DOT) com...
Dreamweaver will display a notice that "fileblahblah is checked out by
fred", and it won't update that page.

if you are all in one workspace-- pass the word to people that you will
do
a sitewide update in 5 minutes, and pls checkin all files.

you can then open either the master site- (with local on the network
drive)
or preferable- open the site with the local defined to inside your
workstation.
Refresh the remove view in Site manage window- and scan for checked out
files- they'll show a green or red notice.

update the library item or template- click okay to it checking out all
files
as needed.

then- when done- click in local side of Site manager window.
use dw menu-->Site-->Site Files View-->Select checked out files
And checkin all the selected files to the network drive.
Then change to the site def that's network drive and the real remote,
and
sync or upload all the changed files.

Something you may want to consider- is changing to SSI instead of
library
items. With many pages, and many designers with their fingers in the
site-
it would make for much less checkin/checkout delays and uploading of
files.

How do Library items work when you check things in / out?
say someone has a page checked out and I change a library item that
appears
on that page.
hows that work?

--
Team Macromedia Volunteer for Dreamweaver
Certified Dreamweaver MX Developer