CCfromGC Posted February 16, 2016 Share Posted February 16, 2016 (edited) I have prestashop 1.6.0.14 When I enable the geolocation option, it stays enabled until a front-end page is acessed and then it is disabled. The country specific pricing rules are therefore being ignored. I tried updating the GeoLiteCity.dat file to latest. I'm sure this used to work fine. It seems to select the correct currency though, even after the geolocation option is disabled. Any ideas? Edited February 16, 2016 by CCfromGC (see edit history) Link to comment Share on other sites More sharing options...
El Patron Posted February 17, 2016 Share Posted February 17, 2016 The only way to disable is to phsyically disable in back office. However we do see instances sometimes with duplicate configuration names. using phpmyadmin, open your DB, the go to table ps_configuration, using Find function see if more than one PS_GEOLOCATION_ENABLED if so, delete either (or rename if you like). then check back office and set enabled if not already set. Link to comment Share on other sites More sharing options...
CCfromGC Posted February 28, 2016 Author Share Posted February 28, 2016 Thanks El Patron for taking the time to repsond. I really appreciate it. There is definitely only 1 PS_GEOLOCATION_ENABLED item in the ps_configuration table. When set in the backend, it has a value of 1, but somehow it gets set to NULL without changing via the backend. Today I could repeat it very easy, Set to Enable in the back end. Access the shop from Australian IP, Access the shop from US IP, check the value in the backend UI and it is set to NULL. Our goal is to allow access to the shop from Australia and the US where we have direct sales model and to prevent access from countries where we have local distributors. Any further ideas? Link to comment Share on other sites More sharing options...
El Patron Posted February 28, 2016 Share Posted February 28, 2016 Then I have to assume there is some 3rd party logic in your shop. 1. back office-->advanced-->performance disable the use of overrides, retest, post results 2. the same but this time disable third party modules, restest, post results. Make sure to enable these again after test. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now