We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 15001
    • 697 Posts
    Hi everyone,

    I’m finishing some layout containing 3 calls to MaxiGallery and all displays pretty well.

    However I’m encountering a few issues on the "manager" side and also have some basic questions.

    1) The "Manage pictures" button is located in a thin table column.
    When the button is clicked, Firefox enlarges the table column and MaxiGallery’s interface is made visible. On the contrary, Microsoft Internet Explorer keeps the column width and most of MaxiGallery backend is invisible (croped).

    Is there a way to make MaxiGallery fields display somewhere else (e.g. in a <div> located above the table) ?

    2) What is the purpose of the "Resynch Gallery" button ?
    Does it re-upload the files from their local folders and permit to regularly update content like advertising banners ?

    3) I have a problem when using the "Delete all pictures" button.
    My page contains thumbnails that display several views of an object.
    But it also have a call to Ditto, to display other objetcts.
    Ditto itself call MaxiGallery to get the first picture of each other object.

    I would like the "Delete all pictures" button to delete all pictures for the current object (i.e. document). But currently, it deletes all pictures for all documents. How can I prevent this ?

    4) A PHP script error displays when I upload new pictures.
    However, the pictures seems correctly loaded and displayed.

    « MODx Parse Error »
    MODx encountered the following error while attempting to parse the requested resource:
    « PHP Parse Error »

    PHP error debug
    Error: chmod() [function.chmod]: No such file or directory
    Error type/ Nr.: Warning - 2
    File: /hsphere/local/home/somesite.com/somesite.com/assets/snippets/maxigallery/maxigallery.php
    Line: 372
    Line 372 source: chmod($mg->path_to_gal.$name,0666);

    Parser timing
    MySQL: 0.0033 s (12 Requests)
    PHP: 0.2043 s
    Total: 0.2076 s

    5) MaxiGallery’s backend uses the "description" field as galery title.
    Is there a way to change this so that it displays the "pagetitle" instead ?


    Many thanks for your help.
      • 7923
      • 4,213 Posts
      Quote from: Jul at Aug 29, 2009, 03:55 AM

      1) Is there a way to make MaxiGallery fields display somewhere else (e.g. in a <div> located above the table) ?
      No.. The management form is rendered where ever MaxiGallery snippet call is. But what you can do (and must do, see below) is to use &manage_target parameter together with &is_target=`1` parameter in the target document to do picture management on separate document. Then set the call to in that document to appropriate place.

      Quote from: Jul at Aug 29, 2009, 03:55 AM

      2) What is the purpose of the "Resynch Gallery" button ?
      It checks the file system folder for any new or removed pictures and synchronizes the gallery to show the changes. So you can upload new pictures via FTP program for example and then hit the resynch gallery button to "upload" the pictures to MaxiGallery.

      Quote from: Jul at Aug 29, 2009, 03:55 AM

      3) I would like the "Delete all pictures" button to delete all pictures for the current object (i.e. document). But currently, it deletes all pictures for all documents. How can I prevent this ?
      I don’t really understand this question.. The delete all pictures button deletes all pictures from that _single_ gallery. It shouldn’t delete pictures from other documents. Of course if you are using view_gallery or query parameteres in other documents to show the pictures from certain gallery and then delete pictures in that gallery, they will disappear from other documents too.

      Quote from: Jul at Aug 29, 2009, 03:55 AM

      4) A PHP script error displays when I upload new pictures.
      The problem is that you have multiple maxigallery calls on a single document. That causes problems to the picture management. What you need to do is to use &manage_target and &is_target parameters. See more about them in MaxiGallery wiki. I suspect that the pictures haven’t really been uploading to correct galleries and that’s why you are having problems with the ’delete all pictures’ button.

      Quote from: Jul at Aug 29, 2009, 03:55 AM

      5) MaxiGallery’s backend uses the "description" field as galery title.
      Is there a way to change this so that it displays the "pagetitle" instead ?
      Yes, do a custom &manageOuterTpl, it’s a placeholder there.


        "He can have a lollipop any time he wants to. That's what it means to be a programmer."
        • 15001
        • 697 Posts
        Hi Doze,

        Thanks a lot.

        Concerning the "Resynch Gallery" button, I’m not sure in which folder MaxiGallery will look for new pictures. You’re telling about FTP transfer. Does this mean that the new pictures have to be uploaded to the gallery folder and MaxiGallery will take them from here to resize them and create the thumbnails ?

        Point 3 above is very strange in my case. My page use 3 MaxiGallery calls.
        One for the main picture, one for thumnails of alternative pictures of the same object, and the third one called via a Ditto chunk to display the first thumbnail of another document pictures. The picture manager is called from the second MaxiGallery call (thus that displays thumbnails). Unfortunately I currently cannot post any url.

        Concerning point 4, the pictures were correctly uploaded in the right galleries (folders). A parsing error displays, but when refreshing the page all is OK.

        Cheers.
          • 7923
          • 4,213 Posts
          Quote from: Jul at Sep 14, 2009, 12:29 PM

          Concerning the "Resynch Gallery" button, I’m not sure in which folder MaxiGallery will look for new pictures.
          /assets/galleries/<document_id_here>/ by default. The base path where maxigallery stores it’s images can be changed via parameter though, but unless you have changed it, the gallery images should be there.

          Quote from: Jul at Sep 14, 2009, 12:29 PM

          You’re telling about FTP transfer. Does this mean that the new pictures have to be uploaded to the gallery folder and MaxiGallery will take them from here to resize them and create the thumbnails ?
          Yes.

          Quote from: Jul at Sep 14, 2009, 12:29 PM

          Point 3 above is very strange in my case. My page use 3 MaxiGallery calls.

          ....

          Concerning point 4, the pictures were correctly uploaded in the right galleries (folders). A parsing error displays, but when refreshing the page all is OK.
          Point 3 and 4 will be corrected when you add &manage_target and &is_target parameters to the snippet calls, or use the disable manager hack and disable picture management for the galleries that should not be managed in that document.

          When you do multiple galleries on a single page, this is the correct way to do it:

          1. Create each gallery on it’s own document that only runs with one MaxiGallery call. For example doc id: 4, 5 and 6 has a call like this:

          [!MaxiGallery? &max_pic_size=`800` &is_target=`1`!]

          2. In a single document, query pictures from a gallery and use the &manage_target parameter to tell on which document it should do the picture management for the gallery:

          [!MaxiGallery? &gal_query_ids=`4` &manage_target=`4`]
          [!MaxiGallery? &gal_query_ids=`5` &manage_target=`5`]
          [!MaxiGallery? &gal_query_ids=`6` &manage_target=`6`]

          Now when you click ’manage pictures’ button from the second snippet call for example, it will redirect you to doc id 5 to do the picture management and that document has only one MaxiGallery call, so it won’t mess things up when uploading.


            "He can have a lollipop any time he wants to. That's what it means to be a programmer."
            • 30552
            • 75 Posts
            Quote from: doze at Aug 31, 2009, 01:00 AM

            Quote from: Jul at Aug 29, 2009, 03:55 AM

            1) Is there a way to make MaxiGallery fields display somewhere else (e.g. in a <div> located above the table) ?
            No.. The management form is rendered where ever MaxiGallery snippet call is. But what you can do (and must do, see below) is to use &manage_target parameter together with &is_target=`1` parameter in the target document to do picture management on separate document. Then set the call to in that document to appropriate place.

            I edited the css file for MaxiGallery, adding a z-index, solid background color, and padding to the managercontainer class, which solved my issue of the manager area being cut off. For me, that was just as good as having the fields display elsewhere.