0 comments on “Where Is Toronto, Ontario?”

Where Is Toronto, Ontario?

If you are in North America you may be asking where is Toronto, Ontario. Depending whom you ask, the answer can be slightly different. It turns out that asking Google Maps Canada yields a different answer than if you pose the same question via Google Maps API.

We’ve touched on this disparity in a prior post about Google Maps returning inaccurate results. Today we’ll discuss a specific example for Toronto, Ontario.

And if you are wondering — our vote is that Toronto, Ontario is at

43.65320000 , -79.38320000

Where Is Toronto, Ontario? 43.65320000 , -79.38320000
0 comments on “Google Maps API Returning Inaccurate Results”

Google Maps API Returning Inaccurate Results

Google does not openly advertise the fact that they have different location data for different users. However there is good anecdotal evidence an hearsay that Google Maps API returning inaccurate results may be by design.

The evidence is most prevalent in the geocoding of locations. The latitude and longitude Google assigns to different addresses is not “set in stone”. It is an interesting anomaly given the fact that places on earth should not move with regard to their latitude & longitude outside of plate tectonics.

The team at Store Locator Plus® has long held a theory that Google intentionally subverts accurate location data; quite likely to gain competitive advantage for their own products and services.

3 comments on “WordPress 4.9.9 File Type Not Permitted Workaround”

WordPress 4.9.9 File Type Not Permitted Workaround

WordPress 4.9.9 as well as 5.0.1 and ALL the “security patch releases” back to 3.7 now have a new CSV file management bug.   Any CSV file that is uploaded is rejected by WordPress due to a security violation.   

The Quick Fix

Add this to your wp-config.php file:

define(‘ALLOW_UNFILTERED_UPLOADS’, true);

Yes, this will effectively disable all those cool new “security features” in the latest release of WordPress but it also will get your CSV imports working again.   Just remember to take this out when WordPress 4.9.10 (or 5.0.2) comes out — assuming they deem this new “security feature” a bug and patch it accordingly.