Support/Comments for Qm (QuickManager)

Quote from: 0x7B at Feb 26, 2009, 05:23 AM

strange. qm works well with local jquery and managermanager.
modx 0963 , FF3 , managermanager 0.3
although jquery gets loaded twice.

That’s strange. I have a default modx 0.9.6.3 install with ManagerManager and Qm. If both are loaded Qm disables all document settings tabs and shows content field which is supposed to be disabled by ManagerManager. All template variables work in the right way though.

Qm is a real diamond but has couple rough edges. This is my approach to improve Qm: http://modxcms.com/forums/index.php/topic,33530.0.html

Quote from: Lammikko at Mar 02, 2009, 04:41 AM

Qm is a real diamond but has couple rough edges. This is my approach to improve Qm: http://modxcms.com/forums/index.php/topic,33530.0.html

1. Thanks for ideas!

2. ThickBox is Good Idea!
3. Fixed must work in all browsers (fixed.htc included in package)
4. Enhances not disabled by default. They work BUT NOT FOR ADMINS (to test it you need to create new role and new user)!
To use enhances you need to insert special string in template description (not described in help).

To test more Qm functions (works where logged in user’s role is not Administrators!) You can do:

1. To set children template for some template just add to parent template’s description: {children=`10`}
Here 10 is ID of child template,  you can use 10,11,12 to set few children templates. In manager template field will shown just children templates!

2. To switch QM mode for template add to template description string: {class=`unit`}
You can use three modes: unit (for object edition), doc (for documents) and set (for folders - parent of document/object set).
Every mode hides some tabs/fields (like ManagerManager for example).

This functions work for all users with role>1 (not admins)
To see this functionality you need to:
1. Create new role (manager for example) and create user with this role.
2. Login with this user and look how it work.

Examples for template descriptions:
House - {class=`unit` table=`realty` pagetitle=`%floors%-stage house`}
here table is name of shadow table for Quid, %floors% is TV floors that is used to autodesign Pagetitle.

Houses - {class=`set` alias=`houses` children=`17,21`}

This functionality is just experimental!

Lammikko, can I use your QM+ ideas/code in QM?

Sorry 4 english, I’m learning for...

Quote from: Urique at Mar 02, 2009, 05:04 AM

1. Thanks for ideas!

You are welcome  I divided my version of Qm from original Qm because I hope when Qm evolves I don’t need my own version anymore. Two slightly different versions are not really needed, but I’m in a hurry with my current project so I needed something quickly.

Quote from: Urique at Mar 02, 2009, 05:04 AM

4. Enhances not disabled by default. They work BUT NOT FOR ADMINS (to test it you need to create new role and new user)!
To use enhances you need to insert special string in template description (not described in help).

Great! This is the way to go.

And thank you very much for the additional information about Qm functions.

Quote from: Urique at Mar 02, 2009, 05:04 AM

Lammikko, can I use your QM+ ideas/code in QM?

Absolutely yes!

This is looking very good. As you say the QuickEdit is a little outdated

I would love a replacement for QuickEdit for Evo 1.0. This looks really promising.

Couldn’t quite figure out the install instructions. (Yeh, I know don’t say it.)

But where exactly do I put everything?

The Read Me file says put everything in the root, but the unzipped folder shows a folder structure of two under assets.

eg assets/js

and

assets/plugins/qm.

Do I follow this structure or do what the Read Me says and takle everything out of these folders and put them all in the root?


Thanks

Put assets in the root - it should merge itself with the existing assets folder.


-- Tim.

Tim,

if I try that I get a message saying everything in my current assets folder will be deleted and replaced with the new one.

Obviously that’s not right.

That behavior depends on your server type. OS X will also do that. So just upload the qm folder into your assets/plugins folder.