New Community Forums are coming. Watch this space for news.
Subscribe: RSS
  • Quote from: opengeek at Jan 24, 2014, 07:16 AM
    Quote from: sottwell at Jan 23, 2014, 09:00 PM
    A bit awkardly; you get the message when you change the template and the page refreshes.
    You mean if you change the Template, page refreshes, and you try to navigate away from the page without saving the change? That is the intention. How is that awkward?
    Actually no. When you change the template, MODx will do the auto-refresh to the new URL and voila - the message is shown. So no, in the auto-refresh to the new URL I'll get the error. Printscreen included. I checked and I have the 2.2.11 version, I just set it up on the server for the client and we are reciving this error. I've copied it on my own server which is already running few different MODx versions (2.1, 2.2.8, 2.2.10) and no other is showing this problem.

    It is also shown when you create a new resource and you save it - the MODx will do the redirect to the new URL and again - the message. IT IS annoying!

    Sumoborac
    • 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?
          Studying MODX in the desert - http://sottwell.com
          Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
          Join the Slack Community - http://modx.org
        • A user keeps telling me that he gets the mentoined warning. I don't beleve that this comes from the Manager but I don't have any proof for that. Therefor I am here to ask the pros wink -> Is this Message from the Manager? -> If so, how can I disable it?

          If the Message is not from the Manager, It would be nice to get some suggestions to solve this Problem.

          Thanks already to everyone smiley


          WTF???? I guess MODx is breaking all around me... I just posted totally different post and this is what was posted. HA?

          So my original post:
          Cache cleared, from printscreen you can see status 200 on all the files from firebug.
          Browser: Firefox 26
          OS: Win 8.1 & Win 7
          Servers: Ubuntu + LAMP & Centos6 + Plesk with LAMP

          Sumoborac

          And files are not attaching.

          3rd edit... 3rd time is the charm? [ed. note: sumoborac last edited this post 5 years, 1 month ago.]
          • 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.
              Mark Hamstra • Developer spending his days working on Premium Extras and a MODX Site Dashboard with the ability to remotely upgrade MODX and extras to make the MODX world a little better.

              Tweet me @mark_hamstra, check my infrequent blog at markhamstra.com, my slightly more frequent ramblings at MODX.today or see code at Github.
            • Chrome and Safari are fine. It's happening in FF, latest version (26 I think).
                Studying MODX in the desert - http://sottwell.com
                Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
                Join the Slack Community - http://modx.org
              • Quote from: markh at Jan 24, 2014, 03:00 PM
                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.

                So far, I can get the bug replicated in 2 ways: 1. Create a new resource, enter the title & alias and click save. When page starts to reload the firefox asks "Stay on the page / Leave page".
                When I save any resource (dirty=false, save button is disabled, content saved) and I wish to move to another resource I get the "Stay on the page/ Leave page" box from firefox.
                • 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.
                        Studying MODX in the desert - http://sottwell.com
                        Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
                        Join the Slack Community - http://modx.org