Problem with mapping tool

[VK3ALB]

Has anyone tried to use the mapping tool recently?

I get a popup saying "This page can't load Google Maps correctly." A sparse map displays with the quote "for development purposes only"

[ZL2WHO]

Hi. I get the same. Haven't had the time or knowhow to investigate. Perhaps Mr google might know the answer ?

[VK6ADF]

See this page. Could be the reason. https://stackoverflow.com/questions/509 ... poses-only

WSPRnet maps has the same problem. I have seen a number of webpages with the problem.

From the above web page
Google Maps is no longer free. You have to associate a credit card so that you can get billed if your site has requests that exceed the $200 credit they give you monthly for free. That is why you get the watermarked maps.

73 Phil VK6ADF

[VK3ALB]

Well there you go.

And so it begins . . . . .

[VK4GHZ]

I noticed the "For development use only" watermark on the DX Path Map (the map embedded in the main logger screen) a few weeks ago.
That map is a two part problem:
1) It uses the scripting for the V2 map API - something that has been obsolete since the V3 API was released 18 months or so ago.
2) It therefore used an old V2 API key
which
3) Recently became invalid with maps no longer being free.

I managed to create a new V2 key linked to my Google account.

Google kindly offer $200 per month free, but above that it begins to cost.

I think useage (a reflection of general activity) has diminished to the point of that not being a problem.

I will attempt to update the Mapping page code with the same key next week, as the internet is crap here in China, even worse via a VPN.

[VK4GHZ]

Band aid applied.
Fixed.

Looks ok in Firefox, Microsoft Edge, and Google Chrome browsers.
Sorry, not tested with ye olde Internet Explorer (because it is not installed on this Win10 notebook) and therefore not tested/supported.

Beacon page also fixed.
(It too has an embedded map).

This will be the last band aid applied to any VK Logger coding.
VK Logger has been on "end of life" for over a year now, as per public announcement September 20, 2017 on the VK/ZL VHF/UHF/microwave Facebook group.

There have been no volunteers to build a modern replacement since that announcement.
If nobody is interested in volunteering, I will nominate a closure date for VK Logger in the near-future to bring about change, one way or another.

I knew absolutely nothing about php, MySQL, etc when I started building VK Logger.
I learnt along the way.
Everyone else can too.

Therefore, there are NO excuses for anyone else not to take on this challenge, and build something that will continue to assist the VK/ZL ham radio community.
All it will take is some time and effort.

The historical data already collected on VK Logger can be made available for import into your new database tables, so that the spots made 2005 - 2018 weren't for nothing.

[VK5PJ]

Hello Adam,
as per most of facebook's content, your post was lost in the litany of adverts and 'fake news' so forgive me for being surprised to see you mention it is 'end of life'.

Is any of the existing code going to be available (on license?) to see if can be moved to vklogger V3 or is your intention to let the current code base die as is?

Regards,
Peter, vk5pj

[VK4GHZ]

The existing VK Logger core coding is based on code from circa 2003.
So no, a complete re-write would be required using modern code and techniques.

I have been forced to keep my three different domains (one of which is vklogger.com) on a prehistoric version of php, simply because the VK Logger coding will not work on anything higher than php v 5.2.17.
My other two Wordpress based sites use various plugin, some of which warn about future updates not working with this old version of php.

Capture.PNG (11.25 KiB) Viewed 5680 times

I have already had to sacrifice a plugin that blocks countries (based on IP addresses) to prevent the never ending stream of spam submitted to forms.
(It too requires a later version of php to work)

Unfortunately all three domains share the same master hosting settings.


Nobody has stepped up to the plate in over a year.
(Although I started making noise about this late 2016)

I guess the easy/LAZY way out is for people to simply use the vastly inferior KST chat - and that's all it is - chat, that is only kept for 2 weeks or so.
There is no spotting ability, no integrated beacon database, no long term history, no mapping ability - just basic chat.
If the community is happy with that rudimentary level of functionality, then so be it.

After all the personal attacks, I lost the passion for this years ago, and I'm busy with other things these days.

I'm quite happy to collaborate with somebody to see the existing database tables are imported into a new platform so that spotting history is maintained and valuable beacon info is retained.

The other benefit of being to upgrade to a newer (higher) version of php is being able to update this forum software, which has also been held back, and is now three years obsolete.