![]() ![]() We're not in a position to recommend any language-switching plugins, but if you find a good one please let us know so we can link to it. There are no plans to introduce this feature into the Loco Translate plugin at the moment. We don't offer help with coding, but if you're looking to build a language switcher of your own, start by looking at the locale filter. Include the minified model of the jQuery Langauge Selector plugin on the web page. We cover this briefly in the beginner's guide and also offer some more tips here, but that's all the technical support we can offer on the topic.ĭynamically changing language (for anonymous visitors) is not a native feature of WordPress, so implementing a public language switcher requires writing some code (and/or installing a plugin). You can change the default value in your WordPress settings. Your WordPress language is a site option. We are focused on the primary functions of file management and string editing. Never tried with WC Vendors but I don’t think it could not be possible if there is a language structure.Loco Translate does not provide a language switcher, because switching language is not the purpose of the plugin. I really enjoy this plugin as it gives real satisfaction by editing. Would you have heared speaking about a simple switcher plugin ?Ĭoncerning Loco Translate, I will have a try with WC Vendors and will tell you what it gives. Because I didn’t find a way to preserve the original URL. So I will not use Polylang, even if I used it only as a switcher. I take note of the /en /fr URL which will be not appropriate to the vendor dashboard page. This will certainly extend to other browsers in the near future hopefully. But I have to say that, even if I mainly use Firefox on my desktop, I use Chrome on my smartphone and I have noticed that it purposes translation on the fly. Sometimes integration, or simply translation, could be more adapted with a plugin we can control. I know you would not promote one or another of your colleague, but just wanted to know, which ones would be more in phase with the way you code WCV, and I want to restart a clean installation with less plugins but most appropriated with WCV which is the main hinge of the structure □ ![]() I search the best way to do what I need (probably Hypothese 1!) So, before starting working on translation of a website with WCV. Is it still relevant ?Īlso, I saw maybe qTranslate would not be maintained. – to generate all language files even if the Theme/Plugin do not have one (with its default template).īut I read that there could be somes issues with the slug with Polylang. – to keep custom languages files safe from updates The translation of default WordPress/Themes/Plugins languages works great with Loco. On other sites I manage (without WCV) I use Loco Translate to do 1/ and Polylang to do 2/ and that’s working fine. Probably requires some massive custom codes from what I read. ![]() mo files)ģ/ Allow vendors to translate on his dashboard the content he record (product description, product name). mo files)Ģ/ Create flag icons menu on frontend which permits users to switch language.ġ/ Translate the frontend dashboard (through default. Considering evolution of WCV Pro, I would like to know which ones could be appropriated/compatible to do that (2 hypotheses) :ġ/ Translate the frontend vendor dashboard (through default. I saw different topics with different support questions about several translation plugins (like WPML, Polylang, Loco Translate, qTranslate…). I would like your valuable advice, please. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |