We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 33372
    • 1,611 Posts
    I have posted an update to the bug report on this with a question about the new query syntax, so if it turns out that is related to your issue I’ll post again here soon.
      "Things are not what they appear to be; nor are they otherwise." - Buddha

      "Well, gee, Buddha - that wasn't very helpful..." - ZAP

      Useful MODx links: documentation | wiki | forum guidelines | bugs & requests | info you should include with your post | commercial support options
      • 25663 MODX Staff
      • 12,272 Posts
      What is different about how Quickedit saves TVs and how the manager saves ... seems like we could solve a lot of pain by adopting the QE code... ?
        Ryan Thrash, MODX Co-Founder
        Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
        • 33372
        • 1,611 Posts
        Quote from: rthrash at Dec 19, 2007, 02:18 PM

        What is different about how Quickedit saves TVs and how the manager saves ... seems like we could solve a lot of pain by adopting the QE code... ?
        In 0.9.6.1 there probably isn’t any difference, although I don’t use QE myself so I haven’t looked at its code at all. But the manager used to have a JavaScript check to determine which TVs had been changed when the document was saved, and it was not triggered by the browser entering autotext (so these TVs were not registered as changed by the script, and thus were not saved). But that part of the "dirty document" script is no longer in the current release, so it should no longer be a problem.

        Instead of determining which TVs had been modified client-side using JavaScript, sirlancelot changed that code to use a REPLACE INTO SQL query. So now as I understand it MySQL is determining whether the POSTed TV values are different from the previously saved ones and updating, inserting, or ignoring them accordingly. So to me it seems that if people are still experiencing a problem similar to the autotext issue in older versions then this may have to do with the way that query is being executed on their server, or it might indicate that they didn’t update all of their manager files.

        Some of these people have reported that disabling strict mode fixes the issue, but at least one person (fruitwerks) still seems to have the problem. Fruitwerks did you reupload all of your manager files when you upgraded? I wonder if you might have some legacy files in there, especially given that you started from Etomite and upgraded.

        I’m not confident enough in my understanding of how REPLACE queries are executed to know for sure whether it might be the wrong thing to use in this case. It looks to me as if it might update (= delete and reinsert) a row when only one of the key values is matched instead of both the TV and document ids. It seems as if that would be causing all sorts of havoc for most users if it were the case, however, and so far it seems as if that’s not happening.
          "Things are not what they appear to be; nor are they otherwise." - Buddha

          "Well, gee, Buddha - that wasn't very helpful..." - ZAP

          Useful MODx links: documentation | wiki | forum guidelines | bugs & requests | info you should include with your post | commercial support options
          • 10226
          • 412 Posts
          I am certain I have have no legacy files on there, unless one of the filenames had changed and is still being referenced, not likely. I have upgraded more than once, and I always read the docs.

          Since it is only me that is s till having issues with 0961 - don’t rack your brains too hard, it is a pain sometimes, but I know how to deal with it.
            • 22770
            • 285 Posts
            I can’t find out whether sql strict mode is enabled here or not, but I can say that I’ve experienced the problems I mentioned with both an upgrade from 0.9.6 (where I didn’t delete the files, just overwrote them) and with a clean install of 0.9.6.1
              • 10226
              • 412 Posts
              the only way I know to check for strict mode is to look in phpmyadmin.
                • 25663 MODX Staff
                • 12,272 Posts
                Quote from: PatrickSamphire at Dec 19, 2007, 03:30 PM

                and with a clean install of 0.9.6.1

                Can you give us detailed steps to reproduce the problem with the clean install?
                  Ryan Thrash, MODX Co-Founder
                  Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
                  • 10226
                  • 412 Posts
                  Well in my case, I use Gentoo linux. I posted my versions earlier. I do use friendly urls, name based vhosting in apache. I don’t use anything fancy, just what is needed to make stuff work. I can post compile options if anyone is interested.

                    • 22770
                    • 285 Posts
                    Quote from: rthrash at Dec 19, 2007, 03:56 PM

                    Quote from: PatrickSamphire at Dec 19, 2007, 03:30 PM

                    and with a clean install of 0.9.6.1

                    Can you give us detailed steps to reproduce the problem with the clean install?

                    Ah, hell. Sorry. Not a clean install, after all. Working on too many different sites at the same time. The one I was thinking of was installed as 0.9.6 then upgraded to 0.9.6.1. As far as I can see, I haven’t had any problems with clean installs of 0.9.6.1, only with upgrades.

                    embarrassed
                      • 33372
                      • 1,611 Posts
                      The specific files that changed when sirlancelot fixed the autotext issue are:


                      • manager/actions/mutate_content.dynamic.php
                      • manager/includes/tmplvars.inc.php
                      • manager/processors/save_content.processor.php

                      Can you confirm that the files in the upgrade installation that has this issue are the same as the ones in the fresh installs that don’t?
                        "Things are not what they appear to be; nor are they otherwise." - Buddha

                        "Well, gee, Buddha - that wasn't very helpful..." - ZAP

                        Useful MODx links: documentation | wiki | forum guidelines | bugs & requests | info you should include with your post | commercial support options