Oslaf

Oh, OK. I’m not running 5.4 in neither my local or my live server, so that’s the problem. Well, I’ll keep using your 1.0.1 version for now, fortunately I had a copy around.

Thanks.

Cool, thanks again. I’ve been using a simple pre_get_posts action to fix the issue (had to give it a ridiculous priority to make sure it actually overrided WPES, though). I’ll get rid of it with the next version of WPES then.

if ( $_GET["post_type"] == 'post' && $query->is_main_query()  ) {
	$query->query_vars['post_type'] = 'post';
}

Hi again; thanks for your quick reply.

That does the trick, but it obviously disables the extended search completely for that form, and I did want to still extend the search to default taxonomies (categories and tags) and some meta fields in the blog post searches.
Plus, it creates a visible URL parameter which can be manually tweaked by the user…

I thought a solution would be possible and simpler to achieve, since the Search Everything plugin does keep the manual search parameters. I’d rather use your plugin, though, since yours is actually way more versatile (and SE is cartoonishly cluttered with pointless options and ads)

Ok, thanks!

Well, so I’ve been doing some more tests, and I’ve narrowed the source of the error to the permalink settings.

It seems that the error triggers if the generated archive URLs and the permalink structure-based post URLs partially overlap; this is what I’ve found:

* Permalink structure is mysite.com/%postname%/ (one of the options provided by WordPress)

In this case, the error doesn’t trigger and everything works fine, since the generated archive URL is mysite.com/2014/06, while the URL of a given post is mysite.com/thepost

* Permalink structure is mysite.com/%year%/%monthnum%/%postname%/

In this case, the error does trigger; I believe this is because the generated archive URL is still mysite.com/2014/06, while the URL of the posts is now mysite.com/2014/06/thepost. There’s overlap, and the language switcher error takes place as described in my first post. (this was my permalink sctructure when I noticed the error)

This is confirmed with another test:

* Permalink structure is mysite.com/%year%/word/%monthnum%/%postname%/

With this, the error doesn’t trigger, because while the generated archive URL is still mysite.com/2014/06, the URL of the posts is now mysite.com/2014/word/06/thepost. No direct overlap, no error.

Sadly, the following is not a solution:

* Permalink structure is mysite.com/blog/%year%/%monthnum%/%postname%/

Adding a prefix or suffix to the structure doesn’t fix anything, since these are also parsed into the archive URL, again causing the error.

Knowing all this, there’s probably several ways of creating a workaround, but I thought you would probably be interested in correcting this behavior in future versions of the plugin.

That’s odd. So the switcher in your test site does successfully direct a ‘site/2014’ address to a ‘site/fr/2014’-style address? Is there a public test/example site for this plugin, so I can check it out?

I’ve created a brand new WordPress installation to test this out (with the default theme). Right now, it contains only the Hello World! post, the sample page, and their respective translations (published at the same time), but I’m still getting the same behavior from the switcher if I activate the ‘Hide URL language information for default language’.

Here, I’ve pulled a couple of screenshots from my configuration screens:
screenshots

Sorry I can’t post a link; I’m developing this site using a local server.

Every post has its translation already set up. Everything works fine except for the problem I described (in a category/tag index the switch works fine too)

Aw, thanks, that’ll do it.
Thanks again for the quick replies; do consider adding the caption slide/fade choice as a feature for this already awesome plugin in the future (maybe some people would like to add different effects to different slideshows).

Well, I was actually refering to the div containing the description sliding on mouseover -not on slide change- (It shows up labeled with slideshow_description and slideshow_transparent classes in the markup).
I was intending to use your plugin on a site in which I’ve already implemented some fading overlays on a grid of masonry formatted items, and I would like to use a similar style for the slideshow -which I would use for the header- to keep it consistent.