By GeekElectro on

Adobe just formally announced Adobe Creative Suite 5 (CS5) product suite, its design and creative workflow software which, among other things includes Adobe Dreamweaver CS5.

Dreamweaver CS5 now supports Drupal CMS, along with Joomla! and WordPress.

Read more on Dreamweaver CS5 at http://www.adobe.com/products/dreamweaver

Comments

pumpkinkid’s picture

pumpkinkid commented

I might just be dense... but other than the code hinting for specific CMSes... How is it integrating with Drupal? All I see is a "Live View" that is very similar to the one I could never get to work in CS4... Can anyone help explain?

david3605’s picture

david3605 commented

Hi - I'm on the Dreamweaver team. There is a sample video from the lynda.com Dreamweaver CS5 course that shows some of the new CMS integration:

http://www.lynda.com/home/DisplayCourse.aspx?lpk2=59959

Once on this page, click the link: "Working with CMS frameworks". The instructor is using WordPress in the video, but the same functionality applies to Drupal.

- David

plotfy’s picture

plotfy commented

I have been trying to get this to work with my Mac using MAMP server. Maybe you can help.

My css files cannot be accessed because for some reason, on my local server, they are calling for .css?8 or .css?2 extensions rather than just .css and it seems to be confusing Dreamweaver. Wordpress does not have this problem, so I assume it's something in Drupal.

Is there something in Drupal I need to change so these extensions are correct on my local server so I can edit in Dreamweaver CS5? Hopefully it's an easy fix I am just overlooking.

Thanks

jon betts’s picture

jon betts commented

I'm having multiple problems too getting Dreamweaver CS 5 to work with Drupal. And I haven't seen an example of it working other than Adobe saying it does. All tutorials are with a very basic Wordpress install. There doesn't seem to be any documentation related to proper setups for Drupal sites either. I certainly wouldn't invest in the product if Drupal integration is important until they demonstrate that it indeed works either through a video demo or installation example.

plotfy’s picture

plotfy commented

They have a 30 day trial, which I have been using with Drupal. As I stated in my previous post, I can't get it to work with the way the .css files are formated on my local server. It can't search for dynamically related files unless I remove index.php from the address bar, Then, when it does a search for dynamically related files, it keeps bumping me out of my Drupal site to a different site and switches to that sites local files. Maybe I have it set up wrong? A Drupal demo would be helpful.
I suggest anyone thinking of upgrading, try the 30 day trial first, let me know if you have any better luck. I will not purchase the upgrade if I can't get it to work with Drupal.

pumpkinkid’s picture

pumpkinkid commented

There are a few accounts on twitter that answer questions on issues like that @dreamweaver @creativesuite and @garazi The last being Adobe's Web Evangelist. I had brought up some concerns to them and they tried to assure me that I was wrong in thinking that there would be issues with it (I thought it would), however uppon trying dw cs5 I must say I too had a hard time understanding how to get it to work.

jon betts’s picture

jon betts commented

Here is what I've found based on weeks of my work as well as others on this site and on Adobe's forum (but no help from Adobe).

1. There is no documentation about how to set up sites properly with Drupal from Adobe.
2. You can sort of get things to work, but not really with multisite.
3. These new features really seem to be geared towards a simple single site WordPress install.

Here in a nutshell is what you have to do as far as I've been able to figure out with help from others (there may be all sorts of flaws with the set up, but there is no documentation specific to the uniqueness that is Drupal so there isn't anything to refer to):

1. Set up a local server (I use MAMP Pro, MAMP is fine too).

2. Your local site folder is the folder to Drupal (e.g.: /Users/name/Sites/drupal)

3. You MUST create a testing server, otherwise you'll get an error.

4. In the Testing Server setup, connect using Local/Network. For Server folder, use the same settings as your local folder (e.g.: /Users/name/Sites/drupal)

5. For web URL enter the URL you use for your local server. I set up a URL like local.example.com. This may be where some of the problems I have lie, as every other demo I've seen assumes something like http://localhost/foldername as the URL. Not sure why this would matter.

6. Go to the advanced tab within the testing server and make sure you select PHP MySQL as your server Model.

7. If you don't define a remote server, you'll need to edit one more setting, in the white tabs area in the left column of the Site Setup dialog, select Advanced Settings, then Local Info. For the Web URL use the same one as you used for the testing server. This may already be there.

Now, once all the cache files are done, you navigate to the index.php file in your DRUPAL folder, not your site folder. Then click on the discover links, then the Live View link. Success! Well, sort of...

Here are the issues:

1. As long as I only want to edit the home page templates, I'm fine. You are supposed to be able to navigate within the live view to any page and then select the "Edit the Live View page in a new tab" command from the page icon next to the address bar in DW. However, when I do this, I get a page not found in site error. (Of course the page isn't found, this is Drupal, pages are nodes in a DB).

This means that I can edit page-front.tpl.php, but not page.tpl.php.

2. There is no way that I can find to isolate a multisite install using DW. The only differentiator is the URL used to access the install. You literally point to the same directory for each site (and this directory includes the sites folder which includes every other site you manage). This means that if you make a change to a page or two and use the sync feature of DW to manage changes between local and testing server, you've got to wait 15 or 20 minutes while DW compares every single file in core and every other site you manage. This is a deal breaker for me. I hope I'm missing something.

3. There seems to be issues with symbolic links. i.e. I can't click on them to access the folder they point to. They seem to appear like files to DW. I figure this is a bug.

