I am useing taxonomies in orchard. i have two types of taxonomy 1: House > buy / rent. and 2. Location > spain / france/ uk. I have decided to use taxonomies based on my other post and orchard cms guru Bertrand Le Roy advice. Orchard CMS best options for list
My example
I have a house content type (tittle, body, 2 taxonomy fields {1: HouseType > buy, rent. and 2: Location > spain, france, uk} ) so a user will have to select 1: buy or rent. Then from the second taxonomy select the house location ie spain. I have 2 houses set up both use house type buy but 1 from location spain and 1 from location uk.
I know create a query and this is the problem: if i add a filter of taxonomy and choose buy i get both my houses as expected, if i set up the filter to have buy and spain (with only 1 filter but choose both from select box) i still get both houses which is wrong i would expect to only get 1. However if i have 2 seperate filters 1 buy and 2 spain then i get no results returned, which is wrong. Can some exlpain why this does not work and how to overcome it. I need to be able to say in the query get me, eg. all houses in spain that are of type buy and only got those houses.
Thanks
Related
[in sale analysis on total two list product and product category there. same things I want to add in quotation pivot table how can I add?
That is not really possible, because the BI (Business Intelligence) reports (you called it "sale analysis" in your question) are actually transformed data with sales order LINES as base. And the pivot of sales order are based on sales order. You don't have product and product category information, because you have a one to many relation to order lines where this information is belonging to. It's only working the other way around (lines information -> order information).
So the solution is probably extending sale analysis (i think the model is sale.report) with every other thing you're missing there instead of changing the pivot of sales orders.
I've got a question with Search on default engine - MySQL
There are products in searching results which have the following coincidences:
Product headings.
Product description.
Product category name (it the name of the category connected to searching query)
Product headings at Related Products, Up-Sells, and Cross-Sells under the product card description.
Product headings at Configurable products under the product card description.
Is everything ok? Or the last two cases are out of results should be?
I'm working on a shoe store. Each shoe has some a product attributes: the brand, size, model,...
However each shoe always only has 1 brand.
So i want to display the brand attribute beneath the product name in the product list.
I added a screenshot for more clarity. http://imgur.com/a/41HLS
You have the product name 'boots / enkellaarzen'.
Under that you have the brand name 'baci'. This name has to be dynamicly 'retrieved'.
Is this possible? If so, how do i do this?
Tldr: what is the shortcode to retrieve a product attribute in prestashop?
If it's a brand wouldn't it make more sense that the brand is manufacturer and not attribute?
You can set it in the product tab Associations at the bottom and display it in the template product-list.tpl with
{$product.manufacturer_name|escape:'htmlall':'utf8'}
I am creating a sample app in which multiple items as per categories can be chosen. Please see flow as below.
If i want to opt 3 items and all are falling in different categories. The configuration will like this.
A) Item 1
Category 1
Price1
ingrdient1
B) Item 2
Category 2
Price2
ingrdient3
C) Item 3
Category 3
Price3
ingrdient3
So to achieve this i have to create parameter1, parameter2, parameter3 and so on.
Is there any way in api.ai which supports collection concept like object[0], object[1], object[3] ....
here object[0] holds
A) Item 1
Category 1
Price1
ingrdient1
Thanks,
Dinesh
Not currently.
Api.ai are working on List entity, comment here on their forum. But currently they don't support objects or arrays being passed as parameters.
You would have set up entities and parameters for price, item, category, ingredient to be passed to your own webservice.
Try asking on their forum though, they're very open to suggestions and improvements for the platform.
Suppose, I have 1000 sellers (S1.....S1000) of Apparels listed on my site. Since all the sellers are paying some amount to me, I am giving them equal weight-age, and the results are shown based on relevancy.
Now, I am planning to start with premium service, where I am thinking to list one supplier on top for each keywords in search results. Let say, S1 has been given premium search for keywords 'Jeans', so if a user searches 'jeans', I first wants to display this supplier on the top, then display other supplier based on relevancy. Plus, this premium service is for only for one month. So, another supplier say S2 can avail this service in next month and so on.
Is there any plugin, wherein I can store which supplier should be shown for which keyword. I am even OK with making 2 queries to meet the desire results.
Please suggest
I think the Query Elevation Component is your friend, you can configure which documents (and hence which suppliers) come first for any given query, see
https://wiki.apache.org/solr/QueryElevationComponent
If that's too much work, you could also add a new boolean field in your documents, indicating whether the document is to be promoted or not, and in the query, sort by this field first (so promoted documents come on top), and by score next (so most relevant documents come right after the promoted ones).
You can maybe also use the reRanking Componant :
https://cwiki.apache.org/confluence/display/solr/Query+Re-Ranking
With using a query like this :
q=jean&rq={!rerank reRankQuery=$rqq reRankDocs=1000 reRankWeight=3}&rqq=(brand:S1)
The top 1000 of results from query jean will be re-ranking thanks to the boost (of 3) add to the documents which contain the field brand with the value S1.
It can be useful, but in your case I think the QueryElevationComponent is the best.
Be careful, reRanking is only available since version 4.9.