I cannot reproduce any of this unwanted behavior in 2.2.11-pl. Please provide specific browser/OS details and MAKE SURE your browser cache has been cleared of javascript from before upgrading to 2.2.11-pl.
Firefox (FF 26/OSX 10.8.5). Browser cache cleared several times. Using Web Developer toolkit, what should I look for in the .js file to see if it's using the new file or the old one?
Can someone create a bug report for the issue related to changing the template? That's a definite bug and sounds plausible knowing the code that checks for changes. I can't reproduce it in Chrome but someone mentioned it was a firefox-only bug?
For clarification:
Revo 2.2.10 + Chrome latest: bug that was resolved in 2.2.11 which because of this line in the core js:
e.browserEvent.returnValue = '';
was occurring on EVERY page change.
Revo 2.2.11: bug with chrome fixed. New intentional warning only when there are any unsaved changes on the resource update panel. If it's occurring in any other cases (such as the template page reload) that is a bug or cached javascript.
Chrome and Safari are fine. It's happening in FF, latest version (26 I think).
-
- 46 Posts
Oh screw it... I give up. I just updated one of the modxCloud installations to 2.2.11 and there is no such problem... any advice what is wrong with the installation on my end?
And yes, same browser, same OS. My server gives the "stay on the page/leave now" on almost any link, while on the modxCloud everything works like it should...
Sumoborac
I have not been able to identify the source of the problem yet. I have experienced it in some situations and not in others.
Because this problem is showing up in too many environments, in addition to some issues with the phpthumb library upgrade, I'm likely going to revert this change (or make it optional if possible) and put up another patch release for 2.2.x until a more agreeable solution can be found.
I recall when this happened in Revo if one had an image TV and the preview thumbnail plugin was used. Since the plugin loaded the thumbnail after the form was complete, it was triggering the "something changed" warning. This makes me suspect that something similar is happening here, one of the multitude of AJAX requests going on in the background is happening after the function that flags changes. Perhaps something to do with TVs? On fresh installs, I only get it when changing the template. On installations where I have other add-ons, TVs, etc. it pops up on just about everything.