Closed (fixed)
Project:
Gallery
Version:
master
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
8 May 2005 at 17:39 UTC
Updated:
17 Oct 2005 at 22:34 UTC
I am running drupal 4.6. I tried installing the gallery module, and installed gallery 2.0 from menalto as instructed.
I activated the module, and the gallery navigation block, and nothing happened. No block.
I visited the bug reports list here, and saw a note that this was fixed in cvs. So I downloaded and installed the gallery module cvs version.
Still nothing.
So I went in and tried adding some images to Gallery2 (from within it's own interface), thinking that maybe nothing would display in the drupal gallery module if there were no images.
Still no dice.
So... is there a way to get this to work?
Coyote
Comments
Comment #1
kiz_0987 commentedYes, the gallery module does work in Drupal 4.6.0 -- I have been using it for a while. A few questions for you:
- Does your gallery2 installation work? When you uploaded your images were you able to see them in a non-embedded gallery2?
- What is the directory structure you have set for gallery2 and drupal? (eg /gallery2 and /drupal or /drupal and /drupal/gallery2)?
- What are the admin settings for gallery? "admin/settings/gallery"
- Do you have a link of your site (is it publicly accessible) so that I can take a look?
K
Comment #2
zhasper commentedI'm having the same problem - not getting any of the blocks showing.
My gallery is working fine on its owh (http://z.com/gallery)
My drupal is at http://z.com
(I'll send you real links in a private message, I don't want to display them here)
Location of gallery2 setting is set to "gallery/"
Any suggestions on what I'm doing wrong?
Thanks!
Comment #3
zhasper commentedWell.. this won't help anyone else, but I figured out what's wrong with mine..
I'm using gallery 1.5, not gallery 2.
Duh.
So I'll just crawl back under my rock..
Comment #4
Coyote commentedI reinstalled from scratch, with the gallery database the same as the Drupal database, figuring that I'd probably had a "duh" moment in giving it its own database.
Which might indeed have been a problem...
(In my defense: The gallery module looked so small that I assumed that it allowed Gallery to make all it's own connections, and that it could be in it's own database.)
But fixing that didn't cause the blocks to appear.
I went in and manually activated and deactivated the blocks, at which point I was able to get the "random image" block to appear. Curious, thought I. That showed up, but no gallery navigation menu.
But when I clicked on an image to view an album.. _then_ the album navigation block appeared.
And then I figured it out. No menu item was enabled to access Gallery, and the nav block only appears when you have accessed/clicked on ?q=gallery
Okay... I do feel silly for not figuring this out sooner. But a note (perhaps in the install file) explaining that no gallery navigation would be visible without actually trying to visit a gallery (and telling the user to make sure they enabled a link to the gallery module) would have been nice though. For us silly people. : )
I do have to say... one of the things that is most incredibly frustrating about this module is the utter paucity of documentation. I really don't have any idea what the module's features actually are. Finding them out through trial and error, and by trying to read the module's code (when I'm not a Drupal developer and am very unfamiliar with how Drupal itself is structured) is sort of nerve-wracking.
The install documentation (the only docs I can even find) basically say "1: install this and 2: It might not work"
I mean, a _little_ more than that would be nice. Just a list of features would help me figure out what I'm doing, without me worrying so much that I'm going to blow something up.
Comment #5
zach harkey commentedUhhhhh... wait a minute. I thought Gallery 2 was supposed to be installed separately and independently of drupal, meaning that it should have its own database. Was I supposed to use the same database as Drupal? Why does that scare me.
Comment #6
kiz_0987 commentedGallery2 and Drupal would normally be set up with separate databases. I would certainly recommend this route rather than try to lump them together.
Comment #7
Coyote commentedThe tables appear to have all-unique names, with their own prefixes, and _appear_ to be able to co-exist in the same database. I've got it working on my dev server.
I'd _prefer_ to have them in seperate databases, myself. : ) I'm going to try a re-install with them in seperate DBs. Putting them together was just one of the things I tried while going crazy attempting to get this thing to work at _all_.
Remember though, there's probably lots of people who only have access to a single database available to them. Not everyone has hosting that allows them to make their own seperate databases. Many hosting accounts give you a single database to work with, or charge you for multiple database setups. It's good if people _can_ put all the tables into a single database if they _have_ to.
Comment #8
snellgrove commentedI can get my gallery to appear embedded, when I have clean URLs disabled and manually typing in /?q=gallery
the block does not appear and the gallery doesn't really work when clean URLs are enabled
Comment #9
raverX commentedI had attempted to get Gallery2 to run with Drupal 4.6.2 and the stable releases of the gallery module without any luck, so I figured I'd update to the CVS of Drupal and the Gallery module - same problem.
The errors I'm getting are:
Any assistance with this would be GREATLY appreciate :)
Comment #10
igy-1 commentedSame problem, with drupal 4.6.2, gallery2 from CVS and gallery.module from galleryupdates.jpmullan.com/
HELP!
Input Array does not match ?: SELECT DISTINCT g2_AccessMap.g_accessListId FROM g2_AccessMap WHERE (g2_AccessMap.g_userId = NULL OR g2_AccessMap.g_groupId IN (1)) AND g2_AccessMap.g_permission & 1 =
user error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 10
query: SELECT * FROM blocks WHERE status = 1 AND region IN ('1') ORDER BY weight, module in /var/www/drupal-4.6.2/includes/database.mysql.inc on line 66.
Fatal error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 10 query: INSERT INTO watchdog (uid, type, message, severity, link, location, hostname, timestamp) VALUES (0, 'php', 'You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near \'\' at line 10 query: SELECT * FROM blocks WHERE status = 1 AND region IN (\'1\') ORDER BY weight, module in /var/www/drupal-4.6.2/includes/database.mysql.inc on line 66.', 2, '', '/', '217.114.173.139', 1121265771) in /var/www/drupal-4.6.2/includes/database.mysql.inc on line 66
Fatal error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 10 query: UPDATE sessions SET uid = 0, hostname = '217.114.173.139', session = 'messages|a:0:{}', timestamp = 1121265771 WHERE sid = '3386b8a6b962f821c0f054f527479017' in /var/www/drupal-4.6.2/includes/database.mysql.inc on line 66
Warning: Unknown(): A session is active. You cannot change the session module's ini settings at this time. in Unknown on line 0
Comment #11
yaus8154 commentedIf you got the input array does not match error, you can try to look for the line in gallery.module:
make it $full = true should do the trick. It work for me in Gallery2 b4.
Comment #12
ergophobe commentedThis thread is now on the same topic as
http://drupal.org/node/21290
perhaps comments RE Gallery Block and the SQL errors and so forth should henceforth go there.
Comment #13
alexandreracine commentedPlease update the version of this module, drupal, and try again.
For the random image block issue, get the fix here. http://drupal.org/node/31398