탐색 건너뛰기

Open

Reported for: WooCommerce Multilingual & Multicurrency 5.3.9

Topic Tags: WCML

Overview of the issue

When using WooCommerce Multilingual with a multivendor plugin as YITH WooCommerce Multi Vendor, the WooCommerce > Orders admin page experiences excessive database queries, resulting in extremely slow performance or unresponsiveness as the number of orders grows.

Note: keep in mind that a similar behaviour may be noticed with other multivendor plugins.

Workaround

Please, make sure of having a full site backup of your site before proceeding.

  • Open your theme’s functions.php file.
  • Add the following line:
    add_filter( 'wcml_should_translate_order_items', '__return_false');
    

2 응답 에게 “High Query Load on WooCommerce Orders Page When Using Multivendor Plugins”

  1. Hello there

    The workaround with the YITH Multi Vendor Plugin works as far as the reduction of DB queries is concerned, but it produces the problem that the items in the orders are no longer translated (and the vendor names are not translated either). This is of course to be expected if the filter mentioned is set to false.
    Can you provide insight into whether the issues (non translated items) are reversible, i.e. will be resolved with a release/fix, or whether the existing orders that were placed with the workaround activated will stay non-translated after the fix is implemented and the workaround is deactivated?

    And is there already an ETA on when a fix can be expected?

    Many thanks in advance!

    • Hello there,
      This issue has been escalated to our Compatibility team. However, we can’t provide you an ETA and it may probably involve working with YITH team in order to get a definitive solution.
      We will keep this erratum updated once we have any news.
      Regards

답장을 남겨주세요

주제를 유지하고 다른 사람을 존중하십시오. 이 게시물과 관련 없는 문제에 대한 도움이 필요한 경우 지원 포럼을 사용하여 채팅을 시작하거나 티켓을 제출하십시오.

다음 태그를 사용할 수 있습니다.
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>