Support/Comments for QuickManager+ 1.3--

Quote from: wdnz at May 20, 2010, 04:26 PM

Firstly a small error in linked readme - you have an example:
- Add in to your Ditto template chunk: <-- qm-edit [+id+] --> is missing the ! in <!-- and so does not work

Second a question; Can I make an Edit Resource button in the content but specify the text on the button to "Edit Product" as I can if creating a "create new Resource" button? ie instead of <!-- qm-edit 1 --> can I do something like <!-- qm-edit 1 ’Edit this product’ -->

Thanks for the bug report and ideas. I actually thought the edit button name matter yesterday but didn’t implement that. Maybe I should. I also noticed a problem with edit/new buttons and user rights so I’ll publish version 1.4.1 very soon.

I also noticed a problem with edit/new buttons and user rights so I’ll publish version 1.4.1 very soon.

Ah, you’re a bloody legend!

I’ve implemented the new qm on two sites today and wow! what a difference it’s made. The new inline buttons allow me to set the correct template and parent container for adding/editing resources which is where the clients are generally making all the balls-ups.

Great work. Any plans to implement it for Revo - it’s one of the few things preventing me from taking the giant leap....

QuickManager+ version 1.4.1 is a bugfix release for version 1.4 and is waiting for repository approval.
Those in hurry can grab the version 1.4.1 here: http://www.maagit.fi/files/qm-plus-141/

Readme file is also available here: http://www.maagit.fi/files/qm-plus-141/readme.html

Changelog:

1.4.1
* Added: Individual user language check, previously QM+ used global language setting for all users
* Changed: Edit buttons in content => Inline edit buttons, New resource buttons in content => Inline new resource buttons
* Changed: Inline edit buttons "placeholder markup" changed to: <!-- "Edit button CSS class" "document id to be edited" ’"Button title"’ -->
* Fixed: Inline edit/new buttons access control

Screenshots: http://modxcms.com/forums/index.php/topic,38605.msg289035.html#msg289035 (QM+ 1.4)

Quote from: wdnz at May 21, 2010, 12:37 AM

Any plans to implement it for Revo - it’s one of the few things preventing me from taking the giant leap....

Unfortunately not yet. QuickManager for Revo will require a whole different approach so it will require complete rewrite.

This is a seriously nice plugin, and the 1.4.1 version is even sweeter with edit button titles.

Is there any way to implement a "Delete this Resource" button, perhaps with the "custom buttons" feature, or is this outside the scope of qm? If it can be done it would make this plugin perfect

Quote from: wdnz at May 21, 2010, 03:34 AM

Is there any way to implement a "Delete this Resource" button, perhaps with the "custom buttons" feature, or is this outside the scope of qm? If it can be done it would make this plugin perfect

I believe "delete this resource" button could be done but the main question is: is the delete button really needed?

Quote from Sottwell:
"I believe that the idea was is that front-end editors should only be able to unpublish; then an admin user could go to the Manager and verify the deletion and do the actual deleting.

Of course, "delete" only marks a resource for deletion, and you have to empty the trash to really remove it, but what’s the purpose of adding the complexity of two more functions to QM when unpublish will have the same effect.
"

It’s also possible to make a custom delete button if you combine custom button with custom snippet.

Make a custom button that redirects to a document with custom snippet that checks referer document id and then deletes the document.

Duh! You’re absolutely right, I completely forgot about the unpublish feature. Please excuse the MODx noob

The first couple of sites I’ve developed with MODx I’ve found I’ve had to introduce the client to back-end editing because they’ve created products in the wrong container and need to move them etc. Now with QMv1.4.1 I can ensure the client uses the correct template and the new document is saved to the container I specify. With the unpublish feature it’s goodbye to the back-end manager for my clients now which will make both them and myself extremely happy!

My latest site is www.rataindustries.co.nz and it utilises qm1.4.1 for all product entry and editing - so easy! Thanks a bundle Lammikko If you’re ever in New Zealand I’ll buy you a beer or 10.

Quote from: wdnz at May 21, 2010, 03:58 AM

My latest site is www.rataindustries.co.nz and it utilises qm1.4.1 for all product entry and editing - so easy! Thanks a bundle Lammikko If you’re ever in New Zealand I’ll buy you a beer or 10.

You’re Welcome! 10 sounds about right

I really like the ’Edit buttons in content’ option, just what I was looking for to take it to the next level, thanks Lammikko!

I have noticed running the latest MODX 1.0.4 with QuickManager+ (either or 1.3.4.1 or upgrading to 1.4.1) that if I change a field and then cancel the page I get the ’Are you sure you want to navigate away’ message after the page closes. In earlier versions this message was supressed from the front-end. Is this just my setup?

Quote from: uxello at Jun 08, 2010, 09:01 AM

I have noticed running the latest MODX 1.0.4 with QuickManager+ (either or 1.3.4.1 or upgrading to 1.4.1) that if I change a field and then cancel the page I get the ’Are you sure you want to navigate away’ message after the page closes. In earlier versions this message was supressed from the front-end. Is this just my setup?

I see it too with Evo1.0.4 + QM+ 1.4.1, even after clearing the whole browser cache.

BTW, why 1.4.1 isn’t in the standard release?