Erick Danzer

@denflows: Yup, we saw that. I think that’s very incomplete picture that notably oversimplifies the choices that face plugin developers in a complicated WordPress landscape where you control very little about the environment in which your plugin is running.

In our case, we *were* using the shortcode API as intended. But there were a lot of conflicts with plugins who weren’t. So we adjusted our implementation to resolve those conflicts. The resulting implementation worked well with WP and avoided conflicts until WordPress 4.0.1 was released.

I’m sure someone out there would say: well, you should just do things the right way, and if there are issues with other plugins, that’s their problem. But anyone who’s supported a popular theme or plugin know the “it’s their problem” approach doesn’t go over well. Users don’t care where problems originate, they just want them solved. Which I understand.

So I’m confident we made the best decision for our user base as whole with the way we were doing it, and we’ve now just adjusted again to accommodate the new circumstances.

@dadaeen: Great to hear! Thanks for taking the time to confirm!

@mellowvision – We prefer to keep each thread focused on its own issue rather than mix them up. Otherwise topics get all jumbled, and hard to follow for other users.

Could we ask you either to start a new thread or, since you’re a Pro member, to submit a support ticket if you’re still having issues? The issues you were having with your albums are definitely unusual. Sounds like they’re resolved, but if not, we’d be happy to help. You’ll get the fastest and most complete response via Pro support ticket. Thanks! (Erick)

@dadaen – the issue was caused by a change in the (somewhat sudden) WordPress 4.0.1 update, not anything on NextGEN’s side.

Hey all – just wanted to confirm that the 2.0.66.31 resolves this issue. @peter Wooster – this issue was introduced by the WordPress 4.0.1 update, not anything on NextGEN’s side.

If anyone updates and still has any issues, please let us know. Thanks! (Erick)

Hey all – just wanted to confirm / follow up on @photocrati.

It looks like the WordPress 4.0.1 release yesterday broke some NextGEN shortcodes. We just pushed 2.0.66.31 to resolve the issue. You don’t need to adjust your shortcodes.

If anyone updates and still has an issue, please let us know. Thanks! (Erick)

@lunar Oratorios, we’re just finding this morning that WordPress 4.0.1 release yesterday broke NextGEN shortcodes and produces that errors, so that’s probably why you are seeing it.

We’ve just pushed a release a few minutes ago (2.0.66.31) that resolves the issue. Can you update and confirm it’s resolved for you?

@inndesign: just wanted to add two thoughts.

1) I have the sense you know your stuff enough to know this, but the fact that a malicious file was found within the nextgen-gallery folder doesn’t indicate that’s where the hack took place. It could be anywhere. You can hack a site through some other theme/plugin/WP core files, and then upload a malicious file anywhere on the instance. I only mention this because it sounded like your engineers were saying that because there was a malicious file in the nextgen-gallery folder, that indicates that’s where the hack took place.

2) If you or those you are working with do actually have some concrete data or analysis that shows the hack originated originally via NGG files, yes, absolutely send us the details.
– FYI – @benjamin asked about which files….this is also probably obvious, but if you do have that kind of info, definitely pass it along via email or contact form to us directly rather than posting here in an open forum.

Thanks!

@track77 – I’d second Cais on this. And even in a review, some more details might be useful. Since galleries are displaying fine for other users, it’s hard to know what to make of this otherwise. In any case, thanks for taking time to leave feedback.

@paul_t – just wanted to note that WordPress 4.0 has been out for a long time now, and with hundreds of thousands of users we’re not hearing about any general issues with NextGEN (any version) and WordPress 4.0.

I did just check to see if you have any support forum threads. I see your WP.org account is just a week old and you’ve just posted this review and one other.

As @photocrati noted, if you’re having any issue, you’re welcome to actually post a forum support topic. Cais is very good at helping users resolve things.

Thanks.

@remco2 – Yup, thanks so much for taking the time to leave a review, and thanks too for the five stars!

Hmm. Thanks taking the time to review @dannyanderson. But I’d second that I’m curious to know what the connection is there. As far as I know, Genesis-based themes don’t have any gallery-related functionality? Not sure if the switch resolved something else for you.

Hey @nwdwp – just wanted to hop in and second Cais on this. A basic thumbnail gallery should definitely be displaying your thumbnails in a grid. So if that’s not happening, there’s something interfering. In the past if we’ve seen this, it’s often been a plugin conflict.

But you definitely don’t need to upgrade to Pro to get a basic thumbnail grid (though there’s lots of other great stuff in the Plus and Pro versions).

So if you’d like a hand looking at it, please do post a thread in the forums. Cais is great at helping people work through these kinds of issues.

Thanks. (Erick)

@wengriffinapt – Thanks for the reply. So based on what you were saying, it doesn’t sound like your problem was finding / using the NGG custom css file. Obviously our thumbnail galleries generally display in grids, and I’d guess you are probably seeing one here:

https://www.nextgen-gallery.com/basic-thumbnail-gallery/

If they are loading in a single column, there’s almost certainly some kind of conflict, usually a plugin conflict. From your latest email, though, it sounds like you may think there’s a conflict with your theme?

There’s no currently known conflicts that produce what your are seeing, so we’d need to diagnose where it’s coming from. The usual way to do that is to try momentarily deactivating other plugins to see if you can identify which is producing the effect. I know that many site owners don’t want to do that, which is fine. But if you do it, and find the source of the conflict, please do let us know.

If it’s not a plugin, there is a chance it’s your theme. Can you tell us what theme you are using?

Thanks. (Erick)

@wengriffinapt – To add on to what Cais already said, you can also just create your own nggallery.css file and place it in /wp-content/ngg-styles/ folder. That folder will be update proof.

We also have documentation on this if it’s helpful.

How do I edit CSS in NextGEN Gallery?
https://www.nextgen-gallery.com/css/

Custom CSS in NextGEN Gallery
https://www.nextgen-gallery.com/custom-css-in-nextgen-gallery/

I hope that helps. (Erick)

(PS. You mentioned you might adjust your rating if this was fixed. Given that there is already a way to do this as well as documentation on it, if you are open to making an adjustment, we truly would appreciate it :).