Skip to main content
cynthias22293582
cynthias22293582
Inspiring
April 5, 2017
Question

Is Dreamweaver serious!?? My entire code I spent a month on was deleted!!!

  • April 5, 2017
  • 4 replies
  • 1736 views

WHAT THE H*LL. Yesterday I duplicate a layer, made edits on the new layer, check back on my old layer, made sure everything was just as it was. All okay, so I save, recheck again, everything is fine, so I shut my computer down. Come back today to see EVERYTHING on my old layer completely GONE! WTH man I spent two months on this code and it was NOT easy. This design is impossible to remake again from scratch. I spend over $200 on this Dreamweaver program only to know that it F-CKS everything up, and that is not the last of it. I've been experiencing countless problems with Dreamweaver and you're telling me this program is worth over $200!?? It's nowhere worth that much if it DELETED my entire code! NOW what am I supposed to do!???

This topic has been closed for replies.

4 replies

farahn28283144
farahn28283144
Participant
April 6, 2017

its very simple dear you need to save your coding in a note pad and make a document and then save that document in your email or dvd or usb thats all.

ALsp
ALsp
Legend
April 5, 2017

It could be a bug or a corruption, but in over 20 years working in Dreamweaver, here is a potential workflow situation where this can happen:

1. You edit a file and then save it with a new name.

2. When doing housekeeping, you decide to remove the original file, but instead you delete the copy.

3. The copy is actually where your changes were saved.

So you are left with the original file in its original state. That is, all the edits you performed are gone.

So, have you checked your deleted files repository?

Another possibility is that there was a glitch in Dreamweaver's Related Files code. There is no recovering from that. My advice to all Dreamweaver users is that they immediately disable the related files feature. We have done a lot of research into how it works and it is highly dangerous and subject to failure.

cynthias22293582
cynthias22293582Author
Inspiring
April 5, 2017

Hm.. I don't know. But I'm 100% sure that's not what I did yesterday. I did check the trash bin, and nothing is there. The related files feature is actually pretty useful to me, but if it's prone to failure like you said, I'll disable it and see about any problems then. Thanks for the advice, I'm just going to redo the entire code over.

pziecina
pziecina
Legend
April 5, 2017

I'm sorry we could not help.

The only thing I can say, is an open secret, in that the Dw team is working on git integration for the next release of DW, which will give you a way to back-up your files in future, and also offers a 'sort-of' version control system, which may prevent such occurrences happening once you start using it.

pziecina
pziecina
Legend
April 5, 2017

No I am not telling you Dw is worth $200, but did you check your old version did not have the same file name, and that that did not overwrite the changes?

cynthias22293582
cynthias22293582Author
Inspiring
April 5, 2017

I'm looking at it now, it doesn't have the same filename at all.

pziecina
pziecina
Legend
April 5, 2017

Providing you have not updated to the latest dot 2 version, Dw2017 did not always delete the file recovery back-ups it made. If you are luck enough, (in this case) that your version had that bug, try searching your files for any file beginning with the first three letters of the file name, (with a * wildcard for the rest, plus the .html file extension, (or whatever the file extension was)).

E
EbaySeller
Inspiring
April 5, 2017

cynthias22293582  wrote

NOW what am I supposed to do!???

LEARN the importance of regular BACKUPS!!!

cynthias22293582
cynthias22293582Author
Inspiring
April 5, 2017

So that's it. There's nothing Adobe can do right? So I gave them $239 for them to run away with, right​? We can agree on that right?

E
EbaySeller
Inspiring
April 5, 2017

Nah, we can't agree on that. It's most likely user error that caused your code to be deleted. I'd be more keen to blame it on something you did to cause the issue than to blame Adobe in this scenario.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices