TOPIC:

I get an error when I do the following

1. Click on Edit this page
2. In the Editor window, click on Source
3. Do NOT make any changes, just hit Close
4. You get a warning message, saying that there are unsaved changes. The entire editor window with the source code is highlighted in Yellow. Hit Yes, No, or Cancel.

5. I hit Yes but get the error shown in the attached window.
5a. If I hit No, then there is no error obviously.

Browser: Safari 7.1 on Mac OS X 10.9.5

Similar to the error reported here: support.toastmastersclubs.org/5-support-...-data-transfer-error

Yeah... that is the change detection code with the yellow... Kind of work in progress.

I thought I had it working correctly for the web pages, but it looks like it may need another pass.

Ok, I did another pass on the webpage javascript. Tightened up the sequencing a bit for the data transfers that occur and generally took a look at what could maybe go amiss.

I am also forcing the editor view to be wysiwyg when you close the dialog and the change detection occurs. The reason is that the browser sees what is in the source view as being different than the equivalent stored version of that HTML. That is not a but, it is because the browser has to basically to specially encode the underlying HTML for human reading ... The encoding basically kills the normal browser interpretation of the HTML so that it is readable in the browser. However, the encoding basically makes the encoded text (in Source View) register as a "change" from the perspective of the change detection code. That is why it gets flagged as a change.

By me forcing it back to wysiwyg on close, it should not get flagged.

Steve -- not sure if you have applied this fix yet. I still get the error. Thanks.

Did you click the reload to ensure that the new code is loaded.

Yes, I did.

Did you try it switching back to wysisyg before saving?

Brian wrote:

Did you try it switching back to wysisyg before saving?

If I switch it to source and then back to wysiwig without making any changes, then none are detected when Clicking Close. In that case, there is no problem. This is certainly the workaround. But from Steve's earlier post, it looked like the aim was to force the editor/javascript to convert to wysiwig before saving.

Ok, I made a few more changes.

I do not use Safari, which is what I understand this is related to. (I could load it if I have to.)

Could you please check a few things for me?

1. First, click the reload link at the bottom of your website.

2. If you load a web page, then add a letter somewhere (e.g., the web page description), then click close (abandon the change)...
___a. Do you get the Unsaved Changes prompt?
___b. If you click Save in the prompt, what happens? (NOTE: I am checking if you have a problem with regular unsaved changes.)

3. I increased the delay on the dialog close after the forced save by the Unsaved Changes prompt. Can you see if this makes a difference?

Again, keep in mind that the Change Detection is work in progress. I do not claim that it will work properly yet... There are just too many user configurations and internal code variables to have it all sorted out just yet. It is going to take some time to get it all sorted out. The forced save is something that I am actually surprised that works at all--my original plan was just to abort the dialog close and make the user click the regular save button. I am just trying to save a mouse click for the user this way.

SteveTheTechie wrote:

Ok, I made a few more changes.

I do not use Safari, which is what I understand this is related to. (I could load it if I have to.)

Could you please check a few things for me?

1. First, click the reload link at the bottom of your website.

2. If you load a web page, then add a letter somewhere (e.g., the web page description), then click close (abandon the change)...
___a. Do you get the Unsaved Changes prompt?
___b. If you click Save in the prompt, what happens? (NOTE: I am checking if you have a problem with regular unsaved changes.)

3. I increased the delay on the dialog close after the forced save by the Unsaved Changes prompt. Can you see if this makes a difference?

Again, keep in mind that the Change Detection is work in progress. I do not claim that it will work properly yet... There are just too many user configurations and internal code variables to have it all sorted out just yet. It is going to take some time to get it all sorted out. The forced save is something that I am actually surprised that works at all--my original plan was just to abort the dialog close and make the user click the regular save button. I am just trying to save a mouse click for the user this way.

There is no prompt when I make a change and Close without Saving. It does not appear to detect the change. It does not Save the changes. This is in wysiwig.

It depends on where you make the change.

The editor change detection is dicey. Not my editor... I have to figure out how to detect changes in the editor. Again, one of the reasons I have a big disclaimer on the change detection.

If you make a change somewhere other than in the editor and abandon, do you get the change detection prompt?