SumeetAnand

same error here too. 1-click upgrade throws an error during db upgrade.. followed other forums too ... no solution yet...

Thank you for the reply. In order to test the geolocation feature, I am using: https://geopeeker.com/ HOLA Chrome extension I can see visits from various countries tracked in Google Analytics; so the above two approaches seems to visit the site from other countries and are able to view the site fully. Not sure what I can do to make it work!

I think I have tried almost everything .. need your expert guidance! - Downloaded, unzipped, and placed the geo file as per the instructions (v1.7.1.2) - Selected 'Visitors cannot see catalog' for restricted countries - Selected 'All features available' for other countries - Selected only USA for countries accessible ISSUE: However, the store is available with all features to all countries, no restriction. - to test the functionality, selected 'Visitors cannot see catalog' for both restricted and other countries and I can see that the store is unavailable (403 forbidden) to ALL countries. I just need the store be available to USA and 403:forbidden for other countries. What am i missing??? Screenshot below:

Found something interesting today, Issue: I started getting CartPresenter.php on line 84 when certain combinations were used for a product. Solution: Found that if the attribute values have white spaces, (Attribute: 'Color', Value: 'Dark Red'), the issue persists. However, if I remove the white space, everything works normally. Also, adding a hyphen instead of the white space was throwing the same exception. Erroneous values: 'Dark Red', 'Dark-Red' Solution values: 'DarkRed' Hope this helps!

Greetings, I have started using PrestaShop for a little over 2 weeks now and stunned by so many features. However, noticed that the forum is not too active. Sad. I believe in sharing knowledge, so as I land in issues / resolutions, would like to share with all. One of the issues I struggled to solve today was that all my emails generated from PrestaShop was landing in recipient's SPAM folder. Tested following scenarios: 1. Test Email landed in SPAM folder. Email was being sent using PHP default Mail() function. 2. Switched to SMTP, same case. How to solve it: - Well in Gmail, you have an option to view Original Message. So do that and it had an interesting entry: SPF: SOFTFAIL with IP <my server IP> SPF stands for Sender Policy Framework I followed this link: https://support.google.com/a/answer/178723?hl=en&ref_topic=2759192 and asked my webhosting provider to add the recommended SPF record in the Domain configuration. They showed me how to do it myself. Following entry resolved the issue: v=spf1 mx include:iprange.spf.<hosting-provider> ~all Hope this helps! Best regards, Sumeet

I was able to resolve it at my end. Added the below code to .htaccess file of the respective domain : php_value memory_limit 256M