nextgen-gallery conflict?

I got exactly the same problem using

Polylang 1.5.3
NextGEN Gallery 2.0.66
Wordpress 3.9.1

Album overview is working but as soon as you click on a link it redirects to the same page again. Thought this was fixed a time ago. Any hint how to repair that?

After searching the support forum it seems the error occured a while ago and was fixed with another polylang version. looks like it reintroduced itself some time ago.

please, any helpful tips appreciated!

This issue is still not fixed in 1.5.4 and very annoying.
Plus no feedback at all from the support.

Very frustrating situation!

Hi everybody,
I’m experiencing the same problem reported by veonline => “I’m being redirect always to the album page.”

Running wp 3.9.2 – polylang 1.5.4 – nextgen 2.0.66.27
Gallery permalink set to /nggallery/

What’s odd is that the site is still running fine on MAMP, but clicking on a gallery redirects user to album page on the live site (???!!!).

In fact the urls of the galleries look like this (fine for me):
https://www.miamitiamo.com/it/album_page/nggallery/master-album/gallery_name

Looking closer with firebug detecs that:

– the first url (built as described above) gives 301 moved permanently status
– it then tries to load an url like: https://www.miamitiamo.com/it//it/album_page/ (which again is marked as 301 moved permanently)
– it then load the album page

The site is https://www.miamitiamo.com.
Some galleries are loaded randomly on the sidebar and the only way i’ve found o get it working for now was to associate every gallery to a page but i don’t want it to work that way!

I’m supposed to fix it for the end of august and I really hope I don’t have to migrate to another plugin!

Any help appreciated!
Thanx.

Hello,

is there any conclusion to this related problem?

I′m having here the exact same issue and also don′t want to create new galleries for each language.

Versions I use:
WP: 4.1
Polylang: 1.6.4
NGG: 2.0.66.37

Please help or give any hints, how to fix that.

Many thanks!

@bofh1976

As you can read here, the developer of the Polylang plugin explained he won’t continue to fix this known problem.

Too bad. We won’t use this plugin on further projects.