Skip to main content
Participating Frequently
June 14, 2019
Question

New Dreamweaver problem with site [was: is a Nightmare]

  • June 14, 2019
  • 2 replies
  • 675 views

I was reviewing my website:  www.yellowstone.co when I noticed a space before a comma.  I went in removed the space and saved the page.  I then uploaded the new page with the correction.  What I got was a totally messed up webpage and I am pissed!  I have been doing this since 1995 and have never had a software on it own add or change code and screw up a website.  This is totally unacceptable and very very frustrating!  Adobe has to fix this right now big time!  Help!  This is the new DW 19.1 build 11240.

    This topic has been closed for replies.

    2 replies

    Participant
    June 14, 2019

    PLEASE ADOBE just Sell Dreamweaver CS6 again... We'll pay double.....

    Jon Fritz
    Community Expert
    Community Expert
    June 14, 2019

    I've never had DW do that either.

    There's really nothing Adobe would be able to do for you if you overwrote a functional page with a newly broken one no matter what the reason for it breaking ends up being.

    Your best bet, and most likely quickest resolution, is probably going to be to go to your hosting company and see if they can pull that page from a backup and replace the problem page online while troubleshooting continues with DW to find where the issue came from.

    Participating Frequently
    June 14, 2019

    Thanks, I am on line and in the que to do that.  I am just afraid to use DW again.  Crap is about all I have to say for the very new DW.  Very frustrating!  Thanks for your time and help!

    Jon Fritz
    Community Expert
    Community Expert
    June 14, 2019

    Do you know what was changed by DW?

    Maybe some more specifics about what has apparently been changed, will help the contributors here figure out what might have happened and get you back on track.

    I know some oddities can arise from DW's auto-complete functionality when it runs into html code errors. It's possible DW tried to "fix" something that was technically broken (but rendering correctly in the browser) and in the process, made a code completion that now forces a bad rendering?


    It's hard to say without knowing exactly what you had, and what you now have.

    Are your code completion settings turned on in preferences?