VesaT

There is another alternative to NextGEN Gallery that works fine with jQuery Colorbox:

NextCellent Gallery – NextGEN Legacy, available through normal plugin updates of WordPress. This is a fork of NGG 1.9.13, currently at version 1.9.15.

What I’ve been testing so far, everything seems to work fine, including a co-existance with jQuery Colorbox.

If you continue having problems with NextGEN Gallery I highly recommend testing it. You need to deactivate NGG for NextCellent to work. And if you happen to have NGG Pro as well, set its Lightbox Effects to “none” and deactivate before you activate NextCellent.

yaardena613, I just dropped using a free fork of WPML because with the latest NGG 2.0.31 it generated a conflict. Before this fork I had used WPML for a few years before it became totally commercial.

After some search I found a free plugin called Polylang, and it was pretty easy to switch over from basically WPML-based translation manatement. However, Polylang does not have any links to professional translators like WPML, but works in many ways easier than WPML – and does cost anything.

The actual reason why I comment relating to Polylang is the fact that you can translate any Alt_text through it as a separate task. It seems Polylang has its own records in the database holding the translations. But this in essence means NGG 2.0.31 Alt texts at least should be translatable by a language management plugin.

A comment to my first complaint above:

“Attach to Post” button started working ok when I reverted back to version 2.0.30. So it is an obvious bug in 2.0.31; prospectively affecting some other functions as well. Looks like the problem with some early 2.0.x versions came back as if there some code has been replaced in 2.0.31 with the code of these non-functioning earlier versions.
Very sad, but I hope I’ll have time to write a bug report tomorrow.

mkaioh2,

in your video you seem to do everything as should, so there seems to be some kind of a bug in NextGEN Gallery.

It might be a conflict with your theme (Artisteer generates technically fairly complicated themes, so hard to say where – and my little test theme with Artisteer did not conflict with NGG) or another plugin (possibly Slimbox as it has a special old javascript bundled with it; and WP flash img show also seems a bit like a suspect). If possible you could try another theme like Twenty Thirteen, and/or disabling other plugins.

As NGG’s Add Gallery / Images interface may seem a bit confusing especially if you create a new Gallery (not folder!) and upload images I would just like to know have you have used “Upload Images” or “Import Folder”.

I have not used “Import Folder” ever so I do not know whether it works and in such a case your wish to fix it is of course valid.

But if you want to create a new gallery and import images into that, the following has always worked for me (after activating NextGEN Gallery):
1. go to “Add Gallery / Images” in WP Admin / Gallery
2. select the option “Upload Images” (not “Import Folder”)
3. “Create a new gallery” by giving it a name into the empty writing area after the gallery selection drop-down list.
4. “Add Files” which should be showing in the box with columns “Filename”, “Size” and “Status”
5. Click “Start Upload” and the images should be imported into your new gallery.

Hope this helps ??

cathyee, you are saying “to get rid of the borders around the images”. What image displays are you talking about here – gallery thumbnails, single pictures, slideshow…?

You can tailor about all aspects of each of those image displays using Other Options / Styles like you have already tried for just removing borders, you only need to know the correct names for the elements you are changing. Some themes may override even NGG’s style settings even though that is highly unlikely (according to tests I’ve made with NGG).

You also need to know what parts of the image display you really want to change; for example NGG’s default display of gallery thumbnails has actually two different attributes that may look like a border: the actual border (by default thumbnails it is 1px wide and grey) and the padding around image showing the background of the thumbnail element (by default padding is 5px and background is white so there seems to be a 5px white border around the thumbnail).

If you want to remove these two “borders” around the thumbnails you also need at least to remove them from the image’s hover (mouse-over) state as otherwise the whole thumbnail grid will move as you move your mouse over one of the images.

Below is an example I’ve used e.g. at my NGG testsite to change the css using NGG’s Styles option; it removes basically the white padding area and also margins around the thumbnails and changes the image opacity on hover using different browsers.

Hope this helps going forward ??

/*
CSS Name: Vesa's NGG Testbed Styles
Description: NextGEN Default Gallery Stylesheet
Author: Vesa
Version: 2.30

*/

.ngg-galleryoverview .desc {
/* required for description */
   margin:0px 10px 10px 0px;
   padding:5px;
}

.ngg-gallery-thumbnail-box {
	float: left;
          margin: 0px;
          padding: 0px;
}

.ngg-gallery-thumbnail {
	float: left;
	margin-right: 0px;
	text-align: center;
}

