Notice the client=gme-canonical parameter. The parameter specifies a Maps API Premier client name. The client "gme-canonical" expired almost a year ago so it's basically luck that this worked at all since then. There are three possible ways to solve this:
1. Canonical could renew their account.
2. Someone could update the launchpad javascript code to use the new v3 API which doesn't require a key.
3. The client= parameter could be removed and the free API used instead. (Possibly the simplest fix.)
Note that SSL is unavailable for (2) and (3), which may be a problem.
Besides this, there are a couple of other issues which could cause problems in the future:
1. The key= parameter is for the free API key. Either the key= or client= parameter should be specified but not both.
2. The sensor parameter is required. It seems that launchpad doesn't use GPS locations of its users so sensor=false would be appropriate.
The editlocation page is loading the Maps API from this URL:
https:/ /maps-api- ssl.google. com/maps? oe=utf- 8&client= gme-canonical& amp;file= api& v=2& key=ABQIAAAACeZ 5XCmHJlEwBYdSuT 5n8xSpSJz2e5W2U 1FEKkpRR5DvAoRn ExQHcQr64ybfyPf b3_vaIFpvET1ZJg
Notice the client= gme-canonical parameter. The parameter specifies a Maps API Premier client name. The client "gme-canonical" expired almost a year ago so it's basically luck that this worked at all since then. There are three possible ways to solve this:
1. Canonical could renew their account.
2. Someone could update the launchpad javascript code to use the new v3 API which doesn't require a key.
3. The client= parameter could be removed and the free API used instead. (Possibly the simplest fix.)
Note that SSL is unavailable for (2) and (3), which may be a problem.
Besides this, there are a couple of other issues which could cause problems in the future:
1. The key= parameter is for the free API key. Either the key= or client= parameter should be specified but not both.
2. The sensor parameter is required. It seems that launchpad doesn't use GPS locations of its users so sensor=false would be appropriate.