User group after purchase stopped working...

-- HikaShop version -- : latest
-- Joomla version -- : latest

We have a user group "athlete" which after purchase = "confirmed" has always worked just fine ... the user just needs to logout and back in and they are "athlete".

However it seems to have stopped working. We just updated to hikashop 2.5.0 in hopes of resolving the issue but it persists.

Please advise if we are doing something wrong.

A screenshot of the setting is below:

Hi,

Are the orders status being confirmed ?
If no, then the problem is with the payment notifications and I'll invite you to check this documentation:
www.hikashop.com/support/documentation/i...or.html#notification
If yes, then could you export the product thanks to the "export" button of the products listing and provide that CSV so that we can check the data of the product ?

Orders are being "confirmed"

Is there a secure method to send the export?

Thanks.

Hi,

The "contact us" form (the support email address).

Regards,

I am sorry but the "contact us" form does not allow for attachments.

Is there another solution?

Thanks.

Hi,

The "contact us" form (the support email address).

You have already used the "contact us" form in the past and you received an answer by email : that is the support email address.

Regards,

Hi,

Thank you for the CSV
The products are configured properly based on your CSV, so it doesn't come from that. And if your orders are still being confirmed, then it doesn't come from payment notifications.
It also doesn't seem that you've changed your checkout for guest checkout (you can't add user group if their is no user account).
So the only thing left is the HikaShop group plugin. Please check that it is activated in the Joomla plugins manager and that its access is set to "public".
Also, do you remember changing something on the website when that stopped working ?

Unfortunately the hikashop groups plugin is published and set to public.

The only "change" I have is one we have done for years and that is to add code in user.php (/public_html/administrator/components/com_hikashop/classes) in oreder to map certain fields to community builder.

Again it has been a hack that has worked for two + years but I will provide the code below:

Hi,

You said that it was working before even updating. So it means that it's not related to the update. But to something that changed on your website. I'm not talking about the code, but it could be anything.
If you confirm manually an order from the backend orders listing, is the user group attached to the customer's user account ?
If you disable the HikaShop payment notification plugin via the Joomla plugins manager, does that help when the orders are confirmed automatically ?

1. If you confirm manually an order from the backend orders listing, is the user group attached to the customer's user account ?: NO

2. If you disable the HikaShop payment notification plugin via the Joomla plugins manager, does that help when the orders are confirmed automatically ? I ASSUME YOU MEAN DISABLING THE AUTHORIZE.NET OR PAYPAL PLUGIN. DOING THIS DOES NOT ALLOW PAYMENT TO BE COMPLETED... OR THE TRANSACTION TO BE "CREATED"

Are there other solutions we might try? We need to get this resolved and are happy to provide backend login access if helpful.

Thank you.

Hi,

1. If you confirm manually an order from the backend orders listing, is the user group attached to the customer's user account ?: NO

Like Nicolas wrote, you need to check your plugin configuration and HikaShop configuration.
Modifying the order status directly in the backend should trigger the plugin which should modify the user group.
So, before start a deeper investigation, we need to be sure that your HikaShop configuration is good.

So please indicate the setting "Payment confirmed order status", the content of the order and the status of the order.
The plugin will only be triggered when the order will receive the "Payment confirmed order status" status and only that one.
It could be also interesting to know if the product is a product with characteristics or not ; because the plugin check only the bought product and not his parent (if it's a variant).

Regards,

AHHHH you just solved it for us. Our developers have created a front end auto create of products and did not add "user group after" status to variants.. only to parent product.

Now we can make the "variants" change and everything should work fine. Many thanks.

Hi,

Good to know that your issue is solved.
I just created "feature request" ticket for the plugin "user group after purchase" in order to add the support of variants ; I guess that it will be easier for everyone if the plugin directly support that.

Regards,