Well, mainly I’m testing the things in Firefox where it doesn’t work even if I exclude the JavaScript libraries loading. In IE it works fine if the libraries are loaded.
It is because the default template already has mootools in it. use &disable_js_libs=`1` in the snippet call to make maxigallery not include the mootools library..
Hmm, I use Firefox too and it worked fine.. I’ll look at it again today evening when I get off from work.. Are you using the default MODxHost template?
Quote from: doze at Feb 21, 2007, 03:43 PMWell, mainly I’m testing the things in Firefox where it doesn’t work even if I exclude the JavaScript libraries loading. In IE it works fine if the libraries are loaded.
It is because the default template already has mootools in it. use &disable_js_libs=`1` in the snippet call to make maxigallery not include the mootools library..
Good point.. actually I have to load the lang file before the $mgconfig is constructed, because some snippet parameters use defaults from the lang file, but I get this fixed today too. Thanks!
Bug: you try to load the language file prior of populating $mgconfig settings from parameters.
Move the lang file loading after setting the $mgconfig array and change $mg->mgconfig[’lang’] to $mgconfig[’lang’].
Quote from: andrazk at Feb 22, 2007, 12:27 AMHmm, I use Firefox too and it worked fine.. I’ll look at it again today evening when I get off from work.. Are you using the default MODxHost template?
Quote from: doze at Feb 21, 2007, 03:43 PMWell, mainly I’m testing the things in Firefox where it doesn’t work even if I exclude the JavaScript libraries loading. In IE it works fine if the libraries are loaded.
It is because the default template already has mootools in it. use &disable_js_libs=`1` in the snippet call to make maxigallery not include the mootools library..
Quote from: andrazk at Feb 22, 2007, 01:52 AMGood point.. actually I have to load the lang file before the $mgconfig is constructed, because some snippet parameters use defaults from the lang file, but I get this fixed today too. Thanks!
Bug: you try to load the language file prior of populating $mgconfig settings from parameters.
Move the lang file loading after setting the $mgconfig array and change $mg->mgconfig[’lang’] to $mgconfig[’lang’].
I’m using my own template with no extra scripts included.
Hmm.. now I’m confused, before you said that you were using MODx 0.9.6-RC1 and MaxiGallery 0.5-RC1 and now you are upgrading 0.9.5 to 0.9.6.. are these two different environments?
Of course I’m not using the default template.
UPDATE: I’ve upgraded 0.9.5 to 0.9.6. Now I had to remove QuickEdit and reinstall in manually for both MG and QE to work properly!
...The default template in MODx has MooTools 1.0 icluded, MaxiGallery adds one more and QuickEdit adds a third one...
Yes, I remember you feature request and I did the &disable_js_libs parameter to RC1 to disable the including of MooTools, scriptaculous and prototype. This is to be used when you already have mootools.js for example in your site template.
Quote from: doze at Feb 22, 2007, 11:15 AM
...The default template in MODx has MooTools 1.0 icluded, MaxiGallery adds one more and QuickEdit adds a third one...
Hey there, doze. This reminds me of another minor feature request that I made a while back (and I don’t think has been implemented). How about adding a parameter like reg_scripts=`false` to completely bypass the MaxiGallery script addition functions? I prefer to add my scripts manually to my template files, and this also makes it easier to use non-standard presentation packages with MaxiGallery. Plus it would keep triple-scripting like this from happening...
Quote from: andrazk at Feb 22, 2007, 06:36 AMHmm.. now I’m confused, before you said that you were using MODx 0.9.6-RC1 and MaxiGallery 0.5-RC1 and now you are upgrading 0.9.5 to 0.9.6.. are these two different environments?
Of course I’m not using the default template.
UPDATE: I’ve upgraded 0.9.5 to 0.9.6. Now I had to remove QuickEdit and reinstall in manually for both MG and QE to work properly!
Anyways, here’s the case: MODx 0.9.6 RC1 and MaxiGallery 0.5 RC1 works together with QuickEdit enabled and MaxiGallery using slimbox display type. The default template in MODx has MooTools 1.0 icluded, MaxiGallery adds one more and QuickEdit adds a third one. But they are all the same libs and both quickedit and maxigallery is working.
In MODx 0.9.5, QuickEdit and MaxiGallery slimbox wouldn’t work together as 0.9.5 QuickEdit uses prototype/scriptaculous. In 0.9.5 you would have to use lightbox v2 in maxigallery.
Does this explain anything, or do you still have some issues?
No problems! Glad that it’s working as it should.. please report any problems that you may find.
Sorry for your time but I had quite a learning experience.
This discussion is closed to further replies. Keep calm and carry on.