+ian-and-penny Posted April 4, 2015 Share Posted April 4, 2015 (edited) A number of Garmin users (many and various models) here in Australia have discovered that their GPS freezes or turns off when they look at recent logs that contain the HTML comment code "<!--". It appears that some log authors are using this HTML comment tag to hide the last edited information added by Groundspeak after the last text entered by the log author. The result is that the Garmin code to render the HTML from GPX data just chokes on the use of this tag and then freezes or turns the unit off when the user views recent logs. Groundspeak should probably strip out this code in logs because they cause a Groundspeak "feature" to be circumvented, but this may take some time to implement. In the interim, GSAK users can update to version 8.5.1.28 which will filter out this code when importing logs (and then do a Database > Repair/Defrag to remove any code already in their database). Unfortunately I don't know of a fix for those that import files directly into their GPS unit. Edited April 4, 2015 by ian-and-penny Quote Link to comment
jholly Posted April 4, 2015 Share Posted April 4, 2015 A number of Garmin users (many and various models) here in Australia have discovered that their GPS freezes or turns off when they look at recent logs that contain the HTML comment code "<!--". It appears that some log authors are using this HTML comment tag to hide the last edited information added by Groundspeak after the last text entered by the log author. The result is that the Garmin code to render the HTML from GPX data just chokes on the use of this tag and then freezes or turns the unit off when the user views recent logs. Groundspeak should probably strip out this code in logs because they cause a Groundspeak "feature" to be circumvented, but this may take some time to implement. In the interim, GSAK users can update to version 8.5.1.28 which will filter out this code when importing logs (and then do a Database > Repair/Defrag to remove any code already in their database). Unfortunately I don't know of a fix for those that import files directly into their GPS unit. It's been this way for years. Nothing new. Quote Link to comment
+Viajero Perdido Posted April 4, 2015 Share Posted April 4, 2015 Oh cool. Thanks for the tip on how to eliminate that "edited by" stuff... If only I could force myself to leave a comment unf Quote Link to comment
+Red90 Posted April 4, 2015 Share Posted April 4, 2015 GSAK has been stripping the bad code for many years. Quote Link to comment
+AnnaMoritz Posted April 4, 2015 Share Posted April 4, 2015 (edited) wrong thread .. Edited April 4, 2015 by AnnaMoritz Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.