I just noticed that in sidebar widget on single post page, there are also links to posts unavailable for currently selected language version. Can I fix that somehow?

Hi Marius,

yes I did set “Hide Content which is not available for the selected language” that you show here http://screencast.com/t/j2LHi6EPm – as I stated right in the first post of this topic.

Thank you for pointing me to “Homepage – with article list” template, I wasn’t aware of that and although it helps a bit, it still is not a real solution becuse the problems with custom built pages persist.

Before, I also said that I use WP v3.8.1 because it is compatible with latest available version of qTranslate. However, I encountered another problems with pagebuilder there (once I added some text block and tried to edit it, I wasn’t able to save/cancel/close it) so I was forced to update the WP to its latest 3.9.1 version.

Luckily enough, qTransalate works on the frontend in WP 3.9.1, except for custom built pages as I said a few times. In the backend, I am not able to switch between post editors for different language versions but that is not a major problem because <!--:en--> or [:en] tags still work as expected.

So to put it simply, my problem is this:
When I make custom page with slider, block or widgetized sidebar that show posts, the theme also shows there posts which are not available for currently selected language.

I also tried not to use my custom built page with slider and instead, use template called “Homepage – bg + with article list” (so that I can have the upper slider, even if it is not exactly the layout I desire), but that doesn’t show the top slider at all!

I assume that it will take some time to fix these, so my question is: what and where should I change to make custom built pages filter out the content that is not available for the currently selected language? If not all custom pages, at least the slider module please.

Thanks in advance,

Thomas

+ visual composer also works in an unpredictable way on our bilingual blog – when I hit “Update” after building a page, blocks and rows are copied (which I would understand, because there are two languages), but also there are being added empty rows, multiple times… is this problem of theme or WP Bakery plugin? Or even qTranslate?

oh and also pagination is not showing on custom built pages (homepage in this case)

yes, I did set up the pagination, in the page builder and it acts weird

only option that works is “Load more button” … I just want the same style pagination as is on categories (showing page numbers and being able to navigate between them)

any way to fix it please?

Hi Marius,
yes I have read this https://forum.tagdiv.com/translate-your-site-in-multiple-language-with-qtranslate-plugin/

The theme works with qTranslate almost perfect, except for custom built pages.

Website is still in development mode but I did set an account for you to take a look

http://jazykove-new.fairlist.cz/
username: guest
password: abc123

In the upper right corner you can switch between Czech and English language.
Notice the posts and right-hand side widget on homepage. You can see there are posts for both languages no matter which one you select. The problem is that not all posts are translated, so we need to show only those which are.

Category pages show only what is desired – posts in the selected language. But there’s a little problem here also – category description is being shown in both languages, the theme ignores qTranslate tags.

Homepage is custom page built as “Homepage – blank” and with no sidebar. However, sidebar is made in the page builder, so it shows as it is supposed to, except language settings. The reason for this is that I didn’t want to show page title on homepage.

Thank you for your reply.

• This reply was modified 12 years by jankosh.

Hi Marius,

thank you for the reply. It is interesting that I had it as you mention but seems that after I sent it, forum somehow changed formatting from two hyphens to dash or something like that.

Anyway I found out the problem!

I had it the (almost) correct way. I guess, because of copying the code somewhere from the internet I had dashes instead of hyphens so at first glance there is no difference between
<!––nextpage––> and
<!--nextpage-->

but wordpress didn’t process that. Maybe you could add that little note to your documentation page, although I think this is a rare case 🙂

One way or another, thank you very much for your reply, it kicked me to final solution!
Have a great day!