Forum Replies Created

Viewing 15 replies - 346 through 360 (of 415 total)
  • Plugin Author tinuzz

    (@tinuzz)

    Hi

    That’s great!

    My comment was going to be, that if nothing shows up in Apache’s log files, then SendLocation is apparently not connecting to the server, so indeed a mistake in the URL could be a logical explanation.

    I’m closing this issue. Please open a new one if you have more questions or issues with SendLocation support or Trackserver in general.

    Regards,
    Martijn.

    Plugin Author tinuzz

    (@tinuzz)

    No problem. I’m closing this ticket.

    Cheers,
    Martijn.

    Plugin Author tinuzz

    (@tinuzz)

    I got that error before, too, when I checked your site, but if I open it now, it all seems to work. And I don’t think that error is related to Trackserver.

    Regards,
    Martijn.

    Plugin Author tinuzz

    (@tinuzz)

    Plugin Author tinuzz

    (@tinuzz)

    Hi,

    I have prepared another fix, but it seems I have seriously screwed up my Git repository, so I can’t make a release right now.

    Please download and install just this file in the plugin directory:
    https://github.com/tinuzz/wp-plugin-trackserver/blob/master/trackserver.php

    Can you let me know if that fixes the problem?

    Best regards,
    Martijn.

    Plugin Author tinuzz

    (@tinuzz)

    A somewhat serious bug was found in v2.0, so I released v2.0.1 with a fix.

    Plugin Author tinuzz

    (@tinuzz)

    Hello eHc,

    I have no idea why this didn’t come up in my tests, but it was definately a bug. I just released v2.0.1 with a fix. Please update the plugin and let me know if it works okay. Thank you for the report.

    Best regards,
    Martijn.

    Plugin Author tinuzz

    (@tinuzz)

    For completeness, the URL scheme I used (and what should be configured in SendLocation) is this:

    http://<wordpress base url>/<sendlocation-slug>/<username>/<access key>/

    Where <sendlocation-slug> defaults to ‘sendlocation’, <username> is your WordPress login username and <access key> is the key configured in your Trackserver user profile.

    Cheers,
    Martijn.

    Plugin Author tinuzz

    (@tinuzz)

    Hi,

    I just released Trackserver v2.0 on WordPress.org with experimental support for SendLocation. Please update the plugin and see the options page and the Trackserver user profile for settings related to SendLocation.

    I have not actually tested this with the app on an iOS device, because I don’t own any. I have tested with the URL specification as given on SendLocation’s iTunes page, and that seemed to work.

    Please try it out. If you find any problems with Trackserver’s support for SendLocation, please open a new support ticket.

    Best regards,
    Martijn.

    Plugin Author tinuzz

    (@tinuzz)

    Hi,

    I am sorry this took such a long time. I haven’t been able to work on Trackserver for some time, but I just released version 2.0 with support for an information bar at the top of the map. To use it, use the shortcode like this:

    [tsmap track=live infobar=y]

    The content of the infobar can be customized via the Trackserver user profile. At the moment, only latitude, longitude and timestamp (in a fixed format) can be added as dynamic elements in the infobar. More dynamic tags may be added in the future.

    If you have questions or problems with this feature, please open a new support ticket.

    Best regards,
    Martijn.

    Plugin Author tinuzz

    (@tinuzz)

    I have found another solution to what you want, but it requires some work to set up, and it requires installation of an extra plugin called Posts in Page (https://wordpress.org/plugins/posts-in-page/).

    This plugin allows you to include multiple posts or pages in a single page using WordPress shortcodes. So if you create a page with a live tracking map for each user that you want to track (make sure that the page’s author is the user in question), you can include all of those into a single page using Posts in Page.

    Trackserver will correctly use the author IDs of the contained posts (or pages) to show the right live track.

    Note that if your sub-pages are actual pages in WordPress (rather than posts), you have to use [ic_add_posts post_type='page'], otherwise the pages won’t be included.

    I hope this helps, it’s the best I can do at this time.

    Best regards,
    Martijn.

    Plugin Author tinuzz

    (@tinuzz)

    After investigation, I found this to be a bug that only occurs on 32-bit systems.

    OsmAnd sends timestamps in milliseconds since 01/01/1970, and that is a number that is too big for a 32-bit integer. When conversion to integer occurs in the code mentioned above, the result is always the same: 2147483647, which is ‘maxint’ on 32-bit systems (2^31 – 1). When divided by 1000 and converted to a timestamp, the result is always 1970-01-25 20:31:24.

    This will be fixed in the next version of Trackserver, which will be released within two weeks.

    If you need to use Trackserver with OsmAnd on a 32-bit system now, please contact me directly for a fix. Or if you are PHP-savvy, change the code on line 1370 or 1371 from this:

    $ts = round( (int) urldecode( $_GET["timestamp"] ) / 1000 );

    to this:

    $ts = intval( substr( urldecode( $_GET["timestamp"] ), 0, -3 ) );

    Thanks to Marc for letting me use his website for troubleshooting.

    Cheers,
    Martijn.

    Plugin Author tinuzz

    (@tinuzz)

    Ah, assumption 😉

    But I think I’d rather pick a solution where the security ID (password) can be changed by the user as often as s/he likes, because it will be traveling over the wire in plaintext. So the device ID is not appropriate anyway.

    Thanks, I’ll let you know once I have something to test (I hope within a week or so).

    Cheers,
    Martijn.

    Plugin Author tinuzz

    (@tinuzz)

    Closing.

    Plugin Author tinuzz

    (@tinuzz)

    Ok, I’ll see what I can do. One question up front:

    Is it feasable to use the device ID as a password? Can you get the device ID from your phone and enter it in a configuration field in the WordPress admin somewhere?

    If not, there are still other possibilities. I could for example also make the secuity code (password) part of the URL, just like the username.

    Can you give me an idea on what would be the most convenient way to implement authentication?

Viewing 15 replies - 346 through 360 (of 415 total)