edanzer
Forum Replies Created
-
@dbemowsk – thanks for the videos. They capture your issues well. The issue with your Album tab in the Insert Gallery Window is so out of the norm, that I just wonder if there is some kind of broader issue with your install.
1) Can you check if you can access the Manage Album page directly from the dashboard menu? Just go to Gallery > Manage Album (rather than going through the IGW). If it loads there, that will give you a way to manage albums for now.
2) If you can access your albums there, can you pull up the album you’re trying to display in your second gallery and confirm a) that it has galleries in it and b) that those galleries have images. Normally, the ‘no images’ message your getting would only happen for an album if there are no galleries, or empty galleries. I recognize, as you noted, that the galleries seem to be showing on the sort page, so I’m assuming they are there, and there may be some other issue. But this is just a check.
3) Finally, if 1 and 2 don’t work, the next thing I’d ask is can you try rolling back to 3.0.8 and tell us if you still have that problem? That would at least tell us if it was existing, or related to the most recent release. You can download 3.0.8 at the bottom of this page: https://wordpress.org/plugins/nextgen-gallery/advanced/
Then just deactivate/delete NGG, and then re-upload and re-activate the zip. Removing and re-adding NGG in that way will not affect your galleries.
4) If you get to number #3 (ie, you can’t solve the problem), whether you roll back or not, would you be willing to submit a bug report with admin credentials for your site so we can troubleshoot? https://www.imagely.com/report-bug/ Be sure to reference this support thread, and say Erick asked you to submit. I’ll have a dev log in and see if we can get a sense for what’s happening there.
Thanks @igs. Appreciated. Even though you’ve changed, I’ll keep you posted once we’ve push the update I mentioned above so you know.
@igs – because of some feedback on the slideshow (yours, and a few other users in a forum thread), I personally worked on this today and pushed a change to NextGEN Gallery that adds the following options to the new slideshow:
Autoplay (yes/no)
Pause on Hover (yes/no)
Show Arrows? (yes/no)
Transition Style (Fade/Slide)
Interval (in milliseconds)
Transition Speed (in milliseconds).So there are more options than the old one. The only thing the new engine lacks is the diversity of Transition Style effects.
This will need to get a review and QA/testing before we release. But it should be ready relatively soon.
If you decide you want to try it in the meantime, I can provide a beta – just email me for it (erick at imagely.com).
Just an update that because of the feedback here, I personally worked on this today and pushed a change to NextGEN Gallery that adds the following options to the new slideshow:
Autoplay (yes/no)
Pause on Hover (yes/no)
Show Arrows? (yes/no)
Transition Style (Fade/Slide)
Interval (in milliseconds)
Transition Speed (in milliseconds).So there are more options than the old one. The only thing the new engine lacks is the diversity of Transition Style effects.
This will need to get a review and QA/testing before we release. But it should be ready relatively soon.
And if anyone wants a beta with these changes, I can provide one. Just email me (erick at imagely.com) to request it.
–
Note: This won’t solve @mahmacc’s issue with the slideshow embedded in theme header. That’s something different and I’m not sure what the issue is there yet.For everyone in this thread, I’d like to underscore that because there are enough of you asking and raising the issue, I’ll have our team put a bit of rush on re-introducing autoplay, showing controls, transition effect, and interval to the slideshow. We’ll try to do that within the next few weeks. So just a heads up that’ll be coming soon.
Thanks to all of you for taking the time to post.
@igs – I should add that because we’ve had enough people ask about it, I’ll probably put a rush on re-introducing autoplay, showing controls, transition effect, and interval to the slideshow within the next few weeks, so users can get close to matching old slideshow. Just a heads up that’s coming.
@newvibe – Thanks for your post. We do very much intend to expose the various Slick.js options as options for the slideshow. That should be in an upcoming release. At the very least, we’ll be exposing options for autoplay, controls, interval, and transition effect. That will match the old slideshow, although the number of transition effects with slick are less than the older engine we were using.
For those comfortable with code, while I haven’t tested, @newbie’s code snippet above does seem correct for adjusting options to mostly match older slideshow. Again, we’ll be exposing those options again in the interface soon.
Hey @igs – Erick here from Imagely. Thanks for taking the time to review.
This release introduced new templates for most display types – thumbnail, slideshow, imagebrowser, compact album, extended album. For all but slideshow, we did this in such a way as to not alter existing displays, so those will stay the same. For new installs, or if someone hits reset, they’ll get new gallery defaults which provide the new look, but they can always get the old look back by adjusting a couple settings.
For the slideshow, we DID take the unusual step of updating the libary that powers all slideshows, so the look is different. The old JS library hasn’t been updated in something like 6 years, and we didn’t feel comfortable having users rely on such an old library.
For this release, we did not add options to the new slideshow, other than width. But we will be adding options for autoplay, showing controls, transition effect, and interval.
–
With all that context in mind, I wanted to ask two questions:1) Once options are added to the slideshow, would that satisfy your concerns, since that’s the only thing that can’t be done exactly like the old version?
2) I see you previously left a 5 star review. Is the change to the slideshow really sufficient to drive you from 5 stars to 1 star? I ask because NGG has six displays and hundreds of options, and also because the old slideshow, frankly, was not that good. If the new slideshow is missing options you’d like, but everything else is good, could we ask you to bump down from, say, 5 to 3 stars?
3) You mentioned bugs. Can you clarify which bugs you’re seeing? After 100K updates, we’ve heard a few complaints like yours about the slideshow, but not really anything about other bugs.
4) You said old versions are vulnerable / unsafe. Are you referring to my point above about the old slideshow engine? If so, there’s no evidence I know of that it’s vulnerable or unsafe. It’s just old.
Even if you don’t change anything about your review, I do want to thank you both for using NGG, and for taking the time to share you thoughts about the new release.
Forum: Reviews
In reply to: [Gutenberg] not usefull, dos’nt works with other gallerys@dischue – Erick from NextGEN Gallery here. I just want to note that:
1) Existing NextGEN Galleries will continue to work when users upgrade to Gutenberg. We’ve tested this. NGG visual shortcodes get parsed into the Classic Text Block, which works like normal.
2) NextGEN has released a Gutenberg-friendly beta of the plugin. We’ll probably officially release within 1-2 months. This version works both with Gutenberg and with the Classic editor. From the Gutenberg interface, you’ll see NextGEN Gallery block. For backwards compatibility and switch-to-Classic-Editor reasons, we leverage the Classic Text block. This means even if you use Gutenberg to insert your gallery, and later switch to Classic editor, even then it should work.
–
More generally, I do sympathize with your view that Gutenberg is placing much less emphasis on backwards compatibility than WordPress traditionally has. And I think there’s a high probability that many themes/plugin will break. The burden has been placed on themes/plugins to make themselves compatible with Gutenberg rather than vice versa. And many won’t.
But for NextGEN Gallery, we should be ready well in advance, old galleries should continue to work, and you should be able to add and manage your galleries via Gutenberg.
Forum: Reviews
In reply to: [Gutenberg] Is not suitable to production@ogalinski – While there’s validity to your point – detailed reviews are more helpful – I’d point out that plugin developers on the WP repo have dealt with these kinds of reviews forever. They are not useless – they reflect users instinctive reaction to a product, and – in the aggregate – can tell you a lot about how much users like a plugin.
It’s also well known that WP reviewers are fickle. If they don’t like particular components of a plugin, they often go straight from five stars to one star. Again, common experience for the thousands of plugin devs.
I guess the point is that while I sympathize with your concerns, Gutenberg is being evaluated the same way, by the same standards, and with the same kinds of reviews, as every other plugin on the repo. To the extent that such reviews are valid for any plugin, they are valid for Gutenberg.
@frg62 – Your missing Effect and Interval is not a bug. We’ll be adding those those back, but there will be fewer “effects.”
@mahmacc – First, I CAN see your issue. I’m not sure Mihai isn’t seeing it or if it’s hard to recognize what it is because of where it’s placed and how it’s breaking. In this case, this is a highly custom integration of our slideshow inside the theme header. That’s the type of integration it’s just hard for us to anticipate.Rather than have you roll back, I’d like to fix it if we can. Can you send me an email at erick at imagely.com so I can ask more specific questions about your site. We may even ask for a copy of the theme or theme code you’re using, and/or access to your site if you are willing.
To address your question of why we changed this… We haven’t done so in 10 years because we know its hard. But the old engine was dangerously out of date. It simply had to be updated.
@stanbob – Again, we’d like to get things working rather than have you roll back. Can you please provide more detail on your issue. If it’s a substantially different issue than the opening poster, you may want to consider opening your own forum thread. You can also email erick at imagely.com if you’d prefer to do this privately. I don’t usually do that, but it’s important to me that any issues with the new slideshow engine be fully resolved, and quickly.
Hey all – Erick here. I’m reviewing this thread. Rather than having folks roll back, I’d rather resolve issues. This is something I’ll put immediate developer attention on if we can see an duplicate an issue.
One note is that we’re using a different JS engine for the slideshow. The one we were using is no longer supported and hasn’t been updated in something like six years. I just think it was reaching the point of being unsafe due to lack of updates.
The new JS engine we’re using only has a couple, simple transitions. Right now, we’re not exposing an option to chagne that, but it’s something we can (and almost certainly will) easily add. Even when we add, the transition options will be more like fade and slide vs the bunch that were there before. We don’t consider this too big a deal because not very many people were using most of the transition effects.
We’ll also be adding timing and interval effects. For now, because of the significance of updating a JS slideshow engine on hundreds of thousands of sites, our main goal was just to be sure that slideshows are still working smoothly.
So there’s a difference between missing options and actual bugs where things aren’t working. Bugs need to be fixed immediately. Options will be added, but they may not match one for one to the old engine.
Those are initial thoughts. I’m reviewing this thread in details and may respond with more questions shortly.
Can you please try removing the [ and ] around Show slideshow in your shortcode. Normally that shouldn’t break, but it may be how the quotes are being interpreted. You might also try using single quotations around it if you want to keep the brackets.
Not sure if you’ve changed anything here, but a couple notes:
1) The url you provided has /nggallery/page/1 on it. The addition of the pages to the URL like that only occurs when ajax pagination is OFF. I see on your gallery, ajax pagination is ON. So if you load the gallery at https://rendersphere.net/archive and navigate, I’m not seeing any change the url. Just the gallery changes.
2) I see a total of 7 pages now, not 8.
3) For the first page, I am seeing all the pages. Looks like: https://monosnap.com/file/QYP6taJlwqYEVf8d08oSAZe9QY203m
I continue to see all pages listed there except when getting to page 7, when page 3 disappears. I’m checking to see if I duplicate that locally.
- This reply was modified 7 years, 7 months ago by Steven Stern (sterndata).
- This reply was modified 7 years, 7 months ago by edanzer.