Anyone else having an issue on desktop when looking at a ridelog, the map is blank, none of the buttons or tabs are working? I have tried using different web browsers aswell as sending the ridelog link to a friend and the issue persists. Everything seems to be working fine on the mobile app.
Unable to sync routes, neither my own or public ones I have added to my wishlist. Trails and regions sync fine but routes just spins. I've tried uninstalling and reinstalling but it's doing the same thing.
Anyone else having an issue on desktop when looking at a ridelog, the map is blank, none of the buttons or tabs are working? I have tried using different web browsers aswell as sending the ridelog link to a friend and the issue persists. Everything seems to be working fine on the mobile app.
Yes, same here. Also checked it on several browsers and OS. Some ridelogs from early this year still work. The more recents ones won't.
Anyone else having an issue on desktop when looking at a ridelog, the map is blank, none of the buttons or tabs are working? I have tried using different web browsers aswell as sending the ridelog link to a friend and the issue persists. Everything seems to be working fine on the mobile app.
Yes, same here. Also checked it on several browsers and OS. Some ridelogs from early this year still work. The more recents ones won't.
deleting the ridelogs and reuploading them via gpx file seems to get them to work correctly again
The editing function for a ride log is not working properly. In fact I can't even access the drop-down menu, where before I could choose the editing option. And I can't access the ride details like trails, jumps, elevation and grade. It seems that there's a new layout, maybe that's the reason?
Fixed. There was an issue if your Ridelog had jump data from Garmin
gmcc wrote:
trailforks not automatically adding in riding location in ridelogs even though it's identifying multiple trails, i have been manually adding for the past month.
Fixed
tbrady wrote:
Unable to sync routes, neither my own or public ones I have added to my wishlist. Trails and regions sync fine but routes just spins. I've tried uninstalling and reinstalling but it's doing the same thing.
There seems to have been a bad data migration. Reinstalling the app will fix it. We'll try and fix with the next app update.
aloeveruschka wrote:
//strava auto sync issue something is off with the strava sync. set it initially up as automatic and its connected. realised it yesterday. no sync of strava recording within 16 hrs. waited to sync to trailfork to get my toonie badge.
There is often a large queue of Strava rides to import, we are greatly throttled by Stravas limits. Over weekends the queue builds up to many thousands. It will eventually import. There is almost never a queue with rides recorded from the Trailforks app or synced from Garmin.
I've noticed recently that ride logs are not respecting the privacy zone I've set. I have a 400 metre privacy zone but freshly uploaded ride logs seem to be ignoring it. If I do a [ recalculate stats & trail identification ] on the ride log this fixes it, but I have to do this manually for every new ride log.
Same here. Moreover, hitting [ recalculate stats & trail identification ] fixes the privacy zone for rides, but it does not work for snowshoe/ski/run, etc.
I am trying to download gpx of files of several activities and am getting gpx files with incorrect time stamps. On my activity https://www.trailforks.com/ridelog/view/40925029/ it shows a 4:01:44 ride time. When I export the gpx another almost identical activity is created with a ride time of 48:40 (https://www.trailforks.com/ridelog/view/40931880/). This is also the elapsed time in the gpx file (this timestamps just seem compressed)
I am trying to download gpx of files of several activities and am getting gpx files with incorrect time stamps. On my activity https://www.trailforks.com/ridelog/view/40925029/ it shows a 4:01:44 ride time. When I export the gpx another almost identical activity is created with a ride time of 48:40 (https://www.trailforks.com/ridelog/view/40931880/). This is also the elapsed time in the gpx file (this timestamps just seem compressed)
That first ridelog has 3X as many GPS points, so the moving time is going to be different (9287 points vs 2913)
Where are you downloading the GPX files? If you are downloading from the app, then time data is not included.
Please view my ridelog list of trails ridden: https://www.trailforks.com/ridelog/view/41251498/#trails
"Steam Donkey", "MX Trail (Old)" and "MX Trail" were old unsanctioned trails and have been hidden to the public. They have been rebuilt and replaced by legitimate legal trails "Bear Springs" and "MX". It is time to delete the old hidden ones, as one of them is causing a "trail data quality error" on the "MX" trail page: https://www.trailforks.com/trails/mx-524824/
Please view my ridelog list of trails ridden: https://www.trailforks.com/ridelog/view/41251498/#trails
"Steam Donkey", "MX Trail (Old)" and "MX Trail" were old unsanctioned trails and have been hidden to the public. They have been rebuilt and replaced by legitimate legal trails "Bear Springs" and "MX". It is time to delete the old hidden ones, as one of them is causing a "trail data quality error" on the "MX" trail page: https://www.trailforks.com/trails/mx-524824/
Just trying to clean up sloppy trail keeping!
I think this is what the "Permanently Closed/Decommissioned" flag is for, alternatively you can archive the trail. Both options are at the bottom of the "edit trail" page. Even with the data quality error the trail will still upload fine, the warning will go away once it gets approved.
I cannot access the hidden trails to do anything to them.
TheCorminator wrote:
trailhunter1 wrote:
Please view my ridelog list of trails ridden: https://www.trailforks.com/ridelog/view/41251498/#trails
"Steam Donkey", "MX Trail (Old)" and "MX Trail" were old unsanctioned trails and have been hidden to the public. They have been rebuilt and replaced by legitimate legal trails "Bear Springs" and "MX". It is time to delete the old hidden ones, as one of them is causing a "trail data quality error" on the "MX" trail page: https://www.trailforks.com/trails/mx-524824/
Just trying to clean up sloppy trail keeping!
I think this is what the "Permanently Closed/Decommissioned" flag is for, alternatively you can archive the trail. Both options are at the bottom of the "edit trail" page. Even with the data quality error the trail will still upload fine, the warning will go away once it gets approved.