Happy Holidays!
Lots of new things this time:
- More UI polishing and small screen fixes
- New e-mail action for points and trips
- Uploading drafts can now be disabled in publisher settings
- New privacy setting can reduce GPS accuracy when publishing
- New web-based help system and how-to
- New Quick Post feature (post directly to blogs, from other Android apps)
- Viewer works without SD-Card
- Reduced notification noise
- No longer requires GPS (it is still preferred though)
- Found and fixed more force-closes
I have some trouble with the publisher, whereblogger report "Status: Published succesfully", but I cant find anything in WordPress. What is the correct url for a wordpress-installation?
ReplyDelete/index.php ?
/?
something else?
Are your posts drafts? Have you configured the blog to not publish draft posts?
ReplyDeleteJust giving WhereBlogger the path to your blog should be enough, the program visits the page and scrapes the metadata for information on where the XML-RPC service lives.
Sorry, to clarify, configured the blog *in the whereblogger publishing settings* to not publish drafts...
ReplyDeleteExcellent; I concider using this to publish the progress during my summervacation (Bike-riding across denmark). I presume there are no way to get timestamp in the kml-file all point during path-recording?
ReplyDeleteNot sure I understand the question. However...
ReplyDeleteWithin WhereBlogger each point is timestamped, so the data you want does exist. When you record a path, points which are 'hidden' (only part of the path, not egligable for publishing as a blog post or a featured point on the map) are presented as a path in KML, which is just a sequence of coordinates.
However, I think if you activate the 'show all data' setting for your trip, every single point will be published as a point, and thus give you the timestamps you want. That may be a bit messy though, and might interfere with other things you would do, especially if you plan to publish to a blog as well.
A different strategy, would be to take a look at the JSON output created - it is basically a raw dump of all the data recorded by WhereBlogger, in a tabular format. Timestamps are presented there as numbers: Unix time, seconds since 1970.