Views

Dear all,
I make use of views mainly to call MySQL procedures, which is an impressive facility.
However I can't seem to find the view associated with the backend removal of products from an order in Hikashop or the frontend removal in Hikamarket (Front End).
I do not use HS (Professional 2.6.3) for commercial purposes, but actually as a core for a corporate environment which provides different types of clothing and special pieces of equipment to various categories of personnel, which are associated with a system of credits specific in time and value to each category, and this calls for a lot of database activity.

Thank you.

Bruno

Hi,

For HikaShop, the delete button is displayed by the file "show_products" of the view "order" with this code: But there is no view for after you click on the button. It just redisplays the view file.
So if you want to add processing when an order product is deleted, you want to create a small plugin of the group hikashop and implement the trigger onAfterOrderUpdate which will give you a variable $order with the products data allowing you to do what you need to do.

Thank you very much Nicolas, I suspected as much but I wanted to be 100% sure.
I guess I'll have to roll up my sleeves and have a go at creating a plugin.
As a temporary solution I have created triggers on hikashop_order_product to call the procedures in question, which works fine, but I would prefer to have them explicitly called from hikashop and database triggers are understandably not encouraged by our IT people running our servers.

Thanks again.

Bruno

Hi,

That's right, a plugin will be more appropriate for that specific task.
Both HikaShop and HikaMarket are re-saving the order when removing a product.
The order object have "product" set with a 0 quantity.

You can for example find in HikaMarket :
So thanks to the trigger onAfterOrderUpdate ; you can check if the order object have that "product" variable and analyze the content.
If you found one product with a 0 quantity, you can know that the product have been removed from the order.

Regards,

Thank you Jerome for this precision, it's all beginning to fall into place now.
Bàt,

Bruno

Hi Jerome and Nicolas,

You were absolutely right, plugins are the perfect solution for solving my peripheral database issues.
In particular, the fact that parameters from the order object can be passed on to the stored procedures (for example $order->order_user_id) makes these a lot more efficient in terms of execution time.

Thanks again.

Bàt,

Bruno

Hi,

Is there any particular reason why trigger function 'onBeforeOrderDelete' does not appear in your documentation?
Can you confirm that this is just an documentary oversight and that deprecating this function is not under consideration?
I use it in a plugin, and it works like a charm.

Thank you,

Bruno

Hi,

The developer documentation is not up to date.
You can be sure that this specific trigger is not about to be removed due to the fact it is used by several plugins and components.

Regards,

Thanks Jerome.
Bon weekend.

Bruno