tinuzz

Trackserver v3.0 was just released on the Plugin Directory. v3 has lots of new features for displaying multiple tracks. See https://www.grendelman.net/wp/trackserver-v3-0-released/ for updated information.

Best regards,
Martijn.

Trackserver v3.0 was just released on the plugin directory.

Best regards,
Martijn.

Hi,

Yes, the problem is that both ‘update’ and ‘updated’ columns are present. There should be only one of those, but which one is hard to say. Which version of Trackserver are you running?

The column used to be called ‘update’, which is actually a bug, because it was always meant to be called ‘updated’. Only in the current development version of Trackserver there is a code to rename te column from ‘update’ to ‘updated’.

I do have an idea on how this situation arose, but it’s hard to know for sure. Can you edit the database on the old host and make a new backup? In that case, please remove the column called ‘updated’.

I just don’t understand how your old database can have both columns. I mean, your new database will not import it because the table definition is invalid, and your old database shouldn’t HAVE the table like this for the same reason!

There’s something else that’s strange: the table has the KEY for the user_id column 3 times. This means that the code that updates the database after a plugin update has run multiple times. This shouldn’t have happened, but it’s not a big problem. So while you’re at it, before creating a new backup, please remove the keys called ‘user_id_2’ and ‘user_id_3’.

I will add some code to prevent this from happening again. Sorry for the confusion.

Best regards,
Martijn.

I am sorry, I have given it some thought, but this request is too specific to be included in Trackserver. I cannot imagine many people having a use for this, so until I am convinced otherwise, I can’t spend any time on this. I’m closing the issue.

Best regards,
Martijn.

Hi Iro,

Just a quick heads up. I am close to releasing Trackserver v3.0 with multisite support. Expect the release next week at the latest.

I would tell you you can download the current development version from Github and start testing, except I found a bug in the multisite stuff that I have to fix first, so it won’t do you any good at this point.

Best regards,
Martijn.

Hello Darren,

What you are trying to achieve is not really possible with Trackerver 2.x, but it will be with version 3.0, which I will release before the end of the month.

To answer your questions one by one:
1. to not show the lines, you have to specify ‘opacity=0’. In Trackerserver 2, this will be applied to all the tracks, so your planned route will also disappear. In v3, it will be possible to specify color, weight, opacity and marker settings for each track individually.
2. Basically same answer as for 1. With v3, you will be able to specify ‘markers=e,n’, meaning ‘end markers only’ for the first track and ‘no markers’ for the second.
3. Do you mean you would like the initial zoom to be less, so that your planned route is visible in the initial view? Didn’t have this planned for v3, but it’s very easy to implement, so I will add it.

Regards,
Martijn.

In this case, the template was overriding the static homepage setting of WordPress with a custom home page, that wasn’t a real page (in WordPress terms), lacking common properties such as an ‘author’ and skipping common WP hooks during request processing.

Trackserver uses these hooks and properties in several places, and that’s why it didn’t work.

The bottom line is: Trackserver’s [tsmap] shortcode only works on ‘real’ posts and pages.

Best regards,
Martijn.