Hi there everyone!

Has anyone already tried the combination of the crawler and the commerce
extension in order to index products and include them in the searchresults?

I am following the docs of indexed_search and the crawler as presented
on typo3.org but that does't have any effect. At least not for the
search results.

As for the crawler himself he seems to do quite ok ... having nearly
5000 records within the queue and having finished about 300 right now.
But then when I switch to the indexed search info module I just dont get
products listed.

I have several category pages within a "products" page and within the
pageTS config there I have

tx_crawler.crawlerCfg.paramSets {
commerce =
&L=[|_TABLEages_language_overlay;_FIELD:sys_language _uid]&tx_commerce_pi1[showUid]=[_TABLE:tx_commerce_products;_PID:112]
commerce.procInstrFilter = tx_indexedsearch_reindex
commerce.cHash = 1
commerce.baseUrl = http://mydevmachine/~myusername/dvl/theproject/trunk/
}

maybe there is someone who already encountered this kind of problems?

Thank you very much in advance!

greets Rico
_______________________________________________
TYPO3-dev mailing list
TYPO3-dev (AT) lists (DOT) netfielders.de
http://lists.netfielders.de/cgi-bin/...info/typo3-dev

Well I managed to get the indexing working but there was still a problem
left which, I guess, would be a nice feature for the crawler.

You can actually manage to crawl pages with plugins on them and their
content with a rule like that:
tx_crawler.crawlerCfg.paramSets.commerce =
&L=[|_TABLEages_language_overlay;_FIELD:sys_language _uid]&tx_commerce_pi1[showUid]=[_TABLE:tx_commerce_products;_PID:112]


But with a lot of category pages ... where one page only shows certain
records from the designated category and all products are stored within
the same sysfolder (_PID:112) you get a lot of junk within your search
table. For example
- on the page for "Vaccuum cleaners" you actually only show the
respective products (e.g. with id 1,3,38)
- overall you have 300 products within the sysfolder for products.
- with the standard condition this will get you 300 possible variations
for that page because it finds that much products within the products table
- so you have 297 useless combinations which will be indexed and
probably fill your db with junk
- now imagine what would happen with about 25 categories!

My suggestion would be to include a filter hook for this kind of
situations where you can just say
&tx_commerce_pi1[showUid]=[_FILTER:someextensionclass->functionname;_SOMEPARAM:somevalue]


and then the crawler object would call the filter function if possible
in order to influence the results


will play around with it a lill

greets Rico


Rico Moorman wrote:
> Hi there everyone!
>
> Has anyone already tried the combination of the crawler and the commerce
> extension in order to index products and include them in the searchresults?
>
> I am following the docs of indexed_search and the crawler as presented
> on typo3.org but that does't have any effect. At least not for the
> search results.
>
> As for the crawler himself he seems to do quite ok ... having nearly
> 5000 records within the queue and having finished about 300 right now.
> But then when I switch to the indexed search info module I just dont get
> products listed.
>
> I have several category pages within a "products" page and within the
> pageTS config there I have
>
> tx_crawler.crawlerCfg.paramSets {
> commerce =
> &L=[|_TABLEages_language_overlay;_FIELD:sys_language _uid]&tx_commerce_pi1[showUid]=[_TABLE:tx_commerce_products;_PID:112]
>
> commerce.procInstrFilter = tx_indexedsearch_reindex
> commerce.cHash = 1
> commerce.baseUrl = http://mydevmachine/~myusername/dvl/theproject/trunk/
> }
>
> maybe there is someone who already encountered this kind of problems?
>
> Thank you very much in advance!
>
> greets Rico
_______________________________________________
TYPO3-dev mailing list
TYPO3-dev (AT) lists (DOT) netfielders.de
http://lists.netfielders.de/cgi-bin/...info/typo3-dev

Hi Rico,

> Well I managed to get the indexing working but there was still a problem
> left which, I guess, would be a nice feature for the crawler.
>
> You can actually manage to crawl pages with plugins on them and their
> content with a rule like that:
> tx_crawler.crawlerCfg.paramSets.commerce =
> &L=[|_TABLEages_language_overlay;_FIELD:sys_language _uid]&tx_commerce_pi1[showUid]=[_TABLE:tx_commerce_products;_PID:112]
>
>
> But with a lot of category pages ... where one page only shows certain
> records from the designated category and all products are stored within
> the same sysfolder (_PID:112) you get a lot of junk within your search
> table. For example
> - on the page for "Vaccuum cleaners" you actually only show the
> respective products (e.g. with id 1,3,38)
> - overall you have 300 products within the sysfolder for products.
> - with the standard condition this will get you 300 possible variations
> for that page because it finds that much products within the products table
> - so you have 297 useless combinations which will be indexed and
> probably fill your db with junk
> - now imagine what would happen with about 25 categories!
>
> My suggestion would be to include a filter hook for this kind of
> situations where you can just say
> &tx_commerce_pi1[showUid]=[_FILTER:someextensionclass->functionname;_SOMEPARAM:somevalue]
>
>
> and then the crawler object would call the filter function if possible
> in order to influence the results
>
>
> will play around with it a lill
>

