MaxiGallery v0.5 - RC 1 | MODX Community Forums

1,611 Posts

ZAP Reply #21, 19 years, 7 months ago

Quote from: doze at Feb 22, 2007, 12:05 PM

Quote from: ZAP at Feb 22, 2007, 11:39 AM

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...

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.

Aha! I figured you would’ve mentioned that here if you’d already added the feature, but that just goes to show once again what happens when you ass|u|me. Thanks for taking care of that!

"Things are not what they appear to be; nor are they otherwise." - Buddha

"Well, gee, Buddha - that wasn't very helpful..." - ZAP

Useful MODx links: documentation | wiki | forum guidelines | bugs & requests | info you should include with your post | commercial support options

4,213 Posts

doze Reply #22, 19 years, 7 months ago

Quote from: ZAP at Feb 22, 2007, 05:34 PM

Aha! I figured you would’ve mentioned that here if you’d already added the feature, but that just goes to show once again what happens when you ass|u|me. Thanks for taking care of that!

There are actually bunch of other feature requests from you in this release too.. check it out man! grin

"He can have a lollipop any time he wants to. That's what it means to be a programmer."

101 Posts

gcruz Reply #23, 19 years, 7 months ago

I got smoothgallery to work, however it seemed really slow.

I would click on the next button, and it would take a few seconds before the next photo would load in Safari. I’ll try on the "PC" in Parallels and report back.

I’m on a MacBook Pro 2ghz with 2gb RAM

4,213 Posts

doze Reply #24, 19 years, 7 months ago

In FF and IE it’s running swiftly.. I would guess that it’s a Safari issue. You can go to the SmoothGallery site and it’s forums to see if there have been similar reports from other safari users.

Also try the examples in SmoothGallery site. If they are running fine, try your gallery in a blank template that has just the doctype, html, head and body tags.

"He can have a lollipop any time he wants to. That's what it means to be a programmer."

138 Posts

sderuiter Reply #25, 19 years, 7 months ago

Not sure if this is related to 0.5 RC1, but on my site http://tlaer.nl/fotos/3456-toernooi-2006-fotos I use the following call:

[[MaxiGallery? &display=`embedded` &embedtype=`lightboxv2` &pics_in_a_row=`3` &max_thumb_size=`110` &max_pic_size=`0`  &thumb_use_dropshadow=`1`]]

The main menu is built using:

<div class="menu">
[[Wayfinder? &startId=`0` &level=`3` &parentRowTpl=`cssplay_revParentRow` &cssTpl=`cssplay_ultdrop`]]
</div>

Now, when I click on a picture, the backgroung gets darkened and the picture loads. However, the main menu is not greyed out as the rest of the site (and remains clickable in IE6, but not in FF2.0)

Have you seen this before?

Thanks for this excellent plugin.

4,213 Posts

doze Reply #26, 19 years, 7 months ago

It’s because in your CSS, your .menu class has a z-index of 100 what is more than the lightbox overlay (90). So decrease the z-index in your .menu class or increase it for lightbox #overlay id.

And if you are using 0.5 RC1, it’s &pics_per_row and not &pics_in_a_row..

"He can have a lollipop any time he wants to. That's what it means to be a programmer."

138 Posts

sderuiter Reply #27, 19 years, 7 months ago

Quote from: doze at Feb 25, 2007, 02:24 PM

It’s because in your CSS, your .menu class has a z-index of 100 what is more than the lightbox overlay (90). So decrease the z-index in your .menu class or increase it for lightbox #overlay id.

Worked. Thanks!

2,204 Posts

Dimmy Reply #28, 19 years, 7 months ago

Quote from: doze at Feb 25, 2007, 02:24 PM

And if you are using 0.5 RC1, it’s &pics_per_row and not &pics_in_a_row..

could this not be made backwords compatible? if I now update from an older version that I need to redo all my tags.

follow me on twitter: @dimmy01

4,213 Posts

doze Reply #29, 19 years, 7 months ago

I can make it backwards compatible, but not sure if the script is totally backward compatible.. tables have gone and the layout is now done in css, so it might look different after you update.. But I’ll make that one parameter backward compatible.

"He can have a lollipop any time he wants to. That's what it means to be a programmer."

1,611 Posts

ZAP Reply #30, 19 years, 7 months ago

You Quote from: Dimmy at Feb 27, 2007, 09:59 AM

Quote from: doze at Feb 25, 2007, 02:24 PM

And if you are using 0.5 RC1, it’s &pics_per_row and not &pics_in_a_row..

could this not be made backwords compatible? if I now update from an older version that I need to redo all my tags.

You don’t have to redo your tags. You could just add something like if(isset($pics_in_a_row)) $pics_per_row=$pics_in_a_row; to the beginning of your new maxigallery snippet. Of course doze could add that to the script itself, but sometimes old baggage just accumulates until it gets in the way...

"Things are not what they appear to be; nor are they otherwise." - Buddha

"Well, gee, Buddha - that wasn't very helpful..." - ZAP

Useful MODx links: documentation | wiki | forum guidelines | bugs & requests | info you should include with your post | commercial support options