There are no images in this gallery.

Have you added the imported images to a gallery?

Those queries don't look like the image_gallery_page function in image_gallery 5x-1.9, which go 'SELECT n.nid FROM {node} n INNER JOIN...'. There is no LEFT JOIN in the module. You sure you don't have a wrong/different version, or the function redefined in template.php or something? Or maybe they're from your testing of '2-alpha, which I know nothing about...

i have no clue what the issue is but im in a fat bind!!. most of my websites run the most cutting edge drupal with all the newest modules and on all the others it (Image) works fine but im using the 5.x to whatever alpha and drupal 5.10 and i have imported almost 250 images, when i goto view the gallery i get a page that is titled "Uncatagorized" witha body message that says there are no images in this gallery. the websites url is tudorlaneexpress.com check it out and see what i mean...

(Fixed the title of this issue...)
OK, go check that you have only ONE of each of the image-related modules ... rename all duplicates to module.bak or something.

Frank.dev: that sounds like a different module interfering - not image.module.

If you use views, your best bet is to use the views-based gallery; it gives you lots more options.
If you don't have views installed, image defaults to its own image gallery.

So that's by design.

Hi Hetta,
I did not undestood your comment.
I'm facing the same problem as you can see on my post here:

http://drupal.org/node/296929#comment-1044434

Actually my default view image_gallery is enable and overriden (maybe I made some modification for desperation) so the disable option it's not present at all. How can I disable this view?
Given that I have views installed how can I use them insted of the image gallery?
In my installation if i create a gallery then a taxonomy term under Image Galleries is automagically inserted and again if I create a taxonomy term for Image Gallery vocabulary then a newgallery gets created.
Should I remove the default Image Gallery vocabulary?

I think is a duplicate of http://drupal.org/comment/reply/296929/1044434 but at this moment I'm ot sure if it's a bug of image gallery or the documention is misleading in some degree

Davide

Whoops meant to post this here....

I am having the same issues.

