Forum Replies Created
-
AuthorPosts
-
KonceptuelMember
If you do not need multilingual, try https://da.wordpress.org/plugins/loco-translate/
April 19, 2017 at 2:27 am in reply to: WPML and windgets layout on the frontpage in Atmosphere pro #204978KonceptuelMemberHi Boris,
try the WPML Widget plugin.
You can always add extra text widgets to a widget area to get the layout you need.
KonceptuelMemberHey there,
you need to add a social icon widget per language and with this plugin installed
https://wordpress.org/plugins/wpml-widgets/
you can set the language per widget.KonceptuelMemberThank you very much for this simple solution.:-)
It works like a charm. I was looking into jquery matchHeight...:-)KonceptuelMemberWhen Gallery Pro is translation ready you can use the WPML string translation module to translate front-end text strings if there are any.
Other than that it is straight forward.KonceptuelMemberWPML recently published a tutorial on how to translate websites build with Genesis child themes
How to translate Genesis Framework into different languages using WPML
KonceptuelMemberYou need to install WPML and WooCommerce Multilingual.
Just follow WPML instructions.
If the Gallery Pro child theme is properly prepared for translation you'll be fine.KonceptuelMemberIt can be done with WPML through taxonomy translation.
In the slider settings you choose the category (primary language) of posts to show in the slider.
The category must be translated to spanish.
When the post is translated to the secondary language it should show up when that language is chosen.July 21, 2016 at 9:17 am in reply to: Digital Pro; Float Header Menu to the left and 1 menu item to the right #189914KonceptuelMemberHi Christoph,
thank you for replying 🙂I tried to do that, but it didn't work.
When I looked at it this morning with a fresh pair of eyes I compared the to style.css in detail and came up with this solution:.title-area { width: 300px; } //Firefox .genesis-nav-menu { clear: none; } .nav-primary { float: none; } .nav-primary .genesis-nav-menu >li.right { float: right; }
Add the CSS class "right" to the menu item and place that menu item as the first item in the menu.
April 18, 2016 at 5:54 am in reply to: meta-entry terms not present in WPML string translation #183819KonceptuelMemberThe words you want to translate is introduced by the theme's functions.php and the code is not properly marked for translation.
January 29, 2016 at 6:12 am in reply to: Genesis Plugins NOT Appearing on Translated Pages (WPML) #177814KonceptuelMemberWhen you are in the widget area admin screen you choose language in the WPML menu in the admin bar.
Now the Featured page widget should be able to see the translated page.
You'll need to remember which language each widget represents and only open the appropriate widget.
It is a little cumbersome, nut I made it work on a website with the Enterprise Pro theme about a year ago.January 29, 2016 at 1:59 am in reply to: Genesis Plugins NOT Appearing on Translated Pages (WPML) #177801KonceptuelMemberFeatured Pages:
Translate your pages.
Install this plugin https://wordpress.org/plugins/wpml-widgets/
Add a widget per language to the widget area.
Choose the translated page.January 28, 2016 at 2:44 am in reply to: Genesis Plugins NOT Appearing on Translated Pages (WPML) #177718KonceptuelMemberThe Genesis Responsive Slider pulls content from Post Categories.
Setup the slider in the main language of your website.
Create a "Slider" post category.
Create Slider posts.
Use the WPML Taxonomy translation feature to translate your Post Categories.
Use WPML to translate the Slider posts and publish everything.This should work for the Featured Page widget as well.
KonceptuelMemberHi there,
you can use a plugin like https://wordpress.org/plugins/loco-translate/ to translate the text strings in the theme from the WordPress backend.
Or you can use https://poedit.net/ to translate the .mo/.po files that comes with the Genesis framework and child themes.KonceptuelMemberHi Naomi,
when your site is in one language only, other than english, you can use a plugin like https://wordpress.org/plugins/loco-translate/ to translate text strings included in themes and plugins.KonceptuelMemberWith Polylang you can translate:
- posts, pages, media, categories, post tags, menus, widgets...
- Custom post types, custom taxonomies, sticky posts and post formats, RSS feeds and all default WordPress widgets are supported.
The ““Read more”, “Folder under” is not content. It comes from the Genesis framework and/or child theme.
You can translate the strings with the Loco Translate plugin or PoeditAnother option is WPML. It has a string translation module and it will replace Polylang. WPML is an All-In-One solution.
Genesis translations is not designed for multilingual websites, but loads the Studiopress translations for a single language website. The Studiopress translations can be found here. The spanish translation is not complete.
KonceptuelMemberYou are welcome.
Feel free to participate in the translation of Genesis. Your help will be appreciated.
The spanish is 61% complete as of today 🙂October 5, 2015 at 9:05 am in reply to: Translate a Custom Post Type's (CPT) Archive Intro Text #167440KonceptuelMemberWell, I think it is because Polylang is for content translation and you are looking for string translation.
Try the Loco translate plugin.KonceptuelMemberThe official repository has no translations for Executive Pro child theme, because you do not need one.
The .pot file has 10 strings to translate and they apply to the backend only.What you need is to load the translations for the Genesis Framework.
They can be found here: http://translate.studiopress.com/projects/genesis-framework/genesisWith a multilingual website you need to consider how to handle translations for Genesis, plugins, and content.
The all-in-one solution is WPML.
The free option is a combination of for example Polylang and Loco Translate. Just a hint, I have never tried this combo.KonceptuelMemberPolylang allows you to translate:
- posts, pages, media, categories, post tags, menus, widgets...
- Custom post types, custom taxonomies, sticky posts and post formats, RSS feeds and all default WordPress widgets are supported.
The ““Read more”, “Folder under” is not content. It comes from the Genesis framework and/or child theme.
You can translate the strings with the Loco Translate plugin or Poedit.Another option is WPML. It has a string translation module and it will replace Polylang and Loco Translate. WPML is an All-In-One solution.
Genesis translations is not designed for multilingual websites, but loads the Studiopress translations for a single language website. The Studiopress translations can be found here. The spanish translation is not complete.
-
AuthorPosts