Support/Comments for QuickManager+ 1.3--

Will you be porting this to Revolution? Besides the RC, this is the only thing that is making me wait

Quote from: eFragPulse at Oct 13, 2009, 03:18 PM

Will you be porting this to Revolution? Besides the RC, this is the only thing that is making me wait

When Revolution evolves to RC-1 I’ll look if it’s possible.

Great work on the new QM+ 1.3.3, it’s getting better every time.

Now, have a question, how would I go about adding a listing of child documents to the QM’s edit bar? It would help me a lot as I have many child documents just holding data in TVs and would like to be able to edit these from their parent page. Can this perhaps be done with a button hack?

Another question, would it also be possible to hide individual TVs from the edit page?

Thanks!

Quote from: rnd at Oct 30, 2009, 08:10 AM

Now, have a question, how would I go about adding a listing of child documents to the QM’s edit bar? It would help me a lot as I have many child documents just holding data in TVs and would like to be able to edit these from their parent page. Can this perhaps be done with a button hack?

This has been on todo list for some time. There is no easy solution for this for now, not even a hack. This is the feature I hope to be able to include for next major version (v. 1.4).

Quote from: rnd at Oct 30, 2009, 08:10 AM

Another question, would it also be possible to hide individual TVs from the edit page?

I suggest you to use ManagerManager plugin for this.

Quote from: Lammikko at Oct 30, 2009, 09:41 AM

Quote from: rnd at Oct 30, 2009, 08:10 AM

Another question, would it also be possible to hide individual TVs from the edit page?

I suggest you to use ManagerManager plugin for this.

I haven’t read the whole thread, so possibly I get something wrong, but I don’t think it’s wise to use ManagerManager for everything, especially if there is a native modx solution.

You can control TVs with Access permissions for each TV’s, just scroll down when editing the TV and assign the TV to a certain group that you want them to have access to it.

cheers eni

Quote from: eerne at Oct 30, 2009, 10:55 AM

I haven’t read the whole thread, so possibly I get something wrong, but I don’t think it’s wise to use ManagerManager for everything, especially if there is a native modx solution.

You can control TVs with Access permissions for each TV’s, just scroll down when editing the TV and assign the TV to a certain group that you want them to have access to it.

Nope, you are getting it just right

Access permissions are absolutely better way to do this, no need for ManagerManager. Thanks for the correction!

I am looking to launch my first site using QM+ instead of QuickEdit... about time too
In doing a few tests I think a bug that was squashed back in 1.1 is back?

"Locked documents with multiple users (cancel button doesn’t remove document lock)"

I am using the latest 1.0.2 MODx install with QM+ 1.3.3
Can anyone confirm my findings?

Quote from: uxello at Nov 20, 2009, 04:58 AM

I am looking to launch my first site using QM+ instead of QuickEdit... about time too
In doing a few tests I think a bug that was squashed back in 1.1 is back?

"Locked documents with multiple users (cancel button doesn’t remove document lock)"

I am using the latest 1.0.2 MODx install with QM+ 1.3.3
Can anyone confirm my findings?

Cancel button doesn’t remove the document lock anymore. This change happened on version 1.3.3 and is related to fixing possible XSS vulnerabilities. You have to logout (or edit some other document) to remove document lock.

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

Cancel button doesn’t remove the document lock anymore. This change happened on version 1.3.3 and is related to fixing possible XSS vulnerabilities. You have to logout (or edit some other document) to remove document lock.

Thanks. I think this could be an issue for many people. Is there no way around this?

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

Thanks. I think this could be an issue for many people. Is there no way around this?

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.