Forum Replies Created
I can only emphasize what Remkus said: for new projects using more than 1 language I will only setup Multisite installs. That’s the solution I recommend to all clients since spring of this year. WPML is a solution for not so “techie” users but it is likely to happen they complain in the long run and will find themselves locked in…
The “Multilingual Press” plugin is an option – I consider it some helper tool but in the end it’s not needed. Multisite on its own is the native best solution. Not only for scaling reasons.
Currently this is not possible with the current plugin version! The slug/rewrite rule is hard coded, so no chance.
It neets to be changed to a filter or maybe to settings option.
I hope the plugin authors will change this soon.
November 20, 2012 at 1:17 pm in reply to: New Sub Forum Suggestions: Internationalization/ Translations #917
I like the idea of not having about 50+ forums for child themes that share mostly an identical code base and differ mostly only in some CSS.
For me the Help Desk feels like “Priority Support” (I’ve also experience on other platforms) and I absolutely go with that!
If this forum here is about to grow, which it IS, we shortly have a big new “knowledge base” which also will contain child theme specific information.
The propagated use of tagging makes really sense because child themes not only consist of PHP & CSS but are part of OUR PROJECTS! Therefore we have to deal with different languages for example… If properly tagged we will have lots of aspects for a specific child theme on the table if needed
November 20, 2012 at 12:34 pm in reply to: New Sub Forum Suggestions: Internationalization/ Translations #906
Thanks for your feedback, both!
I agree with Nick, that it would be really cool to have some language specific discussions/tips/whatever in one’s native language
So, since Brian just opened a sub forum, we have our place to go:
Are you using a custom solution or do you work with specific plugins like “WPML”?
If working with WPML a homepage for every language is possible of course! Here and there you’ll need some code snippets to conditionally load stuff for one language or the other. Best to put this all in a functionality plugin or maybe also in the functions.php…
If working with WPML and widgets (also if used for the homepages) it’s best practice to use widgets on a per language basis with helper plugin “Widget Logic”. I’ve done that a couple of times and it’s working great!
However, I would highly suggest a Multisite install for multilingual websites! This has a lot of benefits, because plugins like WPML (and others) are really awesome and work but tend to lock the user in. For “only” 2 languages WPML might be an option but if you need more in the future or need a migration or whatever it could become a pain in the ass… Also, with WPML you have virtually a “dashboard” for each language site… In Multisite you’ll just have 2 real dashboards. But it’s all more performance optimized and you could do most stuff with default WP core stuff .
To help multilingual sites with Multisite there are two plugins that provide great helper tools – but don’t lock you in.
Multisite allows proper import/export the WordPress way. With above helper plugins you’ll great language switchers and for editors helping inpost metaboxes for the added dashboards (easily switching).
What do you think about that?
–Dave from Germany.
(I am a WP/ Genesis translation expert and have done some multilingual sites already…
Thank you, John!
I hope it helps some users to get a more custom setup.
I am also planning a “pro” version of it which will also bring some new widgets for Genesis users – and therefore also useable on any other widget area