I'm sad to say that this is my first cmsms bulletin. And it's only because it's late at night and I'm very, very mad.
Has anyone else had this problem: you go to update some content, hit 'apply' and your internet lags, so you get impatient and hit apply a few more times only to find out that half of your content was posted and the other half was lost into an internet black hole?
What happens when you do this and it's your sites stylesheet?
I didn't cry, because it was only about 1/3 of the sheet, but let's just say I have a longer day tomorrow than I would have hoped. I think I'll also start manually saving a backup.
Can anyone else relate?
Thanks to everyone who works so hard on cmsms, it's totally changed my life (and the people who I make sites for).
Don't try updating content with bad internet!!
Re: Don't try updating content with bad internet!!
well, I cant figure out why it happened since MySQL would just update the content in tables after a well execution of the script
Good question, not yet explored by me, does the Apply button trigger some client-side function to update the content?
If not, I just can see a server problem.
Let´s wait the gurus to answer why it happened.
Good question, not yet explored by me, does the Apply button trigger some client-side function to update the content?
If not, I just can see a server problem.
Let´s wait the gurus to answer why it happened.
Re: Don't try updating content with bad internet!!
This is absolutely understandable and I have seen it in many apps - not just CMSMS. Here is the problem. If your internet is slow, your editor may never load the content and when you hit apply, the content field is still empty. Hence the page is submitted again with nothing on it. You may want to verify that the content has loaded in the editor prior to submitting.
Re: Don't try updating content with bad internet!!
Hopefully 2.0 is going to have versionning so at least the version before is a backup of the content.
Pierre M.
Pierre M.
Re: Don't try updating content with bad internet!!
Jack, good point.
So our solution is 1) load page 2) wait 3) edit content 4) click 'apply' 5) wait.
These waiting steps are the key, and I've implemented this workaround.
Shall I post a [solved]?!
c
So our solution is 1) load page 2) wait 3) edit content 4) click 'apply' 5) wait.
These waiting steps are the key, and I've implemented this workaround.
Shall I post a [solved]?!
c