1
Answers
Vote up!
0
Vote down!

Use Rules/VBO for sortorder with custom producttype not working

Hi,
I saw this video http://commerceguys.com/blog/power-rules-views-bulk-operations-and-commerce and it is working great for the standard producttype.

My usecase is to be able to order my products on a product-view. I made a field sortorder within my custom producttype and on my standard producttype.
I added this field as sort within my view. I would like to make a rule as in the video on which I can set as an integer the number of the ordering for the product, but I am not succeeding.

It is working great on a site where I only have the standard producttype. But it is not working with more than one producttype and on custom producttypes.
All producttypes have the same sortorder_field added.

My custom producttype name is mob

Can You please help me with this usecase. How can I get my custom-producttype within the component?

Thanks a lot in advance for your reply!
Greetings, Martijn

Asked by: Summit
on March 3, 2013

Comments

UPDATE:

I have it somewhat working, but I had to make a rule per producttype. Eventually it was the same as the screenshow only I have to change "product" to my custom producttype systemname. But when I use this with VBO, I can select another producttype and still use the same rule, which of course will not work. Maybe it is possible to make a rule which is producttype neutral? Because I added the same sortorder_field to all producttypes this should be possible right?

Thanks a lot in advance for your reply!
Greetings, Martijn

- Summit on March 4, 2013

Hi,
I think it is working! I thought I had to make a rule per producttype, but it seems this is not necessary.
You need to attach the rule to a producttype, but because the rule uses a field which is the same field in all contenttypes somehow it still gets updated using another producttype then the one which is set with the component construction.
Strange! But it is working.

Greetings, Martijn

- Summit on March 5, 2013

1 Answer

Vote up!
0
Vote down!

You need to attach the rule to a producttype, but because the rule uses a field which is the same field in all contenttypes somehow it still gets updated using another producttype then the one which is set with the component construction.
Strange! But it is working.

Answer by: Summit
Posted: Mar 5, 2013