We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 32046
    • 75 Posts
    Is there any way to specify a TV value for a new resource directly from QM. For example, depending on which page the user is on when selecting "Create Resource Here" could we somehow pass a var in the query string QM uses such as:
    www.domain.com/index.html?pid=11&quickmanager=1&template=products - if creating the resource from a products page
    or
    www.domain.com/index.html?pid=12&quickmanager=1&template=productCatagories - if creating the resource from a product catagories page
    to preset the TV fields.

    Thanks

      • 28042 ☆ A M B ☆
      • 24,524 Posts
      I have done something similar, but we used PubKitBlog for it, and added a menu item to the QM menu for the page with PKB.
        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
        Quote from: wdnz at May 12, 2010, 12:19 AM

        Is there any way to specify a TV value for a new resource directly from QM. For example, depending on which page the user is on when selecting "Create Resource Here" could we somehow pass a var in the query string QM uses such as:
        www.domain.com/index.html?pid=11&quickmanager=1&template=products - if creating the resource from a products page
        or
        www.domain.com/index.html?pid=12&quickmanager=1&template=productCatagories - if creating the resource from a product catagories page
        to preset the TV fields.

        You can do this but you will need separate templates so this may not be an optimal solution:
        - Template with empty TVs
        - Same template with predefined TV values

        Look more info at QM+ docs:
        http://www.maagit.fi/files/qm-plus-1341/readme.html

        Check especially "New document template type". With "Selected" setting and "inhertTpl" TV you can inherit any template you want.
          Mikko Lammi, Owner at Maagit
          • 36805
          • 354 Posts
          Since it is so easy to add QM+ buttons for adding a document with preselected template i started using it a lot like for example:
          <!-- qm-new [*id*] 8 'Add Article' -->
          <!-- qm-new [*id*] 5 'Add Regular Page' -->

          This is a lot more intuitive then the general add resource which always opens with the default template.

          Now it would be a cool feature if I could style the buttons individually. Currently i can rename the css class qm-new to something else by the plugin configuration. However it uses the same class for every button. Consider the 2 buttons above, it would be cool to use different colors or add a different icon to either of them.

          An ideal solution would be to have a command like
          <!-- qm-new qm-add-article [*id*] 8 'Add Article' -->
          <!-- qm-new qm-add-page [*id*] 8 'Add Page' -->

          Where qm-new is the action that is used and qm-add-article the css class. Currently both action and style class use the same name.

          Please consider this a feature request, not criticism. Its already a really cool plugin as it is!
            • 16610
            • 634 Posts
            Quote from: MrDutchy at Jan 17, 2011, 06:03 AM

            Please consider this a feature request, not criticism. Its already a really cool plugin as it is!

            Great feature request! I’ll add it todo list.
              Mikko Lammi, Owner at Maagit
              • 36805
              • 354 Posts
              When using in Firefox with Firebug enabled the modal box will not stop loading and FB will show: parent.mainMenu is undefined
              Note sure why or how but this issue disappeared huh
                • 16610
                • 634 Posts
                Quote from: MrDutchy at Jan 18, 2011, 06:20 AM

                When using in Firefox with Firebug enabled the modal box will not stop loading and FB will show: parent.mainMenu is undefined
                Note sure why or how but this issue disappeared huh

                I have definitely experienced this issue too. It has something to do with the fact that QM+ uses default MODx manager frame but misses the other two manager frames (topmenu and site tree). If I guess right this error is there after saving the resource in QM+ because after saving QM+ tries to unlock the resource by calling the main MODx manager from JS / Ajax call.

                I’m just guessing here, if someone has investigated this further I would be happy to hear more about it (and possibly apply a fix).
                  Mikko Lammi, Owner at Maagit
                  • 16610
                  • 634 Posts
                  Quote from: Andchir at Jan 30, 2011, 08:52 AM

                  Quick Manager wrong load jQuery.
                  http://bugs.modx.com/issues/3695

                  Thanks! I’ll check this soon and hopefully release a new fixed version.
                    Mikko Lammi, Owner at Maagit
                    • 26931
                    • 2,314 Posts
                    Hi there,

                    - Quick Question -

                    why does/would QM need to load jQuery in the manager? "Load jQuery in manager - true/false"

                    thanks,j
                      • 16610
                      • 634 Posts
                      Quote from: sharkbait at Feb 04, 2011, 12:49 PM

                      why does/would QM need to load jQuery in the manager? "Load jQuery in manager - true/false"

                      QM+ needs jQuery to work. I you are not using e.g. ManagerManager plugin that already loads jQuery you have to load jQuery for QM+.
                        Mikko Lammi, Owner at Maagit