Filters are gone and the archive page has huge whitespace on top

  • wpsolr
    Keymaster
    4 years, 6 months ago #14692

    Can you tell me what is your status now.

    finalwebsites
    Participant
    4 years, 6 months ago #14694

    Still the same problem, it was just one that I looked at the wrong site. I did anything you have suggested, nothing helps.

    wpsolr
    Keymaster
    4 years, 6 months ago #14696

    You did not tell me what errors are in your debug.log

    Also, check that you use PHP 7.1 at least.

    finalwebsites
    Participant
    4 years, 6 months ago #14699

    I’m using php 7.1 (btw it worked last week)
    Here is this log:

    [21-Oct-2019 14:59:30 UTC] WPSOLR message: {“error”:{“root_cause”:[{“type”:”illegal_argument_exception”,”reason”:”Fielddata is disabled on text fields by default. Set fielddata=true on [pa_arrangeur_str] in order to load fielddata in memory by uninverting the inverted index. Note that this can however use significant memory. Alternatively use a keyword field instead.”}],”type”:”search_phase_execution_exception”,”reason”:”all shards failed”,”phase”:”query”,”grouped”:true,”failed_shards”:[{“shard”:0,”index”:”hafabra_index_new”,”node”:”64_mCJnUSO-tD72bkdrQlg”,”reason”:{“type”:”illegal_argument_exception”,”reason”:”Fielddata is disabled on text fields by default. Set fielddata=true on [pa_arrangeur_str] in order to load fielddata in memory by uninverting the inverted index. Note that this can however use significant memory. Alternatively use a keyword field instead.”}}],”caused_by”:{“type”:”illegal_argument_exception”,”reason”:”Fielddata is disabled on text fields by default. Set fielddata=true on [pa_arrangeur_str] in order to load fielddata in memory by uninverting the inverted index. Note that this can however use significant memory. Alternatively use a keyword field instead.”,”caused_by”:{“type”:”illegal_argument_exception”,”reason”:”Fielddata is disabled on text fields by default. Set fielddata=true on [pa_arrangeur_str] in order to load fielddata in memory by uninverting the inverted index. Note that this can however use significant memory. Alternatively use a keyword field instead.”}}},”status”:400}
    [21-Oct-2019 14:59:30 UTC] WPSOLR trace: #0 /srv/users/hafabramuziekshop/apps/hafabramuziekshop/public/wp-content/plugins/wpsolr-pro/wpsolr/core/vendor/elasticsearch/elasticsearch/src/Elasticsearch/Connections/Connection.php(310): Elasticsearch\Connections\Connection->process4xxError(Array, Array, Array)
    #1 /srv/users/hafabramuziekshop/apps/hafabramuziekshop/public/wp-content/plugins/wpsolr-pro/wpsolr/core/vendor/react/promise/src/FulfilledPromise.php(25): Elasticsearch\Connections\Connection->Elasticsearch\Connections\{closure}(Array)
    #2 /srv/users/hafabramuziekshop/apps/hafabramuziekshop/public/wp-content/plugins/wpsolr-pro/wpsolr/core/vendor/guzzlehttp/ringphp/src/Future/CompletedFutureValue.php(55): React\Promise\FulfilledPromise->then(Object(Closure), NULL, NULL)
    #3 /srv/users/hafabramuziekshop/apps/hafabramuziekshop/public/wp-content/plugins/wpsolr-pro/wpsolr/core/vendor/guzzlehttp/ringphp/src/Core.php(341): GuzzleHttp\Ring\Future\CompletedFutureValue->then(Object(Closure), NULL, NULL)
    #4 /srv/users/hafabramuziekshop/apps/hafabramuziekshop/public/wp-content/plugins/wpsolr-pro/wpsolr/core/vendor/elasticsearch/elasticsearch/src/Elasticsearch/Connections/Connection.php(322): GuzzleHttp\Ring\Core::proxy(Object(GuzzleHttp\Ring\Future\CompletedFutureArray), Object(Closure))
    #5 /srv/users/hafabramuziekshop/apps/hafabramuziekshop/public/wp-content/plugins/wpsolr-pro/wpsolr/core/vendor/elasticsearch/elasticsearch/src/Elasticsearch/Connections/Connection.php(220): Elasticsearch\Connections\Connection->Elasticsearch\Connections\{closure}(Array, Object(Elasticsearch\Connections\Connection), Object(Elasticsearch\Transport), Array)
    #6 /srv/users/hafabramuziekshop/apps/hafabramuziekshop/public/wp-content/plugins/wpsolr-pro/wpsolr/core/vendor/elasticsearch/elasticsearch/src/Elasticsearch/Transport.php(110): Elasticsearch\Connections\Connection->performRequest(‘POST’, ‘/hafabra_index_…’, Array, ‘{“from”:0,”size…’, Array, Object(Elasticsearch\Transport))
    #7 /srv/users/hafabramuziekshop/apps/hafabramuziekshop/public/wp-content/plugins/wpsolr-pro/wpsolr/core/vendor/elasticsearch/elasticsearch/src/Elasticsearch/Client.php(1779): Elasticsearch\Transport->performRequest(‘POST’, ‘/hafabra_index_…’, Array, Array, Array)
    #8 /srv/users/hafabramuziekshop/apps/hafabramuziekshop/public/wp-content/plugins/wpsolr-pro/wpsolr/core/vendor/elasticsearch/elasticsearch/src/Elasticsearch/Client.php(1127): Elasticsearch\Client->performRequest(Object(Elasticsearch\Endpoints\Search))
    #9 /srv/users/hafabramuziekshop/apps/hafabramuziekshop/public/wp-content/plugins/wpsolr-pro/wpsolr/core/classes/engines/elasticsearch_php/class-wpsolr-searchelasticsearchclient.php(92): Elasticsearch\Client->search(Array)
    #10 /srv/users/hafabramuziekshop/apps/hafabramuziekshop/public/wp-content/plugins/wpsolr-pro/wpsolr/core/classes/engines/class-wpsolr-abstractsearchclient.php(905): wpsolr\core\classes\engines\elasticsearch_php\WPSOLR_SearchElasticsearchClient->search_engine_client_execute(Object(Elasticsearch\Client), Array)
    #11 /srv/users/hafabramuziekshop/apps/hafabramuziekshop/public/wp-content/plugins/wpsolr-pro/wpsolr/core/classes/engines/class-wpsolr-abstractsearchclient.php(878): wpsolr\core\classes\engines\WPSOLR_AbstractSearchClient->execute_query()
    #12 /srv/users/hafabramuziekshop/apps/hafabramuziekshop/public/wp-content/plugins/wpsolr-pro/wpsolr/core/classes/ui/class-wpsolr-query.php(352): wpsolr\core\classes\engines\WPSOLR_AbstractSearchClient->execute_wpsolr_query(Object(wpsolr\core\classes\ui\WPSOLR_Query), false)
    #13 /srv/users/hafabramuziekshop/apps/hafabramuziekshop/public/wp-includes/class-wp-query.php(3403): wpsolr\core\classes\ui\WPSOLR_Query->get_posts()
    #14 /srv/users/hafabramuziekshop/apps/hafabramuziekshop/public/wp-includes/class-wp.php(622): WP_Query->query(Array)
    #15 /srv/users/hafabramuziekshop/apps/hafabramuziekshop/public/wp-includes/class-wp.php(739): WP->query_posts()
    #16 /srv/users/hafabramuziekshop/apps/hafabramuziekshop/public/wp-includes/functions.php(1105): WP->main(”)
    #17 /srv/users/hafabramuziekshop/apps/hafabramuziekshop/public/wp-blog-header.php(16): wp()
    #18 /srv/users/hafabramuziekshop/apps/hafabramuziekshop/public/index.php(17): require(‘/srv/users/hafa…’)
    #19 {main}

    finalwebsites
    Participant
    4 years, 6 months ago #14700

    pa_arrangeur is a taxonomy (WC product attribute)

    I don’t have those custom fields

    wpsolr
    Keymaster
    4 years, 6 months ago #14703

    It looks like a ghost. pa_arrangeur was selected on a previous env, then cloned. The WPSOLR settings is still using pa_arrangeur, but no field is there anymore on the cloned env.

    finalwebsites
    Participant
    4 years, 6 months ago #14704

    and how can I solve that?

    wpsolr
    Keymaster
    4 years, 6 months ago #14705

    In screen 2.2, uncheck your post type (“Product” I guess”) then save. It should reset your settings.

    Then, check “Product” and configure your taxonomies and fields, again.

    • This reply was modified 4 years, 6 months ago by wpsolr.
    finalwebsites
    Participant
    4 years, 6 months ago #14710

    I can’t disable the Products post type on 2.2.
    After page load the checkbox is checked again.

    wpsolr
    Keymaster
    4 years, 6 months ago #14713

    You can reset your screen 2.2 in the “4. Import/export settings” screen. See https://www.wpsolr.com/forums/topic/reset-configuration/.

    Use the following snippet in the import textarea, then import to reset the 2.2 data settings:

    {
        "wdm_solr_form_data": {
              "p_types": "",
               "taxonomies": ""
         }
    }
    finalwebsites
    Participant
    4 years, 6 months ago #14714

    Okay I did that, but I can’t re-index them I see this error on the screen:

    failed to parse field [id] of type [long] in document with id ‘pa_componist_24886’

    (the same like before)

    wpsolr
    Keymaster
    4 years, 6 months ago #14715

    It seems this product attribute contains a string ‘pa_componist_24886’ in its ‘id’ field, which should be an integer.

    finalwebsites
    Participant
    4 years, 6 months ago #14716

    The database table structure had only integer fields for the IDs.
    So that can’t be possible.

    wpsolr
    Keymaster
    4 years, 6 months ago #14717

    Yes, and ‘id’ is expected to be a string in your index schema. But, according to the error, it is set as an integer.

    It looks like the index is not configured with the proper settings. I suggest to create a brand new index, from the plugin screen “0. Connect your indexes”

    finalwebsites
    Participant
    4 years, 6 months ago #14719

    I did this and after trying to index I get this error on the same page as before:

    failed to parse field [id] of type [long] in document with id ‘pa_componist_24886’

    Looks like some other problem 🙁

Viewing 15 posts - 16 through 30 (of 38 total)

You must be logged in to reply to this topic.