Support/Comments for QuickManager+ 1.3--

I’ll try to upgrade to php5 as well and test if this was causing my problem.

Thank you for all the help!
Alex

That was it! I have received an upgrade to php 5.2.5, and now it works like a charm.
Very cool tool!

Thanks for the info! I have to make some tests with PHP 4, though right now I’m too busy at other work projects.

Quote from: sottwell at Aug 18, 2009, 10:12 AM

What do you mean by saying ’I have several installations in subdirectories’??

On my MAMP installation, the web root is htdocs. In that directory I have several subdirectories, each one containing a distinct MODx installation. These are subject to change as I install various versions for various purposes. I usually have one or two older 0.9.6.x versions taken from a site I’m developing a snippet or module for and want the exact installation that the client is using, as well as one or two of the latest from SVN. I try to keep one pristine bleeding-edge installation that I keep updated from SVN and one likewise prisine installation of the latest "stable" release for reference when I check something for posting on the forums.

To Susan: Ok - Get it. Thanks for reply.

But what’s the solution of my ’problem’??

I’m happy to inform that QuickManager+ 1.3.2 is ready and waiting for repository approval. Those in hurry can grab the version 1.3.2 attached to this post.

I’m little disappointed by the minimalistic look of this version (mainly the modal box window), but there was too many problems with IE and Safari (occasional crashes) with previous version, so I had to make the modal box as simple as possible to iron out all bugs. I hope in the next version the modal box view will be more flashy. There is also an old problem with IE and CSS opacity that makes the text in the QM+ action buttons to look pixelated. And also the buttons (same inconsistency as in MODx manager) are not rounded in IE and Opera. Fortunately these are all quite small cosmetic problems.

Changelog:

1.3.2

* Added: New configuration option - jQuery noConflict mode in front-end
* Added: Check user manager access permissions to current document and show action buttons according to permissions
* Added: It’s now possible to hide QM+ action buttons
* Added: Hide parent frame scrollbars and QM+ buttons when modal box is visible (ColorBox bindings)
* Added: Modal box can’t be accidentally closed by clicking the overlay
* Changed: Stylish ColorBox CSS style didn’t work properly with IE and crashed too often with Safari, had to replace it with minimalistic style for better cross-browser compatibility
* Changed: Updated ColorBox to version 1.3.1, includes for example IE ClearType fix (no more ugly fonts)
* Changed: colorbox.css renamed to qm-colorbox.css and moved to QM+ css folder
* Fixed: All normal MODx manager actions including template and RTE selection works now just fine (thank you very much Susan O. for your ideas!)
* Fixed: Multiple small CSS fixes for IE
* Fixed: Alias friendly logout code (thanks Mair!)
* Fixed: Language selection a bit more robust and offer a level of fallback
* Removed: Use with ManagerManager plugin -option deprecated

* Removed: Use with ManagerManager plugin -option deprecated

I’m assuming that means that if MgrMgr is installed, correct?

Quote from: rthrash at Sep 17, 2009, 07:59 AM

I’m assuming that means that if MgrMgr is installed, correct?

It was an old option for MODx 0.9.6.3 to make QM+ to work with ManagerManager hide sections. It’s no longer needed since manager code was changed in 1.0.0. Now QM+ is always ManagerManager friendly anyways.

Little off-topic: I’ll try to find some time to test QM+ for MODx 1.0.1. I believe it will need some tweaking. Depends how much the manager code has changed from 1.0.0.

The structure of all the fields and CSS will be updated. Nuking the table-based markup and adding proper unique IDs to every "row".

Great work on the plugin Works like a charm and really makes the editing experience much nicer.

Here are some suggestions for improvements:

Configuration for Custom Buttons:

• Using the ’links’ method is a bit of a pain as the system doesn’t handle symbols well. Characters like = & etc do not get handled well and get stripped out on save. Only solution for that seems to be to URL encode those characters in the input string.
  
• Would be great to have an option for "internal" pages, for example if other modules (or custom pages) are used (for example a calendar), it should automatically open that same editing window. We integrated a solution with a new type called ’module’ (where you specify ’link’ or ’new’) which will open something like a calendar admin interface or the DocManager module.

Keep up the good work!

Quote from: twincreekmedia at Sep 18, 2009, 03:37 PM

Here are some suggestions for improvements:

Thanks! I’ll try to fix/improve these in the next version.