Support/Comments for QuickManager+ 1.3--

Quote from: Lammikko at Nov 20, 2009, 06:34 AM

Unfortunately there’s no easy solution around this. I’ll add this to todo list.

I’ll have to investigate if this could be solved with ColorBox bindings by triggering something that removes document lock when user hits the close button.

Thanks again for the responses.

One another note it would be really nice to be able to add a checkbox tv I can set up for documents that when ticked would remove the "Create Resource Here" button - what do you think. Should just need a check in the initial plugin call to check for the presence of a tv and override the $addbutton value?

This would be in preference to using a custom button as it could still make use of the "inheritTpl" functionality used by the "Create Resource Here" button when needed.

Quote from: uxello at Nov 20, 2009, 06:52 AM

One another note it would be really nice to be able to add a checkbox tv I can set up for documents that when ticked would remove the "Create Resource Here" button - what do you think. Should just need a check in the initial plugin call to check for the presence of a tv and override the $addbutton value?

This would be in preference to using a custom button as it could still make use of the "inheritTpl" functionality used by the "Create Resource Here" button when needed.

It’s definitely a good idea and I’ll add it to todo list too. Thanks!

But there’s no guarantee if or when this is going to be implemented. I would really love add more features to QM+ but right now I simply don’t have enough time.

... thinking further it would be even more useful to have the tv as a text entry and have similar logic to the "inheritTpl" tv in that you could specify for example "1,1,0" on a doc and QM+ would show the "Create Resource Here" for the first 2 levels but not the third, also still honouring permissions too of course.

I suppose bottom line is MODx has no inbuilt way to prevent creating of a child document for a particular document or template. If so QM+ could just hook into that.

Appreciated that folk only have so many hours in the day!

Hi uxello,

Have a look at my signature: Template Rules. Does exactly what you need and works with QM

Quote from: cipa at Nov 20, 2009, 08:25 AM

Hi uxello,

Have a look at my signature: Template Rules. Does exactly what you need and works with QM

Hi cipa, I don’t think this is quite what I’m looking for. I already have the "inheritTpl" capability using the "Inherit Parent Template" plugin... though your plugin looks a little more advanced so I’ll give it a go for future projects.

What I am looking to do is have QM+ display or hide the "Create Resource Here" button depending on the template used. I though the same logic of having a tv to determine if the "Create Resource Here" button should be displayed or not would work quite well.

Sorry for the misunderstanding. The coffee wasn’t ready

Quote from: uxello at Nov 20, 2009, 08:49 AM

What I am looking to do is have QM+ display or hide the "Create Resource Here" button depending on the template used. I though the same logic of having a tv to determine if the "Create Resource Here" button should be displayed or not would work quite well.

My opinion is that this functionality is a job for manager user rights...

Quote from: Eol at Nov 20, 2009, 02:39 PM

My opinion is that this functionality is a job for manager user rights...

yes some sort of MODx framework capability to restrict creating child docs would be ideal as it would work from the frontend and the backend, not just a QM fix.
I think user rights alone may be too restrictive though if it was just a global yes/no to allow child docs. More flexable would be some sort of option at the template level, which in conjunction with "Template Rules" would allow the user to create child documents down to a specified template. That template would then be flagged in some way to prevent further child docs. Getting a bit off topic for QM now though

I got some weird issue when clicking Edit Resource all got dark. First I thought the overlay was in front of everything, until I realized that my problem was caused by quickmanager adding overflow: hidden to the body tag. It must be some CSS clash, but I don’t use any overflow on the body myself.

I wonder if this is really needed? because it works perfectly without it here! (FireFox 3.5.5 on OSX 10.5.8)

I commented a part of line 299 and 300 in qm.inc.php



BTW: Why is there no link to forum on http://modxcms.com/extras/package/541

Quote from: eerne at Dec 01, 2009, 05:02 AM

I commented a part of line 299 and 300 in qm.inc.php

// Bindings
$().bind("cbox_open", function(){/*$("body").css({"overflow":"hidden"}); $("html").css({"overflow":"hidden"});*/ $("#qmEditor").css({"display":"none"});});
$().bind("cbox_closed", function(){/*$("body").css({"overflow":"auto"}); $("html").css({"overflow":"auto"});*/ $("#qmEditor").css({"display":"block"});});

These are for modal box to hide "parent page" scroll bars when editing the document. QM+ will work just fine without these lines but modal box will be little annoying if you have long "parent page" under modal box window and accidentally scroll the window. Then the modal box will move too.

Quote from: eerne at Dec 01, 2009, 05:02 AM

BTW: Why is there no link to forum on http://modxcms.com/extras/package/541

Don’t know why, some other resources are missing the forum link too.