Logged out purchase

-- url of the page with the problem -- : my.vource.tv
-- HikaShop version -- : 4.6
-- Joomla version -- : 3.10.10
-- PHP version -- : 7.4.29

I have attempted several real orders on my system.
Each time a make a purchase through paypal I am logged out.

I do not want users logged out the system after they make a purchase.
What settings control this?

Hello Nicolas,

1. What is the code and where is the code located? for the "user group after purchase" that logs a user out of the system after purchase?
I would like to edit it, so I can test to see if logout is necessary, on my site.

RATIONAL
When i change a user's settings on the backend of the website, the ACL change is detected by the user when the user selects a new menu item, or when the browser is refreshed -- without the user having to re-login. Therefore, a user should not have to be logged out for ACL updates to be recognized on the frontend. Especial if the "return to merchant" from paypal, sends the user to a different page.

I am building a video site, so logout of a customer, when compared to other video sites, is not an option. Re-login is a small, but unnecessary inconvenience, we do not want our users to experience.

I would prefer, a smooth one click process :: register - auto login (easysocial), select membership (hikashop), pay, return to video page, watch video.

If my rational does not work with your comp/plugin, please let me know.

Thanks,
Wrina

The timing for this information is extraordinarily useful! I did not know about the Group Plugin.

We've been fighting a problem where the customer has occasionally been forcibly logged out at the end of the checkout. Even though I suspected it involved the user being logged out/in, we haven't found a definite trigger. Your description gives me new ways to test.

A different issue I was thinking might be related.

It seems like the User object is being supplanted by an Identity object in Joomla4, but I haven't found much documentation or discussion about it. Any insights or leads?

I've found a couple of discussions in the Joomla GitHub threads about how they were implementing it, but I never saw any discussion or justification about why. All I can tell is that it works (though the getIdentity() method does not appear to be static, like the getUser() is.) and they seem to be planning to use it to add a getCurrentUser() method to several different types of classes. As far as usage, I've seen it used in a couple of very recent tutorials, but it wasn't the subject of them and didn't seem to do anything different than the User object.

After reading the SSO article, that does seem to be a likely justification. Perhaps, in the future, an active User would need to maintain awareness of multiple Identities ...

Anyway, thanks for the tip.

Alright. In a way, we gave up on our logging out during checkout problem. When we finally managed to narrow down when it was happening, it pointed towards an old version of the STRIPE HikshopPayment plugin, so, rather than bang our heads against that wall, we upgraded to the current one in the Hikashop Market. There's still an issue, but we're not being logged out.

The issue was so bizarre, I will summarize it for you, but I have no more questions about that other than idle curiosity. Basically, a registered user would occasionally be forcibly logged out of Joomla during checkout. What we finally managed to find was a repeatable pattern to trigger it, yet it still makes no sense.

I put logging code into every OrderAPI method (inserted into our plugin) and PaymentAPI method (inserted into the old Stripe plugin) which would just record the trigger name and the User's ID at the beginning and end of each trigger method. What we learned was that the User remained logged in before the order creation, through the payment plugin initialization, but was forgotten before the payment plugin received notification, and remained logged out through to the thank you page. HERE'S THE REALLY WEIRD PART. The site worked in all browsers but Chrome, but it didn't always fail there. If we quit and restarted Chrome, logged in as our user and placed an order, it would log us out. If we logged in again, it would succeed from that point on for multiple orders, even if we logged out and in again. Even if we emptied the browser cache. But always on the first time through, after a fresh restart, Chrome would forget its logged in user during checkout 100% of the time, on PC and MAC, -- always right before the payment plugin handled a transaction notice, yet the order was being successfully confirmed. Since it always happened when the payment plugin was busy, we blame it - but I don't think I could program that behavior if I tried. So we updated the payment plugin.

That issue seems to be gone, but the payment plugin's still temperamental on my partner's Chrome browser for Windows 10 - it won't allow any credit card to be submitted, (valid or test value) and when it fails - there is no message, nothing in the debug log, and the cart gets deleted. (we even shut off ALL Chrome extensions). He's going to test from a different PC tonight.

Like I said, I have no questions right now, I'm just completely baffled by ALL of the weird errors we couldn't figure out. I'm switching back to problems I know I can solve for the night.

So I suppose that you mean that in onAfterOrderConfirm the user is logged in, but in onPaymentNotification the user isn't. I don't really see why that would be the case.