We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 16610
    • 634 Posts
    This is an auto-generated topic for QuickManager+ 1.5.5-GA by lammikko.

    Brief Description:

    QuickManager+ enables front-end content editing.
      Mikko Lammi, Owner at Maagit
      • 26931
      • 2,314 Posts
      Hi Mikko,

      thanks for the updated version!
      is there a way to activate "continue editing" a resource for QM?

      thanks, j
        • 16610
        • 634 Posts
        Quote from: sharkbait at Feb 22, 2011, 02:09 AM

        thanks for the updated version!
        is there a way to activate "continue editing" a resource for QM?

        Unfortunately "continue editing" isn’t supported. I’m sure it would be possible to add it as n new configuration option but I have currently no plans to add new features for QM+ as none of my client haven’t needed such feature.
          Mikko Lammi, Owner at Maagit
          • 20927
          • 6 Posts
          MODx version 1.0.3
          Version codename rev 6653
          Database Version 5.0.51a-3ubuntu5.5
          PHP Version PHP Version 5.2.4-2ubuntu5.10
          QuickManager 1.5
          jquery-1.4.2.min.js OR jquery-1.3.2.min.js
          In the QM configuration: Load jQuery in Manager and in the front-end are both true. As is noConfict mode.
          IE 7/8 and Firefox 3

          When I click Save on the edit modal window the modal remains, but it is filled with the home page. The page I was editing is still in the background and when I click on the X in the lower right hand of the modal it closes the modal, but doesn’t display the changes (though refresh does). Closing the modal also messes a little with the styling.

          It shouldn’t matter, but I’m running 3 subdomains in one MODx installation.

          I’ve reinstalled QM twice with the same results. I tried to update MODx, but it thought that the images,files and flash directories were not writable (though they were all set at 777) which is a different issue for a different forum topic.

          I don’t know if it has anything to do with the issue, but in IE I get 2 scripting error messages:
          1) ’top.mainMenu’ is null or not an object index.php?a=27&id=250&quickmanager=1, line 29 character 17
          2) Expected identifier, string or number index.php?a=27&id=250&quickmanager=1, line 955 character 2

          Can you help with my QuickManager issue?
            • 16610
            • 634 Posts
            Quote from: nancyl at May 12, 2011, 01:34 PM

            Can you help with my QuickManager issue?

            Is your QM+ version 1.5 or 1.5.5. If it’s 1.5, I suggest to update and see how it goes. Also I suggest you to update MODX too to version 1.0.5.

            Though I have a feeling this might be some kind of JavaScript conflict as the saving works anyway. Does your template contain JavaScript libraries or any other JavaScript that might conflict with QM+?
              Mikko Lammi, Owner at Maagit
              • 20927
              • 6 Posts
              Oops. Yes, it’s 1.5.5. And I figured it was probably a JS conflict, but I don’t know how to get around it.

              I stripped the template down to bare-bones with no other JS reference. Same results. Once the editor is displayed there are all sorts of references - MooTools and 2 different versions of jQuery . . . all located in /manager/media.

              On a test site I went ahead and updated to MODx 1.0.5. Now when I click on Edit I get a white Modal box with nothing in it. I also get a "jquery is not defined" in Firefox. Before I upgraded I was successfully running MODx 1.0.4 and QM 1.5.0.

              I took it back to QM 1.5.0 and had the same white Modal box.

              I took QM back to 1.3.4.1 and QM works as expected. Except that when I Click on cancel or X I get an extra vertical scroll bar.

              Thanks for your help and in spite of these issues, I love the plugin and use it successfully in several other sites. If only I could figure out what is different.
                • 16610
                • 634 Posts
                Quote from: nancyl at May 13, 2011, 11:18 AM

                I stripped the template down to bare-bones with no other JS reference. Same results. Once the editor is displayed there are all sorts of references - MooTools and 2 different versions of jQuery . . . all located in /manager/media.

                Doublecheck QM+ plugin configuration options:
                - Load jQuery in manager: False (True, if you are not using ManagerManager plugin)
                - Load jQuery in front-end: True (False, if you are loading your own jQuery in your template)
                - jQuery noConflict mode in front-end: False (True, if you are using some other JavaScript libraries in your template)
                - Load modal box in front-end: True (False, if you are already loading the ColorBox library in your template)

                Just to be sure:
                - Clear MODX cache
                - Clear your browser cache
                - Validate your template code as sometimes invalid code can result odd things
                  Mikko Lammi, Owner at Maagit
                  • 20927
                  • 6 Posts
                  Thanks for your quick response. Both HTML and css validate. In fact the The changes you suggested have not helped with any version. But, I’ve obviously got something else screwy going on. I re-installed QM just to be sure.

                  I also tried downgrading to 1.4.1. When I click Save I am taken back to the home page instead of kept on the page that I just edited. Same with 1.3.4.1. But, I can edit and everything else works as expected except on Cancel and X I get the extra vertical scroll bar (no doubt something with css).

                  I also tried 1.5 on the production site and get a normal back-end edit page in the modal window. In other words it displays the Save, close dropdown, Delete, Cancel and Preview buttons and doesn’t close unless I click on the X in the lower right hand corner.

                  On my test site, 1.5.5 still gives me a white modal window. But, I also have over 100 css errors on the test site.

                  I’m fairly certain these are not issues with QM, but some other issue with JS. I will keep digging and let you know what I find out.

                  Thanks again for taking the time to help.

                    • 16610
                    • 634 Posts
                    Quote from: nancyl at May 16, 2011, 10:56 AM

                    I’m fairly certain these are not issues with QM, but some other issue with JS. I will keep digging and let you know what I find out.

                    One more question: What version of jQuery library you are using?
                      Mikko Lammi, Owner at Maagit
                      • 20927
                      • 6 Posts
                      I have tried both jquery-1.4.2.min.js and jquery-1.3.2.min.js.