@photocrati – as adsoink writes the problem is that the slash isn’t inserted by default (fresh install) in the Other Options.
additional to that new galleries created from Gallery > Add Gallery / Images stores an absolute path to the new gallery (ex. on local machine) “D:/xampp/htdocs/test/wp-content/galleries/first”
galleries created from Gallery > Manage Galleries stores an relative path ex. “wp-content/galleries/second”
Tested with WP3.6 NGG2.0.2 beta
@photocrati – (Running WP 3.6 and Nextgen 2.02.)
1-the pictures in the nextgen widget in the sidebar are not sharp anymore? In 1.9 they are oké.
2-clicking on the picture i get a new window, but cannot go back to the original site by clicking on the picture again anymore?
3- i frequently use the nextgen galleryview plugin, is there a similar option in 2.0?
Hi,
just did the double upgrade. Now running WP 3.6 and Nextgen 2.0.
All seems fine but when trying to view galleries on posts & pages, I get an error instead:
no images were found
Albums display fine (http://www.airboatafrika.com/see-airboats/)
and I can insert new gallery into a page, and access galleries via ‘Manage Galleries’.
So not a database issue?
Somehow Nextgen 2.0 cannot find galleries anymore.
Theme is Suffusion – 3.9.2.
Tried the usual deactivate/reactivate plugins and theme switch. That’s not it.
Any tips on what else I can check / modify?
Merci!
Just tried fresh install of 2.0.2 on my 3.6 WP with new default theme.
Still effects the same – galleries showing simple images in one collum, no frames, shadows.
“Settings” and “add images” pages render empty.
Turned on debug and error logging – no single error line regarding nextgen code.
br, pawel
Hi again,
did some more searching.
Determined the problem to be in the ‘Gallery Settings’ option.
I choose to display 21 images per page to reduce load times.
That’s when the error ‘no images were found‘ is generated.
When choosing to display all images (=0), then all images are displayed correctly. But now pages are very slow to load!
That seems like a code error to me.
Please fix in your next update. Merci.
Thank you all for coming back and giving us information. What will be the most helpful for us, is if you could submit a bug report which will go directly to our developers, through the form here: http://www.nextgen-gallery.com/report-bug
Please include:
– NextGEN Gallery version number( if beta, please include Beta v2.0.x in your report)x being the beta version
– WordPress version number
– Detailed description of the error you’re seeing and steps to replicate the error on your site
– WordPress & FTP login information (this will be VERY helpful for our developers to find a solution, if you’re comfortable allowing us to login) *PLEASE do not reply with login information here in this forum.
Also, I’m wondering if any of you wouldn’t mind temporarily deactivating all plugins (including NextGEN) and then clear your browser cache and reactivate NextGEN Gallery only. Does that help? If not, would you also mind temporarily switching to a WP Default Theme like Twenty Thirteen and see if that helps? I know this is an inconvenience, we’re very sorry. But it would help us diagnose if this error may be a plugin/theme incompatibility.
Please include your results in the bug report.
Thanks!
-Becky
@vesat, @photocrati: I know that the original shortcode should work. The problem is that with the old version of NGG it was given to us on creating a new album and all I have to do is copy/paste the shortcode into the editor (Windows Live Writer) without remembering the exact shortcode and without having to dig deep in search of the id number.
With 2.0 on creating a new gallery you just upload pics (actually both actions are merged in one place in 2.0) and you are not given any code or even an id. In order to find the id you either have to remember the previous id or do 2-3 more clicks (1. Manange albums. 2. Last page (as the order is ascending rather than descending. There you get the gallery ID).
What I meant is that the new interface in this respect is user-unfriendly. That (and my other two issues) led me safely back to 1.9.13 and from what I am witnessing I have no intention of upgrading for another three or five versions in a row to avoid all the stress.
@photocrati: I have no Contact Form or MapPress plugins at all. I am with Bluehost and it says Linux as OS.
Hello,
I have WP 3.6 and installed NGG 2.0.2 and have lots of “bugs” (40 or more) on screen like this:
Strict Standards: Declaration of Hook::call_parent() should be compatible with Mixin::call_parent($method) in C:\xampp\htdocs\work\Blaster\wp-content\plugins\nextgen-gallery\pope\lib\class.extensibleobject.php on line 1377
The WP is in DEBUG mode.
Will be this “problems” solved?
@piotrbesta – Do those errors still appear with all plugins (except NextGEN) deactivated? Which browser are you viewing your site in?
@samaralife – Thank you very much for your feedback. I’ll pass along your feature request to the development team, to have more display info for shortcodes in the ATP. Our intention is to produce an interface that allows you to quickly and easily add galleries and manage those galleries in one location rather than have to switch screens. You present a valid point about those who are used to and prefer using shortcodes. If you have any further thoughts or feature requests, please feel free to send those directly to us here: http://www.nextgen-gallery.com/contact
Thanks!
-Becky
@photocrati – My browser is Google Chrome. Yes, these “errors” are displayed after NGG activation. And only if NGG is active. I think there are some inaccuracies in inherited methods redefinition (function signature). The function signature should be identical like from inherited class. E.g in NGG file named class.extensibleobject.php.
@piotrbesta – If you haven’t already, would you mind submitting what you have found in a bug report to our developers here: http://www.nextgen-gallery.com/report-bug . That’ll be the quickest way to get those findings in front of our developers to resolve in an update. Sounds like you are working on a local install? Do those errors still appear on a live production site?
Thanks!
-Becky
@photocrati – I send this information via your bug reporting page. Yes, I use localhost XAMPP server for testing projects. Not tested on live server, but the “bug” log description show that the problem is inside NGG code.
@piotrbesta – Thank you for submitting the bug report! If you happen to get a chance to test on live production server, we would be curious to know if the errors persist there as well.
Thanks!
–Becky
@photocrati
Using WordPress multisite 3.6
Tried v2.0 and Beta 2.2 of your plugin.
Getting errors like:
Warning: Invalid argument supplied for foreach() in /wp-includes/query.php on line 1702
Caused by your plugin I believe. When disabled, errors disappear.
Update on 2.0.2 does not work?
My problem with 2.0.0 is this:
Not one gallery can be opened anymore. When users klick on a gallery it says “content not found”.
I tried to update to 2.0.2.
– Downloaded the Hotfix
– Deactivated NextGen
– Uploaded the Hotfix with Filezilla FTP (no problems, worked all)
– Re-activated NextGen
– Cleared Browser Cache
In my wordpress Dashboard it tells me I am still on 2.0.0!! And the problems have stayed.
What did I do wrong with the Update?
