Since updating to the newest version of Dreamweaver CC 2014.1 Release 6947 Build, I have noticed when clicking on an image the Image map tools in the bottom left of the properties box are missing. The only time they show is if I open an existing HTML I have created with maps on, and click inside the code view on the map coding. This still doesn't allow me to draw new maps on the image in design view. Where can I find the Image Map Tool in this version?
im in design view but i still cant see he mapping tools
Me neither. Getting rid of Design view is completely idiotic, IMO.
For the work-around to work, you need to make sure all other files are closed. Make the change to the Fluid Grid's css file, save and restart DW.
From there on out, you should have Design View for those files that use that particular Fluid Grid's css file.
Adobe realized they botched the Live View editor and left out a lot of the functionality that needs to be there in order for it to work correctly. They are working on it and should have it fixed in an upcoming version. For the time being, you can use the work around, or get the slightly older DWCC 2014.0 where Design View still exists vis direct download:
Thanks, Jon. I did finally get it to work and the image map seems to be working correctly in all screen views because my image happens to be a set size. Glad to hear that the developers realize that getting rid of Design View altogether was short-sighted at best.
Okay -- back to image map problems. I am working on an older file that is not fluid and I cannot add any new image maps. I can click on the old image maps and see them, but there is no way to get to the property if you click on a new image. Am I missing something or did they remove this ability all together???
What view are you in?
Image Maps are still only available in Design View.
If you are in Design View and aren't seeing the tools when you click on an <img> (you can't map background-images), make sure your Properties window (Ctrl + F3) is expanded. There's a tiny little triangle in the bottom right of the Properties window that needs to be pointing up in order for the image map tools to show.
QuimbyDog is right - there is no way to add image maps anymore. Yes, the triangle in the bottom right is pointing up.
I assure you, Image Mapping is still part of the program. Here is a screen capture of DWCC 2015 with Image Map tools...
You must be in Design View and have an actual image selected as shown in the screenshot above. If you are in Live View, you cannot access the Image Map tools. If you are using a Legacy Fluid Grid Layout, you would need to make a small change to the LFGL's .css file in order to access Design View which is disabled by default in both CC2014.1 and CC2015.
Another possible reason for the tools to be missing could be html errors in the offending page(s).
DW relies on clean, valid code for much of its functionality, more so now than in the past (which could explain why an older page that used to work, no longer does).
If you are in the right View, have an image selected and still are not seeing the options in the Properties window, I would suggest running your problem pages through the validator at http://validator.w3.org/nu to make sure a code issue isn't causing the root of the issue.
If all of the above criteria are met, and the code is clean, but you still aren't getting the options, I'd suggest clearing the program cache, renaming the personal config folder and/or restoring preferences to see if there's a possible corruption in your program causing the issue:
The options are Code, Split Code, Live and Code and Live. There is no Design view. There are no html errors - I tested using a brand new html doc, and inserted one JPEG.
Design View has been moved into a dropdown menu along with Live View (CC 2014.1 and later).
If you are not using Fluid Grids, you have to click the little arrow to the right of the Live View button in the toolbar.
If you are using Fluid Grids, you need to do the following to get Design View back...
Close all other files, open the Fluid Grid's css and add the X shown below:
Dreamweaver Fluid Grid Properties
dw-num-cols-mobile: X 4;
Then save and close the file.
Restart DW and you should have Design View from there on out on any files using that fluid grid .css file.
I see, Design view is in the drop down menu in the toolbar.
Thanks. What a work-out!
This added code:
Dreamweaver Fluid Grid Properties
dw-num-cols-mobile: X 4;
...solved my problem in DW CC 2017 but how utterly ridiculous it is that I have to do that in order to get my design view tab back in a fluid layout. I assume this is only a problem when using fluid layouts from older versions of the software?
I'm using a textbook to teach DW CC (unfortunately it's for v2014 which is the newest version of this particular textbook that we can find) and I have been pounding my head against the image map directions - not to mention the table - for the last 1/2 hour because it doesn't work. Then I stumble across this thread and find out that in a fluid layout that I should have a design view option and I don't. No wonder, the fluid layout CSS needs those lines of code.
Adobe I'm getting ready for the new school year. I've taught Dreamweaver for more than 10 years with our most recent version being CS6. I have NEVER had this many problems prepping my demonstrations as I have with CC. DW has been an outstanding tool. DON'T RUIN IT!!
It's more than a bit concerning that you're "teaching Dreamweaver" using such an outdated version. A lot has changed in the decade plus since CS6 was released, both in the program and online.
The developers are trying to keep pace with "the internet" in general and FGLs just weren't that good at what they did. I'm actually sort of surprised they left any vestige of FGLs in the program when they took them out several versions back. They've been replaced with the much more robust Bootstrap Framework.
Basically FGLs were a good idea with poor execution, and when something "better" came along, Adobe abandoned and replaced them. For some reason, they left the ability to work with them hidden in the program and one of the contributors here found a work-around for it.
If you still want to use the obsoleted Fluid Grid Layouts, without the work-around, you can download and install a previous version of the program from the CC Desktop App (I believe CC2014 or earlier will do the trick). As a CC Subscriber, you can actually go all the way back to DWCS6 Cloud which is much closer to the version you were using, and have every major version installed on the same machines at the same time under a single subscription. They won't run concurrently, but it would allow you to use the legacy FGLs in the older version, close and switch to a newer version to use newer features.
If you're installing newer versions when older ones exist already, make sure to click the "Advanced Options" link in the installer dialogue window. That will allow you to turn off the checkbox for "Remove Older Versions". All 5 major versions of DW Cloud will coexist peacefully on one system (CS6 Cloud, CC, CC2014.x, CC2015.x and CC2017.x) however dot releases will overwrite each other (there are 3 versions of CC2017 available in the app, but only 1 can be installed at any given time).
I may need to clarify a couple things....
I totally agree with everything you said. I've actually been teaching DW at the high school level going way back to when it was a Macromedia product. We had no choice but to use CS6 up until this school year as that's all my school district had. We now have the funds to upgrade to CC so that's what we're doing for this year. When they did the CC install our technicians went with the most up to date version which is 2017. That leads to the next problem...
There's not many textbook options out there for DWCC2017. And unfortunately, when the deadline to make a book decision was on us several months ago we picked the most up to date textbook we could find. Turns out, that book apparently is for version 2014 - we have 2017. I figured we could make it work but the further I get into the book the bigger the problems are becoming. For the first few chapters I was finding minor things (ie find option XXX under menu YYY but option XXX is now called something else). As I moved through the chapters I'm finding bigger issues that will really confuse students learning web design for the first time (ie can't make an image map in live view if the page is based on the old fluid layout technique because you can't switch to design view, but that's what our new textbook files used, so what's the workaround?). The next chapter I'm working on is all about fluid layout but that doesn't exist so now we'll have to create all our own materials to teach responsive design.
Granted, these types of problems aren't all because of Adobe - the textbook we're using is a contributing factor. Obviously the nature of this industry changes rapidly and the tools to do it need to change just as quickly. But consider my initial reason for finding this discussion thread... (1) What is the logic of not allowing a user to make an image map in live view, or (2) Why not make the design view work even on pages that use the legacy stuff like fluid layout?
I'm also frustrated with DW's lack of true support for the development of data driven sites (ie PHP, asp.net). The days of DW being THE tool of choice for web designers can't exist solely on the ability to design nice looking static web pages, but that's another rant better suited for a different thread.
CC 2017.5 is a total departure from the old Creative Suite. Among other things, the current DW has a new code editor, new interface, new menus and new features to support modern coding practices like integration with GIT versioning and a built-in pre-processor for LESS & SASS support. The target user has shifted from the casual coder who mainly works in Design View to responsive web & app developers who want to work with code. For database users who need utilities, DMX Zone sells DW extensions to replace the deprecated server-behavior panels. Yes, a lot has changed. It's unfortunate that your textbook is already 2-1/2 versions behind CC 2017.5. Owing to Creative Cloud's rapid release cycle, the printing press can't keep pace with these changes. Online tutorials are probably the most current resources available.
Yeah, we're finding CC 2017 was a pretty significant jump. Like I said, textbook resources are the issue. Yes, there's tons of online resources that can be pieced together to teach particular concepts - and that may be the approach we'll have to take where our book falls short - but some of my fellow teachers need more than just tutorials. They want resources (objectives, assignments, assessment materials, etc).
So the question becomes, do we downgrade back to version 2014 so everything aligns with the book or do we use what we can and create what we have to for areas where the book falls short. The decision for me is simple, I would never choose to use old software with my students when I have access to the latest software. Guess I've got a lot of work to do between now and the start of the school year in a month. 🙂
By the way, sorry for hijacking this thread....we've sort of drifted off topic here.
I'd say, lacking any newer print resources, my choice would be to roll back if possible.
It may not be, if your school purchased a volume license though. If I recall correctly, they work a bit differently from the standard subscription model.
1. I have no idea and have wondered that myself. It seems like it would be something that could be done, but maybe it's harder than we think to modify the browser within DW (Live View) to allow it.
2. That one, I'm guessing, is to stop people from using the outdated technique. Fluid Grid Layouts were notoriously fragile and better ways exist. It's most likely part of the "Modernizing of Dreamweaver" that Adobe has been trying to do over the last 4-5 versions.
3. Many people are frustrated by the lack of database panels in the latest versions. Adobe removed the old panels because the code was horribly outdated and no longer works under PHP7 (which many hosting companies are now installing on their servers). Rather than spend the time and resources to update it to mySQLi or PDO themselves, they chose to hand it off to third party developers to make modern code driven panel extensions. WebAssist and DMXZone are two I can think of who have come up with extensions for that aspect of the program.
PHP/ASP.net - yes, I see your point. It's just a shame because what we had back in, I think it was CS3, was pretty decent for teaching introductory concepts in ASP.net and PHP. No it wasn't the best tool for the job, but it was included (free), and was enough to teach high school kids the basics of creating data driven sites. Plus it was fairly intuitive to use. If we use something else now I need to ramp kids up on whatever IDE we're going to use before I can teach content.
Thanks to all of you for chiming in on this discussion. It has been helpful as we continue to put all of the pieces together.