Old (CS6) Dreamweaver site Needing to be opened in 2021 Cloud

11 replies
401 views
Translate

I recently upgraded from CS6 to the 2021 Adobe Cloud. My co-worker who also updates our website (which is housed on our local servers), has not yet upgaded to the Cloud version. I need to know how to migrate or import our current site and hopefully still have both of us be able to continue editing and working on it till they are also able to upgrade to the Cloud.

This topic is closed to new replies. Start a new post to keep the conversation going.

Nancy OShea

Community Expert

Open DW CC.

Go to Site > New Site and define your local site folder.

Enter your server's log-in credentials and root directory.

Translate

Nancy O'Shea— Product User & Community Expert

B i r n o u

Legend

I had understood that both people had to be able to work simultaneously on the same project, one from CS6 and the second one from the last build

Translate

Nancy OShea

Community Expert

Does it really matter which code editor & S/FTP client they use to download & upload files from server? No.

That said, Dreamweaver's proprietary File check-in/out feature doesn't work with other tools. It only works with Dreamweaver.

Translate

Nancy O'Shea— Product User & Community Expert

B i r n o u

Legend

The question, is did you use features specific to DW CS6 as the Server Behaviors... I don't remeber what exactly was still present in CS6, that has been removed since... as Spry library, Widget ??, jQuery Mobile, ...

so, if the web site doesn't use that stuff, it's just plain HTML (either if SB are plain PHP, they're first obsolete using v5 and bad pilote for DDB and second the palet was removed...) , Spry is also plain JS but the lib is obsolete, widget can cause trouble too...

now, if you want to share the web site and works remote... both of you will have and own a local web site, they can be different... so be aware when you upload files to not overwrite the remote files in a bad way...

so you should set a second remote server, for testing purpose, then when the testing web site is correct you send the testing files on the production server. (I'm not sure for being clear... so please don't hesitate)

DW propose a Archive / Extract process, but it is really pain full...

now if you aware of GIT, the new DW builds allow us to work using a reprository and being able to set forks...

here again let us know what best fits for you, if you need further help

Translate

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.