Known Plugin & Theme Conflicts with NextGEN 2.0

@bushidopt : NG 2.0 works well for me with Advanced TinyMCE. (but not with CKEditor)

All very helpful information! Please continue to submit these through our bug report form as well: https://www.nextgen-gallery.com/report-bug

Thank you!!!

–Becky

In any post, when you select text and want to link it to a URL, you’d normally click the LINK button. This is grayed out for me and I cannot click it.

If I deactivate NextGen 2.0.0 than it works just fine again

We did, however, also release a public beta version of NextGEN 2.0. It was available for a month, shareed via blog/email/social media, and downloaded over 1000 times. We got a lot of public beta testing feedback. A lot of the feeback was very positive, and most of the issues were relatively minor. No public beta testers reported the kind of significant conflicts we’ve been seeing here.

Given the public beta testing results, I must say we were surprised at what at the volume and severity of some of the issues and conflicts, and wondering why we didn’t see more indications of this from public testing.

Your beta gave no indication that this was going to happen fairly quickly, and your warning basically said “don’t even think about using this on a production site”, with as long as it took to issue updates since Photocrati took over the project, and the verbiage about the upcoming “Pro” version, which implied it would come along after a release .. that pretty much gave the impression that this testing period was going to go on for a while.

I am using NextGen with Theme David/Paige by WordPress for Artists and the plugins, Jetpack, WordPress SEO and Portfolio Slide Show. Version 2.0.0 did not read css for the lightbox and lost the thumbnail layout. I did not look at the admin area. I have successfully rolled back to 1.9.13

Hey,

New conflict with the plugin: WP-PostViews.

When NexGen Gallery is activatated, the plugin stopps working and doesn’t count the views anymore. If NexGen is desactivated, it works.

When do you think you will be releasing the new version?

as tdiaz has commented, the beta testing was poorly managed.

Normal practice for well organised beta tests is two or three betas, followed by one to three Release Candidates. No-one familiar with beta testing puts anything before the Release Candidates on a live site.

Now obviously photocrati wouldn’t have the same level of resources, and so might not be expected to go through such an exhaustive testing sequence, but at least one release candidate would have been good practice.

WP Clean Up plugin, after pressing the OPTIMIZE button, the error appears on the gallery page.

array(1) { [“display_type”]=> array(1) { [0]=> string(20) “Invalid display type” } } Invalid Displayed Gallery

Solution: downgrade to NexGen Gallery 1.9.

Word Press Image Store. https://xparkmedia.com/support/plugin/image-store/ WP Site https://www.ads-software.com/plugins/image-store/

This plugin pretty much breaks the gallery and ability to open, select, view photos in this client plugin for proofing/ purchasing photographs.

Disabling the NextGen Plugin Did nothing to fix the issues with my other plugin.

Additionally on my site after installing this with the HER Theme the columns are not displaying in rows/ columns correctly.

I can give access to my test site if needed.

@rtb1982 –

I’m so sorry to hear about this. Yes, we’d love to check this out. If you wouldn’t mind sending in your login credentials and as much information as you can about how to replicate this issue, and the steps you’ve already taken to troubleshoot, in a bug report to us here: https://www.nextgen-gallery.com/report-bug , we’ll do what we can from our end to help things be compatible.

Being that this sounds like a live production site, you might consider rolling back to v1.9.13 until we release our next update, see: https://www.nextgen-gallery.com/how-to-rollback-a-version/ . We hope to have the next update available by the end of this week. When you send us login credentials, if you’re willing it would be best and ideal to login to a test site if you have one available with the same setup where the issue is present.

Thanks!
–Becky

ATM I must admit I’m a bit confused about what to do. My site is functional, but has some issues (that I’ve mentioned here already) which are problematic, but certainly not fatal. A member here has written that a roll-back did not work for them. I’m now not so sure that rolling back to the previous version will fix my problems–perhaps only make them worse.

Do we have any kind of time-line of where things are at, and when this cluster-f!*# might be heading towards some kind of resolution?

@puda – We hope to have the next update available by the end of this next week. We’re doing some internal testing and verifying all major known issues are resolved. We deeply appreciate everyone’s patience and understanding. It’ll be a long process to work towards compatibility with all the several plugins and themes available, but we’re tackling the most widely used and popular ones first. Please keep sending in your findings through our bug report form here: https://www.nextgen-gallery.com/report-bug . This way our developers will for sure see them. If you’re willing to allow us to login, that will really help. Please note we’ll be very respectful of your site when logging in.

Thanks!
-Becky

Also conflict with Pagelines 2.2.4 (haven’t tried with new Pagelines DMS). Seems to work fine on the front-end but white screens in most of the Gallery admin. Have to switch themes to Twenty Twelve to be able to administer the galleries, then back to Pagelines.

Please Please Please fix the conflicts with Contact Form 7 & Magic Fields. I use these plugins a lot, along with NextGEN Gallery for almost all of my projects.

I’d be happy to assist with testing if you provide patched versions with fixes for these.

Thanks!
Jake

This plugin has a negative effect on the Photorific wordpress theme also. When activated it will disable the background slider on the homepage as you stated before, AND it will remove all background images from each page. Any luck on fixing that bug?

Thanks