WPSolr Not Replacing WooCommerce Archives
- cbarwinParticipant3 years, 8 months ago #20855
Nothing happens.
I am getting this error though now:
2020/07/08 14:48:42 [error] 1736#1736: *217427 FastCGI sent in stderr: “PHP message: WPSOLR Elastisearch query: {“from”:375768,”size”:36,”sort”:[{“date”:{“order”:”desc”}}],”_source”:[“id”,”PID”,”type”,”meta_type_s”,”title”,”numcomments”,”comments”,”displaydate”,”displaymodified”,”*categories_str”,”author”,”*post_thumbnail_href_str”,”*post_href_str”,”snippet_s”],”query”:{“bool”:{“must”:{“query_string”:{“query”:”text:(*)”,”default_operator”:”AND”}},”filter”:{“bool”:{“must”:[{“terms”:{“type”:[“product_variation”]}},{“bool”:{“must”:{“term”:{“type”:”product_variation”}}}},{“terms”:{“type”:[“post”,”product_variation”]}},{“bool”:{“must_not”:[{“terms”:{“PID_i”:[0]}}]}},{“bool”:{“should”:[{“bool”:{“must_not”:[{“bool”:{“must”:{“exists”:{“field”:”is_excluded_s”}}}}]}},{“terms”:{“is_excluded_s”:[“n”]}}]}},{“bool”:{“must_not”:[{“terms”:{“_id”:[“wpsolr_doc_id_attachment”]}}]}}]}}}},”aggs”:{“flat_hierarchy_product_cat_str”:{“filter”:{“match_all”:{}},”aggs”:{“flat_hierarchy_product_cat_str”:{“terms”:{“field”:”flat_hierarchy_product_cat_str”,”size”:100}}}},”attribute_pa_brand_str”:{“f…PHP message: WPSOLR message: {“error”:{“root_cause”:[{“type”:”query_phase_execution_exception”,”reason”:”Result window is too large, from + size must be less than or equal to: [10000] but was [375804]. See the scroll api for a more efficient way to request large data sets. This limit can be set by changing the [index.max_result_window] index level setting.”}],”type”:”search_phase_execution_exception”,”reason”:”all shards failed”,”phase”:”query”,”grouped”:true,”failed_shards”:[{“shard”:0,”index”:”trade_connect”,”node”:”R31moLjFT9SC4IVxvSGmMQ”,”reason”:{“type”:”query_phase_execution_exception”,”reason”:”Result window is too large, from + size must be less than or equal to: [10000] but was [375804]. See the scroll api for a more efficient way to request large data sets. This limit can be set by changing the [index.max_result_window] index level setting.”}}]},”status”:500}PHP message: WPSOLR trace: #0 /www/s41tradeconnect_319/public/wp-content/plugin
wpsolrKeymaster3 years, 8 months ago #20856Issue explained on https://www.wpsolr.com/forums/topic/result-window-is-too-large/
cbarwinParticipant3 years, 8 months ago #20886Error message
E_WARNING: Illegal offset type in isset or emptyStack trace
…1tradeconnect_319/public/wp-content/plugins/facetwp/includes/
class-request.php (134)
…y_vars called at /www/s41tradeconnect_319/public/wp-includes/
class-wp-hook.php (287)
…ilters called at /www/s41tradeconnect_319/public/wp-includes/class-wp-hook.php (311)
…ok::do_action called at /www/s41tradeconnect_319/public/wp-includes/plugin.php (544)
…array called at /www/s41tradeconnect_319/public/wp-includes/class-wp-query.php (1768)
…posts called at /www/s41tradeconnect_319/public/wp-includes/class-wp-query.php (3432)
…uery::query called at /www/s41tradeconnect_319/public/wp-includes/
class-wp.php (624)
…ins/wpsolr-pro/wpsolr/core/classes/services/class-wpsolr-service-container.php (146)
…ins/wpsolr-pro/wpsolr/core/classes/services/class-wpsolr-service-container.php (39)
…loaded called at /www/s41tradeconnect_319/public/wp-includes/class-wp-hook.php (287)
…ilters called at /www/s41tradeconnect_319/public/wp-includes/class-wp-hook.php (311)
…ok::do_action called at /www/s41tradeconnect_319/public/wp-includes/
plugin.php (478)
in do_action called at /www/s41tradeconnect_319/public/wp-settings.php (562)
in require_once called at /www/s41tradeconnect_319/public/wp-config.php (161)
in require_once called at /www/s41tradeconnect_319/public/wp-load.php (37)
in require_once called at /www/s41tradeconnect_319/public/wp-blog-header.php (13)
in require called at /www/s41tradeconnect_319/public/index.php (17)——————-———————————————————————————————————————————————————————
——————-———————————————————————————————————————————————————————
——————-———————————————————————————————————————————————————————2020/07/08 21:22:16 [error] 2536#2536: *62900 FastCGI sent in stderr: “PHP message: PHP Notice: Trying to access array offset on value of type null in /www/s41tradeconnect_319/public/wp-content/plugins/wpsolr-pro/wpsolr/core/classes/extensions/suggestions/class-wpsolr-option-suggestions.php on line 168″ while reading upstream, client: 173.235.72.171, server: s41tradeconnect.com, request: “GET /test/ HTTP/1.0”, upstream: “fastcgi://unix:/var/run/php7.4-fpm-s41tradeconnect.sock:”, host: “s41tradeconnect.com”
cbarwinParticipant3 years, 8 months ago #20897I figured it out. When I disable Toolset Blocks (Toolset Views is now Toolset Blocks) it correctly replaces the Query. Is WPSOLR no longer compatible with Toolset Views/Blocks? Is there a way to disable Toolset replacing the query so WPSOLR can correctly replace the query?
When Toolset Blocks is enabled, this is the Query:
SELECT SQL_CALC_FOUND_ROWS wp_posts.ID
FROM wp_posts
LEFT JOIN wp_term_relationships
ON (wp_posts.ID = wp_term_relationships.object_id)
LEFT JOIN wp_term_relationships AS tt1
ON (wp_posts.ID = tt1.object_id)
LEFT JOIN wp_postmeta
ON ( wp_posts.ID = wp_postmeta.post_id )
LEFT JOIN wp_postmeta AS mt1
ON (wp_posts.ID = mt1.post_id
AND mt1.meta_key = ‘rms_rm_uniq_meta_post_id’ )
LEFT JOIN wp_postmeta AS mt2
ON (wp_posts.ID = mt2.post_id
AND mt2.meta_key = ‘rms_remote_featured_image’ )
LEFT JOIN wp_posts AS p2
ON (wp_posts.post_parent = p2.ID)
WHERE 1=1
AND ( wp_term_relationships.term_taxonomy_id IN (5831,5832,5833,5838,5839,5840,5841,5848,5849,5850,5851,5852,5853,5854,5855,5856,5861,5866,5867,5884,5891,5892,5893,5894,5899,5902,5904,5917,5923,5945,5946,5947,5948,5969,5992,6025,6078,6461,6849)
AND tt1.term_taxonomy_id IN (5831,5832,5833,5838,5839,5840,5841,5848,5849,5850,5851,5852,5853,5854,5855,5856,5861,5866,5867,5884,5891,5892,5893,5894,5899,5902,5904,5917,5923,5945,5946,5947,5948,5969,5992,6025,6078,6461,6849) )
AND ( wp_postmeta.meta_key = ‘_stock’
AND ( mt1.post_id IS NULL
AND mt2.post_id IS NULL ) )
AND wp_posts.post_type = ‘product’
AND (((wp_posts.post_status = ‘publish’
OR wp_posts.post_status = ‘private’)
OR (wp_posts.post_status = ‘inherit’
AND (p2.post_status = ‘publish’
OR p2.post_status = ‘private’))))
GROUP BY wp_posts.ID
ORDER BY wp_postmeta.meta_value DESC
LIMIT 0, 24And this is the caller:
WP_Query->get_posts
WP_Query->query
WP->query_posts
WP->main
wp
require(‘wp-blog-header.php’)———————————————————————————————————————————————-
———————————————————————————————————————————————-
———————————————————————————————————————————————-When Toolset Blocks is disabled, this is the query
SELECT wp_posts.ID
FROM wp_posts
LEFT JOIN wp_postmeta
ON (wp_posts.ID = wp_postmeta.post_id
AND wp_postmeta.meta_key = ‘rms_rm_uniq_meta_post_id’ )
LEFT JOIN wp_postmeta AS mt1
ON (wp_posts.ID = mt1.post_id
AND mt1.meta_key = ‘rms_remote_featured_image’ )
WHERE 1=1
AND wp_posts.ID IN (961484,941936,944419,940164,939624,945252,943702,942953,940196,942957,943769,934002,941009,944113,944055,959876,953704,1020577,940154,943373,942961,1019968,1017436,943016,1544697,938169,945675,944429,944042,943759,938285,944683,957265,943149,944069,944469,944474,944653,946850,1009672,949413,944675,1343108,1020000,944424,944430,946649,988593)
AND ( wp_postmeta.post_id IS NULL
AND mt1.post_id IS NULL )
AND wp_posts.post_type IN (‘product_variation’, ‘product’, ‘product_cat’, ‘attachment’)
AND ((wp_posts.post_status <> ‘auto-draft’
AND wp_posts.post_status <> ‘tco-data’))
GROUP BY wp_posts.ID
ORDER BY FIELD(wp_posts.ID,961484,941936,944419,940164,939624,945252,943702,942953,940196,942957,943769,934002,941009,944113,944055,959876,953704,1020577,940154,943373,942961,1019968,1017436,943016,1544697,938169,945675,944429,944042,943759,938285,944683,957265,943149,944069,944469,944474,944653,946850,1009672,949413,944675,1343108,1020000,944424,944430,946649,988593)
LIMIT 0, 48And this is the caller:
WP_Query->get_posts
WP_Query->query
get_posts
wpsolr\core\classes\engines\WPSOLR_AbstractSearchClient->get_posts_from_pids
wpsolr\core\classes\ui\WPSOLR_Query->get_posts
WP_Query->query
WP->query_posts
WP->main
wp
require(‘wp-blog-header.php’)
You must be logged in to reply to this topic.