Search

WordPress AI Recommendations
- SEO, conversions -

Forum Replies Created

  • scmsteve
    Participant
    3 years, 3 months ago in reply to: Updated documentation? #23108

    I cannot edit my post, but I do see some search results, I just can not tailor anything to be the way I would like it despite changing the “Define your search” settings and jquery selectors/etc. I haven’t seen any examples about the backend search and how that is supposed to work, just the fact that it is mentioned that it does. Well, it doesn’t here. 🙂 That is, in the orders list, it isn’t displaying anything about orders, the search box is showing messages/replies from our bbpress forum. Very strange.

    scmsteve
    Participant
    3 years, 3 months ago in reply to: Updated documentation? #23106

    I am not generally stupid, but I still can not figure out how to get anything useful out of this beyond getting elasticsearch loaded up locally, defining indexes, and seeing them index, but I can’t get anything meaningful at all in backend or frontend searches.

    Is there a simple set of instructions specifically tailored for that? On the frontend to get it searching using this, ideally with perhaps search fields in different areas searching different content (i.e. posts versus pages versus products) and how to get the backend, for example the orders list, to use this search?

    I’m really missing something vital but simple it seems, just can’t get anything to work. 🙁

    scmsteve
    Participant
    3 years, 6 months ago in reply to: Gets "stuck" indexing orders #21909

    After removing that old (pre WooCommerce 2.00) _order_items metadata, everything indexed fine under 21.9, although I still am working through getting the searches up and running.

    scmsteve
    Participant
    3 years, 6 months ago in reply to: Gets "stuck" indexing orders #21907

    A side note: It takes a VERY LONG time to load the “Data” tab to select the fields/etc, and there over sixteen thousand in our case, I had to change our PHP config to allow that form to post as it was limited to 5000 fields. Would it be possible to break that page up into smaller sections? I’ll post this as a feature request, whether you are interested in doing it or not at least it will be out there.

    scmsteve
    Participant
    3 years, 6 months ago in reply to: Gets "stuck" indexing orders #21906

    Very good question, I did not think of where it was coming from, I just know that it was there. I did a grep through our entire plugin directory and only found it in two places.

    WooCommerce has it in an old wc_update_200_line_items() where it migrated from that format and put them into the newer line item format. So this must be very old data that never was migrated. There are also a lot of _order_items_old which was done as part of that conversion. I will check with the site owner, but I think this can be deleted now probably. Strangely enough, of the existing (717) _order_items metadata entries are either blank (19), for the same product (698), or (19) that contain that product and others. It seems that that product, for whatever reason, failed conversion when it was done, but these can go away.

    I will put 21.9 back in, exclude that field now knowing it is not relevant, and report back. Thank you for your help to get me to look into this further, I just saw the data in there and assumed (bad move) that it was standard WooCommerce data.

    scmsteve
    Participant
    3 years, 6 months ago in reply to: Gets "stuck" indexing orders #21903

    Also, the content has the same fields as the categories array, just in string form, with the array as 181. Array. 0. 2015-06-08T13:31:41Z. ….
    I’ll blow away the index and go back to 21.8, even though it is known to have issues with WooCommerce 4.4.1 and WordPress 5.5 (5.5.1 installed here).

    scmsteve
    Participant
    3 years, 6 months ago in reply to: Gets "stuck" indexing orders #21902

    I don’t believe it is related at all, as with the 21.8 release it indexed the whole table, only with 21.9 is it not indexing it. But strange, as the contents of the _order_items field are NOT the order items.

    “_order_items_t”: [
    {
    “account”: null,
    “item_meta”: null,
    “line_subtotal”: null,
    “line_subtotal_tax”: null,
    “line_tax”: null,
    “line_tax_data”: null,
    “line_total”: null,
    “name”: null,
    “product_id”: null,
    “qty”: null,
    “tax_class”: null,
    “type”: null,
    “variation_id”: null
    }

    And the “categories” field has this, which also seems to make no sense:

    “categories”: [
    “redacted first and last name and email”,
    “redacted email”,
    “redacted email”,
    “Redacted First Name”,
    “Redacted Last Name”,
    “2015-06-08T13:32:32Z”,
    “redacted ip address”,
    “181”,
    {
    “account”: null,
    “item_meta”: null,
    “line_subtotal”: null,
    “line_subtotal_tax”: null,
    “line_tax”: null,
    “line_tax_data”: null,
    “line_total”: null,
    “name”: null,
    “product_id”: null,
    “qty”: null,
    “tax_class”: null,
    “type”: null,
    “variation_id”: null
    },

    Since it is complaining about the categories, it makes sense that the latter is what it is having problems with, maybe because it expects an array of strings not an embedded array? I don’t know why there is one in there, what 181 means, and the fact that the other entries in there are not categories to begin with.

    scmsteve
    Participant
    3 years, 6 months ago in reply to: Gets "stuck" indexing orders #21899

    Oh, I had updated to the interim release 21.9 for the WooCommerce 4.4.1 release, maybe that added this problem.

    scmsteve
    Participant
    3 years, 6 months ago in reply to: Gets "stuck" indexing orders #21898

    Strange, I thought I had answered this. Built-In search was extremely slow, but I still don’t have this working right to compare. I have “results” autocompleting in that box, but having a hard time getting *relevant* results, it is bringing up pages/posts not orders. Strange. I’ll pursue that in a separate thread if needed.

    But this saga continues… While I had it complete an index, I made some changes and, for testing, re-indexed everything and now it is hitting an error I didn’t see the first time:

    {“nb_results”:0,”status”:0,”message”:”failed to parse field [categories] of type [text] in document with id ‘250804’. Preview of field’s value: ‘{tax_class=null, line_subtotal_tax=null, type=null, item_meta=null, line_total=null, line_tax_data=null, variation_id=null, line_subtotal=null, qty=null, product_id=null, name=null, line_tax=null, account=null}'”,”indexing_complete”:false}

    That is an order, should it have a “category”? Or does it mean category on the product in the order? If so, the order only has one item which is in a category of “Other”.

    scmsteve
    Participant
    3 years, 6 months ago in reply to: Gets "stuck" indexing orders #21885

    Had one more error, due to a long field, the order items field where they had a VERY LARGE order, over 32766 chars in that field. So I changed that type to the text that is too large to fit in other types and it seems to be indexing past that point now as well. 🙂

    Not quite “plug and play”, much to learn, but I think this is going to give us a huge improvement once done.

    scmsteve
    Participant
    3 years, 6 months ago in reply to: Gets "stuck" indexing orders #21878

    This seems to be orders that were imported from another system earlier than our WooCommerce store:

    “_order_number_i”: [
    64698707615563
    ],
    “_order_number_str”: [
    64698707615563
    ],

    The error after importing one row at a time was:
    {“nb_results”:0,”status”:0,”message”:”failed to parse field [_order_number_i] of type [integer] in document with id ‘261149’. Preview of field’s value: ‘64698707615563’”,”indexing_complete”:false}

    I guess that number is too large for an integer? I will change the data section so that the order_number is text (sortable) instead of integer, that should fix it. There are too many that were imported with numbers larger than will fit in an integer.

    This may be my fault, I don’t think the default for the order_number was integer, I didn’t know there were values that would overflow it. 🙂

    scmsteve
    Participant
    3 years, 6 months ago in reply to: Gets "stuck" indexing orders #21877

    Actually, *this* thread seems more relevant, but I am not running PHP 7.4:

    Error when indexing products

    Going to try debug on with batch of 1 to see if I can find the order and maybe find what is wrong…

    scmsteve
    Participant
    3 years, 6 months ago in reply to: Gets "stuck" indexing orders #21876

    Did not fix. I did get “{“acknowledged”:true}” when I ran it, but still the error happens. I removed the index and started again, it failed. I started just the orders indexing again, checking to start from the beginning but leave existing data in place, and it was right around 80,000 when it went to 0 and is just sitting there now. Maybe when it times out I will find an error, but the number before I started said there were 210583 orders left to index, the last time it was 210578 so it seems there is something right around that point (whatever that point is) that is causing problems.

    scmsteve
    Participant
    3 years, 6 months ago in reply to: Error when indexing articles #21875

    Is there an explanation of what this does and why it is helpful? And what cases it applies to or resolves?

Viewing 14 posts - 1 through 14 (of 14 total)