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

Support/Comments for QuickManager+ 1.5.3-GA

    • 16610
    • 634 Posts
    Lammikko Reply #1, 15 years, 11 months ago
    This is an auto-generated topic for QuickManager+ 1.5.3-GA by lammikko.

    Brief Description:

    QuickManager+ enables front-end content editing.
      Mikko Lammi, Owner at Maagit
      • 18367
      • 834 Posts
      MarkG Reply #2, 15 years, 11 months ago
      As i understand it Quick Manger is preinstalled with Modx evo.

      As such there’s nothing to see in the backend.

      IS there someway I can prevent a frontend user from accessing the backend manager via the toolbar?

      Hope that makes sense.

      Thanks
        Content Creator and Copywriter
        • 28042 ☆ A M B ☆
        • 24,524 Posts
        sottwell Reply #3, 15 years, 11 months ago
        Yes, it makes perfect sense wink

        Go to the QuickManager plugin (Elements -> Manage elements, the Plugins tab) and check out its Configuration tab. You can disable existing menu items or add custom items to the menu bar there.

        You can prevent a manager user from accessing the manager at all in his User tab (Security -> Manager Users), the Manager Interface Access radio options for yes/no.

        While QM is part of the default Evo installation, it’s just a plugin and can be omitted during installation if preferred. It’s by no means part of the Evo core.
          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
          • 18367
          • 834 Posts
          MarkG Reply #4, 15 years, 11 months ago
          Thanks Susan,

          that did the trick.

          In the meantime I’d tried bulk setting document permissions and user groups in the Doc manager and got into all sorts of trouble with the dreaded "ERROR Too many forward attempts"

          Yikes. Keeps you on your toes.

          All sorted now though.

          I also discovered the other way you mentioned about disabling the access in the user manager security tab. But that just prevented her from editing anything.

          It’s been an interesting evening.

          Thanks again.

          grin
            Content Creator and Copywriter
            • 26931
            • 2,314 Posts
            anonymized-26931 Reply #5, 15 years, 11 months ago
            You can prevent a manager user from accessing the manager at all in his User tab (Security -> Manager Users), the Manager Interface Access radio options for yes/no.
            I also discovered the other way you mentioned about disabling the access in the user manager security tab. But that just prevented her from editing anything.
            yes, i’m experiencing the same ...can’t edit if "Manager Interface Acces"-Radio button is set to "no"
              • 16610
              • 634 Posts
              Lammikko Reply #6, 15 years, 11 months ago
              Quote from: sharkbait at Oct 13, 2010, 08:28 AM

              You can prevent a manager user from accessing the manager at all in his User tab (Security -> Manager Users), the Manager Interface Access radio options for yes/no.
              I also discovered the other way you mentioned about disabling the access in the user manager security tab. But that just prevented her from editing anything.
              yes, i’m experiencing the same ...can’t edit if "Manager Interface Acces"-Radio button is set to "no"

              QM+ uses the same manager frame as the real manager. Setting this to no will prevent QM+ to work at all.

              I think you could also write a little plugin (OnManagerInit event) to disallow real manager access and work only on front-end.
                Mikko Lammi, Owner at Maagit
                • 26931
                • 2,314 Posts
                anonymized-26931 Reply #7, 15 years, 11 months ago
                thanks Lammikko,

                You can prevent a manager user from accessing the manager at all in his User tab (Security -> Manager Users), the Manager Interface Access radio options for yes/no.
                ... any ideas what that setting is actually intendet for? i mean, why creating a manager user, when he shouldn’t access the manager? (okay, maybe you want to block him for a while, but there’s already another option "Blocked")
                  • 28042 ☆ A M B ☆
                  • 24,524 Posts
                  sottwell Reply #8, 15 years, 11 months ago
                  It’s supposed to allow front-end management access; I believe it worked fine with the old QuickEdit front-end editing system. QuickManager is quite a bit different.
                    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
                    • 16610
                    • 634 Posts
                    Lammikko Reply #9, 15 years, 11 months ago
                    Quote from: sottwell at Oct 13, 2010, 04:44 PM

                    It’s supposed to allow front-end management access; I believe it worked fine with the old QuickEdit front-end editing system. QuickManager is quite a bit different.

                    I just tested this with the old QuickEdit and it doesn’t work either.
                      Mikko Lammi, Owner at Maagit
                      • 36805
                      • 354 Posts
                      MrDutchy Reply #10, 15 years, 9 months ago
                      Upgrading the QuickManager+ that comes with 1.0.4. to the current repository version (1.5.3-GA) breaks your site’s frontend.

                      If logged in to the manager everything shows in front or backend. If not, you get only this:

                      « MODx Parse Error »

MODx encountered the following error while attempting to parse the requested resource:
« Execution of a query to the database failed - You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1 »
      SQL: SELECT setting_name, setting_value FROM `cits_modxdb`.`modx_user_settings` WHERE setting_name='manager_language' AND user= 
      [Copy SQL to ClipBoard]
 
Parser timing
  MySQL:	0.0022 s	(15 Requests)
  PHP:	0.0424 s	 
  Total:	0.0446 s

                      If you experience this problem download evo 1.0.4. and reupload/overwrite the folder assets\plugins\qm\

                      EDIT: One more problem I’ve been experiencing that it refuses to play well with jquery 1.4.4 .. for me it would not show the modal box.