We're having enough trouble just making terms non unique without crashing larger sites when we upgrade, so changing post content to arrays is monumental and unlikely.

]]>ChrisFo on "Native Multilingual CMS Features, one more time"https://wordpress.org/ideas/topic/native-multilingual-cms-features-one-more-time#post-27796
Sun, 25 Jan 2015 17:04:44 +0000ChrisFo27796@https://wordpress.org/ideas/I'm no dev, but this seem to be reasonable modifications to the core to allow better ML support/plugins.
]]>MRA_Andy on "Native Multilingual CMS Features, one more time"https://wordpress.org/ideas/topic/native-multilingual-cms-features-one-more-time#post-27523
Fri, 21 Nov 2014 10:32:33 +0000MRA_Andy27523@https://wordpress.org/ideas/This is needed for WordPress!
Multi-language is an important feature. I don´t have the time and I don´t feel like running a multisite setup with different languages. Plugins are difficult, sometimes not consistent and a core ability would be really appreciated.
My special problem is, as I said, a full mutlisite setup with different languages is too much work. However, sometimes an article is important to me, so I like the idea of having an english translation as well. Today the only possibility is to have one article with the text stored in both languages next to each other or to post that article multiple times, each time with a different language.
Both possibilities are not the way to go for me and as I only translate a few articles, multisite isn´t either.
]]>Abhishek V Ashok on "Native Multilingual CMS Features, one more time"https://wordpress.org/ideas/topic/native-multilingual-cms-features-one-more-time#post-27248
Sat, 04 Oct 2014 06:00:05 +0000Abhishek V Ashok27248@https://wordpress.org/ideas/Yes then it will be awesome by the way can you help me in one issue all just go to responsive theme support forums and see my thread within the first page and help me out please
]]>Alan Massimiliano Schiaretti on "Native Multilingual CMS Features, one more time"https://wordpress.org/ideas/topic/native-multilingual-cms-features-one-more-time#post-27210
Fri, 26 Sep 2014 15:45:18 +0000Alan Massimiliano Schiaretti27210@https://wordpress.org/ideas/It would be really nice! Wordpress needs to be a modern CMS with multilingual support in core.
]]>Ihor Vorotnov on "Native Multilingual CMS Features, one more time"https://wordpress.org/ideas/topic/native-multilingual-cms-features-one-more-time#post-27185
Thu, 11 Sep 2014 01:34:31 +0000Ihor Vorotnov27185@https://wordpress.org/ideas/It's been discussed many times and voted high. No significant changes since. Don't get me wrong, I love WordPress and make my living with it for many years. But when I start building large sites in multiple languages I start hating WordPress being oriented to only one language.

I've heavily used these plugins - Polylang, WPML, qTranslate, tested all the rest. Each of them has good and bad sides. So here's the best of all words and how I see it.

1. Add built-in kind-of-taxonomy language, which can be attached to any WP Object - post/page/CPT, taxonomy/CT, nav_menu etc. Make it the first part of URL: example.com/%language%/

2. Add relations to connect any WP Object to another one as a translation (corresponding object in another language). The way it is done in Polylang is pretty nice.

3. Make slugs for any WP Object NOT UNIQUE. WPML plugin allows to have pages and posts in different languages with translated titles and SAME slugs. But it can't do this with tags, categories and custom taxonomies. If we have a language super-taxonomy as a highest hierarchy level (first part of url) then we can differentiate between objects with same slugs. For all internal operations consider slug to be %language_code%-%slug%. This is UNIQUE. But the slug itself is not.

4. Modify core functions to work with translations. For example, wp_insert_term() or wp_insert_post() should accept some extra args, like:

This is not the complete list of changes, of course, but a good point to start from. It will make lives of all non-US developers and users much easier.

Here's why it would be useful. Just one example of many use cases.

Example: Let's pretend we have a site in 2 languages - English, and Russian. And we have a countries custom taxonomy. Russian names are transliterated to latin characters.

example.com/country/russia
example.com/country/rossiya

It's possible to achieve right now, because term slugs are different. But what about Laos (and many other countries as well)? Transliteration will be exactly the same.

example.com/country/laos
example.com/country/laos

Houston, we have a problem! But if we add and parse the language code in front of our url, we will get:

example.com/en/country/laos
example.com/ru/country/laos

Now this allows us possible to filter posts in one language for the given country. But term slug must be NOT unique.

I hope you get the idea.

]]>anca dumitru on "Set category to be used in URL when assigning 2 or more categories to a post"https://wordpress.org/ideas/topic/set-category-to-be-used-in-url-when-assigning-2-or-more-categories-to-a-post#post-24812
Thu, 16 May 2013 20:39:04 +0000anca dumitru24812@https://wordpress.org/ideas/Hello Henry!

]]>Steve Powell on "Make slug collisions more obvious"https://wordpress.org/ideas/topic/make-slug-collisions-more-obvious#post-22412
Fri, 06 Jul 2012 20:09:41 +0000Steve Powell22412@https://wordpress.org/ideas/When I enter a new post title like "My Latest Greatest Idea" the slug becomes 'my-latest-greatest-idea' and I type in my content, post it, and all is well.

7 months pass and I get another idea.

I then start to enter a new post entitled "My Latest Greatest Idea" and the slug becomes 'my-latest-greatest-idea-2' and I type in my content and post it.

I'd like the permalink area on the screen to turn red or orange or something to tell me that a duplicate title was detected and a -2 wart is being added.

Perhaps a note on the screen box says "Note: Another post has a similar title and the permalink was adjusted. <link>View the other post here</link>."

"Even if I trash the first post, I can't get the -2 to go away."

Our users find it frustrating when they see the -2 or -3 or -4 show up on their URLs and they can't figure out why. We hunt down the issue and it turns out the original permalink is on a post in their trash. Emptying their trash allows them to get a clean slug on the permalink.

Providing the informational box above will help alleviate this issue.

Coding this should be somewhat trivial. 1) Find the code where the duplicate slug is detected, 2) use that post info to assemble the cautionary note, 3) update the UI css and content with that note.

Thoughts?
Thanks!

]]>Henry on "Set category to be used in URL when assigning 2 or more categories to a post"https://wordpress.org/ideas/topic/set-category-to-be-used-in-url-when-assigning-2-or-more-categories-to-a-post#post-21771
Mon, 16 Apr 2012 06:53:39 +0000Henry21771@https://wordpress.org/ideas/Currently the category with the lowest ID gets used in the URL when assigning more than two categories to a post.

Would be nice to be able to choose which category gets used in URL.

For example

I assign 3 categories to a post

1. Bars (ID is 3)
2. Restaurants (ID is 16)
3. Hotels (ID is 7)

With default behaviour of WP, the URL will look like this as "bars" has the lowest ID so gets used in the URL:

example.com/category-base/bars/post-title

]]>Wander on "wp_tag_cloud orderby option"https://wordpress.org/ideas/topic/wp_tag_cloud-orderby-option#post-19162
Sun, 24 Apr 2011 03:53:19 +0000Wander19162@https://wordpress.org/ideas/I'd like to suggest that the wp_tag_cloud function be ordered by 'slug'.

Actually only 'name' and 'count' options are available. Ordering by slug is better because some languages contain characters that area not being corrected ordered, i.e., á, ó, ã...