@ernietamminga – NGG 2.0.40 works fine on the latest beta of WP 3.8 and Genesis 2.0.X. What you describe as “too huge a headache” is standard debugging practice in WP. You should be able to safely deactivate and reactivate plugins without losing settings, and the bulk options in WP make doing this task on several plugins easy. Here are some tips to make it easier.
1) Don’t deactivate all of your plugins at one time. Instead, do 1/2. If you problem persists, you know the incompatibility is with the half that you did not deactivate.
2) Skip plugins that are not likely culprits. For a plugin like NGG, likely culprits will include plugins that make heavy use of Javascript or that are feature-rich. Simple plugins that focus on doing 1 thing are typically not the source of incompatibilities. If you skip some plugins and don’t find the source of the problem, you’ll have to go back and check those.
3) Know your basic server config details. NGG might work fine with your plugins on my server, but it might not work on yours because of things like too little memory. NGG is a powerful plugin, and powerful plugins consume resources. If you have a lot of big plugins on your site, you may not have enough resources to make them all happy. That’s not the fault of NGG.
With those suggestions, you can usually narrow down the source of a problem very quickly.
@studiobytes – Every update runs the risk of introducing incompatibilities. That’s true of NGG and every other plugin on your installation. If you’re not comfortable with trying to debug problems, you always have the option of not upgrading. That’s just kicking the can down the road, because at some point the updates to WP might make old plugin versions obsolete, and that might force you to confront a bunch of upgrades all at once. It’s part of the fun of administering your WP install on your own.
