Not working correctly since version 3.6.6

  • Resolved Warren

    (@rabbitwordpress)


    2 years, 4 months ago

    Hi there,

    We have been experiencing issues with ElasticPress for a number of months now. Running versions 4.0.0 to 4.3.1 certain search queries have produced inaccurate results. A number of SKUs have also produced ‘not found’ when in fact they do exist, both in the desc field and sku.

    We worked with Kualo, our web hosting company for help but after weeks of investigation and tests were unable to diagnose the issue. Kualo recommended we seek help from ElasticPress.

    Contact was made with ElasticPress and we were told they are unable to debug since our queries were logged on a third-party/self-hosted server. In order to fix the problem and provide assistance we were advised to signup to one of the ElasticPress monthly plans or hire an engineer @ $150 per hour.

    We signed up for the Essential plan and worked with engineers at ElasticPress for over two weeks but unfortunately they were not able to get it working. We cancelled the plan and ended up back at square one.

    Looking back at the ElasticPress changelog I noticed some major changes in version 4.0.0. I decided to rollback the plugin to version 3.6.6 and to our relief everything worked perfectly again!

    Please see changelog here: https://github.com/10up/ElasticPress/blob/develop/CHANGELOG.md#400—2022-03-08

    Specifically – case ‘description’: from ElasticPress\Indexable\Term\Term::parse_orderby removed and new ’Sync’ page, could these be the changes affecting our website.

    FYI we will continue using version ElasticPress 3.6.6 in the ‘Third-Party/Self-Hosted’ server from now on in the live production site until a solution is found that enables us to upgrade to the latest version safely.

    To demonstrate the problem please try searching:

    Harvey Jones

    on:

    Staging site – ElasticPress 4.3.1 [NOT WORKING]
    https://dev.usedkitchenexchange.co.uk/

    Live production site – ElasticPress 3.6.6 [WORKING]
    https://www.usedkitchenexchange.co.uk/

    Can you help and do you have any solutions for this please so we can upgrade to the latest version?

    Many thanks
    Warren

    • This topic was modified 2 years, 4 months ago by Warren.
    • This topic was modified 2 years, 4 months ago by Warren.
Viewing 1 replies (of 1 total)
  • Plugin Contributor vhauri

    (@vhauri)

    Hi @rabbitwordpress ,

    If you’re looking to get cost-free support and you believe this issue is a general bug in the plugin, please use the Github issues list to submit an issue https://github.com/10up/ElasticPress/issues. However, Github support is limited to resolving plugin bugs, and we cannot provide support for individual sites running custom code (as we’ve determined applies to your site), unless you’re able to provide initial troubleshooting and identify the bug does not lie with your code, but is present in ElasticPress without any custom code running.

    The code you referenced above is unlikely to be related to any issues you’re seeing with inaccurate results. This is because the Terms feature plays no part in the search on your site, and the Sync page is simply an enhancement to how the content is synced with Elasticsearch–it does not affect search results in any way.

    However, between 3.6.6 and 4.3.1 there have been major changes to the search algorithm, which would change how results are displayed. Using the Debug Bar ElasticPress plugin will show you the exact queries being sent, both from WordPress’ and ElasticPress’ perspectives, as well as the results from your Elasticsearch endpoint.

    This entire process is contained in open code which can be easily troubleshot, with the exception potentially of your Elasticsearch endpoint itself, where logging is a matter of you implementing an adequate solution. For example, the Debug Bar ElasticPress output will show you if your SKU is being properly searched by the search query, and also if the SKUs are being properly synced to your Elasticsearch index. If the data is not being synced, you can use the filters ElasticPress provides to add it to the sync. If it’s not being searched, you can add it to the weighting engine page or simply hardcode the field and a weighting value using the appropriate filters in the plugin. This is the work we’d perform if you engage with us for consulting services, but it can just as easily be performed by your team or a freelancer with experience in WordPress.

    As you noted, we recommended that you engage with us for engineering consulting, since this issue will require customizing results specifically for your site, and we’re unable to change or write code specific to single sites through Github/general plugin support. Again, this entire issue can be easily debugged on your end, but we’re simply not in a position to offer free support on a per-site basis for one-off issues.

Viewing 1 replies (of 1 total)
  • The topic ‘Not working correctly since version 3.6.6’ is closed to new replies.