Support/Comments for QuickManager+ 1.3--

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

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?

I think this behavior has been there at least from MODx 1.0.3. The alert message comes from MODx manager not from QuickManager+. I’ll look in to it if there’s something to do in QM+ to prevent the extra alert message.

Quote from: Eol at Jun 08, 2010, 03:10 PM

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

I don’t know for sure. Propably because I’m the responsible for QM+ development but I don’t have user right to update QM+ in MODx SVN. Hopefylly this is going to change since I recently filled the MODx Contributor License Agreement.

I hope to move and update QM+ docs to MODx Wiki (Confluence) in the future too.

Oh, and QuickManager+ 1.5 is nearly ready featuring TV editing (like the old QuickEdit): http://modxcms.com/forums/index.php/topic,50024.0.html

Quote from: Eol at Jun 08, 2010, 03:10 PM

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

I think all that is needed is a "documentDirty=false;" adding to the cancel button around line 501 of qm.inc.php (qm version 1.4.1)

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

I think all that is needed is a "documentDirty=false;" adding to the cancel button around line 501 of qm.inc.php (qm version 1.4.1)

Thanks uxello! Works great! I’ll add this to QM+ 1.5.

I’m probably going to ask something really dumb now, as I’ve only been using MODx for a couple of days. I’ve basically got my client’s website pretty much ready to go, except that it would be much easier, and less risky for him/me, if he could duplicate a specific resource (a page containing a Maxigallery snippet call).

Is that possible with QM? Looking through the readme I can see various customisation features, but I was kind of hoping that there’d be an equivalent of the manager-view duplicate resource command - but I could be missing something....

[Edit - I am a dunce, I guess the way to do this is to put my snippet call in a template variable, and trust him to tick the box! ]

Quote from: odeclas at Jun 10, 2010, 10:19 AM

I’m probably going to ask something really dumb now, as I’ve only been using MODx for a couple of days. I’ve basically got my client’s website pretty much ready to go, except that it would be much easier, and less risky for him/me, if he could duplicate a specific resource (a page containing a Maxigallery snippet call).

Is that possible with QM? Looking through the readme I can see various customisation features, but I was kind of hoping that there’d be an equivalent of the manager-view duplicate resource command - but I could be missing something....

[Edit - I am a dunce, I guess the way to do this is to put my snippet call in a template variable, and trust him to tick the box! ]

as an alternative you could set the page to be copied with a specific MODx template that contains the MaxiGallery snippet (maybe call it ’content with gallery’ for example), then duplicating the page (resource) would use the same template.

The poster wants to be able to duplicate a resource from the QM. This is also something I have often wished to be able to do. I wonder if it would be possible to make a custom link to the duplicate_content processor? The tricky part would be passing the current document’s ID.

Quote from: sottwell at Jun 10, 2010, 10:37 AM

The poster wants to be able to duplicate a resource from the QM. This is also something I have often wished to be able to do. I wonder if it would be possible to make a custom link to the duplicate_content processor? The tricky part would be passing the current document’s ID.

oops, my bad. Though there comes a point where there is so much functionality wrapped in to a front-end solution that I’d say the client would be ready to edit through the backend manager

Indeed; with the addition of the capabilities of ManagerManger to tweak the back-end interface, fear of the Manager is mostly a matter of attitude.

Quote from: sottwell at Jun 10, 2010, 10:37 AM

The poster wants to be able to duplicate a resource from the QM. This is also something I have often wished to be able to do. I wonder if it would be possible to make a custom link to the duplicate_content processor? The tricky part would be passing the current document’s ID.

The current document’s ID problem is adressed in QM+ 1.5 released just minutes ago: http://www.maagit.fi/quickmanager-plus

Now it should be even easier to create all kinds of custom buttons including duplicate document button.

From changelog:
- Added: Custom buttons now support standard MODx [*id*] tag, e.g. http://www.example.com?refererMODxPageId=[*id*]