NextGen gallery: Singlepic: Alt-text displayed. No image.

Thanks, beernews!

Just got the same problem and editing my .htaccess did the trick! Weird thing is that this problem really happened all of a sudden, I didn’t change my .htaccess for a while, or added new plug-ins.

I had the same problem, but wasn’t using rewrite and had no .htaccess.

I debugged the code and replaced in
nextgen-gallery/view/singlepic.php
in line 20
[…] src=”<?php echo $image->thumbnailURL ?>” […]
by
[…] src=”<?php echo $image->thumbURL ?>” […]

somehow there was no thumbnailURL in my $image object…

Also tried all previous suggestions
– disabled all plugins
– changed theme (even used classic and standard WP)
– removed blank-lines in php files (maybe to avoid header-sent-bugs?)
– checked database-structure

WP Version 2.7
NGG Version 1.1.0 (german translation)

@juro83: Danke, deine L?sung hat mich vom Basteln erl?st!
I had also tried all the suggestions you named but without any result.
Your solution finally did it: Thumbnails are displayed using [singlepic]
I don’t understand the way you figured out this, but maybe it is a bug that should (and is easy to) be fixed? v.1.2. is just before release…

@michelalexander: np – bin froh, wenn ich helfen konnte ??

I’m used to php, and NextGEN is well programmed and commented. Just not sure, if my solution ist correct, because maybe thumbnailURL should be some kind of temporary/dynamically created thumbnail in the given size instead of the precreated thumbnail.
I think the real bug is somewhere else where thumbnailURL is set to some php-script that creates a thumbnail with given parameters.

I had some extra white space somewhere, I think. I tried pasting the singlepic url with nggshow in it, directly into the url bar and got a header error. Told me there was something being sent to the browser before the image.

I don’t know exactly where it was since I did so much, but it was in nggshow most likely. After messing around, and re-uploading files, it suddenly started working.

hmm … now I’m really confused. A few hours ago I was just happy to see some pictures using [singlepic] but Juro83 is right: changing singlepic.php as he described is NOT the correct solution because instead of the picure its thumbnail is displayed. Changing its size via w=xx h=xx doesn’t work, too. Clicking on the thumbnail opens the right picture in the right size.
How can I help solving this issue? I’m not used to php so I don’t know where to start exactly.

A few minutes ago my hoster deactivated php’s safe mode and everything works fine now – maybe this might help others, too (maybe not).
But thanks for your help anyway!

safe mode=off might help.
I could deactivate it, but I don’t want to, cause I don’t trust the installed plugins and themes (always remember: themes and plugins with bad code can open doors to hackers) nor do I trust the server security.

In my case – I don’t need singlepic anymore. I wanted to create an own imagebrowser with per-picture-comment, but now i just took the html code and don’t use singlepic.
perhaps with safe-mode=on one can get it to work by switching to the other image-library…

I have the same problem as that described by Juro83 above.

I upgraded yesterday from 0.91 to the current version and all my singlepic requests now fail using the older shortcode:

[singlepic=2689,250,,,right]

The @href, @title etc are all correct in the A:element but the img:element has no value for @src. At the time of writing, you can currently see this problem here:

https://www.mikepadgett.com/travel/europe/monschau-and-vogelsang/

As michelalexander points out, changing thumbnailURL to thumbURL doesn’t take account of any width and height settings in the original shortcode request because (I assume) it just calls the thumbnail used in the admin section.

I’d like to be sure that support for ‘legacy’ shortcodes could continue rather than having to change 100s of posts, but can we address this?

Any thoughts, Alex?