XML (0,0) 
Autor: Luis S.I just had another crash that gave me the dreaded XML (0,0). error in wich the project is by not means recoverable, luckily I just lost a half of an hour's work and I have a fast working pace so I can recover, but come on guys, I'm not the only one that has reported this bug that has plagued X5 since Ver.13.
You must put your hands into this matter ASAP, because as of now, I -as many other, I assume-, feel more like a beta tester than a customer (that renews the software every year).
In case you wonder: Fresh W10 install, I5procesor, 8GB of ram, all Visual C++ and latest NET framework installed according to the info you give on every related post, the program is run with admin privileges and my antivirus is Malwarebytes.
The file "project.iwprj2" is 0kb. so it's corrupted and the only recoverable backup is from when the project was almost empty.
For starters, it would be nice to have the option to download older versions of the software in case that some update does not work fine for any of us, I understand that as a company, you prefer to have us all in the same/latest version of the software, but please, if you cannot/wouldn't fix the problem, at least let us go back in case something is wrong.
.
BTW, If anyone has the previous version backed up, please be kind and share it with me :(
Luis, please make generous use of the backup now feature accessed with the down arrow next to save, and the occasional export.
I believe v14.0.6.2 has less instabilities than earlier versions, but I do have most of the earlier releases
(sadly too big to make available here)
+1 Luis
Incomedia proposes us an evolution but is it a real improvement for us?
So many of us are complain and think like you about crashes and others dysfonctions; it's auwful to loose our project, to spent time to test and try to resolve issues, even though many moderators and users give us solutions (THANKS++).
In my case I bought V14 on 20th october 2017... I don't think that V15 will be released before 20th october 2018... so, as usual, I'll have do buy the new version.
Sorry, but I don't understand the different for me; may be for new customers.
I hope I'm wrong...
Danielle
Thanks Esach for reminding us all the updates. that's what I criticized in my commentary
in https://helpcenter.websitex5.com/es/post/188062
Esach, I know you are doing everything you can to help us...
Danielle
Autor
What? why did you edited the title of my post?, you could at least tell me the reason instead of editing the title at your convenience.
The title was in no way offensive, I have been paying for years for your software, the least I deserve is some respect when I post something relevant for the community.
.
The title was: Update protection is here!, ok let's start by fixing the bugs, please.
Luis - it wasn't me :-)
Are you referring to this post or another??
Autor
Hey Esahc, i'm almost sure that no mod did it, you guys are always very committed to the community, even when some users get to be somehow toxic.
I posted this topic like 17 hours ago with the title I mentioned, but I guess someone was upset with it and change it to "XML (0,0)" a title that obviously is not going to attract much attention (let's hide the problems under the rug?), anyway, this questionable person didn't even posted a reason for the edit, I mean, it wouldn't have been much of a problem if he/she had, at least been constructive with the problem at hand, so I can only feel disappointed at this moment and pretty certain that a fix for this matter will never come.
-
But hey! at least we (Ver.14 users) have like 8 month of Update Protection :) </sarcasm>
hello Luis, we never know why they hide the posts as well. I read yours and I agree with you. we have the same problems as you, others too. do not feel alone.
Luis, are you continuing development with v14.0.6.2, and if so are you now happy with the stability?
I'm pretty sure I can crash WX5 if I torture it too much with header/footer/page structure/large gallery and original size image changes then request a preview before saving if I have large numbers of empty cells on pages which is likely during early development or redevelopment of a site.
Autor
Thanks for the support, it's the first time it happens to me :/
Hi! I just finished a page (2 hours work) without crashes by working slower and leaving no empty cell before every preview, as you posted, the app tends to crash more often when we work fast making changes and previewing often, it's like it somehow chokes when the workflow goes too fast.
I always work with optimized images, fullwidth backgrounds are always no more than 1800px width, and never over 250kb per image and as a rule for all my clients galleries are 30 images max with pictures 800x600 max.
I'll see how it behaves from now on (working slower and leaving no empty cells), but yesterday's crashes were caused just by inserting an object, so I imagine the bug is also caused by some cumulative background process.
I will also try to recreate the crash to see if it's caused by something we can avoid to do.
Love it if you could discover a replicatable event :-)