Whole page lost. - VERY long page. -...

User 528054 Photo


Registered User
209 posts

Also, you should ALWAYS keep a backup of all files...


Mmm, I learned the hard way too........ It wont happen again, ever

Backup to servers, or little hard drives like mine.

I prefer the hard drive option, its cost me nothing for two drives and £1.99p for each HD Caddy...

Whilst I have been writing this I just backed up my entire website :)

I guess this one episode is the SHOCKER when it happens and everyone gets shocked at some point.

If the file is lost, I think maybe just take a deep breath and set about sorting the backup stuff so it never happens again.

And then move on, the new release is due soon so that's a good thing

Peter

User 38401 Photo


Senior Advisor
10,951 posts

Yep backing up your files is your responsibility and should be done at least every other day if you are doing a lot of file changing. Less often if it's only a random change in things here and there. I do weekly backups of my system to an external harddrive so that this type of thing can't happen again to me either.

Truly it's good practice to do so and it's not CC's fault that you completely lost that file if it was an update to the file, you should have kept a backup that you can go back to. And once again I still don't think the program is the issue here at all. I don't think that the problem was related to CC, but it did lose the file which would happen to anything you used if it crashed.

If you change settings on any program at all and it crashes before you shut down you will lose every single setting you did. That's normal when things crash so it's not uncommon that you would lose a page you have created if it crashes before it's saved, what is uncommon is that the crash would cause a blank page. That part may be something that messed up the program when it crashed, but I don't think that initial issue was caused by the editor at all.

Either way, I will hope that at this point on you'll keep backups on another drive or uploaded periodically so you have them to fall back on. If the page was an edit and not a newly created page then you still should be able to get a backup copy from your hosting company should you need it bad enough.

Other than that, we really don't need a step by step description of your support situation. Just because you filled in the blanks doesn't mean the person you're talking to in support got that information. Give them a break already and let them help. IF you cannot do what they need you to do, don't come bashing them for it here. You're the one choosing not to let them help you not them.
User 45086 Photo


Registered User
28 posts

I didn't back up the file I was JUST CREATING.
Support asked me questions which were supplied in the form (version using), so I supplied that again, then he told me IF I am in 12 to upgrade. Ignoring both times that I am in 12.5 (included the build)...

Now, when the problem can't be recognized how in the world can you say it is fixed? No one has a clue as what was 'broke'.

I'e never had a problem with CC program until this build.
I miss 'that' "Margaret, your strange".
Version 12.7 Build 454
User 528054 Photo


Registered User
209 posts

I was working on one article and am sure I 'saved' after placing the 'date/article title' header, and only part way into the article itself.

When I re-opened CC, to this file, the whole page is blank.


I may be wrong here, and probably am.... But the 12.5 release when it first appeared did have a bug, previously saved files could be flagged on closing them, and a request to save made, if you accepted that and saved again, reopening the file would produce a blank empty page.

End of story for the file contents if you didn't have a backup with which to overwrite and restore the blank file.

This bug has been dealt with and the next release will have it covered. I dont think anymore questions about it will be any use answer wise, other than.... The next release will not have that behaviour again...

I also had this happen, with the reopened file being wiped clean, but luckily I had another

Regards
Peter
User 103173 Photo


VP of Software Development
0 posts

Katherine K Hebenstreit wrote:
I didn't back up the file I was JUST CREATING.
Support asked me questions which were supplied in the form (version using), so I supplied that again, then he told me IF I am in 12 to upgrade. Ignoring both times that I am in 12.5 (included the build)...

Now, when the problem can't be recognized how in the world can you say it is fixed? No one has a clue as what was 'broke'.

I'e never had a problem with CC program until this build.

Even though you may have filled out the version and build number, we always have to verify that. You would be amazed at how many people just don't fill that information out correctly. We are not trying to insult you by asking, so don't take it as a personal criticism. You should instead look at it as us trying to be very detailed to make sure we are properly looking into this.

We can debate in forms and support over and over on this issue but that will just get you absolutely no where Katherine. Just follow what I wrote you in my last email. You took the time to ask for my help (and those here), so take it and don't argue. Download the update I sent you and lets try to move forward and not just spin in the same place all day. ;)
Learn the essentials with these quick tips for Responsive Site Designer, Responsive Email Designer, Foundation Framer, and the new Bootstrap Builder. You'll be making awesome, code-free responsive websites and newsletters like a boss.
User 2073552 Photo


Registered User
1,625 posts

Scott Swedorski wrote:
Katherine K Hebenstreit wrote:
I didn't back up the file I was JUST CREATING.
Support asked me questions which were supplied in the form (version using), so I supplied that again, then he told me IF I am in 12 to upgrade. Ignoring both times that I am in 12.5 (included the build)...

Now, when the problem can't be recognized how in the world can you say it is fixed? No one has a clue as what was 'broke'.

I'e never had a problem with CC program until this build.

Even though you may have filled out the version and build number, we always have to verify that. You would be amazed at how many people just don't fill that information out correctly. We are not trying to insult you by asking, so don't take it as a personal criticism. You should instead look at it as us trying to be very detailed to make sure we are properly looking into this.

We can debate in forms and support over and over on this issue but that will just get you absolutely no where Katherine. Just follow what I wrote you in my last email. You took the time to ask for my help (and those here), so take it and don't argue. Download the update I sent you and lets try to move forward and not just spin in the same place all day. ;)


So saith the lord...
"An Apple doth not fall far from its tree, yet an orange does."

https://lbwebsitedesign.com - Responsive Web Design & Web Hosting Services.
http://helpsite.sirage.com - HTML5, CSS3 and CC Help Video Blog.
User 2733 Photo


Ambassador
426 posts

The only thing I have read here anyone should consider weak is your web development skills. YOU should have made a backup of the file you were working before editing it. YOU should have a working knowledge of how RAM is used on your system. YOU should have made a screenshot of the error (Print Screen). YOU should have opened a support ticket promptly. YOU should not have ranted in this or any other forum.

Scott and the support team at CoffeeCup answer support tickets very quickly. I get a response in less than an hour, sometimes minutes.

That is far from weak support. That is awesome support. I strongly urge you to lose that whole "squeaky wheel gets the grease" mentality, and start taking some responsibility for your own foolish habits.

We all want to help those who want help. Inger and Jo Ann help so much they have nearly 7,000 postings in these forums. Their efforts are sincere. You have less than two dozen posts. So, you either lurk, or are new here. Either way, show some decorum.
Let's not get all hurt.

Have something to add? We’d love to hear it!
You must have an account to participate. Please Sign In Here, then join the conversation.