Is anyone else having a problem with this?
Dylan/Decrepit could you have a look at this and identify if it's a KA72 or GPSTC issue and fix it?
Yes same for me for the last few weeks. Been mainly foiling so haven't bothered manually posting....
Me too.
There is a way around it . Go to my tracks page and down load it from there . I think that's how I did it .
If you go into view the tracks/info using the globe icon after you upload it it will post from there. It hasn't been working from the summary page before that for me for a little while.
When clicking the button in ka72.com, the post is sent to gpsteamchallenge.com.au/sailor_session/post which is then redirecting to gpsteamchallenge.com.au/user/login which then, for some reason redirects again to gpsteamchallenge.com.au/user/login (note this is a different url, http not https) for the actual login, which means that the user is logging in to the http version of the site, not the https version.
I am seeing similar weird behaviour if I just go direct to gpsteamchallenge.com.au/user/login and then log in, I get sent to an http page which says "The information you're about to submit is not secure Because this form is being submitted using a connection that's not secure, your information will be visible to others."
I'm not sure I can do anything to fix this behaviour at my end. The redirect seems to be happening from the https version of the page at gpsteamchallenge to the non-https version of the page.
I also noticed this message in my Chrome console:
I've seen this happen on old pages that have been moved to https but still contain references to full URLs. In this case, you can usually drop the "http:" from the url entirely and the browser will use the correct protocol for the circumstances.
Dylan
There is a bit of an arduous workaround that works for me. Which is to log out of gps team challenge, then, making sure your are on the https version of the site (e.g. via this link: gpsteamchallenge.com.au ), log in again from the home page. Afterwards, the upload from ka72 seems to work fine as long as you don't leave it too long between uploads. (Not sure what the exact time limit is, but it seems to be several weeks at least.)
I had that issue for a long time but using a different browser got around it. Chrome wouldn't work but Firefox or Edge did.
There is a bit of an arduous workaround that works for me. Which is to log out of gps team challenge, then, making sure your are on the https version of the site (e.g. via this link: gpsteamchallenge.com.au ), log in again from the home page. Afterwards, the upload from ka72 seems to work fine as long as you don't leave it too long between uploads. (Not sure what the exact time limit is, but it seems to be several weeks at least.)
Sorted, thanks Dylan
change browser to login? worked for me a few times, from chrome to fire fox or to edge or to safari instead?
I just write down the results from KA72 and enter them manually...
Urgh so 1970's
There is a bit of an arduous workaround that works for me. Which is to log out of gps team challenge, then, making sure your are on the https version of the site (e.g. via this link: gpsteamchallenge.com.au ), log in again from the home page. Afterwards, the upload from ka72 seems to work fine as long as you don't leave it too long between uploads. (Not sure what the exact time limit is, but it seems to be several weeks at least.)
Sorted, thanks Dylan
Me too
Just make sure your book mark is set to, https ://www.gpsteamchallenge.com.au/index.php?country=0
instead of http ://www.gpsteamchallenge.com.au/index.php?country=0
They both work, except for sites that require a secure connection.
For the last week I have not been able to upload to GPSTC via KA72 link
Is anyone else having issues ?
For the last week I have not been able to upload to GPSTC via KA72 link
Is anyone else having issues ?
Have you tried Dylan's fix detailed above
For the last week I have not been able to upload to GPSTC via KA72 link
Is anyone else having issues ?
Have you tried Dylan's fix detailed above
Thanks John
I just got around to trying to sort this out now
In my case it was as simple as logging out of GPSTC and then logging back into GPSTC before sending track over from KA72
This worked on for me on both Android phone and windows computer
Cheers
TK