.ngg-gallery-thumbnail img {
	background-color: #FFFFFF;
	border: 1px solid #A9A9A9;
	-webkit-opacity: 1;
	-moz-opacity: 1;
	opacity: 1;
	display:block;
	margin:0;
	padding:0;
	position:relative;
}

.ngg-gallery-thumbnail img:hover {
	background-color:#FFFFFF;
	border:1px solid #A9A9A9;
	display: block;
	-webkit-opacity: 0.40;
	-moz-opacity: 0.40;
	opacity: 0.40;
	-webkit-transition: all 0.5s ease;
	-moz-transition: all 0.5s ease;
	-ms-transition: all 0.5s ease;
	-o-transition: all 0.5s ease;
	transition: all 0.5s ease;
}

You need to go to Manage Galleries –> the gallery you uploaded the images to. At the gallery management page you have an option to move images into other galleries.

One of the things you may also check in case of some NGG function displaying duplicate galleries is the /gallery folder (i.e. the folder where NGG stores your galleries) for possible duplicate folders containing duplicates of galleries.

At least in one case an earlier 2.0.something version of NGG just copied one of my galleries to another folder with a different name (that folder name repeated parts of the original gallery folder name) and redirected the gallery folder link into that new gallery folder. There were still two folders holding the same images even though e.g. NGG’s Manage Galleries listed that gallery only once.

seadad, if you really do not see the duplicate galleries anywhere else (e.g. ngg admin / manage galleries), this looks like some kind of a bug. Possibly a conflict with the theme you are using or a conflict with another plugin.

Just found out there seems to be a bug with NGG 2.0.30: if you select to look galleries from albums, the gallery image thumbnails will be displayed using NGG’s default formatting, not your own styles done with css in Other Options / Styles – which work ok if you just display a gallery as thumbnails.

If you use Pro Album display, the gallery will dispaly in “Pro” style which is different than NGG’s basic gallery thumbnail display.

seadad, if you are wondering about how the album/album/gallery hierachy may be displayed using NGG 2’s default display settings, have a look at my NGG testsite and especially this page:
https://bisnes-it.com/wordpress-ngg-test/?page_id=188

There are also alternative display types for albums with NGG Pro (just have a look through the menus), and I’ve tried to include here all NGG & NGG Pro bundled display types in pages and sidebars. By the way, if you wonder why my galleries display the way they do, I’ve made a specific style for displaying gallery thumbnails here using NGG’s Other Options / Styles.

Hope this helps you and prospectively others to make decisions on design options with NGG.

seadad, you only need to make one additional album that contains your three albums and NextGEN Gallery will handle the rest. With NGG 2 you can select among several options to show your album(s).

Within all albums you can add descriptions of each and also attach an image that will display when you have a single thumbnail along the descriptions on that page. When you click the album, next level on the same page will open up, showing the album thumbnails of the three albums you want, and clicking any of the the galleries will be displayd. This is needed especially because an album containing only albums does not have a “natural” thumbnail image which for albums containing galleries will be automatically picked from one of the galleries.

So your album / album / gallery hierachy needs to like this:
– Album (containing your three albums 2,3,4 and their galleries)
–Album 1 (first second level album)
—Gallery 1
—Gallery 2
–Album 2 (second second level album)
—Gallery 3
—Gallery 5
–Album 3 (third second level album)
—Gallery 6
—Gallery 7
On the page, insert just the highest level album. That’s all ??

Martin, I think you should post this into Photocrati’s NextGEN Pro support pages. They have promised to answer within 24h even on weekends ??

Hmm, my install of NGG 2.0.17 still shows the widget “NextGEN Slideshow” and it also has been working for me.

I have not used it in my headers, but e.g. Meteor Slides plugin is compatible with NGG 2.0.x and allows also the possibility to link the slider images to your selected URL (external or just page/post).

There is something weird here, as for me NGG 2.0.17 works pretty much ok – and I haven’t found any real replacement for NGG when you have a couple of thousand photos and 100+ galleries.

There are a couple of things in 1.9.13 still not working that I would welcome any day
1. NO translations available for the plugin
2. Several hacks to NGG Photocrati themselves have promoted not working:
– css edits do not work for me the way 2.0.17 should work – but there is a workaround for this
– getting a gallery name/title display onto a page when you view a gallery within an album – no clue how to do this because of the structural changes to the plugin…

I tend to think the new Pope-structure is something you really should not have in a WP plugin as it clearly complicates debugging, and tailoring the plugin far too much.