if you have found a solution, i'll be glad to add this to the commerce
manuel. Could you send an email at team(at)typo3-commerce.org?

Many thanks

ingo

> greets Rico
>
>
> Rico Moorman wrote:
>
>> Hi there everyone!
>>
>> Has anyone already tried the combination of the crawler and the
>> commerce extension in order to index products and include them in the
>> searchresults?
>>
>> I am following the docs of indexed_search and the crawler as presented
>> on typo3.org but that does't have any effect. At least not for the
>> search results.
>>
>> As for the crawler himself he seems to do quite ok ... having nearly
>> 5000 records within the queue and having finished about 300 right now.
>> But then when I switch to the indexed search info module I just dont
>> get products listed.
>>
>> I have several category pages within a "products" page and within the
>> pageTS config there I have
>>
>> tx_crawler.crawlerCfg.paramSets {
>> commerce =
>> &L=[|_TABLEages_language_overlay;_FIELD:sys_language _uid]&tx_commerce_pi1[showUid]=[_TABLE:tx_commerce_products;_PID:112]
>>
>> commerce.procInstrFilter = tx_indexedsearch_reindex
>> commerce.cHash = 1
>> commerce.baseUrl =
>> http://mydevmachine/~myusername/dvl/theproject/trunk/
>> }
>>
>> maybe there is someone who already encountered this kind of problems?
>>
>> Thank you very much in advance!
>>
>> greets Rico


Mit freundlichen Gruessen
--
Ingo Schmitt mailto:is (AT) marketing-factory (DOT) de
Marketing Factory Consulting GmbH http://typo3.marketing-factory.de/
Content Management mit Typo3: Beratung - Schulung - Realisierung
_______________________________________________
TYPO3-dev mailing list
TYPO3-dev (AT) lists (DOT) netfielders.de
http://lists.netfielders.de/cgi-bin/...info/typo3-dev

Will surely do!

Ingo Schmitt wrote:
> Hi Rico,
>
>> Well I managed to get the indexing working but there was still a
>> problem left which, I guess, would be a nice feature for the crawler.
>>
>> You can actually manage to crawl pages with plugins on them and their
>> content with a rule like that:
>> tx_crawler.crawlerCfg.paramSets.commerce =
>> &L=[|_TABLEages_language_overlay;_FIELD:sys_language _uid]&tx_commerce_pi1[showUid]=[_TABLE:tx_commerce_products;_PID:112]
>>
>>
>> But with a lot of category pages ... where one page only shows certain
>> records from the designated category and all products are stored
>> within the same sysfolder (_PID:112) you get a lot of junk within your
>> search table. For example
>> - on the page for "Vaccuum cleaners" you actually only show the
>> respective products (e.g. with id 1,3,38)
>> - overall you have 300 products within the sysfolder for products.
>> - with the standard condition this will get you 300 possible
>> variations for that page because it finds that much products within
>> the products table
>> - so you have 297 useless combinations which will be indexed and
>> probably fill your db with junk
>> - now imagine what would happen with about 25 categories!
>>
>> My suggestion would be to include a filter hook for this kind of
>> situations where you can just say
>> &tx_commerce_pi1[showUid]=[_FILTER:someextensionclass->functionname;_SOMEPARAM:somevalue]
>>
>>
>> and then the crawler object would call the filter function if possible
>> in order to influence the results
>>
>>
>> will play around with it a lill
>>
>
> if you have found a solution, i'll be glad to add this to the commerce
> manuel. Could you send an email at team(at)typo3-commerce.org?
>
> Many thanks
>
> ingo
>
>> greets Rico
>>
>>
>> Rico Moorman wrote:
>>
>>> Hi there everyone!
>>>
>>> Has anyone already tried the combination of the crawler and the
>>> commerce extension in order to index products and include them in the
>>> searchresults?
>>>
>>> I am following the docs of indexed_search and the crawler as
>>> presented on typo3.org but that does't have any effect. At least not
>>> for the search results.
>>>
>>> As for the crawler himself he seems to do quite ok ... having nearly
>>> 5000 records within the queue and having finished about 300 right
>>> now. But then when I switch to the indexed search info module I just
>>> dont get products listed.
>>>
>>> I have several category pages within a "products" page and within the
>>> pageTS config there I have
>>>
>>> tx_crawler.crawlerCfg.paramSets {
>>> commerce =
>>> &L=[|_TABLEages_language_overlay;_FIELD:sys_language _uid]&tx_commerce_pi1[showUid]=[_TABLE:tx_commerce_products;_PID:112]
>>>
>>> commerce.procInstrFilter = tx_indexedsearch_reindex
>>> commerce.cHash = 1
>>> commerce.baseUrl =
>>> http://mydevmachine/~myusername/dvl/theproject/trunk/
>>> }
>>>
>>> maybe there is someone who already encountered this kind of problems?
>>>
>>> Thank you very much in advance!
>>>
>>> greets Rico
>
>
> Mit freundlichen Gruessen
_______________________________________________
TYPO3-dev mailing list
TYPO3-dev (AT) lists (DOT) netfielders.de
http://lists.netfielders.de/cgi-bin/...info/typo3-dev