I’m not much of a geek, although I taught computer applications in the Apple IIe days and early Mac days. Your position on responsibility is pure wisdom.

Best regards,

Hugh


/opt/local/bin/wget --directory-prefix=/path/to/save/ToodledoBackups --no-check-certificate --save-cookies /
tmp/toodledo_cookies.txt --post-data 'email=myemailaddress&pass=mypassword&remember=1' http://www.toodledo.com
/signin.php http://www.toodledo.com/xml.php


Obviously replace “myemailaddress”, “mypassword” and “/path/to/save/ToodledoBackups” with appropriate things for you and your system.

This just runs wget, first on the Toodledo login page, posting my username and password and (effectively) checking the “remember me” box so a cookie gets saved. Then it visits the “xml.php” page, which simply dumps all the logged-in user’s tasks in XML format. wget will automatically save with new filenames if the file it’s getting already exists, so this will create a new backup file in the specified directory every time it’s run, rather than overwriting the same one each time.

If you prefer a different format, “csv.php” will download a CSV file, and “txt.php” will grab plain text. There are links to all these pages from the Import/Export/Sync pages at Toodledo.

I’ve got this in a script which removes the old cookie file before it runs the wget; can’t remember whether that’s actually needed or not.

There will be a nicer, cleaner and safer way of doing this — using the API with a registered API key is probably the way to go. But as this never broke, I never bothered fixing it

Plus there’s an application or two which will sync with Toodledo, I believe (maybe their iPhone app? Not sure) which would be an even easier way of making sure you didn’t lose everything if Toodledo ever went away.