I had about 10 galleries, with upwards of 60-70 images in each gallery (yah that's like 600-700 images), and I was sitting pretty with Drupal 5.2 (yah I know OLD), and Image 5.x-1.x-dev. But it's stuff like this that really cause me to realize WHY I don't upgrade. I was upgrading for security reasons, and hoping for additional functionality in some of my other modules, but I am no realizing it's not worth it.

Not having this work is a huge PITA. I basically causes me to have to redo or rework a lot of work. Developers of these modules really need to take a working perspective of the uses of these modules. Upgrade paths need to be mandatory. It's not like I upgraded from 4.7!

Back to the issue at hand, I too cannot see the main image gallery listing, nor can I see the individual gallery grids, that are working exactly the same way (with upgraded modules of course) on my pre-upgrade install.

I even downgraded image, and imagecache, as well as image api in hopes that this would all revert to a "working" configuration, but alas the problem is persisting.

This is the one hold up in going to the upgraded version of the site.

I am wondering if this is a views integration issue.

I would say this is a VERY CRITICAL issue, if a very fundamental function of the module is not working at all.

P.S. Unlike the above poster, I am not seeing ANY errors in my logs as to why this isn't working.

Frank.dev, I sympathize with the language barrier here, but I was having a hard time understanding what you meant here.

So heres my understanding and clarification.

I merely upgraded my drupal installation, along with all of the modules I had previously installed. No configuration change was made. I think this is a huge thing for the developer to understand. Things have and were working just fine, but somehow during the upgrade, things don't translate correctly.

Frank.dev is correct, if you go into views, and click "Disable" for the "image_gallery" view, the "view" actually works correctly. Wow as Frank.dev explains, VERY STRANGE behavior. It's using the view, but it's disabled.

So that's my solution, but it's a "broken" solution, and doesn't really help to resolve the issue for others who WILL encounter the same problem.

I don't understand the developer also saying this is by design. It's like saying a pinto blowing up from being hit is "by design", yah it's because it was designed badly and incorrectly. Doesn't make it correct, usable, or logical.

Fix it for the sake of the Drupal community.

It's by design:
EITHER you use the views-based gallery,
OR you use the image-based gallery.
If you use the views-based one, the image-based one won't work.

I don't use views, so haven't followed things all that closely - the newer views APIs have broken views' image setup (including the galleries), but it's possible that that's in D6.

Drewish is the developer ... I just try to help keep the issue queue more or less manageable, mostly by removing duplicates and by explaining things which have been decided months ago to new issue queuers.

What does it means "by design"

If the developer is expecting that users will use image gallery or views, the developer MUST PUT AN ALERT on the documentation page.
Instead you discover the truth only after digging into the issues. This is not the correct way to work on a module. People upgraded for security issues and broke all their work for nothing.

According to Hetta statement (that is true) Image documentation related to image gallery is completely wrong:

http://drupal.org/node/207216

Documentation states that views and image gallery works together that it's completely misleading.

Davide

I concur.

It's not intuitive, it's using the "views" still, it's just not enabled. That sounds broken to me, not "by design".

I agree with Bocio, if I had seen something about this when I went and downloaded the newer version I wouldn't have been so caught off guard. Even so, it still doesn't make sense, it sounds like a "by design" cop out.

I sympathize with your trying to manage the deluge of requests, but tagging this off as "by design" doesn't help others, HELP YOU, HELP EVERYONE try and figure it out. Some of use DRusers also know PHP, we may not be programmers, but I can hack my way through this, and if push comes to shove I figure out a solution to the problem. I may not have the time or resources to fix this problem, but others may have more motivation/time/resources to solve the issue.

How do you not use Views? Views, is like CCK, it's almost a necessary and required module to build even a mildly full featured website. Blaming the issue on the developer of views seems like an all too common, "tech support guy" kind of way of saying 'it's not my fault, and I am not fixing it, or going to try and figure out why it's broken', because that's how all this open source stuff works. I can only assume that the views developer is going to say the same thing and point the finger at the developer of image. Pretty circular if you think about it.

Heh. I don't run either views or CCK, and I run a fully functioning site without them.

You have a large site with thousands if not tens of thousands of nodes (25k), images (29k), taxonomy terms (17k) and visitors a day (15+k), then? And pay less than USD 100 a year for hosting?

If you do, I'd LOVE to hear how you manage things.

If you don't, well, know that on a large site, even with half of the nodes laid down as static and a few other tweaks, a site can crash and burn very easily just by adding one more module.

Were I to add lots of modules, I'd need a dedicated server, and with the size of my site, and the # of visitors, I'd pay about $1000 a month in hosting fees, pretty much right away. I know, cos I asked ...

Hetta, way to get off topic, and detract from the point of this issue/thread.

The point wasn't if you ran CCK or views, but most do, and if your a developer of something that says it integrates with either of those 2 modules, you might want to run them, even in a test scenario to try and make sure YOUR developed module sits pretty.

I think I have made my point here, and I am just beating a dead horse. I am willing to live with the dead views entry, (EVEN THOUGH IT'S USING THE VIEW), but I think others may not put 2 and 2 together to get things working for them.

Thanks for the fix.
Disabling the 'image gallery' view fixed my problem.

I would like to express my anger at the developer for implementing this. I am not a tech savvy person, but I run a website which connects a small community in the remote north of Australia. The site image galleries has been broken for 3 weeks or so now. I have only just found this post on how to correct the mistakes made by the developers of this module.

I appreciate that progress needs to be made on all modules, but before setting the module update to 'recommended' in status update please make sure these types of issues do not occur.

Thanks Frank.dev for the fix.
And please keep making progress with this module. Just warn people they may experience difficulties, and fast fixes for the issues.

Mike

www.goveonline.com

Marking as duplicate of #207371: There are no images in this gallery.