Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

We're retiring the forums!

The SilverStripe forums have passed their heyday. They'll stick around, but will be read only. We'd encourage you to get involved in the community via the following channels instead:

All other Modules /

Discuss all other Modules here.

Moderators: martimiz, Sean, Ed, biapar, Willr, Ingo, swaiba

Image Gallery Extension: Testers Needed

Go to End

417 Posts   95352 Views


Community Member, 23 Posts

24 February 2009 at 5:11am


Andrew Houle

Community Member, 140 Posts

24 February 2009 at 5:29am

Congrats on the new extension! I just finished installing it. It works flawlessly so far, thanks so much for your hard work on this. SS desperately needed a good gallery module.


Community Member, 187 Posts

24 February 2009 at 5:31am

Hey Uncle Cheese

Took your advice and installed Image Gallery... just what I needed

It all seems to install ok and database rebuilds but when I try to create a new page with type Image Gallery I am unable to save and Firebug says I have an internal Server error 5000 at prototype.js (line 760) which is 'this.transport.send(this.options.method == 'post' ? body : null);'

I am running SS 2.2.3 and trunk revision 37 of Image Gallery/swfupload/dataobject manager

Any ideas on what might be wrong?




Forum Moderator, 4102 Posts

24 February 2009 at 5:35am

Hi, mschiefmaker,

First, upgrade to 2.3. I haven't tested it in the 2.2 environment because I knew 2.3 was so close to release.

Also, just confirming it's a 500 error, not a 5000 error, right?


Community Member, 41 Posts

25 February 2009 at 12:58pm

UncleCheese, very good work, thanks.

I have a DB error (2.3rc4 + 2.3 with ImGal Rev 37 and embargoexpiry):
sapphire/core/model/MySQLDatabase.php line 394
Unknown table 'Page_Live',256)
line 394 of MySQLDatabase.php

This error appears after the first defining of the description and the cover images for the albums. "Save" is possible, but with "Save and Publish" I get that error.


Community Member, 37 Posts

25 February 2009 at 2:52pm

Edited: 25/02/2009 2:57pm

This is great! WAY more reliable and easier to use than before. Thanks for all the dev time youve been putting in!

I still have the request of having the lightbox navigation span the multiple pages of images within an album. I often have albums with hundreds of images in them. Nobody wants to have to close the lightbox, click next page, then open the lightbox again. For now, my workaround is loading all 250 thumbnails on a single page.. not so hot.

Also, and in the same vein - why the 20 image upload limit? If I'm uploading 2-300 images at a time, the limit really slows the process down.

All in all, great work! MUCHAS THANKS!

Shawn Parr

Community Member, 60 Posts

26 February 2009 at 4:11am


You mention not to install the Gallery module as things will 'blow up.' Does your new set of modules allow for some of the features of the old gallery module? i.e. Galleries of files that are not images, like PDF files, Movies (with lightbox type display), etc?

Obviously I haven't dug into the new version much yet, but I'm curious. I'm part of a team that is rolling out multiple sites, and we want to have a uniform setup. Some sites will not need image gallery function, but might need a gallery of other file types. While some will just need image galleries, and some might need both.


Forum Moderator, 4102 Posts

26 February 2009 at 9:31am

Edited: 26/02/2009 9:31am

@ Shawn -- No, the image gallery (by definition) only handles images. If you want something more flexible, I recommend using the FileDataObjectManager.

@ Joshuarr -- Do a checkout of dataobject_mangaer and image_gallery. Then build. See the new UploadLimit field on the ImageGalleryPage under Configuration. You can now set your own. As far as cross-page browsing in the lightbox, it's not a bad idea, but we have to be careful about how many images actually get loaded on the page, as it can create a lot of overhead. If the page load time becomes to long, then users can easily click on an image before the javascript has been loaded, and that's very, very bad.

Go to Top