We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 34162
    • 1 Posts
    This is an auto-generated support/comment thread for <a href="http://modxcms.com/extras/package/541">QuickManager+ 1.3--</a>.

    Use this forum to post any comments about this addition or any questions you have regarding its use.

    Brief Description:
    QuickManager+ is an alternative to QuickEdit to quick access and control content from frontend.
      • 34162
      • 1 Posts
      This is an auto-generated support/comment thread for <a href="http://modxcms.com/extras/package/541">QuickManager+ 1.3--</a>.

      Use this forum to post any comments about this addition or any questions you have regarding its use.

      Brief Description:
      QuickManager+ is an alternative to QuickEdit to quick access and control content from frontend.
        • 25663 MODX Staff
        • 12,272 Posts
        Thanks for the update Lammikko. Can you go over what updates have been made to this since Evo 1.0’s frankenversion was included? Thanks! (Ideally, we’d get them in sync for the next release.)
          Ryan Thrash, MODX Co-Founder
          Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
          • 16610
          • 634 Posts
          QuickManager+ v1.3.1 updates since version v.1.1.1 (bundled with Evolution 1.0.0):

          1.3.1

          * Added: It’s now possible to change template once. After that you can’t change the template again but of course you can press cancel button and try again.
          Note: ToDo: Investigate if there is a way to detect parent frame in PHP to solve this problem

          1.3

          * Added: Support for MODx Evolution 1.0.0 version, better combatibility with MODx Carbon manager theme
          * Added: Support for jQuery in noConflict mode by default
          * Added: ColorBox modal box support
          * Added: Modal box (ColorBox) window width
          * Added: Modal box (ColorBox) window height
          * Added: Possibility to add custom link buttons
          * Removed: Thickbox window max width
          * Removed: MODx versions below 1.0.0 are not supported due manager interface changes
          * Removed: ThickBox modal box support

          1.2

          * Added: Plugin disabled option
          * Added: Show go to manager button option
          * Added: Custom add buttons option
          * Added: Hide document sections from front-end editors option
          * Added: Hide document tabs from front-end editors option
          * Added: Dynamic ThickBox windows size adjustement, window size is calculated without refreshing the window
          * Added: ThickBox window max width option
          * Added: Logout to configuration option added, needs event OnManagerLogout
          * Fixed: Documentation changed to html file
          * Fixed: Clearer plugin folder structure
          * Fixed: Hiding templates if only one template
          * Fixed: Load jQuery in front-end was not working properly
          * Fixed: mcc.class.php => hideTab & hideSection
          * Removed: ThickBox windows width and height options removed.

          To sum up, v1.3.1 is very similar compared to v1.1.1 (bundled version). Biggest difference is many new configuration options. But other than that they look and function in a same way.
            Mikko Lammi, Owner at Maagit
            • 16610
            • 634 Posts
            Next minor release (1.3.2) will contain at least one new configuration option to handle better different jQuery noConflict situations. Read more: http://modxcms.com/forums/index.php/topic,33530.msg232064.html#msg232064

            For version 1.4, I hope there will be new ways to handle Ditto listings from front-end. This will require some regular expression solutions that I haven’t compleatly solved yet.
              Mikko Lammi, Owner at Maagit
              • 22770
              • 285 Posts
              Fantastic work! Thank you. smiley
                • 2297
                • 31 Posts
                The "readme.txt" file says:

                Installation
                1. Extract all files from package to site root.

                The directories created when the zip file is extracted are
                assets / js
                assets / plugins


                I wonder if I’m not reading this correctly. But won’t extracting to the site root overwrite the entire current assets directory? And the current js and plugins directories?


                  • 2297
                  • 31 Posts
                  Cross-post from the Evo 1.0 board because I figure I’ll be advised to post this question here anyway smiley



                  I can’t get TinyMCE to work in QuickManager. It shows up in the Manager, but it doesn’t show up in the QuickManager. The option for TinyMCE is there, but nothing happens when it’s selected. The content editing window is the same as it is when "None" is selected, which is just plain HTML.

                  What’ve I missed? smiley

                  **On edit: I upgraded to QuickManager 1.3.1 in hopes that would sort it, but the TinyMCE editor is still not showing up in QuickManager.

                  I have looked in the support thread for QuickManager (both versions) and for TinyMCE, but have been unable to find anything about this. I would be very, very grateful if someone could point me in the right direction finding a way to solve this.

                  Really beginning to wish I hadn’t upgraded from 9.6.3 now. Having a controllable RTE for web users was *the* selling point for doing the site I’m doing now in MODx. If this isn’t a fixable problem, it’s a show-stopper. If that’s the case, is there a way to revert back to 0.9.6.3?
                    • 5340
                    • 1,624 Posts
                    I suspect a javascript conflict.
                    Any javascript errors in Firebug?
                      • 16610
                      • 634 Posts
                      Quote from: AspenDew at Aug 11, 2009, 01:09 PM

                      I wonder if I’m not reading this correctly. But won’t extracting to the site root overwrite the entire current assets directory? And the current js and plugins directories?

                      No it won’t. It just overwrites folders and files that exist (in this case QuickManager+ related folders and files). Any other folders or files in assests folder will remain untouched. Try yourself to see how it goes.
                        Mikko Lammi, Owner at Maagit