I’ve got the exact same problem. Whereever I go, the singlepic shotcode returns the picture with the lowest pid in the database. My DB is optimized and there are no errors in it.
What could it be and more importantly: how can it be resolved?
– Rogier
The problem is due to an NGG bug, but there’s an easy workaround until it’s fixed. The Photocrati folks are already aware of the bug.
Visit Gallery->Other Options and be sure the Sort in what direction? option is set to Ascending.
If it’s set to Descending, NGG grabs the image with an ID=1, and displays that for all uses of the shortcode displaying a single pic.
Given that NGG is an extremely popular plugin, unless you are one of the 1st to adopt a new version or the bug only applies to an edge case applicable to you, it’s something that others have probably already come across and resolved. A thorough search of this forum would have yielded threads that explain what I repeated.
Hope that helps.
I’ve been using NextGen on my site for 4-5 years and updated the plug-in when WordPress plugin manager told me there was a update for it. The ‘fix’ above has corrected the problem on my site temporarily so thank you very much for that but I didn’t find the fix even after searching the forum.
best regards
Kev Lewis
@frisco,
Nope, this didn’t fix my problem. Also, this isn’t the bug I’m referring to. NGG does _not_ grab a picture with pid=1, since there is no picture with such id.
Do you really think I didn’t search the forums for this? I have tried almost everything and still NextGEN Gallery doesn’t display the correct images, whatever I have tried.
I’m now on 2.0.65, which does display my pictures. I’ll try updating the plugin when there is a new version available. Until then, I consider 2.0.66.17 ‘broken’.
– Rogier
Do you really think I didn’t search the forums for this?
Your comments in 3 different threads over a short period so soon after joining these forums relating to the same topic led me to the conclusion that you didn’t find the previous discussions and were probably frustrated.
If you found them and we’re aware of a separate issue that you don’t think is related to your problem, it’s important for you to provide that information – that you are aware of the other issue, tried the already-reported techniques to fix it, and they didn’t work for you. That’s basic troubleshooting. Otherwise, every new issue starts with a rehash of what’s already been covered, which is a waste of time.
Your problem might be a separate issue, and it will get fixed faster if you provide all the relevant details of what you investigated in your effort to resolve it in 1 separate thread. Not providing the details only makes it more likely that the particular bug you experienced doesn’t get fixed.
I can understand why you think that; I first searched the forums and when I wanted to reply, I registered. I now realize me responding to 3 posts wasn’t the best course of action. I guess I did post them out of frustration.
– Rogier
@frisco – Thanks for your time and explanations!
@photosbykev – Yes, this is a known issue and @frisco has provided the work-around. I’m glad its helping you in the short-term.
@rogiermaas – If @frisco’s work-around did not help, then as they suggested it could be something different affecting your site. We will try to address this difference and as suggested it would be best in a new topic.
Thanks!
– Cais.
@photocrati – No prob.
@rogiermaas – We all get frustrated from time to time. No worries.
@rogiermaas & @photosbykev – Since both of you looked for this issue and didn’t find it, it might be helpful to take a step back and explore how to look for things here. Use regular Google search. If your issue is a new (such as with a plugin update that just came out), set the last update in Google search to past month. Set the site to wordpress.org to just get results from the WP site. Finally, search for the plugin name and a few words that might be specific to your issue. In this case, that word is singlepic. It’s better to start with fewer words and refine it with more words if the results aren’t relevant.
Here’s my Google search for “nextgen gallery singlepic” for results on WordPress.org in the last month.
https://www.google.com/search?as_q=nextgen+gallery+singlepic&as_epq=&as_oq=&as_eq=&as_nlo=&as_nhi=&lr=&cr=&as_qdr=m&as_sitesearch=http%3A%2F%2Fwordpress.org&as_occt=any&safe=images&tbs=&as_filetype=&as_rights=&gws_rd=ssl
The SERP shows a couple of results that indicate this is a problem since .16 was released and include the tip that I repeated above.
Hope that helps.
@cais: Thanks. I searched using Google like I always do and I’ve seen all the posts regarding this problem.
The suggested action did nothing for me. Changing the sort-order into anything keeps displaying the same picture – the one with the lowest pid. I’ll keep an eye out for solutions.
– Rogier
@frisco
It’s strange that you say it’s a known problem since .16 because the problem didn’t occur on my site running .16 where I did have the sort order set to descending (I’ve always used this sort order with the NextGen plugin) it only raised it’s head when I installed .17 version.
regards
Kev
@photosbykev – For us and others reporting here, the problem does occur in 2.0.66.16 but did not occur in 2.0.66. If you repeat the search I linked to above, you’ll see that it was reported by others for version .16 at the end of July.
I can’t speak to why .16 worked for you, and I haven’t had a chance to run a diff on .16 compared to 2.0.66 to see what broke.
The sort option is a relatively new option to NGG. IIRC, it got introduced around 2.0.40, but that’s just a guess. If your first install of NGG was after the introduction of the setting, it may be that your settings are different from those who upgraded from older versions.
Hopefully, the NGG folks get it sorted out quickly. The descending sort option is useful when it works.
My first installation Of NextGen was back in the days of the original software author Alex, maybe 5 years ago. I was a fairly early adopter of the plug-in as Alex provided some significant support to get my site live.
regards
Kev
