• Resolved kruge

    (@kruge)


    
    I'm working on the ic-consult.com page and Search&Filter Pro is one of the plugins used on it.
    
    The customer now wants to switch from Polylang to another Translation plugin, because they want a better interface. Already tried WPML and broke the page with it. :D And another tool before that I already forgot the name of, didn't work either. (the page grew over five years based on Polylang and of course every Plugin was selected and custom code scripted to work with Polylang in that time).
    
    I was already using Translatepress for something on the page (some corner that Polylang wouldn't touch ^^) so the obvious thought is now to try and use Translatepress for the whole page.
    
    But while testing the functionality I now encountered a problem that, if it can't be solved, I would consider the end of that attempt:
    
    I use Search&Filter Pro in several places on the page to filter through some custom content types. The filters are placed on the page via shortcode. In Search&Filter I need to provide the URL to the "target page" where the Plugin will display the results.
    
    In Polylang I use 3 individual searches, each for one of the languages (English, German, French) and each pointing to the target URL of that language (.../en/..., .../de/..., .../fr/...).
    
    But of course in Translatepress there's only the English page so when I switch to German in the frontend and then change a filter that'll send me back to the target URL provided in the filter - which is the English one. This pretty much breaks a big part of the page the way it is, because it relies on Search&Filter in a bunch of places.
    
    Is there a way to solve this I don't see? Google couldn't help and I can't find anything about this in the forums as well.
    
    This would be a pity, because otherwise so far Translatepress masters everything I'm testing on the page (of course on a DEV instance and not live ^^).
    
    Now, I'm also thinking about a possible workaround and one thing that seems to work is this:
    
    I add both the German and the English Filter to the page - each with the right target URL for the language. And if I use the English filter now, I land on the English page, when I use the German filter I land on the German page.
    
    Now, this does work and I could, with CSS, also remove the "wrong" filter from each page, so the visitor isn't confused. Buuuuuut: The pagination links still only point at the English page, no matter whether they're under the German or the English Results.
    
    And last but not least: While, indeed, the workaround partially solves the problem (for the filters, not for the pagination) it seems rather clumsy to me and when more languages are added to the page as planned I'll have to add those filters to the page as well and I don't know if that's endlessly scaleable or will lead to it's own problems later...
    
    So, do you have any suggestion what I could try to make this work?
Viewing 2 replies - 1 through 2 (of 2 total)
  • <span style=”background-color: initial; color: rgb(64, 82, 97); font-family: Arial, Helvetica, Verdana, Tahoma, sans-serif; font-size: 14px; white-space-collapse: collapse;”>Hey there,</span>

    <span style=”color: rgb(64, 82, 97); font-family: Arial, Helvetica, Verdana, Tahoma, sans-serif; font-size: 14px; white-space-collapse: collapse;”>Thanks for reaching out to us!</span>

    <span style=”color: rgb(64, 82, 97); font-family: Arial, Helvetica, Verdana, Tahoma, sans-serif; font-size: 14px; white-space-collapse: collapse;”>??It seems that you have an ongoing conversation on this topic with one of my colleagues, do you wish to keep this topic open on www.ads-software.com also???</span>

    <span style=”color: rgb(64, 82, 97); font-family: Arial, Helvetica, Verdana, Tahoma, sans-serif; font-size: 14px; white-space-collapse: collapse;”>Please let me know about this.??</span>

    <span style=”color: rgb(64, 82, 97); font-family: Arial, Helvetica, Verdana, Tahoma, sans-serif; font-size: 14px; white-space-collapse: collapse;”>Best Regards,</span>

    Thread Starter kruge

    (@kruge)

    no, thank you, it can be closed

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Search and Filter and Translatepress’ is closed to new replies.