[
https://issues.apache.org/jira/browse/OFBIZ-4755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13250184#comment-13250184
]
Jeremy Olmstead commented on OFBIZ-4755:
----------------------------------------
Okay, that is perfectly logical. I tried it exactly as you suggested, but
still can't get it to work. It's odd because as soon as I set
parameters.SEARCH_CATALOG_ID from within KeywordSearch.groovy, I print out a
debug message that shows it has been set correctly. Immediately following this
is the call to processSearchParameters, but a debug message in this Java method
shows that SEARCH_CATALOG_ID is not a part of parameters! Any idea what I
could be missing here?
Thanks,
Jeremy
> E-commerce search does not always functioning correctly
> -------------------------------------------------------
>
> Key: OFBIZ-4755
> URL: https://issues.apache.org/jira/browse/OFBIZ-4755
> Project: OFBiz
> Issue Type: Bug
> Components: specialpurpose/ecommerce
> Reporter: Jeremy Olmstead
> Priority: Minor
> Attachments: ecommerceSearch1.patch, ecommerceSearch2.patch
>
>
> There seems to be a number of problems with the way e-commerce search works.
> I'll just a name a few examples of things I have tried that don't seem to
> work the way I think they should. I can delete a catalog from a store and
> the catalog still shows up and is completely searchable. I can delete a part
> from a catalog, then search the catalog and it still shows up, if you click
> the part from the search results you get a NullPointerException error. To
> take things a step further, after deleting the main catalog from the web
> store, I changed it to View Allow instead of Browse Root, then I even changed
> every category within the catalog to internal and search still finds parts
> from that catalog. Then I created a new catalog and category and put a
> product within. From here I can drill down to the part from the newly
> created catalog, but when I click on the part for details, it still directs
> me to the other catalog!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
