Comments on: Drupal, Gallery2 integration, and a recent module update

By: matthew

matthew — Mon, 25 Feb 2008 18:28:42 +0000

The latest 5.x-2.x-dev version of the gallery module fixes the problem. A new "stable" release is expected shortly.

By: matthew

matthew — Sun, 24 Feb 2008 03:29:52 +0000

hQuadrat: thank you for pointing to that solution. It seems to have taken care of the problem on my site.

For everyone else, the solution for the moment is to change the top line of gallery.module to read

if (function_exists('drupal_get_path')){ require_once(drupal_get_path('module', 'gallery') .'/gallery_base.inc'); }

This test is a good workaround that allows the site to work with the performance cache enabled. It's not a perfect solution, as we still get errors in the site log. I know the devs are working on the issue and hopefully they will be able to get a better solution written in to a new release shortly.

By: hQuadrat

hQuadrat — Sat, 23 Feb 2008 20:28:26 +0000

Hi there,
had the exactly same issue with the gallery.module v. 5.x-2.1.
Look back at the thread you had commented on, comment #6:
drupal.org/node/224598#co...

You just have to add two lines to gallery.module and it should be working again.

Greets, hQuadrat

By: matthew

matthew — Sat, 23 Feb 2008 19:32:45 +0000

Okay, I get what you mean. I cleared the cache tables in the database and it had no effect on the issue. I still get the error if the Drupal performance caching is turned on, and the error disappears if the feature is turned off.

That was a good idea to try though. Thank you.

By: Andrew Zajac

Andrew Zajac — Sat, 23 Feb 2008 19:05:50 +0000

You can run:

DELETE FROM cache;

Or simply empty the tables by hand from phpmyadmin. I have had to clear the views cache like that, too.

By: matthew

matthew — Sat, 23 Feb 2008 13:10:51 +0000

Hi Andrew.

If you mean the local browser cache, yes.

If you mean the Drupal cache on the server, I have only done what I described in in the post and comment #1. Is there something further I can attempt?

By: Andrew Zajac

Andrew Zajac — Sat, 23 Feb 2008 13:00:33 +0000

Have you tried clearing the cache?

By: matthew

matthew — Sat, 23 Feb 2008 09:16:45 +0000

I have commented on an existing bug, that I believe is identical, on the drupal.org site at drupal.org/node/224598#co... .

By: matthew

matthew — Sat, 23 Feb 2008 08:59:37 +0000

Something to add… Re-enabling the cache causes the error to reappear, so this is repeatable. I am currently unable to use caching on the site in question. Again, that site has very little traffic, so it isn’t a big deal, but for large traffic sites, the problem could remain.