We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 21395
    • 91 Posts
    Gallery 1.5.1

    Just upgraded.

    GalleryAlbums snippet fails with message: Fatal error: Call to a member function set() on a non-object in /home/jepse724/public_html/core/components/gallery/model/gallery/galalbum.class.php on line 255

    The snippet call is:

    [[!GalleryAlbums? &rowTpl=`galAlbumRowWithCoverTpl`&showName=``]]


    The template chunk has been changed to:

    <li[[+cls:notempty=` class="[[+cls]]"`]]>
        <a href="[[~9? &[[+albumRequestVar]]=`[[+id]]`]]">
            [[+image:notempty=`<img src="[[+image]]" alt="[[+title]]" />`]]
            [[+showName:notempty=`<span>[[+name]]</span>`]]
        </a>
    </li>


    (to force a specific output page where the Gallery and GalleryItem snippet calls are).

    Uninstalling and reverting to gallery 1.5.0 cures the problem.

    I'm running:

    Revo 2.2.1
    phpThumbOf 1.3.2
    mySQL 5.1.62
    PHP 5.3.10

    Do I have a bug?
      MODX Revolution 2.6.5-pl (traditional)

      Hosted on MODX Cloud

      Skype: nicbaldeagle
      • 21395
      • 91 Posts
      Looks like we have a radical redesign of how gallery images are stored.

      Package release notes say:

      Note: Make sure to backup your Gallery files in the location in the 'gallery.files_path' System Setting before upgrading, as this update moves gallery file storage to an album-centric storage method.

      Which might well be upsetting how my gallery-of-galleries (GalleryAlbums snippet) is called/displayed. Documentation hasn't caught up with this release, so I have no idea what the implications of this change are and what has in fact changed and what I have to do. Anyone ahead of me on this?
        MODX Revolution 2.6.5-pl (traditional)

        Hosted on MODX Cloud

        Skype: nicbaldeagle
        • 34120
        • 236 Posts
        I'm getting this exact same error, did you figure anything out?

        Edit: I can also confirm reverting to 1.5.0 solves the issue. [ed. note: bobwal last edited this post 14 years, 3 months ago.]
          • 36722
          • 101 Posts
          I can confirm both the bug and the solution is to downgrade.
            Shawn Himmelberger
            Himmelberger Design
            https://himmdesign.com/services/website-development/modx"" target="_blank" rel="nofollow"> MODx Web Design | https://himmdesign.com/services/website-development/modx"" target="_blank" rel="nofollow"> MODx Web Development