gallery set to embedded, but large images displaying on new page

Hi
Using maxigallery for the first time - testing locally on Apache and install/setup etc fine - but problem is that all large images are showing on a new page, whereas the gallery is set to embedded and i’m calling the &embedtype=`lightboxv2` paramater. Here’s the call in full:
Container:

Document:

Is it a local testing problem or is there anything glaringly obviously wrong here? Or ... do i need to create the templates/chunks for the ’Picture and thumbnails on same page’ instructions in the documentation?
The related container/docs are all set to Cacheable.

Thanks in advance

Do you perhaps have some other javascript libraries included to that document or is QuickEdit enabled?

lightboxv2 uses scriptaculous+prototype js libraries. QuickEdit uses MooTools and those don’t go well together. The slimbox display type is same as lightboxv2, but uses MooTools, so you may want to try it out.

There is probably also some js error visible in your browser.

Thanks.
BTW, i’m testing this in the modx install site - would have thought this was okay with no extraneous javascripts around, but tell me if not please.

Switched off RTE, logged out, and that got things moving with lightboxv2 inasmuch as i got a white box overlay but no image and no 50% opacity screen overlay - see this snip of the screenshot:


so as a guess I added:

but no difference.

Here’s the slimbox code which also doesn’t overlay but goes to a new page:

As i’m doing this locally could it be a r/wr permissions thing? That would be odd but i gotta cover it.

I’ve got the ’Basic’ gallery working fine so i guess there’s no fundamental flaws anywhere ...

The lightbox doesn’t work in default modx template straight away, because there are css collisions. I don’t remember what it was at the top of my head, but there are threads about it here in maxigallery subforums.

It has been a while that this has posted, so might be hard to search for it.. you could start just cutting the site template css out to try and see what it was.

thanks, i’ll hunt.
also i’ll try it in some really basic templates with no other js within the page to see if that works.