VesaT

No scale up that I would have seen. That is also what WordPress supports in its own media gallery.

Yes there is, use NextGEN Slideshow widget.

Your slideshow responds ok (width & height) with Chrome, Firefox & IE10. Are you using Safari? I’ve had similar problems with Safari and responsive designs using NGG images sometimes already with NGG 1.9.xx. Basically this could be fixed editing CSS.

I think the scaling is only to crop large images to fit the screen, not to scale up. So images with less resolution than the screen (say an image with 600 x 400 px resolution on a 1920 x 1080 screen) will not fill the area. For me this is ok as the low resolution in a large size will not look good.
Solution? Photocrati should make a scale up option – or you have to upload images using a higher resolution.

@mhcaus: NextGEN Gallery structure changed so much with 2.0 release that I would not try what you are asking for. Instead I recommend the following:
– set NextGEN Gallery Other Options –> Lightbox Effects–> to “No lightbox”; this allows using external lightbox plugins
– install an external plugin to show lightbox effects; one that can show description text and works nicely is jQuery Colorbox, it also has several different themes to select the best suited layout for the popped-up lightbox.

Currently I do not know of any free lightbox that would show both the image name (title) and description text – and would work nicely with NGG 2.0. Any suggestions for such a free plugin are welcome ??

Obviously this change in NGG 2.0.20 does not affect NGG Pro, where Pro Lightbox will not close in Opera.
Should be fixed, Opera is still about 3% of all visits on the sites I maintain.
PS. I raised a bug report for NGG Pro about this ??

@frontierblogger, I create my themes from scratch. Every time a site which uses my theme and needs a major change in the design I create a totally new theme and give it a new name. In those cases you need to change the style.css of the child theme to use the new theme ie. its template name and folder.

If you name your new theme the same as your previous theme you can avoid changing the child theme – but that in my experience easily leads to situations where you would not really have a possibility to go back to a previous theme in a controlled way if something would be wrong with the new theme.

Just a comment to child-theme use: it is a good solution as long as you stick to one theme (name / folder).

My usual practice with sites I maintain is that I create a theme with a new name and folder always when there are major design or functional changes in the layout. Doing that you always need to change your child theme (template & theme folder) when the used theme changes. If you have a similar approach, then ngg_folders is a better option for NextGEN edits, as it basically should be upgrade safe within NGG and you only need to touch that if you make any edits into NGG’s css.

And for others and especially @photocrati: my personal site’s current theme seems to include something that breaks both the use of a child theme and the use of ngg_styles folder (Styles edit) – but direct edits to NGG’s thumbnail css file works ok. My other themes seem to work ok with NGG’s “Styles” edits.

@photocrati: just a small correction to my first post in this thread regarding nggallery.css in /ngg_styles folder ie. done with NGG’s Other Options / Styles editor:

I just tested whether those edits would have worked with NGG 2.0.14 as I claimed in the first post here. It did not, neither with NGG 2.0.17. This done at my hosted (linux etc) live site. A local copy of that full site neither works even if I change the theme to Twelve Thirteen and disable all other plugins except NGG and NGG Pro. When I upload an edited nextgen_basic_thumbnail.css file into NGG’s /modules/nextgen_basic_gallery/static/thumbnails/ the edits work ok.

The same hosting provider also hosts my NGG test site and on this site the “Styles” edits work ok also when used with other plugins.

So I have no clue what is causing this ??

@photocrati: yes, only on Opera – and currently I’ve only got version 12.16 installed.
Other browsers I’ve tried (IE, Firefox, Chrome, Safari) Lightbox Pro closes properly. Opera is currently the 5th most used browser at my personal site after the ones above (those listed from 1st to 4th based on use).

@photocrati: my local copy of a live web site with over 2000 photos does not obey nggallery.css in ngg_styles folder, but the same problem exists also with this live site. Deactivating all other plugins except NGG and NGG Pro and using Twenty Thirteen theme does not help at my local testsite (pretty much impossible to make a test like this on my live site).

However, my NGG testsite in the web works correctly in this respect. This testsite uses a lot less other plugins than my full live site.

There is still the issue of nggallery.css in /ngg_styles folder.

With NGG 2.0.14 the latest fixes seemed to work both at my local testsite and on a live website. After 2.0.17 custom “Styles” within /ngg_styles stopped working, and 2.0.18 beta still has the same issue on my local testsite.

“Styles” however seem to work ok at my web-based NGG testsite where I use only a few other plugins than NGG/NGG Pro. So possibly there is a conflict with another plugin.

EDIT: I deactivated all other plugins except WPML (my site does not show anything without it) at my local testsite – nggallery.css does not work with 2.0.18 ??

I use jQuery Colorbox along NGG’s Pro Lightbox, and it works fine at least with NGG 2.0.14.

Main reason for using both is the fact that Pro Lightobox does not display images inserted into posts/pages using “insert media” function of WP. Some day soon NGG Pro Lightbox hopefully will also work with all images in posts/pages ??

If you would want to use jQuery Colorbox only, then you have to select “no lightbox” in NGG and set jQuery Colorbox on both for “Automate …for all images in posts..” AND for “Automate … for all other images” (the latter will enable jQuery Colorbox e.g. for NextGEN Galleries).

@frontierblogger – yes, a child theme is a good way even if it may somewhat complicate maintaining the possibly complex structure of your main theme and several plugins.

Update: Styles-based CSS edits seem to work on linux-based servers with NGG 2.0.14, but not on a local Windows-based server. NGG still uses the default legacy css even if there is an edited nggallery.css in the ../ngg_styles folder.
At least I usually format NGG displays and my themes on a testserver before launching them to a live site. And my testservers run on Windows (typically Wampserver). So, a fix please ??