☆ A M B ☆
The .htaccess in the qm folder reads:
Quote from: ThaClown at Mar 16, 2010, 05:42 AM
Thx for the help, any other ideas suggestions?
Scratching my head...
Any "custom" .htaccess files affecting plugins/qm/ -folder? For example something that denies direct access to close.php file?
It seems, that close.php is not for reason working properly and therefore closing/refreshing parent frame under ColorBox window.
# Restrict direct access to script file types and templates <FilesMatch "\.(php|tpl|inc)$"> Allow from all </FilesMatch>
The .htaccess in the qm folder reads:
☆ A M B ☆
☆ A M B ☆
Quote from: pachinko at Aug 23, 2009, 05:28 AM
Does qm+ have any system requirements, maybe? I have php 5.2.9 locally, and php 4.3.11 live.
As far as I know there shouldn’t be any reason why QM+ wouldn’t work with PHP 4. Though there is some legacy code in QM+ from original QuickManager plugin left but still with quick overview I can’t see any problems. I’ll have to test with PHP 4 when I have the time.
Can someone confirm that QM+ has problems with PHP 4?
$e = & $this->modx->Event;
I am sorry by an old topic.
qm.inc.php line 68
$e = & $this->modx->Event;
php 4 work.
I have installed Evo 1.0.3 onto my server with the integrated install of QM+ 1.3.4.1 and I don’t appear to be able to get the front end manager to appear on my site. The code is present in the HEAD tags, but the front end doesn’t seem to want to work whether I use my own template, or a the "minimal" template.
<html> <body> <h1>[*pagetitle*]</h1> [*content*] </body> </html>
Want to add custom buttons not only with id. but with alias for example.
