We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 10101
    • 4 Posts
    I’m trying to integrate MaxiGallery into an existing collection of photos. The photos are organized into "galleries", where each gallery is directory with a human readable name. Each gallery can contain sub-galleries (sub-directories) and images.

    After playing with MaxiGallery, there seems to be 2 issues that prevent me from realizing my integration plans:

    1) MaxiGallery uses the document ID as the name of the directory where a gallery is stored. Is there a way to specify a specific directory instead of using the document ID? Could it be pulled from a TV? Or specified as one of the parameters to the snippit?

    2) When an image is added to a MaxiGallery gallery, MG creates a thumbnail in the same directory as the image. If you’ve told MG to also save the "big" version, it creates a big_* image file in the same directory. So for any image, you have 3 files. Assuming I could get a resolution to No. 1, Is there a way to prevent MG from messing with the contents of the directory where the original "big" image is stored?

    The idea here is that the gallery directory structure is used by other applications (in read only mode) to present images and galleries for other purposes (HTPC, etc). I don’t want MG thumbnails to show up in those directorties, nor have the original "big" image renamed with a "big_" prefix. I want MG to treat the gallery directory as read only, just like the other applications.

    Of course, this might make MG’s upload feature moot. I suppose, in an ideal world, I could configure MG to still upload images, but put the originals in the "real" gallery directories, and the thumbs and such in a MG specific directory.

    Is any of this possible?

    -Tab
      • 7923
      • 4,213 Posts
      No, sorry, not possible. Maybe some day with another snippet..


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