Recently I have notice the problem with search. I remember clearly that I did not have that problem before and I do not know if it is connected with the recent upgrade of MySQL, PHP, Gallery, Drupal or else.

I have all the latest versions of Drupal, Gallery and the Gallery module. Here is more information:
Drupal 5.1
MySQL database 5.0.27
PHP 5.2.0
Web server Apache/1.3.27 (Unix) (Red-Hat/Linux)
Gallery version = 2.2-rc-2 core 1.1.30

Also I have URL rewrite in both Gallery and Drupal
The 'Show Item' rule is set to: gallery/%path% as described in http://codex.gallery2.org/Gallery2:How_to_Embed_Gallery2_in_Drupal#URL_R...

This way you have a beautiful paths like http://your_site.com/gallery/album in Drupal, or http://your_site.com/gallery_install_folder/gallery/album as a standalone.

If I use the Drupal Search module to find "album_name" then the result page contains three tabs: Content, Gallery, Users. Once I click on Gallery I have the following error message
"Unable to initialize embedded Gallery. You need to configure your embedded Gallery."

This issue seems to be connected much with the http://drupal.org/node/108422.

If you look into the logs then you can see that the problem is with the link
http://your_site.com/search/gallery/album_name.

To resolve the problem I just need to replace gallery/%path% with, say, gallery1/%path%, or anything else in the Gallery module settings.

Seems to me that I can not use 'gallery' anywhere in the URL except right after http://your_site.com/. Otherwise it does not work.

But the thing is that it worked before. I do recall any problems with gallery search by means of Drupal, and I did not have any 'v/%path%' or other not good looking settings.

Can you help me to figure out what the problem is, please? What did trigger it?

Comments

kylehase’s picture

Same problem here.

CentOS 5
PHP 5.1.6
Apache/2.2.3
mod_rewite
Gallery 2.2.1
Drupal 5.1
Gallery Module 5.x-1.0

profix898’s picture

Component: Code » Code / API
Status: Active » Closed (fixed)

Thats not a bug in the module, but simply a configuration issue (see http://drupal.org/node/193152#comment-635221 for details). Closing.