Forum Replies Created
- MuratParticipant3 years, 3 months ago in reply to: shop page does not display all products #23594
currently i have ended up stopping using elastic search, and have switched to apache SOLR – works like a charm.
MuratParticipant3 years, 3 months ago in reply to: shop page does not display all products #23513I am correcting my self – please ignore or (delete) my last erroneous response about putting “index.max_result_window: 1000000” in the elasticsearch.yml … as it turned out this parameter does not work starting in recent versions of elastic search engine…
I have followed your guide – but had to fix the quotation strings as curl was giving many errors in ACE string conversions….
Therefore, finally — this is the CLEAN one AS-IS – which worked.======================
curl -X PUT ‘https://127.0.0.1:9200/sharif/_settings’ -H ‘Content-Type: application/json’ -d ‘{ “index” : { “max_result_window” : 1000000 } }’
=======================MuratParticipant3 years, 3 months ago in reply to: shop page does not display all products #23511Thanks a lot
I have dug further and resorted to making that permanent by adding this line to the “elasticseach.yml”index.max_result_window: 1000000
MuratParticipant3 years, 3 months ago in reply to: Real need for better Filtering Widgets #23479thanks- i will create a separe ticket for each problem above – will consider first one as answered being a mere style stuff.
MuratParticipant3 years, 3 months ago in reply to: Allow to exclude certain facet value from taxonomy/attributes/categories filters #23471Thanks for the update – i will be testing that and reporting back.
MuratParticipant3 years, 3 months ago in reply to: Fatal Memory Leak #23416Hmmm,,
Having disabled that – the error still persists — I have cleared my DEBUG file and now after second attempt to clear cache and revisit different pages on site I collected the following notices and errors:
=================
[04-Jan-2021 10:00:58 UTC] PHP Notice:
Trying to get property ‘ID’ of non-object in /home/sharif-bazar.com/public_html/wp-includes/class-wp-query.php on line 4019
[04-Jan-2021 10:00:58 UTC] PHP Notice:
Trying to get property ‘post_title’ of non-object in /home/sharif-bazar.com/public_html/wp-includes/class-wp-query.php on line 4021
[04-Jan-2021 10:00:58 UTC] PHP Notice:
Trying to get property ‘post_name’ of non-object in /home/sharif-bazar.com/public_html/wp-includes/class-wp-query.php on line 4023
[04-Jan-2021 10:12:38 UTC] PHP Notice:
Trying to get property ‘post_date’ of non-object in /home/sharif-bazar.com/public_html/wp-content/plugins/woocommerce/includes/rest-api/Controllers/Version3/class-wc-rest-product-categories-controller.php on line 61
[04-Jan-2021 10:12:38 UTC] PHP Notice:
Trying to get property ‘post_date_gmt’ of non-object in /home/sharif-bazar.com/public_html/wp-content/plugins/woocommerce/includes/rest-api/Controllers/Version3/class-wc-rest-product-categories-controller.php on line 62
[04-Jan-2021 10:12:38 UTC] PHP Notice:
Trying to get property ‘post_modified’ of non-object in /home/sharif-bazar.com/public_html/wp-content/plugins/woocommerce/includes/rest-api/Controllers/Version3/class-wc-rest-product-categories-controller.php on line 63
[04-Jan-2021 10:12:38 UTC] PHP Notice:
Trying to get property ‘post_modified_gmt’ of non-object in /home/sharif-bazar.com/public_html/wp-content/plugins/woocommerce/includes/rest-api/Controllers/Version3/class-wc-rest-product-categories-controller.php on line 64
[04-Jan-2021 10:12:42 UTC] PHP Notice:
Undefined variable: message in /home/sharif-bazar.com/public_html/wp-content/plugins/sharifbazar-brands/functions.php on line 35
[04-Jan-2021 10:13:07 UTC] PHP Notice:
Undefined property: WP_Error::$term_id in /home/sharif-bazar.com/public_html/wp-content/plugins/woocommerce/includes/rest-api/Controllers/Version3/class-wc-rest-terms-controller.php on line 497
[04-Jan-2021 10:13:07 UTC] PHP Notice:
Undefined property: WP_Error::$taxonomy in /home/sharif-bazar.com/public_html/wp-content/plugins/woocommerce/includes/rest-api/Controllers/Version3/class-wc-rest-terms-controller.php on line 497
[04-Jan-2021 10:13:18 UTC] PHP Notice:
Trying to get property ‘post_date’ of non-object in /home/sharif-bazar.com/public_html/wp-content/plugins/woocommerce/includes/rest-api/Controllers/Version3/class-wc-rest-product-categories-controller.php on line 61
[04-Jan-2021 10:13:18 UTC] PHP Notice:
Trying to get property ‘post_date_gmt’ of non-object in /home/sharif-bazar.com/public_html/wp-content/plugins/woocommerce/includes/rest-api/Controllers/Version3/class-wc-rest-product-categories-controller.php on line 62
[04-Jan-2021 10:13:18 UTC] PHP Notice:
Trying to get property ‘post_modified’ of non-object in /home/sharif-bazar.com/public_html/wp-content/plugins/woocommerce/includes/rest-api/Controllers/Version3/class-wc-rest-product-categories-controller.php on line 63
[04-Jan-2021 10:13:18 UTC] PHP Notice:
Trying to get property ‘post_modified_gmt’ of non-object in /home/sharif-bazar.com/public_html/wp-content/plugins/woocommerce/includes/rest-api/Controllers/Version3/class-wc-rest-product-categories-controller.php on line 64
******************************
[04-Jan-2021 10:13:36 UTC] PHP Fatal error:
Out of memory (allocated 12582912) (tried to allocate 1392640 bytes) in /home/sharif-bazar.com/public_html/wp-includes/functions.php on line 4669
[04-Jan-2021 10:13:36 UTC] PHP Fatal error:
Unknown: Cannot use output buffering in output buffering display handlers in Unknown on line 0MuratParticipant3 years, 4 months ago in reply to: Allow to exclude certain facet value from taxonomy/attributes/categories filters #23214i think it is better not to prevent the indexing – as this should not be affecting the global search
but only intention is to present a sub-set of filters per web-site preference.MuratParticipant3 years, 4 months ago in reply to: replace the white overlay of loader with animated white gradient #23175i tried overriding the css style for the div.overlayloader – but it did not work, as it was always -by-design of that juqery plugin having its css defined as inline.
to make it easy I edited the main js file as followsvar _defaults = {
color : “rgba(255, 255, 255, 0.8)”,
custom : “”,
fade : true,
fontawesome : “”,
image : “…..”
imagePosition : “top left”, // <<<<<<<<<<<<<<
maxSize : “100px”,
minSize : “20px”,
resizeInterval : 50,
size : “50%”,
zIndex : 9999
};
==============
Alternatively, I have commented out the no-repeat property::if (settings.image) overlay.css({
“background-image” : “url(” + settings.image + “)”,
“background-position” : settings.imagePosition,
// “background-repeat” : “no-repeat”
});MuratParticipant3 years, 4 months ago in reply to: the facet counts in the braces should be inside a span with a special class #23171Lovely, worked like magic.
earlier i hacked the class-wpsolr-data-facets.php to achieve that effect.
screen 2.6 saved my day – big thanks.MuratParticipant3 years, 4 months ago in reply to: I failed to create a filter for products on sale with WPSOLR+WooCommerce #23155Yes true that I have it shown neither as taxonomy nor as field property like you have noticed.
Keep in mind also that I did not custom build it, as it is available out of the box.
you can see it yourself by following these steps on a sandbox as follows:
– install WordPress + woocommerce with dummy products that come with any theme builder, or you add a few standard products manually.
– enable woocommerce REST API and generate the API keys from within the woocommerce app
– install postman (https://www.postman.com/downloads/)
– try to make a simple a simple HTTP GET request through postman
https://stackoverflow.com/questions/47675850/how-to-authorize-android-app-to-communicate-with-woocommerce-site-using-postman
see for yourself that the property “on_sale” is available out of the box.
I strongly believe that WPSOLR must somehow regard that very important field boolean property to serve day to day mainstream use cases of having to filter products on sale – as this is a global requirement each website must provide as part of the out-of-the-box experience.
already other product search filter addons do support mapping to the in-built on_sale boolean property:
– annasta filters
– woobeewoo
– etc…MuratParticipant3 years, 4 months ago in reply to: I failed to create a filter for products on sale with WPSOLR+WooCommerce #23142i am not using the WPSOLR solely on my site – all filters configured, and having more than 60,000 products
these are fed into the wooCommerce site through REST API
yes, I am having all my filters successfully configured , an I understand your explanation.
However, my point is, it would be a redundancy to create an attribute and/or custom field to capture the boolean flag of the product as being either on sale or not on sale, especially that this property is already found in the woocommerce system.
The ration is, from a cleaner setup point of view, redundancy of properties/attributes should be avoided.
I could see on the filtersWPSOLR only identities the following fields, and skips the internal on_sale property, which I believe should be also hard-coded in WPSOLR – as this is a very standard usage common usage scenario
==============Camera_Date forsage_id _price _regular_price _sale_price _sku _supplier_name sale_currency sale_currency_rate_USD_UAH sale_min_qty_price total_sales _backorders _downloadable _download_expiry _download_limit _edit_lock _manage_stock _product_attributes _product_version _sold_individually _stock _stock_status _supplier_address _supplier_email _supplier_min_price _supplier_phone _tax_class _tax_status _thumbnail_id _virtual _wcmmq_s_min_quantity _wcmmq_s_product_step _wc_average_rating _wc_review_countMuratParticipant3 years, 4 months ago in reply to: I failed to create a filter for products on sale with WPSOLR+WooCommerce #23138it is an attribute – that i can see through json API, if you use postman to execute an HTTP GET on woocommerce REST API – you would see as this extract below
{ "id": 249988, "name": "703 violet", "slug": "703-violet", "permalink": "https://..........", "date_created": "2020-12-17T18:03:33", "date_created_gmt": "2020-12-17T18:03:33", "date_modified": "2020-12-17T18:03:33", "date_modified_gmt": "2020-12-17T18:03:33", "type": "simple", "status": "publish", "featured": false, "catalog_visibility": "visible", "description": "...........", "short_description": "", "sku": "s568108", "price": "320", "regular_price": "320", "sale_price": "", "date_on_sale_from": null, "date_on_sale_from_gmt": null, "date_on_sale_to": null, "date_on_sale_to_gmt": null, "price_html": ".......", "on_sale": false, // <<<<<<<<<<<<<<<<<<< "purchasable": true, "total_sales": 0, "virtual": false, "downloadable": false, "downloads": [], "download_limit": -1, "download_expiry": -1, "external_url": "", "button_text": "", "tax_status": "taxable", "tax_class": "", "manage_stock": false, "stock_quantity": null, "stock_status": "instock", "backorders": "no", "backorders_allowed": false, "backordered": false, "sold_individually": false, "weight": "", "dimensions": { "length": "", "width": "", "height": "" },the exact limitation I am facing with WPSOLR is that it does NOT expose the boolean property ‘ON_SALE’
thus depriving me of being able to filter against it as a whole.
I used before woobeewoo filters, and it has that feature.
but when I enable WPSOLR , it takes over the search engine, and even woobeewoo does not work anymore… as all the searches against the woocommerce products are piped through WPSOLR.i suggest if you could advise of a suitable PHP snipper to be added for the time being to the functions.php to enable exposing the ON_SALE property in the filters of WPSOLR
MuratParticipant3 years, 4 months ago in reply to: I failed to create a filter for products on sale with WPSOLR+WooCommerce #23136So, afterall let us skip my idea of creating a new page dedicated for filtering on-sale
and let us focus on understanding how can I enable a filter to show products on sale on the main shop page (no more custom pages)