We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
MODX Community Forums Archive

QuickEdit MooTools 1.2.1 compliant

    • 8522
    • 145 Posts
    eerne Reply #1, 17 years, 10 months ago
    Hi
    Attached is an attempt to make QuickEdit MooTools 1.2.1 compliant. You will have to include the mt-1.2 scripts in the template yourself for now.

    Tested on OSX/FF3:

    • drag working
    • checkboxes working
    • menu can be opened and closed

    Known Bugs:

    • the same menu can’t be opened after closing. it works only if you opened an other item between.

    Dependencies
    MooTools 1.2.1 core and 1.2 More (Drag)
      • 34001
      • 428 Posts
      Jean-Christophe B. Reply #2, 17 years, 10 months ago
      Ohhh... great ! smiley

      It’s exactly what i was looking for. I will try it ASAP.

      Thanks !
        Intégrateur web freelance
        • 25663 MODX Staff
        • 12,272 Posts
        Ryan Thrash Reply #3, 17 years, 10 months ago
        Thanks eerne. smiley
          Ryan Thrash, MODX Co-Founder
          Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
          • 13428 ☆ A M B ☆
          • 1,031 Posts
          Jako Reply #4, 17 years, 6 months ago
          Quickedit seems to use more than only ’1.2 More (Drag)’. With all things activated in the More-Builder it is possible to use that patch.
            • 17883
            • 1,039 Posts
            MadeMyDay Reply #5, 17 years, 5 months ago
            You will have to include the mt-1.2 scripts in the template yourself for now.

            Or put their call in line 223 of output.class.inc:


            <!-- Start QuickEdit headers -->
<script type="text/javascript" src="{$site_url}manager/media/script/mootools/mootools-1.2.1.js"></script>
<script type="text/javascript" src="{$site_url}manager/media/script/mootools/mootools-1.2-more.js"></script>



              MODx deutsch | Webdesign Karlsruhe | Ressourcen für Webdesign
              • 36693
              • 66 Posts
              kurucu Reply #6, 17 years, 5 months ago
              With respect to this, I use mootools in my client side as well as manager. Is it good to reference the manager script, or use a common one for both?
                • 17883
                • 1,039 Posts
                MadeMyDay Reply #7, 17 years, 5 months ago
                With respect to this, I use mootools in my client side as well as manager. Is it good to reference the manager script, or use a common one for both?

                The manager doesnt run with mootools 1.2 atm (see my request in Jira), so I would include the new one in the frontend and leave the backend as it is. Since QE is only loaded in the frontend, there should be no problem.
                  MODx deutsch | Webdesign Karlsruhe | Ressourcen für Webdesign
                  • 36693
                  • 66 Posts
                  kurucu Reply #8, 17 years, 5 months ago
                  Ah yes, I knew that.

                  I guess the surprise comes from the fact that QE runs on the client pages, and yet uses the manager script, taking away freedom on the client side (unless hacking such as that done in this thread is performed).

                  This made me think about how I actually tackled this situation, and I did exactly as you suggest.
                    • 26978
                    • 4 Posts
                    sheeplover Reply #9, 17 years, 4 months ago
                    Installing mootools 1.2.1 disables the document tree in the manager. Any ideas on that? huh

                    --
                    sheep