Longtime Adobe user here, starting with PageMaker, Photoshop 2.5, I think it was, and got Dreamweaver back during the Macromedia days, near the dawn of the internet. I don't recall being as disappointed with an upgrade as I am with Dreamweaver17. This is also the first time I've felt compelled to post on this forum, although I've consulted it often over the years.
I put off upgrading from CC15.5 because I have a legacy site written in classic ASP (yeah, I know -- we'll be switching it over to PHP, but for the moment, it still uses VBScript/ASP), so I waited to upgrade until I saw deprecated server behaviors were back. At that point, I upgraded, and it's been a huge trial ever since. In my attempt to resolve problems I was having, I uninstalled and reinstalled DW17, which apparently wiped out my previous install of CC15.5 in Creative Cloud, because now I have no previous version to go back to. So that's my first question -- if I have no previous version of DW showing in Creative Cloud, is there a way to roll back?
My other questions/comments involve the following problems I've encountered since upgrading. Looking to see if anyone has solutions to any of these, or even if anyone else is also experiencing these:
- Unable to scroll through classes in the property bar using the mouse wheel - instead, I must use the VERY SLOW arrow icon at bottom of the dropdown to scroll down the list.
- In design view, unable to preview changes in browser using F12, Real-Time preview, or right-clicking the page tab and selecting "Open in Browser." The browser opens, but shows the previously saved version. To view any changes made after the last-saved version, I must save, upload the file using the Put command, then use F12, etc.to see the change. This happens even though I've set "Automatically push files to testing server" and "Automatically upload files to server on save."
- In Split/Live View, every little change to the code is either met with a dialog box asking if I want to save the file before I can preview it on the Live view side, or else the change is made in the code, but Live View remains unchanged. Maybe this is the way it's supposed to work, but it's so annoying, I'm not bothering with it.
- Live view doesn't allow me to edit on the Live View side -- didn't it used to? I didn't use it because it was too slow; is this the fix?
- Selecting text in Split/Live View doesn't highlight it on the code side, so you have to poke around to hunt through the code to find the spot that you need to edit.
- Split button can only be selected; clicking again to deselect doesn't work, it remains highlighted. To go back to the previous code or live design view, you have to select either the code or Design/Live button. Just weird to have a button you can't deselect -- seems like deselecting it would set the view back to what it was previously.
- In Design view, the background color of a <div> with a colored background disappears when scrolling up to see the rest of the page below the window. If you scroll back up to the top of the div after scrolling down, the background color disappears entirely. The background color will only reappear by scrolling back to the top of the div and moving your cursor outside the div and then back over it. If you've used white text on a <div> with colored background on a white page, the text becomes invisible when the background color disappears, making it impossible to work in that div in design view..
- Code hints stop working if you create a filtered recordset on an ASP page. (I know, don't yell at me about ASP).
- Find and replace of selected code causes the cursor to jump to the top of the page when done.
- Really hate having find and replace as a huge drop-down at the top of the screen. I prefer to move it off to my second screen instead of taking up all that real estate at the top.
It's acting like I don't have enough power to process here, but I don't think that's the problem (64-bit machine, Win7, 16GB RAM, dual Xeon E-5 processors, Quadro 4000 graphics card). I'm thinking this app just was not ready for release, and I'm resentful of having my time wasted to beta-test something this buggy.
Desperate to go back to DW15 so I can get some work done - ideas?
1 Correct answer
3
Replies
AdChoices