qm's jquery head inclusion malfunctioning

11 Posts

jas Reply #1, 16 years, 5 months ago

Hi guys following phenomena:

I’m using Evo 1.0.3 and if I’m right its using JQuery 1.3.2

Problem is its automatic inclusion in the head section has no (or not quite the right) effect. The toolbar is there and "Manager" and "Logout" work but with the other two (Resources buttons) it first seems to work but finally I only get a blank screen.

However when I manually include JQ in the header everything works fine - but then I have 2 same JQuery inclusions when I look at the source. Doesnt seem to make any trouble so far but it just doesnt seem right..

(I have mootools included as well and I assumed thats the problem but I tried everything from taking it out of the head section to deleting the mootols folder from the manager/media/script/ folder - doesn’t change anything)

Any idea what the problem could be or any other hint how I could find out?

By the way - little off topic - does anybody know why I can’t include mootools with snippet:

Snippet AddScript
<?php
$addcode = (isset($addcode)) ? $addcode : 'pathtomootools';
if ($addcode != '') $modx->regClientStartupScript($addcode);
?>

other ("normal") js I can include this way without any probs..

Jas

634 Posts

Lammikko Reply #2, 16 years, 5 months ago

1. Just a confirmation: Is the jQuery in place if you look at page source code?

2. What do you mean by this: "it first seems to work but finally I only get a blank screen"? Does QuickManager+ open the modal box window but the content of that window is blank? If so, try to delete ".htaccess" file located at "assets/plugins/qm/" -folder.

3. Does your page source validate without QM+? I have seen something like this before if the page has missed HEAD -tag etc.

Mikko Lammi, Owner at Maagit

11 Posts

jas Reply #3, 16 years, 5 months ago

Hi again, well when I tried this morning everything was as it should be. I have absolutely no idea why, I didn’t do anything since then.

Thanks anyway!

☆ A M B ☆
24,524 Posts

sottwell Reply #4, 16 years, 5 months ago

Could have been a browser cache issue. Next time something like that happens, try logging out, clearing the site’s cookies and the browser cache.

Studying MODX in the desert - http://sottwell.com
Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
Join the Slack Community - http://modx.org

11 Posts

jas Reply #5, 16 years, 4 months ago

Thanks will try that next time