beheist

Hi Katinka,

as long as you’re using the buttons version of the language switcher widget and not the dropdown list, this request is extremely simple to implement with CSS only. Just add the following lines to your template’s style.css:

.qtranxf_language_chooser .active {
	display: none;
}

This hides the language that is currently active, just as requested.
Best regards and good luck with your project.

Bastian

Hi John,

I tried it locally and the more and nextpage tags are working now – thanks for that!

Also, I opened an issue on the github page to discuss whether we should include the slugs functionality in qtranslate-X altogether – please see here: https://github.com/qTranslate-Team/qtranslate-x/issues/1.

Edit: Just found this post, so nevermind about the broken editor in Chrome – works again.

Hi John,

sorry for not replying earlier, I was on a business trip with little spare time.. the <!–more–> tag creates a mark for wordpress to add the “Read more” link in archive views. <!–nextpage–> allows you to paginate individual posts.
I never tried qTranslate original, but since qTranslate-X separates the language versions of posts with similar comments, I assume something is going wrong there. I will take some time this weekend to investigate since you now have a github page available. Thanks so far!

Good Morning eirikv,

sure, I’d be happy to support you guys. Is there a github page for qTranslate-X also or are you exclusively using SVN? I haven’t used that yet, so is there a similar mechanism to the pull requests in github, so I could make a contribution for you to review?

Yes, it is in fact reproducable with the following steps:

• Install WordPress, qTranslate-X and my version of qtranslate-slug
• Switch pretty permalinks on and set qTranslate-X to pre-path mode
• Add the language switcher

As I suspected, the bug can be circumvented by removing the “Hide URL language information for default language” checkbox.

I will investigate where this bug comes from. However not today – have to start preparations for tonight ??

Good morning Thomas,

I had a look and the behavior is in fact strange. When I visit https://www.foolsmission.org/, the page shows up as Spanish, so I assume that is the default language. However when I look at the language selection listbox, I see the following:

<option value="https://www.foolsmission.org">English</option>
<option value="https://www.foolsmission.org/es" selected="selected">Espa?ol</option>

So the language selector seems to think that English is the default language, as it tries to send you to the root url. As a quick fix, you could try disabling the “Hide URL language information for default language” checkbox in the qTranslate-X advanced options. I will try to reproduce this issue in a local installation.

Hi guys,

I created a pull request to qtranslate-slug today that contains the functionality to make it work with qTranslate-X. You can find it here: Github repo. I hope it will get merged into the plugin. If not you can also download it from my repo (https://github.com/beheist/qtranslate-slug)