Support/Comments for QuickManager+ 1.5.1-GA

This is an auto-generated topic for QuickManager+ 1.5.1-GA by lammikko.

Brief Description:

QuickManager+ enables front-end content editing.

hello,

thanks for this great plugin.
One question is open.
Can i delete Doc’s from the frontend ?

Quote from: iNoize at Aug 10, 2010, 07:05 AM

Can i delete Doc’s from the frontend ?

There is no delete button, use published option instead.

Longer discussion about QM+ and delete button: http://modxcms.com/forums/index.php/topic,38605.msg289264.html#msg289264

I have had problems using QM 1.5.1 (Evo 1.0.4). Many parse errors, configuration currently reset to default settings (had set noConflict mode to "true", now "false"). QuickManager+ is the first plugin on OnParseDocument event.

Now getting this error:



I would really love to use this! I would hugely appreciate any help solving these parse errors, or at least this one to start with...

Quote from: wlhh at Aug 11, 2010, 10:34 AM

I have had problems using QM 1.5.1 (Evo 1.0.4). Many parse errors, configuration currently reset to default settings (had set noConflict mode to "true", now "false"). QuickManager+ is the first plugin on OnParseDocument event.

Now getting this error:

QuickManager+ - OnDocFormPrerender
An error occurred while loading. Please see the event log for more information.

Parse error: syntax error, unexpected T_STRING in /home/horseink/cvda.org/manager/includes/document.parser.class.inc.php(746) : eval()'d code on line 34

This error sounds very odd. At least I’m quite sure it has nothing to do with QM+ configuration options. Try to disable QM+ plugin. If your site is working ok after that I would delete the QM+ plugin and all related files and then try to install it again.

Thanks for your reply! I did disable it, and things are fine. I will try reinstalling it again (have already done so once) and report back. Maybe I missed something

Hi Lammikko

I have a couple of comments on the latest release... which I am making great use of by the way.

1) First a small feature request. How about a custom button link that opens in a new window? Sometimes useful.

2) And now the comment. I found the latest version was loading webpages noticable slower for IE browsers, 2-3 seconds pause before the page became responsive on the very first page load of a browser session. It was fine after it had been cached by the browser.
I narrowed it down to the use of AlphaImageLoader when you load the colorbox. I commented these 8 css calls out it was super fast again.
Basically AlphaImageLoader is a known cause of slow loading pages for IE. I now make sure my sites are completely AlphaImageLoader free!

I think the slight loss of nice shading is a small price to pay for the increase in speed

Keep up the great work!

Richard

Quote from: uxello at Sep 09, 2010, 05:11 PM

1) First a small feature request. How about a custom button link that opens in a new window? Sometimes useful.

2) And now the comment. I found the latest version was loading webpages noticable slower for IE browsers, 2-3 seconds pause before the page became responsive on the very first page load of a browser session. It was fine after it had been cached by the browser.
I narrowed it down to the use of AlphaImageLoader when you load the colorbox. I commented these 8 css calls out it was super fast again.
Basically AlphaImageLoader is a known cause of slow loading pages for IE. I now make sure my sites are completely AlphaImageLoader free!

I’ll add these to todo list. Not sure if they make it to the next minor release though since version 1.5.2 is already practically ready (contains only bug/validating fixes).

Thanks again for the great suggestions!