• Hot
  • Top
  • New
2
votes

You have ... votes left in this category for this week!

completed

Add existing filters to woocommerce breadcrumbs

This should be an optional configuration: Do not reset filters when clicking breadcrumbs

The default category breadcrumb URLs should contain filters just like FWW Product Categories widget with this option enabled: https://prnt.sc/w64m3a

e.g. existing filter is black: https://foundthru.com/product-category/dogs/dog-bowls/black/

I would like to change my breadcrumbs
from this: https://foundthru.com/product-category/dogs/
to this: https://foundthru.com/product-category/dogs/black/

2
votes

You have ... votes left in this category for this week!

Advanced logging feature of scraping process

For Price Comparison Pro, I would like to have a detailed view of which URLs it is trying to scrape but also what happens when it doesn’t scrape a URL or when the scrape process is stuck in an infinite loop.

The details of the scrape logging could also be provide in a .txt or .csv format as we could then be able to pinpoint any faulty URLs.

This allows us to further troubleshoot the scrape process and also provide best practices based on our findings.

1
votes

You have ... votes left in this category for this week!

Scrape multiple variations

On a page where multiple variatons of a product are listed and the CSS pulls out the correct price in response to a user selection, it’s not currently possible to get Price Comparison Pro to pull out all the variations of a product from a single page to populate the database.

So this feature request is for PCP to be able to extract multiple variations from a single page to populate the database.

e.g. https://www.animeddirect.co.uk/metacam-1-5mg-ml-oral-suspension-for-dogs

0
vote

You have ... votes left in this category for this week!

Add conditional prefix or pattern match check on search string to determine in postmeta should be searched

Super Speedy Search latest updates have made postmeta search even faster than before, about 3 seconds against a million products.

But – 3 seconds is still quite slow, and if you remove the meta search then the SQL query is blindingly fast – negligible load on your server.

It seems in the majority of cases, users are enabling the _SKU meta item to be searched and not really using meta search for anything else. Because of this, I think there may be a sort of cheat I can implement to speed search up further.

What I’m thinking is that many stores will have a prefix or a pattern of some kind for their SKUs –

* Maybe SKUs are always a minimum length?
* Presumably SKUs are always 1 word?
* Maybe SKUs have some kind of pattern – like they always start with WPI or something similar for your store?

What I’m thinking is that I could add a pattern test to the search string to check if postmeta should be searched at all, and if the pattern test fails then skip searching postmeta.

For example, you could configure: WPI* as the pattern for your metadata searches to be activated and then if a user searches for “Dell Monitor” it would skip checking postmeta. If a user searches for WPIX1023 then it *would* search postmeta.

The idea being that this would speed up product search massively for your users who are probably mostly not entering SKUs – I’m presuming again that this addition of SKU search is actually mostly for the benefit of your site admins?

Please provide as much info as possible to help here so I can make Super Speedy Search *even* faster than it already is!