For each of the two affected collections (I experimented with two different calendars whilst testing Things 1.0.1) I now have .ics export files, products of Chandler Desktop 1.0.2.
I gained these by importing from a good .chex whilst my computer was disconnected from the Internet. (The disconnection prevented Chandler Desktop from automatically re-gaining all that is wrong from the Hub. I exported to .ics whilst disconnected.) So now, for each affected collection, I can: 1. un-publish (remove from Hub) 2. re-publish. However: I guess that doing so can not preserve the UID of the collection, nor the validity of the tickets. (Chandler Hub Account Browser allows revocation and creation of tickets, but offers the account owner no interface to edit existing UIDs or tickets. This logic is understood.) Is second publication, with loss of original UIDs and tickets, the closest I can get to a 'push of the truth'? TIA Graham -- View this message in context: http://n2.nabble.com/-dataloss--How-to-push-the-truth-in-Chandler-Desktop-1.0.2-to-Chandler-Hub--tp2184993p2187120.html Sent from the Chandler users mailing list archive at Nabble.com. _______________________________________________ [email protected] mailing list unsubscribe here: http://lists.osafoundation.org/mailman/listinfo/chandler-users Chandler wiki: http://chandlerproject.org/wikihome
