Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
This seems to be caused by enabling a gallery block without correctly configuring the path parameter of the gallery module. Prior to enabling any blocks, go to administer/settings/gallery in the navigation menu, and fill in the "Location of Gallery2" field. The path required seems to be the relative path from the drupal root directory to the gallery2 directory. For me, that's some horrible thing with lots of ../../../ involved, so I just symlinked gallery2 into the drupal directory, which seemed to work.
While you're here, remember to check some of the "Image Block" and "Show" checkboxes, or things won't work.
It's a pretty evil error, though, drupal blows up completely if it hits it. You can set the status of the gallery modules in the mysql blocks table to 0 while you fix it.
I can reproduce this bug in the same way. Not knowing that I had to configure gallery.module under settings, I immediately went to the blocks and saw the same error after enabling them.
Since there is no more activity here, Gallery 2 is out, Drupal 4.6.3 is out and gallery.module was updated by Walkah a couple of days ago, please update everything and try again.
Comments
Comment #1
(not verified) commentedThis seems to be caused by enabling a gallery block without correctly configuring the path parameter of the gallery module. Prior to enabling any blocks, go to administer/settings/gallery in the navigation menu, and fill in the "Location of Gallery2" field. The path required seems to be the relative path from the drupal root directory to the gallery2 directory. For me, that's some horrible thing with lots of ../../../ involved, so I just symlinked gallery2 into the drupal directory, which seemed to work.
While you're here, remember to check some of the "Image Block" and "Show" checkboxes, or things won't work.
It's a pretty evil error, though, drupal blows up completely if it hits it. You can set the status of the gallery modules in the mysql blocks table to 0 while you fix it.
Comment #2
Steven Mansour commentedI can reproduce this bug in the same way. Not knowing that I had to configure gallery.module under settings, I immediately went to the blocks and saw the same error after enabling them.
Comment #3
alexandreracine commentedSince there is no more activity here, Gallery 2 is out, Drupal 4.6.3 is out and gallery.module was updated by Walkah a couple of days ago, please update everything and try again.
Closed.