- This topic has 13 replies, 4 voices, and was last updated 8 years, 7 months ago by .
-
Posts
-
Hello,
I am working on behalf of a client and we just purchased the Pro Pack for SLP. The original plugin is working great! However, the client wanted the geolocation functionality from Pro Pack and even after I turned on the location sensor the prompt to use the location isn’t popping up. I’m not sure if it’s just my machine or if I didn’t set something up properly.
We are using the most recently updated SLP plugin and Pro Pack, so everything should be the most updated versions. The website we’re working with is http://tacosandtequilatnt.com. Any sort of guidance would be much appreciated!
Thank you,
Chelsea
I hope this sheds some light on how Location sensor works. It depends on browsers, how people have their settings etc.
Just a heads up: . Your theme appears to be using jquery 1.11. WP 4.5 requires at least 1.12. See the WP info blog and the SLP Info Blog about the issues that can occur, especially when using SLP or Google Maps API.
jquery.js?ver=1.11.3:5 XMLHttpRequest cannot load http://new.tacosandtequilatnt.com/wp-content/plugins/store-locator-le/images/icons/bulb_red.png. No ‘Access-Control-Allow-Origin’ header is present on the requested resource. Origin ‘http://tacosandtequilatnt.com’ is therefore not allowed access.send @ jquery.js?ver=1.11.3:5
scripts.js?ver=5.0.7:111 element query css parsed
I can just add that for me the location sensor is not working in Chrome but is working in Firefox and Edge. I have not spend any time to investigate yet so I am not sure if theres a chrome issue or just a setting in my browser I have missed. I have no details in this just an observation for the moment.
Hi Guys,
I am not sure if the info I am sharing below bears any weight as far as the location sensor and Chrome issue. I am going to discuss more with Lance when he gets back. I have been watching this development out of curiosity (I am not a programmer)
i.e. Google , Chrome browser, has been sending warnings out for months and months about “Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user’s experience. For more help, check https://xhr.spec.whatwg.org/.”
I have read in the Developers support forums and apparently they are getting serious and it was reported as a bug back in Nov 2015 in the Chrome project. I came across this issue report about geolocation and not sending if not secure origin. (http as opposed to https) I see that the tacos website is http,,, @ Piani. (I do not recall your client site , is it https or http?)
Most recently (apparently Feb when they went to chrome 50) they changed the geolocation if queried over an “insecure” site instead of position unavailable if over http , they changed it to be consistent to be “permission denied”. Since this effecting some customers and not others, I think that it may be the case .
Update geolocation over HTTP error to use PERMISSION_DENIED When geolocation is used over HTTP, we had been using POSITION_UNAVAILABLE, but it was pointed out that using geolocation over a file:// URL uses PERMISSION_DENIED instead. To be consistent, this updates the HTTP failure to use PERMISSION_DENIED. BUG=561641 Review URL: https://codereview.chromium.org/1642903005
No that isn’t what it is saying, Not what I intended to pass along,
The plugin and add-ons will still work fine, I am wondering if it might be an explanation as to why certain versions of Chrome might not ask you for your location even if you have the location sensor enabled. In the ProPAck documentation that the developer wrote years ago, when Location sensor was first introduced, it was explained that some Browsers configuration might not allow location sensor or might not be accurate.
It is just my theory that Chromes latest update has added the twist. Location sensor works even using Chrome on some customer sites and yet not others. My theory is that those sites with https: cert . Again, as Piani mentioned it works using all the other browsers.
I wont know if my theory is correct until I can discuss with the developer, Lance . It is ONLY Chrome version 50 that introduced the secure vs unsecure site and location sensor quandry.
The argument towards having every site go to https because of security threats has been discussed in the worldwide programmer, developer, IT community for a while now. It isn’t just this particular subject.
Glad we could be of assistance. Although I am not promoting the SSL process, I know it is not an easy switch after seeing what Lance had to go through to change the SLP site to https. But it is something to keep in mind going forward.
Here is an article Lance wrote on the subject.
If the community as a whole convinces all thenbrowsers to go this route , it will be a big deal, ( sort of like how the government made TV cable companies to go digital For other reasons, such as bandwidth not internet security.
I’ve actually just found that after updating Pro Pack that I’m running into the same location sensor issue, among other issues. It doesn’t function properly with Chrome. This is actually a problem as according to my server logs, it makes up a very large part of visitors to my site.
Browser-based detection needs to be a fallback for IP based geo-locating. Using one method over the other isn’t sustainable as browsers tighten security.
Jason, Do you have the https:// SSl certification on your site? That is the issue with the Chrome server extensions. Those site who are using HTTPS seem to not be having the same issues.
Are you saying if you do not update ProPack and use whatever version you had before ( not sure since you ahvent posted your versions etc) that Location sensor with Chromne ext, 50 works but some other version of proPack doesn’t?
If you could shed some light on your Plugin Environment and your configuration set up it would be appreciated whereas everyone could share in the knowledge and the developer could look into what the differences are.
Are using WP 4.5.2? If you are still having issues you need to upgrade and also ask your theme author to upgrade. Jupiter is using jquery 1.11 and the current version of SLP and ProPAck are written to work with WP 4.5.2 which uses jquery 1.12 Test your site and see your error messages about headers, and your directory path to your icons, . Check your AJAX returns as well, there is a tutorial that will show you how to do it, it is fairly simple to follow. There are security patches with WP 4.5 , we understand that people do not want to update because their themes might not work properly but the solution is to either get the theme developers to update and fix the themes or change themes. WP has a plethora of ideas on how to test your plugins and themes.
See the Troubleshooting guide on how to do this. It is throwing the error messages and we can not promise you ProPack or your results will work correctly until this is addressed.:
/*! jQuery v1.11.3 | (c) 2005, 2015 jQuery Foundation, Inc. | jquery.org/license */http://tacosandtequilatnt.com/wp-includes/js/jquery/jquery.js?ver=1.11.3
Yes I tested by going to your site, Firefox sends me a message saying , this site wants to access your location…but Chrome is assuming that , for the safety and security of their users supposedly, they aren’t even going to ask. If you are http, they assume you are not a secure site. If a site deems it as important for that message for everyone to be asked to share their location regardless, perhaps they should consider researching if converting to https, makes Chrome happy. .regardless if people do not want to share their location, they can say No to it anyway, at least for desktop surfing.
- The topic ‘Location Sensor Not Asking to Use Location’ is closed to new replies.