Impasto

Also experiencing it, except my problem is my inability to log into the backend. I keep getting redirected to the login page. My difference is I'm running Prestashop version 1.7.6 This only happens in Chrome, not Firefox. (On a side note, a similar issue popped up on another site of mine... a WordPress site with membership capabilities. I suspect it has more to do with Chrome and its handling of membership cookies than Prestashop. Is there some way to force cookies to expire the moment we log out of Prestashop? Like a module or a line of code for the config file?)

Is there some way to add another piece of information to be validated against? eg: Email address AND and IP address. This would prevent so much fraud. I see the value of the validator plugin, but I don't want to manually approve every account application. Purchasing must be as smooth and pain-free as possible. I don't want shoppers sitting with a cart waiting to checkout at 10pm, but can't because I have to approve their account application first (sometime in the morning). We'll lose customers with that hurdle.

I'd also like this feature. I'd like like to block new accounts on many levels (email / telephone number / IP address) to prevent duplicate accounts from being made. We want to offer a significant discount to new members signing up, so we can't have one person sign up 20 times just to get the discount. Are there ways built into Prestashop to prevent one person signing up multiple accounts, or are we going to have to search for a custom module to solve this problem?

I'm wanting to do the same thing. Did you find a solution?

I also solved the problem with downgrading my PHP version. Initially, I installed on php.4 (I got the exact same error message & view on the pulldown menues) Downgrading to 7.3 , 7.2 and 7.1 all gave me error 500 messages from the server php 7.0 works perfectly.

Sorry, I genuinely feel your pain. And STILL no PrestaShop representatives even trying to solve your problem. Perhaps create a new post and reference back to this discussion. Maybe being classified as "Solved" means it's being ignored? Though with 12 replies and 2777 views, this thread is one of the hottest in this forum. Surely someone MUST have noticed it by now?

We set front office cookies life to 0 hours (as per screenshot). The setting is on the Administration / Preferences page. It initially didn't do anything because that only related to new cookies, and all the old ones had a lifespan set to a few hundred hours so they were still active. This was why we moved my client to a completely virgin browser without any login legacy. Additionally, I see we are running the site with friendly URLs off and absolutely every scrap of caching turned off. On that topic, we found caching caused a few problems as well. It seemed to be remembering previous logins (possibly by IP address) because we'd been using multiple accounts for testing and my client was signing up customers on their behalves. Login as John and then a few pages later, we'd be automatically logged in as Mary. Log out, browse a few pages and we're magically back in as John. View order history and we'd be presented with Mary's orders. Reload the page and we see John's history – utter chaos! (and of course this is all happening on the client's laptop so there was no hiding it) If you do this, make sure you delete the cache manually. We did an update of PrestaShop and deleting cache only deleted the cache from that new version – not the previous ones so we kept leaving bits n pieces lying around. There were also a few cache folders for javascript etc beyond just the standard Smarty cache folder. Be ruthless and empty them all out. I hope this helps.

We set cookies to expire immediately upon logout and instructed our client to use a dedicated browser (chrome) only for her site and to always use it in incognito mode. This seems to have solved our login/logout problems. Firefox has a special setting in "Security" to remember login cookies. That might have been forcing constant logins despite logging out. (all the other cookie settings are under the "Privacy" preferences) Again... not a proper PrestaShop solution, but I've not had a single complaint from my client regarding this in over 6 weeks. PrestShop's silence & lack of solutions on login bugs like this is deafening. I suspect a major caching issue that they can't fix and is now relying on version 1.7 to quietly fix. I'd love to be proven wrong because I don't have any clients who will want me to rebuild their site just to get an upgrade. (I can't wait for 1.7, but only for new sites)

It's good practice to have an SSL certificate. If nothing else, it will create confidence in the shopper that your site is legitimate. It shows your attitude towards security and privacy. It's more important if you're on a shared hosting account. (type https instead of http on your own site and see what you get – I often get someone else's site presented to me because it just loads the first SSL protected domain on that hosting server. MAJOR issue for me.) I suspect we are going to start seeing Google penalising non-ssl sites in its rankings and some browsers might even start blocking the sites. I already have experienced problem sites viewed in Chrome – Chrome gives you a security warning if the site has issued its own ssl certificate as a "spam warning". I issued myself a certificate through my cPanel and was presented with warnings from Chrome every time I viewed the site. I bought a RapidSSL certificate for about $20 issued by a third party and I am now fine. (seems you can't self-endorse your own domain) I'm seeing more and more hosting packages that include a free SSL certificate in the specs. To save you the effort/knowledge, I'd advise just buying one of those hosting packages and make it all of this your hosting company's responsibility.

No, the problem is in the site because we also occassionally experience it, but a solution was in the browser. We can't expect every client to go through these hurdles for a smooth, reliable experience. I'm certainly not thrilled at all. I'm out of the pot into the fire on this job. I'm moving away from WooCommerce because WordPress is rapidly becoming a security risk through popularity and requires a lot of maintenance with 3rd party plugins & updates, but now Prestashop just seems to have core problems that can't get fixed (Judging by the forum discussions, login problems seem to have plagued Prestashop for years through 3 different versions... and yet it's still not properly fixed? Very concerning)

Sort of. We couldn't fix it, but since it was only a problem on my client's computer because she was the only one using multiple accounts, I managed to get her to change the way she was using the site. She was using Chrome, so we moved her over to Firefox for the sole purpose of using her site. Use sae browsing mode so no cookies, history or cache is kept. There's even a setting specifically for Firefox to keep/delete login cookies. She quits Firefox between logins. This way, her browser ensures fresh, unique logins without confusing baggage, rather than relying on Prestashop to function properly. Not ideal, but it does seem to be working as a solution.

That's lotsa love, thanks. I'll give them a call and post their answer so others can also try.

This feels identical to the problem I posted last week for Prestashop v1.6 No reply to my problem, let alone a solution. I'm starting to think this is a serious problem that is recurring through multiple versions of Prestashop and no one has a solution for it.

Anyone out there? I'm not feeling the love...

Hi world. What's happening, is once a customer has logged out of the shop front, they are automatically logged back in the moment they view another page. This is not such a huge problem if you're a single customer, but it is a huge issue if multiple login accounts have been used on a single computer because the logged in customer can suddenly change. Eg: customer A logs out and customer B logs in. When customer B views his purchase history, he is presented with customer A's history. Reload the page and customer B's history now shows. Then, when customer B logs out and we view a new page, it's a toss up which customer will be, again, logged in. All caching is turned off (which is seriously hurting the speed of the site so I really want to turn it back on) and all the cached smarty files have been manually deleted. Is there an extra layer of caching or cookies that preventing new content from displaying or is keeping customers logged in? Is it perhaps the version of PHP of my hosting ISP's server? (I'm running Prestashop v1.6.1.4 running on php v5.5). Is it an SSL issue? I did find references on Prestashop's forums about a similar problem way back in version 1.4 that was solved with some code in the config file to force cookies to expire, but it has not been an issue since then. Login issues were also being experienced when friendly URLs were being used with SSL, but I've turned off that feature as well. The main problem is that it's my client that's experiencing the problem because she's creating accounts on behalf of other people. (It's unlikely that anyone else is going to notice this because they will be logging in with a single account – it's just typical that it's the client that's having this problem) I'm using pf_newfashionstore as the theme and the site can be viewed at: https://khulisanetwork.co.za All help and assistance will be appreciated. Thanks.