Cyrillic topic slugs are limited to ~33 characters on Rosetta forums

[SergeyBiryukov]

Background: #1298

This is essentially a WordPress core issue (​#wp10483), but since it's a regression on the forums after the upgrade to bbPress 2.x in #1544, maybe we could tackle it on WP.org separately?

Currently, topic slugs on Rosetta forums are limited to ~33 characters, and anything after that is just silently cut off.

For a language where most words are longer than in English, this is often insufficient. English topic slugs, on the other hand, allow up to 80 characters (which is the maxlength attribute on the input).

Some examples of recent topics where the title is OK, but the slug was cut off:

• ​https://ru.wordpress.org/support/topic/как-настроить-уведомления-на-email-о-получ
• ​https://ru.wordpress.org/support/topic/написание-плагина-скрытый-контент-оп
• ​https://ru.wordpress.org/support/topic/загруженные-изображения-не-привязыв

To get a feeling of what it looks like to a Russian speaker, imagine if these (random) topics on English forums:

• ​https://wordpress.org/support/topic/fatal-error-call-to-undefined-function-add_shortcode_param
• ​https://wordpress.org/support/topic/new-post-gives-you-are-currently-editing-the-page-that-shows-your-latest-posts
• ​https://wordpress.org/support/topic/i-cant-update-the-plugins-but-i-see-they-need-to-be-updated

had slug like these:

• ​https://wordpress.org/support/topic/fatal-error-call-to-undefined-fun/
• ​https://wordpress.org/support/topic/new-post-gives-you-are-currently/
• ​https://wordpress.org/support/topic/i-cant-update-the-plugins-but-i-s/

Doesn't look too informative, does it?

Previously, slugs were cut around ~48 characters, which is still is less than enough, but better than ~33.

[Otto42]

I went and had a look at the tables, and the post_name is indeed a varchar(200). So, any solution we have to this would probably need to be increasing that size, which means we need to rely on what the plans for core are to do it properly.

Any progress on this in any other core tickets?

[netweb]

I just peeked at ​#wp10483 and the gist of it seemed to be to wait until MySQL 5.x was the default, that has now come and gone and MySQL 5.0.x is now only 4.2% according to ​https://wordpress.org/about/stats/

How about doing ​#wp10483 4.7-early?

[netweb]

Replying to netweb:

I just peeked at ​#wp10483 and the gist of it seemed to be to wait until MySQL 5.x was the default, that has now come and gone and MySQL 5.0.x is now only 4.2% according to ​https://wordpress.org/about/stats/

How about doing ​#wp10483 4.7-early?

MySQL 5.0 usage is now 2.2%, will update ​#wp10483 and propose this for WP 5.0

[dd32]

Technically a regression, but lets close in favour of ​#core10483