RobbieBlokeToys

I believe I've established that it has to be the theme. I found information on a very similar problem and that person swapped out 2 theme files for core theme files. I attempted that and it seemed to fix the problem but only once. The problem quickly returned again for the second attempt. This suggests to me that more theme files would need to be changed. Things I've tried: 1. Deactivated modules relating to customer accounts/orders (other than the primary cart module) 2. Removed/replaced shipping options to rule them out. 3. Removed/replaced countries to rule them out. 4. Ensured no tax settings are impacting account creation. The only thing it can be is the theme. If anyone can recommend which theme files I should attempt to swap out for the original theme files, and what might need to be changed, I would appreciate it. I would like to attempt that before I remove the theme entirely and return to the original theme. For those who it might help the theme is "Food Store", which now seems to be unsupported and abandoned. So, I would recommend not using it. If I can't get this fixed in the next couple hours I'm going to spend the day rebuilding the site with the original theme. And in the future, I will only be investing in paid themes with active support.

Anyone else have any updates on this? I have the same issue. Whatever default country I select is the only one customers can register with. I can change the default country to any in the list and that's the only one that works, whenever anyone attempts to register a country that isn't the default it redirects to a login. I have attempted to swap out the two tpl files in case it's the theme, but while it seemed to work on the first try the problem quickly came back again. I really don't want to go back to the default theme, because all the work I have done on the current one will be lost.

Update 2 When I disable guest checkout anyone can order from any country, but the page throws a 500 error and has to be refreshed. Once refreshed the address is there but the customer then has to click to go back home or change address etc, there is no continue button to go to payment.

Update, Through lots of trial and error I have narrowed down the problem to the default country setting under International > Localization > Configuration. If I change the default country from UK to USA, now only addresses for the USA can be created and all others redirect to a log-in without saving. If I change it back to my own country UK, the problem returns for all other countries. I have no idea why this is happening.

Hello, I updated to a new theme and ever since I've been experiencing a terrible problem where customers outside the UK cannot progress through the order process. Personal Information is completed and progresses. Addresses only works for UK customers, when any other country is selected from the drop and the customer clicks "Continue" the page refreshes to a log in. I'm completely baffled. There has to be an issue with the theme but I have no idea what I need to do about this. Anyone have any advice?

I've spent far too long trying to work out what the answer is to this but apparently almost every problem I have with Prestashop is unique to us. We have several languages in our store - EN, FR, ES, GB (we plan to add more in the future). We also have all relevant currencies including Euro, Dollar and British Pound. We have Geo by City to auto select lang and currency by user IP. In the last month we changed "redirection to the canonical URL" to 301 (recommended). Since then Google has been returning only $ results, even on pages with GB lang - although most results in UK serps are EN and not GB. It seems the redirection that is "recommended" is NOT recommended for multi-language or multi-currency stores. Activating this setting seems to have told Google to only display EN and $ results, even for UK searchers. Can anyone confirm that in our case we should turn canonical redirect off completely? We have been working on all translations of all products, categories and pages. If I'm right, I really think PS needs to change the wording of this canonical option, or just offer more information to clarify. If you have unique texts for every language option you don't want to be pointing all those products to the default language you started with and this should not be "recommended".

Can confirm updating the module worked for me. Thank you!

Just being a good citizen and explaining what happened with me regarding this problem. While testing a new theme and going back to the original one while I fix images etc everything was knocked out of whack. I thought i was just hook positions but Prestashop Checkout module was also affected. There is no way to know this from the back end. Everything looks normal. Customers couldn't place orders at all. This problem was solved by resetting the module and logging back into PayPal. I would recommend people try this first before moving other things around that might cause more problems. This is quite a stupid bug for an e-commerce platform to have. The priority should always be that customers are able to purchase. Everything else should be secondary to that. Prestashop should be hardened against the possibility any new module, theme, or minor change could simply close off all payment capability without warning. This should be added to the (already long) list of things PS needs to fix.

Having the same issue. Trying to click to the next page of blog posts leads to 404. Don't suppose you've worked out a solution?

I would love to know this also. I've been trying to work this out for the last 2 months and I cannot find any information about how to implement this. Neither Prestashop nor MaxMind seems to have any basic instructions for how to use their service and it's quite bizarre.

More than a year later and we're experiencing the same thing, dozens of these fake accounts being created per day. Just because you only see three people reporting it here doesn't mean it's not a problem, it just means most people experiencing this aren't here reporting it on an English speaking forum, and if they do come here looking for help they're finding nothing of use (but snarky comments) so there's no reason for them to participate. And to clarify: 1. Adding captcha to forms reduces sales. It just does, it's a fact. Which is why people don't want to do it. 2. I have only 2 modules from a trusted developer, this problem existed before I added both. 3. Everything is up-to-date on my install.

I figured it was being very generous in assessing online visitors, but it's disappointing they haven't rectified this over the many iterations of PS. We're currently enjoying a free trial of a live chat bot and I think we're going to go with the paid version. This shows us who is online and allows us to communicate with them in real time. I was skeptical, but we have actually seen a good increase in sales because of it. It's already paid for itself. I would recommend those who can try a live chat solution. That allows you to actually make use of online data.

We've just installed a live chat module and it flags whenever there is a visitor on the site. Chat module: 5 visitors on site. Google Analytics: 10 visitors on site. Prestashop: 126 visitors on site. Even if we average it out over the "in the last 30 minutes" it doesn't match any other source of information. There's nothing you can really do with this statistic anyway, apart from assess usage, but if it's wrong (and it clearly is) that makes it completely worthless as a data point.

Our store currently has two languages, EN and FR. When creating standard FEATURES (such as colour, length, material) and adding presets for those in both EN and FR, when adding a product and switching to FR to fill out all the translations none of the drop downs for the added FEATURES offer any of the RF translations we added when inputting. For example, when we created all the options under length, we added both the EN and FR (5 Inches, 5 Pouces) in the appropriate fields. Only EN options are available on the product creation pages. Does anyone have a fix for this? It's incredibly tiresome to have to manually add all these for every product, and it causes an error conflict in the Features section when saving.

Thank you for the quick reply Daresh. I have send you a message.