tinuzz

Please ask specific questions and describe what you tried and what didn’t work, otherwise people will not be able to help you.

Best regards,
Martijn.

Hi,

1. Yes, but only in specific fomats meant for internal use by Trackserver, and in GPX format. See https://github.com/tinuzz/wp-plugin-trackserver look for the [tslink] shortcode. All of these methods are protected with WP nonces, so it’s generally not possible to call those URLs from outside WordPress.

2. To use Trackserver, the user needs the ‘use_trackserver’ capability, which is normally only given to admins and editors. For now, you would need to use a plugin like https://nl.wordpress.org/plugins/user-role-editor/ to add the capability to other roles. In the future, I might make that easy from within Trackserver.

3. No. AFAIK, you would only be able to specify a static name in the URL in OsmAnd, so why not set it in Trackserver, and be done with it? At least you can have time-based trackname rotation then. You can always create a feature request on Github, if you need it!

4. Trackserver doesn’t work with bearer tokens. If you use the MapMyTracks protocol, the use of HTTP Basic Auth is mandatory. I suspect you use a plugin for OAuth in WordPress, and Trackserver should recognize the validity of the token? I guess that would be doable, but the point is that Trackserver is made to work with specific clients, meaning that the MapMyTracks protocol implementation is made for OruxMaps’ client impementation, which doesn’t do OAuth. So there never was any reason to implement it that way.

I hope this helps,
Martijn.

Ah, so you need the ‘href’ value part only, without the HTML tag…

Trackserver doesn’t support that right now, but it would be quite easy to add:

Find the function ‘handle_shortcode3’, in either class-trackserver-shortcode.php or class-trackserver.php (the structure of Trackserver’s code has changed a bit since the last official release).

At the top of the function, add this to the $defaults array:

'href_only' => false,

Then, near the bottom of the function change this line:

$out = '<a href="' . $alltracks_url . '" ' . $class_str . '>' . htmlspecialchars( $text ) . '</a>';

to

      if ( $atts['href_only'] === false ) {
        $out = '<a href="' . $alltracks_url . '" ' . $class_str . '>' . htmlspecialchars( $text ) . '</a>';
      } else {
        $out = $alltracks_url;
      }

Then, you can use

[tslink id=... href_only=y]

to generate the URL.

If you use PHP code (template?) to render the button, you can get the link like this:

$url = do_shortcode( '[tslink id=... href_only=y]' )

I haven’t tested the latter, though. I think it should work.

I’ll include the ‘href_only’ shortcode attribute in the next release.

Does this help?

Great!!

Cheers,
Martijn.

Hi Chris,

The ‘maxage’ parameter only works for actual live tracks, i.e. tracks that are requested with the ‘user=’ parameter.

Specifying tracks by ID and adding ‘live=true’ doesn’t make them live tracks in that sense, it merely tells the Javascript to reload the tracks every 10 seconds as if they were live tracks.

I realize that this may be a bit confusing, and right now I can’t think of any compelling reasons why ‘maxage’ shouldn’t apply to all tracks, other than that it doesn’t really make a lot of sense, if you view tracks that are specified by ID as non-updating. It least, that’s how they were intended, and that’s why the concept of live tracks (user=) was invented.

‘Live=true’ is merely a hack, mainly intended to work with external files (GPX/KML).

Best regards,
Martijn.

• This reply was modified 5 years, 9 months ago by tinuzz.

Glad you got it working! If you still want me to add this to Trackserver, please create e feature request issue on Github.

https://github.com/tinuzz/wp-plugin-trackserver/issues

Cheers,
Martijn.

Isn’t this actually the same question as in the other topic?

While this isn’t in Trackserver right now, it’s really easy to accomplish.

In trackserver.js, find the infobar code, which looks something like this in summarized form:

if (mymapdata.is_live) {
   if (track_id == follow_id) {
     if (mymapdata.infobar) {
       if (alltracks && alltracks[track_id]) {
         metadata = alltracks[track_id].metadata;
       }
       else {
         metadata = _this.get_mydata(div_id, track_id, 'metadata');
       }
       ...
       mymapdata.infobar_div.innerHTML = infobar_text;
     }
   }
 }

If you pull the metadata assigment two levels up, you can very easily add a tooltip to the end_marker:

if (mymapdata.is_live) {
   if (alltracks && alltracks[track_id]) {
     metadata = alltracks[track_id].metadata;
   }
   else {
     metadata = _this.get_mydata(div_id, track_id, 'metadata');
   }
   if (track_id == follow_id) {
     if (mymapdata.infobar) {
       ...
       mymapdata.infobar_div.innerHTML = infobar_text;
     }
   }
 }
 end_marker.bindTooltip(metadata.userlogin).openTooltip();

That last line adds a tooltip with the user’s login name. You can als use the display name:

end_marker.bindTooltip(metadata.displayname).openTooltip();

or any other information that is available in the metadata.

Does that help?

Best regards,
Martijn.

Hi,

Can you clarify what exactly you have in mind for a ‘label’?

Best regards,
Martijn.