Yeah, the decorators have been giving me grief. I didn't think it would work to extend the ImageGalleryItem directly since the ImageGalleryPage class includes the ImageGalleryItem in its has_many array, which would mean editing the ImageGalleryPage class, defeating the purpose of separating my additions into a separate module. However, after thinking about it a bit, your suggestion may actually work, since I CAN decorate the ImageGalleryPage successfully... I'll try it this afternoon.

On an entirely unrelated note, I'm also working on a module that organizes various SilverStripe features into a package for user-management. In working on this, I noticed that the die() statement used to render a single album gallery breaks the built-in SS security model. For example, if you create a Page with Access set to a specific user-group, then make a Image Gallery Page as a child of the secured page, it is still possible to access the gallery via its URL if there is only one album because the die() statement stops further PHP execution. My quick fix was to change the die() to a redirect like this:

if($this->SingleAlbumView()) {
   //FIX: changed die() to redirect to only album in order to solve security issue...
   $gallery_ID = $this->data()->getField("ID");
   $gallery_URLSegment = $this->data()->getField("URLSegment");
   $album = ImageGalleryAlbum::get_one("ImageGalleryAlbum", "ImageGalleryPageID = ".$gallery_ID);
   $album_URL = $gallery_URLSegment.'/album/'.$album->Folder()->Name;
   Director::redirect($album_URL);
   //die($this->renderWith(array('ImageGalleryPage_album','Page')));
}

The URL isn't as pretty, but it fixes the security issue... any thoughts on a better way to do this?

Moving the die() to the index() function solved the security problem for me without the sloppy URL... good call!

In the init() I now have:

if(!isset($this->urlParams['Action'])) {
   //SingleAlbumView, handled in index()
} elseif($this->CurrentAlbum()) {
   $this->includeUI();
}

And in the index() is the die():

public function index() {
   if(!isset($this->urlParams['Action'])) {
      if($this->SingleAlbumView()) {
         die($this->renderWith(array('ImageGalleryPage_album','Page')));
      }
   }
}

EDIT: It doesn't get rid of the unconventional use of die() though...

Yeah, I've never used that module. Do you have any instances of a DataObjectManager running successfully? Because the albums interface is just a straight DataObjectManager -- nothing fancy going on. I have a feeling if that is failing for you, then DataObjectManager is not compatible with NestedURLs, which means perhaps ComplexTableField isn't, either, because they both use the same URL handlers.

Hmm..

Hi Uncle Cheese,
The NextAlbum function is not returning the next album. It is actually returning the last album. Has anyone else seen this problem?
I just re-installed all the newest versions of DataObjectManager, ImageGallery, & SWFUploadField, but no luck.
I also tried re-sorting the albums and then placing them back to their original positions with no luck. Please help!

You can see what I am talking about here: http://66.147.242.166/~pascetti/railings-stairs/album/Cable-Railings

Thank you for your help!

*** I got it ***

*I changed the ImageGalleryPage.php file *
from this

* * * *
public function NextAlbum()
   {
      return $this->adjacentAlbum("next");
   }
* * * *

to this

* * * *
public function NextAlbum()
   {
      return DataObject::get_one(
         "ImageGalleryAlbum",
         "ImageGalleryPageID = {$this->ID} AND SortOrder > {$this->CurrentAlbum()->SortOrder}",
         false,
         "SortOrder ASC"
      );
      
   }
* * * *

It is now working. Yay!