We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 14900
    • 22 Posts
    I am relatively new to MODx but have had great success with Ditto & Wayfinder.

    I’m starting to explore MaxiGallery in the hopes of constructing a client-editable gallery, but am having a few problems. I started by:

    1) downloading and installing the snippet, V.0.5.2
    2) following the wiki instructions and setting up a parent container document called "My Galleries", with 1 child document called "Gallery 1"
    3) Adding the content: [!MaxiGallery? &display=`childgalleries`!] to the containing document "My Galleries"
    4) Adding the content: [!MaxiGallery? &display=`embedded` &embedtype=`slimbox` &pics_per_row=`3` &max_thumb_size=`110` &max_pic_size=`0` &thumb_use_dropshadow=`1`!] to the child document "Gallery 1"

    I assigned both container and child docs to a newly created, bare bones template completely devoid of any css,javascript, jquery, or mootools calls. I then previewed the document, added 5 images, and checked the resulting page in a different browser.

    The result was a bare bones gallery with 5 images, no slimbox style gallery at all. I’m not so concerned with fancy embedded type galleries at this point, but I am wondering why, when returning to and editing my child document "Gallery 1":

    - all changes to &pics_per_row and &max_thumb_size are completely ignored in the maxigallery output (even after re-uploading the pictures)
    - even completely Deleting the contents of "Gallery 1" has no effect on the output!

    What am I missing here, how come my maxigallery call is being ignored? I’m guessing maxigallery is going to the default installed templates...I am working locally with MAMP and modx version 0.9.6.3. Any help would be greatly appreciated.
      • 7923
      • 4,213 Posts
      Note that you have to upload the pictures using the "Gallery 1" child document. The parent document will also have manage pictures button, but that will upload pictures to the parent document.


        "He can have a lollipop any time he wants to. That's what it means to be a programmer."
        • 14900
        • 22 Posts
        Thanks for the clarification -

        I ended up installing managermanager in order to use the very cool maxigallery backend manager widget.

        I also revised my maxigallery snippet calls to follow the "Picture and thumbnails on same page" javascript example on the Maxigallery Wiki.

        The results are very promising - the backend manager works like a charm, and the wiki example (with the addition of a closing ’>’ script tag in the javascript in step 3) also works as advertised.


        I am still, however, having an issue controlling thumbnails via the maxigallery call.

        I have a document called ’My Galleries" with the following code:

        <div id="thumbnailsmaxi">
        [!MaxiGallery? &pics_per_row=`3` &galleryPictureTpl=`mgGalleryPicture` &js=`mgJs` &max_thumb_size=`40px` !]
        </div>
        
        <div id="example">
        [!MaxiGallery? &pictureTpl=`mgPicture` &display=`pictureview`!]
        </div>
        


        The 2 divs position the thumbnails and main picture on the page. The css they follow is incidental, but:

        #thumbnailsmaxi {
        	width: 250px;
            position: absolute;
        	top: 450px;
        	left: 75px;
        }
        
        
        
        #example {
        	border: 0px;
        	width: 450px;
        	height: 300px;
        	margin-bottom: 5px;
                padding: 0 0 0 0px;
                position: absolute;
        	top: 78px;
        	left: 390px;
        }
        


        My Problem is i’m still only getting the maxigallery call to work partially:
        &pics_per_row=`3` works fine, for example, however &max_thumb_size=`40px` has no effect.

        I find that i can control the thumbnail size via CSS:

        .thumbnail {
        	width: 40px;
        	height: 40px;
        }
        


        but I would prefer to do so via the Maxigallery call. I have tried adding a few other parameters (such as the various thumb masking params) also with no effect.

        Any ideas?




          • 7923
          • 4,213 Posts
          All parameters that affect to the images requires that the image is re-uploaded. The resizing, filters and masking etc are done on upload. And &max_thumb_size=`40px` should be just &max_thumb_size=`40`. That means that maxigallery will resize the thumbnail to be at maximum 40 pixels wide and tall, keeping image dimensions.

          You can also use phpThumb together with maxigallery to create a setup where you use maxigallery to just manage and render the galleries, and phpThumb to resize / mask the pictures. phpThumb caches the images itself, so you don’t have to re-upload images when you change phpThumb parameters. You can find more information about MaxiGallery + phpThumb setup from the sticky information post.


            "He can have a lollipop any time he wants to. That's what it means to be a programmer."
            • 14900
            • 22 Posts
            Thanks again for the quick response -

            &max_thumb_size=`40px` was a later attempt at getting the maxigallery code to effect the thumb size

            I went back to the original: &max_thumb_size=`40` , also re-uploaded the images, and still no effect. My documents are all set to "uncacheable" and all maxi calls are in the [! ... !] format, but still no effect on the thumbnail size.

            I am working locally on MAMP, if this has any effect?

            Any further ideas on what I am doing wrong? I guess the next step is working with the phpThumb PHx modifiers in the maxiGallery templates.

              • 7923
              • 4,213 Posts
              I would need to see your gallery setup.. I still think that you are uploading the pictures from "wrong" snippet call.. I don’t remember how managermanager works, eg. did it have a maxigallery snippet call somewhere in its code.. and if you need to put the parameters there.. There’s no reason why that parameter wouldn’t work if the resizing with default values work.


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