4. There seems to be issues with uploading files to the testing server. For instance, if my local URL is local.example.com, then the folder on my local server is named likewise. However, my testing server url is www.example.com. So what happens is when I upload files to the testing server, a new folder is created called local.example.com. This seems to be a symptom of not being able to isolate a specific site. If one could point to each site's individual folder within the sites folder (ie local.example.com) in the site manager, then this probably wouldn't happen as the "root" folder wouldn't be the Drupal folder, it would be the site's folder.

5. If you want to edit a specific css, you need to open it, make it active and then select "this document only" from the css edit popup. Not a big deal, but it isn't as transparent as CSSEdit. However, CSSEdit's floating windows drive me nuts! :-) Definitely prefer DW CSS editing.

I'm sure there are other issues that I just haven't stumbled upon yet, but to be honest, the above issues are enough to drive me back to my previous workflow. I think DW CS5 will work fine with a single site (though I have no idea how to solve the page not found in your site error).Multisite is another issue.

I hope someone involved with Adobe or a beta tester can chime in here and set me (and others) straight. As mentioned, time is running out on the demo.

pumpkinkid’s picture

pumpkinkid commented

While I totally agree with you with 99% of that, I wanted to let you know that while there could be a newer issue with symlinks I haven't seen in cs5 yet, I had noticed before that under certain circumstances ftp protocols cannot follow symlinks, this obviously would include DW's FTP client.

I'm interested in seeing if you can access the same directory using filezilla or other ftp client.

jon betts’s picture

jon betts commented

I've got it setup as local/network so FTP shouldn't an issue. It works fine using the finder, Transmit4, and Coda. It is flakey at best. The links seem to work internally within files, but the site manager doesn't seem to support them. I've moved on until there is some documentation on this as I just need to get work done and unless proven otherwise, Dreamweaver CS5 does not seem to support Drupal 6 multisite installs in any practical way.

petrakev’s picture

petrakev commented

All,

There is a small bit of documentation from Adobe on Drupal. Perhaps you find what you're looking for at:
http://www.adobepress.com/articles/article.asp?p=1590589

ronnqvist’s picture

ronnqvist commented

I figured that the Inspect feature doesn't have any clue about what files belong to the actual theme and what CSS-files it should keep its hans off. This means that you might very easily find yourself editing CSS-files that belong to Drupal core, which is a big no no. And noobs might very well want to use a base-theme to build a sub-theme upon, in this case it'll go messing with the base-theme. This renders the Inspect-feature pretty much useless... which would have been the thing setting Dreamweaver apart from just using a simpler editor and a browser with Firebug.

Another thing I noticed was that I was unable to log into my site through Dreamweaver's live view, which kind of puts the last nail in the coffin.

I used Dreamweaver up until MX 2004, after which I started doing CSS literally 'by the book' and didn't feel I needed the bloat of a WYSIWYG anymore. Due to numerous positive reviews mentioning how Dreamweaver now has a more coder-friendly focus and Drupal support (+WordPress&Joomla) I thought I'd give it a shoot. After much time wasted really trying to give it a shoot I'm unlikely to ever look back. Goodbye Dreamweaver!

Stephan_M’s picture

Stephan_M commented

Hi,
i was able to log in to Drupal in Live View (i don't mean the F12 Browser but the Layout-Window). In the Menu use View-->Live View Options --> continuosly follow links (or some such, i don't know the correct translation, as i am using a german Dreamweaver). Now you can click on the Log-In Button.
Also, getting Drupal to run on a xampp and properly inside Dreamweaver CS5.5 was a breeze. It automaically chose to include Drupal Code Hinting, too.
Cheers

mduros’s picture

mduros commented

Okay, I've read and read and tried all of the fixes I can find to connect Dreamweaver CS5 to a live Drupal site, but I cannot get it to work. I have watched the wonderful tutorials out there that show you how to do it and how to get around the common error codes, (mainly the "Dynamically-related files could not be resolved because the site definitions is not correct for this server. Retry|Setup" but this does not seem to work on my Windows 7, 64-bit system. Are there any Windows users that have successfully connected to their established Drupal sites? All of the tutorials and fixes I have found are for mac users. I know that it shouldn't make a difference but I think it may, or the fact that I have a 64 bit system. I have tried using acquia drupal, but also have tried using xampp and wamp just in case acquia drupal was the problem.

It seems to otherwise work fine for the default template it sets up for Drupal. I just can't get the server names and paths right to make a local testing version of the live site.

I am new to Drupal but a long time Dreamweaver user and feel that being able to work with it through Dreamweaver would help my learning curve tremendously. I have inherited an established running drupal site from one of my clients.
Thanks,
Mary.

mduros’s picture

mduros commented

Figured it out. It was all in the way my local server setup tied into CS5. I finally got it working correctly by following this set of instructions to a T on my Windows 7 64-bit computer. http://www.adobe.com/devnet/dreamweaver/articles/setup_php.html It worked beautifully. Afterwards I did read that there may be a problem running xampp (which the article used) on 64 bit machines but I didn't run into any problems whatsoever. After going through the tutorial in the article I linked a local copy of my live site into it without issue.

tribe_of_dan’s picture

tribe_of_dan commented

Hi, thanks for the link, I found it helpful. I have Win 7 x64 also and am using Xampp. This got me further but I'm still getting the error. I'm using a multisite install also, this may be the cause. Any clues? Thanks.