Category index in Kaltura is defined under partnerSortValue parameter.
In Kaltura 9X, this parameter is 0 for a new category and is updated only when moving category in the KMC (changing category order in the categories tree).
When deleting category, partnerSortValue does not change for other categories (in the same sub tree of course)
Is it different for Kaltura 10X, or does the Kaltura manage the partnerSortValue value for creating/moving/deleting categories?
Just checked this issue on a newly installed Kaltura Server and the behaviour is the same.
partnerSortValue is a numeric field used by external applications to sort categories using the category.list API with parameter filter.orderBy = +partnerSortValue
http://www.kaltura.com/api_v3/testmeDoc/?object=KalturaCategoryOrderBy
So this field should not be modified internally in the API.
Related
In an Index i have two documents Example: Product and Sku. In Product Document i have indexed all product related properties like Product name, Product Brand and in sku document we have indexed all sku properties like Price, Inventory.
We will have many skus mapped to a product but vice-versa will not happen. So we have created parent child relation between Product and sku. We made Product as Parent and Skus were mapped as child to Product. Issue is when we query for product or sku we are getting only Product related properties(name and brand) or only sku related properties(Price and Inventory).
But in Our case when we query we need to get all Product and sku related properties as well(Name, Brand, Price and Inventory). How to get all the properties of Parent Document when we query for child (or) How to get all child sku's and their properties when we query for Product.
Is it possible in Elasticsearch. Please help. Thanks.
I am Using Elasticsearch version 2.3.1.
In my previous project we encountered the same issue having a parent (catalog-item) and children (configured products - item specified with color... etc). As mentioned by khituras you can apply hasParent- and hasChild-queries, though they won't return combined result sets of parents with children... (link).
Probably you should try InnerHits-queries, which seems promising.
Does your data set change often, so you benefit of the parent-child relationship, as parent- or child-documents do change frequently? Else, you may consider embedding the parent documents into each child. Elasticsearch comes by with a document based data model, so you must be aware of possible drawbacks when using parent-child relationships. During my project we applied the embedded-approach, since we failed to apply aggregations against parent-information on child-documents.
Cheers, Dominik
im currently using Algolia with my Magento shop. Is it possible to index attribute values which are not associated to a product.
ie. I have an attribute called Brand with over 1000 values. But only 50 of them are associated with atleast one product.
I would like to index all 1000 brand values in Algolia, so that i can use them in different request.
thanks in advance.
Best way is to write a small script to and index them yourself on an other index. You can have a look at how additional attributes index are getting their values => https://github.com/algolia/algoliasearch-magento/blob/master/code/Helper/Entity/Additionalsectionshelper.php
Magento is appending '-1' only to certain categories URL key despite not being defined by us like that in backend.
Eg. if URL key for category 'sample' is 'sample' .. in frontend its showing as '/sample-1'
It's not the case with all categories but 2 or 3 that too in desktop version alone. It's working fine in mobile version. What could be the issue?
There are few things that can cause this.
Duplicate Categories trying to use the same URL, upon reindex Magento will auto increment these values. To the next higher integer.
It's sometimes easy to miss.
Say you have the category "shoes" as a subcategory of "women"
The URL key created automatically for this category would be "/shoes"
Now say you have the category "shoes" as a subcategory of "men"
This category would automatically have the url key of "shoes" however because it already exists Magento will auto increment this key to "shoes-1"
Under a multi-store instance of Magento, you also can't have two categories with the same url keys even if they are part of different stores.
Additionally, Magento Enterprise 1.13 has a whole different problem with auto increments of URL Ids
What version of Magento are you running and is it a multi-store platform? I can provide further assistance from there.
So I am modifying a module and I've successfully queried the product ID. So if I am browsing products and go into the product details page, I can see my product ID using
JRequest::getInt('product_id');
but for some reason I cannot get the category ID. I've tried.
JRequest::getInt('category_id');
and it always comes out to zero no matter what category I go to. Anyone else experience this? I could get it from the nonSEF url but there's gotta be another way. My goal is to basically query the category ID when I am browsing that category or if I am in the product details of a product.
I assume, you're using some OpenCart component for Joomla. In this case, you have to look into controller and model files for OpenCart. It's not THAT easy to get certain values sometimes, because these are 2 different engines.
In short, you may have to use VQMod for OpenCart, add category_id to data array and only then JRequest it. Solely depends on task.
I'd like to alphabetically sort the items in the department/region dropdown. This dropdown is visible on the billing information section on the checkout page.
I am using Magento CE 1.7.0.2 and setting an address in France, hence trying to see France's departments sorted.
Rewrite the Mage_Checkout_Block_Onepage_Billing block (+ Mage_Checkout_Block_Onepage_Shipping if you also need to), and in the new class(es), copy and adapt the getRegionHtmlSelect($type) method from Mage_Checkout_Block_Onepage_Abstract.
What you need especially is to sort the result of $this->getRegionCollection()->toOptionArray() before using it with setOptions(), knowing that it is an array of arrays with value and label keys.
One solution consists in rewriting the script js/varien/forms.js.
In its update function, create a sorted collection of regions, then iterate over this collection and add each region's option.
A better solution, performance wise, is to re-affect region ids in the table directory_country_region. Currently, region's ids order the region by country_id and code. Re-setting the region ids so that regions are ordered by country_id and default_name would do the work.