Hi all,
I've configured more than one time the brillant gallery module (on drupal 6) without any problem. today I'm trying to install it on a new work and picasa galleries are not shown. I setted up the right path, the /brilliant_gallery url is working perfectly but I can see no images if I create a page with the right tab [bg|url] (yes, input format set up is correct).
Furthermore, at the top of the drupal page that should include the gallery I have the following txt content (i.e. the README.txt file)

/* $Id: README.txt,v 1.12 2007/12/21 16:25:49 tjfulopp Exp $ */ Highly customizable table gallery of quality-scaled images from multiple defined folders. Installation, demo and tips are all at http://www.vacilando.eu/bg Author: Tomas Fulopp (Vacilando) If you use this module, find it useful, send me a message via http://www.vacilando.eu/contact (and don't forget to include a link to your gallery!) The author can also be contacted for paid customizations of this and other modules. Development of this module is sponsored by Vacilando.org ( http://www.vacilando.org/ )

The problem is not a picasa problem as I can see the same picasa public rss from within other installations.

Comments

veselyr’s picture

Hi, I have simmillar problem, just don't see readme file. Empty page. When linked to local folder BG works fine. When linked to RSS Picasa link nothing appears

vacilando’s picture

Try the same Picasa RSS in another BG v3.4 installation and see if it works.
You can also post it here so that I test on my v3.4.

You can also post a link to the problematic page - if it is on a public server.

I've never heard about README.txt showing up anywhere through a module - most weird! Check your folder settings -- maybe your module folder was set as the image location (but it's a guess).

veselyr’s picture

fitzkarraldo’s picture

sorry,
my error was too strange so I removed the disabled the module, removed the folder and installed it again.
now everything works fine, great module!

vacilando’s picture

Status: Active » Fixed

All right; glad this mystery is solved :-)

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.