Problems, need help? Have a tip or advice? Post it here.
14 posts Page 1 of 2
Hey,

Not sure if this really is a bug, but every time I'm wanting to navigate in the admin panel to a different page template, chrome will ask I want to leave with a popup. I hadn't made any changes to the page I was on but still it happened.

Is this a Couch issue with regards to moving away from unsaved changes (even though i didn't have any)?

Edit: Also have another issue with image uploads, upon page save it'll display a blank white page and won't actually save the image in the defined editable region.
Hi,

The 'unsaved content' message should ideally appear only when there indeed is some unsaved content.

Are you getting the false alarm only on one of your templates or is it happening with all the sections of the admin-panel? If it is only the former, please PM me the template in question and I'll try to see if I can duplicate the issue.

Regarding the 'white-out', it is most likely an insufficient memory issue (which runs out while processing the uploaded image). Please try searching this forum and you'll come across several threads discussing the solution.
I have also had this issue with 2.0 where I get false warnings when I haven't edited anything. I haven't been able to discern any pattern, it just seems to crop up at random. Wouldn't know how to intentionally reproduce it.
I can only conceive of this being the result of the richtext editors (CKEditor/NicEdit) transforming the existing values. One possible avenue of investigation includes saving a page in one browser, and then opening it to edit in another. There may be instances as well where updates to CKEditor are included in a Couch release (think v2.0) that results in a change in markup parsing.

Nevertheless, I haven't personally run into this issue before...
Thanks, @cheesypoof. I don't have anything new to add to that, except that I'm pretty sure that when this has happened to me, there have been richtext regions involved. So I think you're on the right track.

In regards to warnings about losing data, I wonder if you managed to address any of the other potential pitfalls. I ask because a couple of times now, I've hit the save button only to be redirected to the login page. I guess my session ended. I know there was a plan to address these kinds of data losses, but it doesn't seem to be working yet in v2.0, at least for me.
@tim
I ask because a couple of times now, I've hit the save button only to be redirected to the login page. I guess my session ended. I know there was a plan to address these kinds of data losses, but it doesn't seem to be working yet in v2.0, at least for me.
The last time this issue was discussed on the forum, in response to those discussions the session timeout duration was increased from 12 hours to *at least* 24 hours (max is 36 hours) - which means, theoretically, that if one opens up an edit screen and then keeps working on the same screen for 24 hours, a save done when that period has passed could result in a session expire notice (this period could stretch to 36 hours).

I don't suppose that is a very practical scenario and your case is a result of this (yours is the first instance of someone reporting this phenomenon since we made the mentioned change).

There has to be some other reason at play. Perhaps the 'unsaved' message is also linked to it.

Do you see this happen only after upgrading to v2.0 or did you come across it even in 1.4.7?
I will try to give as thorough an account of the circumstances as I can.

This is a website that has been managed by Couch for several years. I recently updated to v2.0 from the zip file on the forum. I don't remember any specific incidents where this happened previously, but I think I may have experienced it at some point in the past. Maybe. It certainly hasn't been a common issue. I'm sorry I don't have a clear answer to your query, but I don't want to pretend to be confident and end up giving false information.

I have been adding a lot of new data to the site over the past several weeks. I'll add data and update pages, then save them. At the end of a work session, I close all of the browser tabs and windows, but I generally don't quit the browser. It stays awake in the background, but closed.

The next day when I go back to work on the site, I open up the admin panel in a new window, and a lot of the times I'm still logged in. I go to work adding, updating, and saving. But a couple of times, without warning, instead of saving, the admin panel has redirected to the login. The data I was saving is gone.

It hasn't been a big deal because I save often, but it happens unexpectedly and without any warning. Anyway, this sort of sudden irretrievable loss of data doesn't seem like the correct behavior in this circumstance.
For what it's worth, I am currently looking to integrate Sisyphus.js to end the potential for data loss (barring failure of your local computer storage). The difficulty is with handling dynamic fields like repeatable regions, as well as providing an interface so the user knows when data is restored (and offer the ability to clear the client-side draft).
Great find, @cheesypoof! Sisyphus certainly deserves a closer look.
Perhaps that is the solution we have been looking for.
I don't know if this is related, but if you create an editable region in a template with content in it, every time you leave the page on the admin panel it will ask you to save the data until you do.
14 posts Page 1 of 2