• Since the upgrade to version 2, Nextgen Gallery isn’t usable any longer. Here at the support forum, you always tell the users, that it might be a problem of the blog itself, server configuration, etc.

    But that’s not the way to solve. The most problems come from your programming… I updated the plugin on 10 different WP Installations and I have nearly the same problem on every installation… so, I don’t think, that it is my configuration… Ten different WP-Installations on different servers, etc. I just wanted to buy the pro version, but after reading all the error entries and the discussions, I won’t… I just rolled back all the installation to the 1.9 version… who’s paying the time I lost ???

    1. Problem: On the startpage, when you display a list of the last blog entries, Sourcecode is displayed instead of the gallery. (Reading all the entries in the support here, a lot of users seem to have the same problem)

    2. Read this silly error message. It tells me, that my css is not in a safe place and gives me the advice, to put it to this place… ?!?!

    nggallery.css is currently stored in /wp-content/themes/theme1768/nggallery.css, which isn’t upgrade-safe. Please move the stylesheet to /wp-content/themes/theme1768/nggallery.css to ensure that your customizations persist after updates.

    3. Going to the nggallery admin menu, the following error message occurs…
    Warning: Invalid argument supplied for foreach() in /wp-content/plugins/nextgen-gallery/non_pope/class.nextgen_style_manager.php on line 205 Warning: Invalid argument supplied for foreach() in /wp-content/plugins/nextgen-gallery/non_pope/class.nextgen_style_manager.php on line 205

    This Error also can be found in any installation…

    http://wordpress.org/plugins/nextgen-gallery/

Viewing 7 replies - 1 through 7 (of 7 total)
  • Jimmy

    (@jimmy-godin)

    I agree, I had the same problems on 2 installations, I downgraded to 1.9.13. I think the number of errors is too large and too many users have too many problems. This is not a good sign, therefore I downgraded and come back in a few months.

    Best solution is to stay in 1.9.13 … wait until this support forum is free of major complaints. Even plugins supporting Nextgen like Justified Grid recommend not to upgrade Nextgen yet …

    Thread Starter netmorix

    (@netmorix)

    It’s a shame that a really good tool like NGG ist now falling victim to new business models, which need to be quick realized…

    I’m still fine with Nextgen, as a backend tool that is. I have checked their pro version demo, not interested as one cannot pinch images to enlarge or decrease size at will on a mobile phone with their offered galleries. It’s no good, mobile usage is power these days, and imagine an application where one cannot pinch an image, it’s primitive :-). We can always ask our viewers to bring their own magnifying glass of course attached to their phone. Best to use the free Nextgen and link with another good “Lightbox”.

    So will still use 1.9.13, nothing wrong with it, and hope Nextgen guys will be able to fix it before WordPress rolls out another new WordPress version that will finally break 1.9.13. So far, still good even with latest WordPress.

    I get the same symptoms as netmorix.

    I got that when I updated to 2.00 and reverted to 1.9.13 awaiting a later release in the hope that it would be resolved. Alas, still the same problem.

    I use the MEGAZINE theme.

    I’m curious is ANYONE is successfully using 2.0 and above. What a mess it is! Thankfully, the rollback when without a hitch and my nextgen is back to its former glory.

    Hope they get it fixed (and get my back my “go to gallery” link post uploading!)

    I also wish they’d give an option for galleries in alphabetical order in the dropdowns. 🙁 But no sense in asking for that until all the other probs are solved! 😀

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    JSF1000: 2.0 works for me on 5 sites. 2.0.7 broke 4 of those.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘A lot of errors’ is closed to new replies.