Viewing 12 replies - 1 through 12 (of 12 total)
  • Thread Starter DODO Internet

    (@studioviv)

    I have reindex the table and now the “hester” is going good. But I still have DE products in my NL products search list:
    https://super-seat.com/?s=st%C3%BChle&post_type=product&type_aws=true&lang=nl

    PS for the previous post: NE is NL

    Plugin Author ILLID

    (@mihail-barinov)

    Hi,

    So speaking about search results on page https://super-seat.com/?s=st%C3%BChle&post_type=product&type_aws=true&lang=nl – can you please give me an example of some DE products here?

    Regards

    Thread Starter DODO Internet

    (@studioviv)

    Hello,

    All chairs with ‘stühle’ in its name are DE products. ‘stühle’ is the German translation of chairs. So there are no ‘stühle’ products on the super-seat.com site. They are only visible on super-seat.de.

    Plugin Author ILLID

    (@mihail-barinov)

    I see it not. Yes very strange indeed. Please tell me plugin AWS plugin version you are currently using?

    Also – is that products with ‘stühle’ word are translated to NL or have only DE translation.

    Regards

    Thread Starter DODO Internet

    (@studioviv)

    I have AWS Version 2.63 installed and active. Also WPML Version 4.5.11, WooCommerce Version 6.8.2 (at the moment I cannot update this plugin to 6.9.4 because of some other plugins) and WordPress Version 6.0.2.

    The products with ‘Stühle’ word are translated products. And have an original NL product. I must say those products are imported products, not created in WordPress.

    Plugin Author ILLID

    (@mihail-barinov)

    Did you mentioned this issue in the previous plugin versions. I think that the problem was probably appears after version 2.63.

    Maybe you can re-install it to version 2.62 and check search results one more time? Old plugin version you can find on this page.

    Regards

    Thread Starter DODO Internet

    (@studioviv)

    I did not mentioned it back then. Because the WPML plugin is recently installed on the site. So i don’t know if the plugin did worked with the previous versions.

    I tried version 2.62, but unfortunate with that version it also doesn’t work correctly. I see in the changelog of 2.63 the fix “SQL query for language selection”. Do you know what this fix was about? Maybe it is related to that bug?

    Screenshot of a search: https://snipboard.io/9hGRzv.jpg

    I did a test with AWS deactivated and with a normal wc search form. And then it works. So there is something buggy in the plugin. Maybe somewhere in the search query?

    I also did a test with a different language URL format. But that didn’t fixed it.

    Plugin Author ILLID

    (@mihail-barinov)

    I see in the changelog of 2.63 the fix “SQL query for language selection”. Do you know what this fix was about? Maybe it is related to that bug?

    Yes, maybe the problem is related to this update. But I can’t tell for sure. So what you can do to test is is to open advanced-woo-search/includes/class-aws-search.php file, find line

    $query['lang'] = $wpdb->prepare( " AND ( lang = '%s' OR lang = '' )", $current_lang );

    and replace it with

    $query['lang'] = $wpdb->prepare( " AND ( lang LIKE %s OR lang = '' )", '%' . $wpdb->esc_like( $current_lang ) . '%' );

    Also open plugin settings page -> Performance tab and click ‘Clear cache’ button. Then check search results one more time.

    Regards

    Thread Starter DODO Internet

    (@studioviv)

    I have changed the code and cleared the cache. But that didn’t fixed it.

    I can create a staging/testing area so you can test, check and change codes in there. Maybe that will help us solve it a bit quicker. What mailaddress can I use for your user account? Because I cannot create a private message for the credentials in this chat.

    Plugin Author ILLID

    (@mihail-barinov)

    Please write directly to [email protected] .

    Thread Starter DODO Internet

    (@studioviv)

    I have send you an email with the login credentials.

    picciudesign

    (@picciudesign)

    Hi,

    we have the same issue, how do you solve this?

    Thanks

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘WPML bug’ is closed to new replies.