edanzer

@netmediamarkets – Thanks for the extensive reply and details. I just reviewed our internal tickets. We do have a conflict reported with Avada, but I’m not sure this is the same issue.

I ensure our team takes a renewed look at your issue and that it gets some attention. Can you email me directly with that website link and a link to this thread? Maybe reference me in the subject. If you have had interactions with us on the forums, maybe lint those too. You can send to erick@imagely.com.

Thanks again.

@fusionstream – Thanks for taking the time to leave your thoughts. Just wanted to respond on some points here.

1) On SSL: NextGEN Gallery definitely runs on all https. We’re doing it right on http://www.imagely.com where NextGEN lives. If you’re not able to get that working, there’s something else at play.

2) Interlinking code and classes extending classes. NextGEN uses something called Aspect Oriented Design https://en.wikipedia.org/wiki/Aspect-oriented_programming. This is an advanced and widely respected approach to code design. It ensures separation of concerns via modules, and allows child classes to easily override parent classes when needed.

This is not a common design pattern in WordPress themes and plugin, and it probably appears more complicated than most WP code. But that’s, in part, because much of code around WordPress is fairly basic compared to the wider world of software engineering.

In any case, there’s nothing nefarious about the code design :). It’s just a standard – perhaps advanced – code approach.

3) Tracking and projecthoneypot. Four points on this. First, the code you are referring to is actually part of Freemius, a partner we and many other popular plugins work with to allow opt in contact via the dashboard. Second, we don’t track anything without consent. When new users activate NextGEN, they see an opt in screen. They can opt in or skip. About 1/3 choose to opt in. Third, the projecthoneypot reference is in code that NEVER gets executed for NextGEN, because of how we’ve chosen to integrate with Freemius. But if it does, it is, ironically given your impression, an anti-spam mechanism that prevents users from spamming email fields via freemius code.

4) Wasting server resources. As you can see, there’s nothing here that should be wasting server resources. If you’re seeing some indication to the contrary, we’d love to hear about it and troubleshoot what may be happening.

–
Unlike so many 1 star reviews on WordPress.org, yours is thoughtful and based on some analysis of the plugin. But I think the conclusions you’re drawing are not accurate.

If you have any follow up thoughts, please feel free to let us know.

Thanks!
Erick (founder/CEO, Imagely)

• This reply was modified 9 years, 5 months ago by edanzer.
• This reply was modified 9 years, 5 months ago by edanzer.

Hey @acekin – I know I’ve had a lot interaction with you over the years, including immediately after the 2.0 release. Just wanted to drop in and say thanks for nice review! (Erick)

Yup I’d be interested to hear any details on this as well.

Thanks for taking the time to leave a review @codebot. While we know a lot of people like all the options and power, I’d say we agree with you based on feedback that we need to find a way to streamline the interface and make it a bit simpler to get started, ideally without losing the power and flexibility of the plugin. In any case, thanks for the input.

Hey @marviestoto – We’re not quite sure we’re following the issue you were having. Looks like two issues:

1) You have subscribers on your site who, when logged in to the back end, could access the Gallery tab/area? So they could upload and manage galleries on the site.

It sounds like you were playing with the roles and permissions. I’m not sure what your goal was, but by default, the roles are set so subscribers cannot see your gallery area. You would have had to set that yourself I think.

We’ll see if we can duplicate some scenario in which subscribers would otherwise have access to your galleries, but we’ve never seen anything like that unless a NextGEN user specifically sets it that way.

2) Sound like there were attempts to hack your site?

I’m not quite understanding why you’d be attributing that to NextGEN though. The link you posted is just a NGG admin page – our insert gallery window.

If your site was hacked, it’s unlikely that NextGEN Gallery was the vector. We monitor security issues closely, and with 1 million + active installs, as soon as there is a security vulnerability, it’s widely advertised and known. There are also a range of dedicated security firms that are always looking for vulnerabilities in our plugin (and other popular plugins). If they find any, they generally report them to us. But it’s been a long time since anyone has found or reported an active security vulnerability in NextGEN Gallery

If you do think you have legitimate evidence of a security vulnerability, then please reach out to us via email and let us know. You should know that once your site is hacked – no matter how someone gets in, they’ll put extra code all over your install, including WP core files, theme files, plugin files, etc. So the existence of a malicious file in your nextgen-gallery folder (or any other theme/plugin) is not evidence of a vulnerability.

–
If you think I’m mistaking what you wrote above, feel free to let us know.

@alexmmo – we have lots of users using NextGEN and Buddypress, so most likely this is going to be something quite specific. As for the post from two years ago, that’s like a century in web time. I think we’ve pushed several buddy press related fixes since then. So it could be it’s the same, could be different, could be it was resolved and came back (either from a change on our side or on buddy presses).

I’ll see if our team can look into this and duplicate it. If we can duplicate it, we’ll prep a fix. If you think there are any other details that might be useful in helping us duplicate the issue or diagnose it, please let us know.

Thanks. (Erick)

@franhaseiden – Thanks for taking the time to leave a response. Sorry NextGEN wasn’t the right fit for you. Hope you find something that works better for your needs. Two quick notes:

1) “impossible to handle large bulks of images” -> Actually, for what it’s worth, the handling of bulk images (upload and then management, including sorting) is widely considered to be one of the core strengths of NextGEN Gallery. Not sure what issue you were having specifically, but my sense is you views on this run counter to most people who use NextGEN.

2) A gallery is a collection of images. An album is a collection of galleries.

3) When you delete a gallery in NextGEN, yes, you do delete the images within it. NextGEN creates and manages galleries, and the images are just part of those galleries.

Thanks for your input and good luck in finding a better fit. (Erick)