edanzer
Forum Replies Created
-
@paulmfield – Thanks for your report. As noted for the original poster, we’d need to see some evidence of a possible exploit or security vulnerability in NextGEN Gallery. If you have that, please send us the details in a bug report http://www.nextgen-gallery.com/report-bug/ and we’ll be on it quickly.
But to emphasize the same point we made to the original poster: the fact that you have NextGEN Gallery on a website and that website was hacked, doesn’t at all indicate that NextGEN was the source for the attack.
That is the case even if you found malicious files within the NextGEN folder, since once your site is hacked, the hacker may put malicious files in any location.
We do track any security reports very closely, and again if you can provide any evidence that NextGEN actually has a specific vulnerability, we’d react very quickly. But as it stands, there is no indication of a vulnerability in NextGEN that we know of. Usually if there is, we quickly find out about it from multiple sources just because NextGEN is active on so many websites.
Thanks! (Erick)
@sswaim – thanks for the update. So it sounds like you are thinking that it’s a theme conflict? If your theme is active, something is not working with NextGEN uploads? If so, can you give us the name of the theme so we can give it a try ourselves. If there’s an issue there, we’d love to resolve it. Thanks!
Quick note @borisrio – not sure if you had already made the change, but the review is still showing the original two stars…
@borisrio – Must have mis-typed on my email about the original rating, but thanks for the offer to bump it one. That’s much appreciated!
If you have any issues like this in the future, please don’t hesitate to contact us here or via bug report.
Thanks! (Erick)
@kencooperjr – Ok, thanks for the follow up. If that’s the case, then yup, we’re letting you down as it stands.
Just FYI – this *will* happen. I know it’s no solace, but we have basically two developers on NextGEN and NextGEN Pro, supporting hundreds of thousands of users. There’s always more to do than we have resources for. To prioritize, we generally emphasize issues that are either the most serious or get the most user reports/requests.
And we just don’t get that many users wanting to manage their galleries from their ipads. It’s generally front end viewing that’s been most important. But as we get more and more done, this is getting more and more on the the radar.
In any case, thanks for taking the time to add the extra details. We really do hope you find an alternative that meets your needs.
@fowler – thanks for the follow up and extra details.
Honestly, I think there’s some real value in your suggestions. Given that we have pagination for other gallery types, it makes sense to add it for Pro masonry. And yes, you’re right, breaking large Masonry galleries into pages would have a notable impact on page load times since you’d reduce the total image numbers.
I wouldn’t be surprised if we do that in one of our next releases.
As a side note – you could have used basic thumbnail, pro thumbnail, or pro film galleries, all of which do have pagination. I’m assuming you just really wanted to use masonry in this case.
Another side note – one big thing that’s happening in the next Pro update is an update to galleria which runs our pro lightbox. We’re testing that now, and pro lightbox loading is basically instant.
In any case, I’m sorry we didn’t get that and other performance enhancements out in time to meet your needs.
Thanks. (Erick)
@infernowrx – just following up on some old reviews. Thanks for the detail in yours. For what it’s worth, NextGEN really isn’t a “Slider” plugin. It’s a gallery management plugin that happens to have a slideshow as a gallery display type. But even then, a slideshow is very different from a slider in terms of what it’s supposed to do.
Given all that, I’m not too surprised it wasn’t great for your needs. Regardless, we appreciate you giving it a try. Thanks (Erick)
@trackoholic – Thanks very much for posting the update and for the extra details and suggestions. Not all reviews provide that kind of balanced useful feedback. You’re not the first to mentioned we need to improve documentation, so we’ll bump the priority on that. Much appreciated.
We hope you’ll give a try sometime again. In the meantime, we really hope TN3 works out for you. Thanks! (Erick)
@bill57 – Just following up to see if you are still having this issue (if you’re still working with NextGEN). As far as we know, NextGEN is loading fine for recent WP versions. Thanks! (Erick)
@sswaim – just following up on some old posts. Did you ever resolve this issue? Thanks (Erick)
@rubensedanoc – Just wanted to follow up on this. First, thanks for reaching out to us when you did about a possible security vulnerability. We always take that stuff seriously, and we appreciate the notice.
I was reviewing your correspondence with our team. I think we’ve confirmed that this was resolved. As a extra note for you and others, the vulnerability report that you sent actually notes this issue was only present in 2.0.63 and less and was confirmed patched in 2.0.65 (May 2014).
If you still see an issue, can you please follow up on our email thread. But assuming this issue is resolved, we’re wondering if you might consider bumping your one-star rating?
Thanks again. (Erick)
When you say “through a library” do you mean you’ve uploaded them to the WordPress media library?
@kencooperjr – Just reviewing some recent reviews and came across this. I just wanted to be sure you understand that NextGEN support front end gallery displays on iOS just fine. We do actually test our gallery displays on tablets.
It’s back end functionality in tems of uploading and managing your images in the back end that’s bumpy in iOS. Is that what you’re needing?
Thanks (Erick)
@dwrz – Quick follow up. Assuming you’re up and running now, any way you can revise that one-star rating? If you think it’s still deserved, that’s fine. But if not, just wanted to point it out and ask if you could give it a bump.
If you have other issues, of course, let us know. Thanks! (Erick)
@dwrz – I’m glad to hear it’s resolved. Thanks for taking the time to post an update!