Menu - Cannot change URL's in sub item per language #120
Comments
herrvigg
added
legacy PR
herrvigg
changed the title
herrvigg
added
enhancement
|
Hi, please, read FAQ https://wordpress.org/plugins/qtranslate-x/faq/, topic "How can I prevent URL of a custom menu item from being converted". Please, take the latest version from github, like https://github.com/qTranslate-Team/qtranslate-x/archive/3.2.9.8.3.zip, as 'setlang=no' feature was broken in some of earlier versions. Also, for Spanish you need 'es/diseno-web/#hosting', otherwise it will not switch language: https://qtranslatexteam.wordpress.com/2015/02/26/browser-redirection-based-on-language/. I am closing it now, to save clicks, we can continue discussion under closed issue, or can re-open it, if needed. |
|
Hi again, I have the latest version installed. I go to: Appearance / Menus / English Tab Conclusion: I cannot add different URL's per langauge in the menu sub item - but I must be able to do this as those are the basics of a multilingual site or not? So I do not know why you are closing this thread as for me it is a bug. Please explain. And re-open this thread as I think it is not working as it should. we should be able to add different URL's per language in custom sub items - but it is not possible You can check on my dev site if you like... Thanks |
|
explained one and another here: |
|
It is explained that it is not working right now ;-) |
|
Ok, indeed, it seems I misread the issue.
This is right, the URL field is not multilingual, and it is not needed to be. Put basic bare URL there and conversion to active language happens automatically when menu is rendered on front-end. Is that what you need? The FAQ I cited, explains how to cancel this behaviour if needed. |
|
Hi, Thanks yes it does create URL's but not translated ones. I believe the whole problem already starts when creating pages. I create a page and call it: English: Photography Now the SEF URL's for those pages should be: English: mysite.com/en/photography But this is not the case! It creates the URL's English: mysite.com/en/photography So as you see it creates SEF pages but NOT translated ones and "photography" is not translated. When creating one page - I cannot change the permalinks of those pages as per language - I can only change them for all languages. Example: When I change the permalink on the Spanish Tab of "Photography" to "fotografia" in the permalink and save it - it saves it for all Languages instead of only for one language in this case Spanish - as I selected the Spanish Tab. I can translate those URLs to their correspondent language using "qTranslate slug" Plugin and then yes I can add the slugs to each language and my URL's look as they should: English: mysite.com/en/photography HOWEVER this does not work for Custom sub Item URL's: When I do the translations with "qTranslate slug" it does not create the slugs if you add a Custom sub item Link to "Photography" It then again creates the non translated URL's such as (It takes you to the correct place in the frontend but with a URL that is NOT Translated.) English: mysite.com/en/photography/#sub-item instead of expected: English: mysite.com/en/photography/#sub-item-english I believe that if you made the native wordpress permalinks inside the Pages translatable and work with qTranslate-X it would already solve the whole problem - but that is just a guess... and if you could solve the problem from that point the third party plugin "qTranslate slug" would not be needed and nobody would depend on their dev's... I hope you understand the problem now. As I believe anybody who wants his URL's SEF in a multilingual environment wants them to be translated in the according language. |
|
Again, qTranslate Slug causes problems. A workaround with SEF urls is possible. you say "But this is not the case! It creates the URL's" |
|
@mediafish: this should be addressed to QTranslate Slug plugin, not here. We used to be in touch with them, but they went silent: not-only-code/qtranslate-slug#108. Unless they start acting again, we plan to re-implement -slug functionality under q-X natively, and then this problem will be gone. Until then, I suggest not to use QTranslate Slug, since the problem you address here is not the only one, you will discover more as you go deeper. BTW, if we do this, it will be done in this way: English: http://www.mysite.com/photography since slug defines the language, unless it is spelled the same, then /xx/ language code will be added. |
|
BTW, @mediafish and @Grafcom, what would you think is better, to add /xx/ for slugs spelled the same, or to require from user to always spell them differently? |
|
Hi, Thanks but I do not want to talk to qTranslate Slug... as I think qTranslate-X should offer SEF URL's in their own Plugin - as the Plugin is Good and should really offer this - I think it is basic to have URL's translated to their according language.... The URL's must be: English (If main language of the site no /en/ is shown at least on my site and this is good...): http://www.mysite.com/photography AGAIN: I think if you fixed that we can translate Permalinks inside pages for each language - the problem would be solved... The user should be able to add those in the according language @johnclause what do you mean by: "slugs spelled the same" ? |
|
/xx/ should just be the language identifier, as is now also, I think |
|
yes language identifier should stay as now... if that is the question |
|
I do not get what you are saying here ... Slugs currently come from QTranslate Slug plugin, and that plugin has to be modified to make it work correctly with q-X. If we re-implement it, we will have to also provide an import function to import the slug data from Q-Slug to q-X.
In most of the cases slug will be different for each language, and then language code /xx/ becomes redundant in the url, as many people noticed. Then it makes sense to drop language code like '/xx/' from url, since slug already defines the language - it will look nicer then. I think there is no disagreement on that, everybody to whom I mentioned it, agreed, do you think so? However, when in rare case two languages would have the same spelling (for example, british and american can have that easily), then we have to decide, whether we force users to make slugs different anyway or to put back /xx/ language code in url. I personally is not strongly decided, but I am inclined to the forcing users to use different urls, since this gives them opportunity to do something more creative than robotic /xx/. They can still do 'slug-en' or something like this, which resembles the robotic way too, if nothing else is better. What do you think? |
|
No, I disagree. For example: mediafish uses mysite.com/de/fotografie (German) photography (fotografie) is the same in both languages. More and more English words are as a name and then this goes wrong. Art Journals for example is an understanding (concept) That's what Marit :-) and I think. |
|
I do not see how what you are saying contradicts to the fact that URL like looks better than while they both define the language? What is it exactly you disagree with? I think there is a misunderstanding here. Besides, I remember you, @Grafcom, about a month ago, asking why do we need extra /es/ in a case like this ;) In any case, I guess we will have options for users to define how they want it. |
|
Good morning, Here my experience and known standards for multilingual sites I have worked with over the last 10 years: 1.) We must keep the language codes - there is no doubt about that. a) Now for the main language it does not show the language code on my site now - which is fine and I will show you why. (However Joomla for example offers the option to chose if you want to show the main language with language code or without) This is due to the fact that we have country specific domains for example mine ends in mysite.es and my language structure looks like this: Spanish: mysite.es/fotografia So as you see there is no need to add a language code to the Spanish version due to its domain ending. .es it makes it perfectly clear to users that the language will be Spanish Now if you had a site such as: mysite.com and you wanted your main language in Spanish - it would be nice to have the option to add the language code to your site - however this is optional but the URL would be more SEF Spanish: mysite.com/es/fotografia 2.) @johnclause "AGAIN: I think if you fixed that we can translate Permalinks inside pages for each language - the problem would be solved..." I am talking about the WP integrated Permalinks inside Pages - I am not talking about qTranslateSlug Goto: Pages / Yourpage - that is how it looks like: Language Tabs on Top Yourpage Title When you click the edit button you can change the link - this is WP integrated! But unfortunately this is not integrated in qTranslate-X You should make those Permalinks Translatable and then nobody would rely on a third party Plugin like qTranslateSlug.
We can translate the name of the Category but not the Slug of each language - this must be translatable as well on a well working multilingual Plugin... So those are the main problems I see - there are certain standards - and please do not take the language codes out - EVER. Leave it as an option for the users if they want to show language code in their main language or not - but do not take them out as this would be re-inventing the whole wheel and we do not need that...
Thanks |
|
qTranslate also, see Settings - Languages - Advanced Settings - URL Modification Mode - Hide URL language information for default language. You can choose. |
|
@mediafish thanks for the input - very valuable 👍 Item 1) was already addressed by @Grafcom, indeed we have that option too.
Ok, now I understand what you meant. This is exactly what we are going to do if we re-implement -slug under -x. There is also "Slug" item, when you pull "Screen Options" down, and that one will also respond to Language Switching Buttons. However, it requires a lot of coding due to specific of slug being a part of url, it is not similar to any other translatable field. Look how much code QTranslate Slug has, this is what we would have to add approximately. Having Q-Slug plugin as an example makes it much easier, but still, it is a lot of work. I am not even sure, we may implement it as a separate plugin too. |
|
@Grafcom - thanks ok - I was not sure if it did or if it was by default only know the Plugin for 2 weeks. @johnclause - good :-) I understand this is a free plugin and requires a lot of coding... however I think qTranslate Slug is not using the native Permalinks of WP it is using their own system as Permalinks are hidden when using qTranslateSlug and their own custom fields for slugs appear - so there might be an easyer way. I just hoped your Plugin could do this already... as I am really fed up with the blown up WPML - so I really think you could be successful even charging for it - if it works of course - let's hope you will implement it one day - or WP adds multilingual use to it's core... |
|
hi, sorry for being silent :) yes, qts is big.. a big mess! :D but its working, and i've just updated qts language widget to play nice with qtx! |
|
Just updated the version to qTranslateX Version 3.2.9.9.3 and qTranslate Slug Version 1.1.16 and I can still not translate custom URL's in the menu (sub-items) per language - so - no need to talk ;-) If you want you can test it on my site... no way it is working. I want the English URL for my sub-item to be: en/webdesign/#maintenance It simply does not save the URL per language but saves 1 URL for all Also I get the Warning Message: Qtranslate Slug: But my WP Version is 4.1.1 - qTranslateX Version 3.2.9.9.3 so why the warning? |
|
Got rid of warning message as I had to access the site with FTP the folder name must be qtranslate-x but it was qtranslate-x-master so I changed it but only got rid of warning message - I can still not translate sub item URL's to according language - it translates always all URL's to the same.. |
|
I hope to have language dependant slugs soon, this is quite important for SEO. Now it looks like it's possible, but it's not, because it -as stated by others- simply changes things for all languages. That said, i also agree that it should keep the language indentifiers in the URLs, because it's much more clear to the user (especially if not all content is translated) and better for SEO (definitely not force unique slugs across languages). /de/fotografie should both be able to exist. And then things like /en/photography |
|
@mediafish , you're right, custom links aren't parsed by qts. let me see if i can fix it next releasee. @koen84, if you're not using not-only-code/qtranslate-slug yet, you should ;) |
|
Besides the URL / slug for pages and posts, it would be good if we could apply it also to categories. |
|
you can |
|
@koen84 , qtx was running too fast away from the original qtranslate, so things broke a lot. We were always compatible with qtranslate and mqtranslate. I've updated qts to be compatible again with qtx now that mqtranslate stop being actively developed. you can use it from the main wordpress site: wordpress.org/plugins/qtranslate-slug |
|
@LC43 and @koen84 - I started this topic and its about translating sub item URL's. @koen84 - with the latest qTranslate Slug https://wordpress.org/plugins/qtranslate-slug/ together with the latest qTranslate-X Beta Version https://github.com/qTranslate-Team/qtranslate-x/archive/master.zip you can translate category names - just make sure after installation of qTranslate-X to access the site with FTP the folder name must be qtranslate-x but it is probably qtranslate-x-master... if that is done it translates categories - but NOT menu sub item URL's... So thanks for posting but it does not concern this topic. |
Tuesday Apr 07, 2015 at 08:17 GMT
Originally opened as qTranslate-Team/qtranslate-x#120
Hi,
In Appearance > Menus I have one menu.
Now I created sub Custom sub item with URL's but I cannot change the URL's per language - when changing one URL it applies to all languages which is not what I would expect.
I created various ID's on my page - in this case on the page web-design for example: Hosting
In the English version the URL to it would be
en/web-design/#hosting
In the Spanish version the URL to it would be
/diseno-web/#hosting
In the German Version the URL to it would be
de/webdesign/#hosting
But it does not let me create different URL's and save them in the Menu Structure > Custom sub item.
Now I can create different Navigation Labels and Title Attributes for each language and it saves them but it does not save the different URL's... which is very strange.
I deactivated all plugins except qtranslate-x and activated the theme 2014 having this same result.
The text was updated successfully, but these errors were encountered: