Oh, and the TF website when viewed on mobile auto-opens the top right menu automatically. Sick of having to close it every time (it covers the entire screen!)
... Also don't have any way to access the videos I've posted via my profile any more. ..
It's nice to know which trails I've posted full trail videos for without having to click through every trail in the area. Please bring back videos in profile pages (make it a private list if needed).
"Today I get Bad ID when When I click on Add Video & Photo."
what link where?
anywhere, trail or skill park it does not matter. When I click on Add/Edit > Add Video
or Add/Edit > Add Photo
ATTENTION Message: Bad trail id
The issue does not seem to be browser related. As it happens in several, Atleast Firefox 125, Chrome 123.0.6312.123 It happens every single time, so it makes it impossible to add photos and videos.
Checked some more I also get Message: Bad region id
I think I've mentioned this before without any response, but for some reason trail names don't display on the map for dark blue trails (advanced grade in NZ grading system).
Names display for every other grade/colour, but never for dark blue.
Its the same for both the app and website, and doesn't matter how much you zoom in/out.
Auto-routing does not work anymore (just getting straight lines) when creating routes on the website. This seemed to be working still week or so ago....
Tested both on Chrome (123.0.6312.124) and Firefox (124.0.2).
Problem solved. Missed a screen that was set to Winter Fat Bike, changed it to Mountain Bike and things are as they should be
My trails tab isn't showing up on my ridelog. I do see the Details, POI, Elevation and Grade tabs but not the Trails tab. Was able to edit the ridelog and add the trails but did not get any of the other data you normally get. Should I just uninstall and reinstall the app or is there an easier fix?
1) Posted these POI over the weekend, were approved, clicking to "add photo" results in error page "Message: Bad poi id" - https://www.trailforks.com/poi/145350/ - https://www.trailforks.com/poi/145351/ Note: clicking status button still goes to status input page as expected
2) I usually bulk upload photos for a trail, then edit specific ones with description if needed, it now goes to a blank page at "https://www.trailforks.com/contribute/x_photoedit/" after editing and does not save the edit. I also got the same blank page at that url when originally uploading, but it saved the photos to the trail.
When clicking on a "Your thing was approved" in the notifications box, it opens a new tab to the area of the page you are currently on, instead of showing the thing that was approved. Previously showed the thing that was approved.
Auto-routing does not work anymore (just getting straight lines) when creating routes on the website. This seemed to be working still week or so ago....
Tested both on Chrome (123.0.6312.124) and Firefox (124.0.2).
Yes seems it broke April 11th. Looking into it now.
Canadmos wrote:
Is it still mandatory for people to add a note, when submitting an edit?
I saw a bunch of region edit submissions with no comment on them recently.
Admins can bypass the note field.
Ampfrog wrote:
Two image issues:
1) Posted these POI over the weekend, were approved, clicking to "add photo" results in error page "Message: Bad poi id" - https://www.trailforks.com/poi/145350/ - https://www.trailforks.com/poi/145351/
this has been fixed now. There is a new trail lookup field that broke this.
Don't think photos are quite fixed, but there was a "down for maintenance" just after this, may have cut off the upload: https://www.trailforks.com/poi/145547/ (click bee photo - black pop-up, no bees. Also, I had uploaded two bee photos at that time) If bad timing, please delete and I will re-upload.
Why did my profile page suddenly show 0 submissions of any kind / 0 score (should be around 7000 score), then showed a score of 18,000 with a log link to someone in Mexico?
Update - appears back to normal
Honestly, this is the scariest bug I've seen. Someone else's data shown in my profile. That should never happen on front end or back end. Huge security risk.