We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 38813
    • 29 Posts
    Hi,

    I've been playing with MIGX and the "Doodles" tutorial and I'm getting a strange error. Everything seems to go fine until I save the various changes from the MIGX tab and then, when I click the "Done" button, I get the error message "quip.thread_err_save".

    I've tried this on Revo 2.2.0-pl2 and Revo 2.2.6-pl and both are exactly the same... as soon as I hit the final "Done" button, up pops the "quip.thread_err_save".

    I'm running on a Windows server in the office which isn't visible from the Internet. PHP version 5.3.2 and MySQL 5.5.15

    Does anybody have any idea what could be causing the "quip.thread_err_save" error?

    Michael
      • 38813
      • 29 Posts
      Since my original post above, I've also tried a completely clean install of Revo 2.2.6-pl and gone through the Doodles tutorial from scratch. I get exactly the same "quip.thread_err_save" error with the clean install.
        • 28042 ☆ A M B ☆
        • 24,524 Posts
        I fail to see what anything "quip" has to do with whatever you are doing. Unless you've installed Quip or Articles?
          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
          • 38813
          • 29 Posts
          Nope, no Quip or Articles. Clean install and I've never used either anyways. I'm totally stumped.
            • 28042 ☆ A M B ☆
            • 24,524 Posts
            I see several references to quip... error messages in MIGx files. Are these artifacts of the original code?
              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
              • 23018
              • 353 Posts
              Hello michaelc,

              please check if you really have created your custom table. I had the same problem today and in my case the table was not created even though the migx create table tab seemed to do its job.

              I'm working on the problem. If I find out what happened, I'll leave a message.

              You can find a dedicated MIGx forum here: https://forums.modx.com/board/?board=271

              If you post your question there, its very likely bruno17 will notice your post and help you out.

              Regards,

              pepebe [ed. note: pepebe last edited this post 13 years, 8 months ago.]
                Homepage: pepebe.de | MODX snippets (and other stuff) at github: https://gist.github.com/pepebe
                • 4172
                • 5,888 Posts
                I see several references to quip... error messages in MIGx files. Are these artifacts of the original code?

                they are.
                  -------------------------------

                  you can buy me a beer, if you like MIGX

                  http://webcmsolutions.de/migx.html

                  Thanks!
                  • 23018
                  • 353 Posts
                  @michaelc: Check your error log (topmenu -> reports -> errorlog). Most probably you'll find a bunch of errors related to table creation.

                  In my case I suppose this could be related to a malformed xml schema. If I use the original doodles xml, everything works as expected.

                  Did you modify the doodles xms scheme?

                  Regards,

                  pepebe
                    Homepage: pepebe.de | MODX snippets (and other stuff) at github: https://gist.github.com/pepebe
                    • 23018
                    • 353 Posts
                    A malformed XML syntax was the reason for this behaviour.

                    If this is also the same problem for you, check you error log. There should be a message like: You have an error in your sql syntax... near "some sql code" ...

                    In my case I wrote btype="varchar" instead of dbtype="varchar". Stupid...

                    Regards,

                    pepebe.

                    @bruno: The success message after creating the table is misleading. I think it should be something like "Could not create custom table". Check your modx log file for more info.
                      Homepage: pepebe.de | MODX snippets (and other stuff) at github: https://gist.github.com/pepebe
                      • 4172
                      • 5,888 Posts
                      Hi Patrick,

                      @bruno: The success message after creating the table is misleading.


                      I know, all processors in MIGX's package-manager return allways success.
                      Didn't invest efforts into some error-handling here.
                      Perhaps you want to file this as a bug at github
                        -------------------------------

                        you can buy me a beer, if you like MIGX

                        http://webcmsolutions.de/migx.html

                        Thanks!