The main thing to look out for here is to see if the directory structure is clean: All of the contributed modules should be placed in sites/x/modules (where x is "all", or in a multi-site environment, perhaps a URL). That way, whatever method you use to update Drupal core will not destroy any custom or contrib modules used in the site's architecture. Then: see http://groups.drupal.org/node/19513 Read all of it, it shares many experiences and opinions on the updating of both Drupal core and contrib modules. Victor Kane http://awebfactory.com.ar http://projectflowandtracker.com On Sun, Mar 8, 2009 at 10:17 AM, Steve Kessler <skessler@denverdataman.com>wrote:

I have never used a site that has been built using CVS before. I have inherited a site that was built using CVS. We don’t have SSH set-up yet with the host but I want to make sure I am not going to mess anything up by adding a modules to the site that is not downloaded through CVS and then when we get SSH I can replace it that way.

Thanks,

Steve

Steve Kessler

*Denver DataMan *

303-587-4428

Sign up for the Denver DataMan Free eNewsletter<http://www.denverdataman.com/content/enewsletter-signup>

-- [ Drupal support list | http://lists.drupal.org/ ]