Omnibus

Price is dynamically changed for product variant, but not for plugin.
Link here

Hi,

Ok.
If you edit a variant of that product in the backend, what do you see in the "price history" section of the variant edit form ?
Did you save each variant of the product once after updating the plugin so that it can register the price of the variant in the price history table of the database for each variant of the product ?
If not, could you try to do it for this product ? Does it help ?

Thank you. OK, now it seams to work.
So one must update/save all products and variants to activate/start that history?

Is there a quick way to do that? Mass action?

Hi,

Yes. With mass actions you can use the "update the values" action. This will trigger the save system of products, followed by the smart search indexation via the finder plugin.

What values should I select and configure for that action?

nicolas wrote: Hi,

Ok.
If you edit a variant of that product in the backend, what do you see in the "price history" section of the variant edit form ?
Did you save each variant of the product once after updating the plugin so that it can register the price of the variant in the price history table of the database for each variant of the product ?
If not, could you try to do it for this product ? Does it help ?

Not working on specific product.

By default it shows price from one of variant (not selected as default). When you change size, you get ok price.
Try to select some variant and then back to 90x200.

Hi,

Well, you could use for example the column product_published with the value 1, provided that your products / variants are already published. Or, in "operation" mode with the tag product.product_published to dynamically use the value already in the database.
Or another column with something similar.

Regarding the product with the issue in your latest message, I'm not sure. Did you save each variant once ? Could you provide a backend access and a FTP access in order to check things out ?

Hi,

Thank you for the access. We were able to understand what the problem is and made a patch. It seems to be working fine now on that page and other pages I checked on your website.
We've published a new version of the plugin with that patch.