Forums › Forums › Search & Filter Pro › GTranslate language lost
Tagged: GTranslate
- This topic has 6 replies, 3 voices, and was last updated 5 years, 4 months ago by
Ross.
-
Trevor(Private) November 11, 2020 at 4:26 pm #266072
I think the GTranslate plugin translates the web pages in the front end? We do support plugins like WPML and Polylang because they translate by creating new posts and taxonomies and assign them to each language, which is the way our plugin works (it needs a form per language, linked to that language).
Our plugin cannot support translations done in any other way, sorry (apart from the default language of course).
Ross Moderator(Private) November 17, 2020 at 11:24 am #266715This reply has been marked as private.Ross Moderator(Private) November 18, 2020 at 9:05 am #266846Hi Tony
It looks like you’re on the right path with modifying the URLs.
It can get tricky making a solution that covers all cases because a few things need to be condsidered:
1) Display method – if display method is “shortcode”, for ajax – an
admin-ajax.phprequest is performed – and sometimes we need to add a URL param, and implement that manually into the query to affect language (you can see how we do it with Polylang by checking:search-filter-pro/includes/third-party.phpand searching for the filters:sf_archive_results_url sf_ajax_results_url sf_ajax_form_urlIf we use another display method, the ajax request is usually performed on the front end of the site.
2) What happens when we enable something like WooCommece with products and variations – we would need to do a lot of testing on this
It’s basically going to take a fair bit of testing and integration – while we are happy to get this included at some point – we’re focussing all our dev resources on finishing version 3 of our plugin.
Once that’s complete, we can revisit this and get something official done.
Best
-
AuthorPosts