I guess I just had 'dust' on my addresses
I meant for you to type 'walletpassphrase' in the same debug console you showed in your screenshot, but using the 'clamd' interface works too.
It's possible your DOGE were in a 'change' address on the day the snapshot was taken. You might want to try importing the whole DOGE wallet (after unlocking your CLAM wallet, as before). That will cause it to check all the change addresses you might own too.
Ok, this is what I have tried now. I enter walletpassphrase XXXXXXXXXXXXXX 3600 and press enter. This seems to work. I then go and choose import the wallet.dat from the Dogecoin directory:
/Users/family/Library/Application Support/Dogecoin/wallet.dat (I am using a Mac) - the only 'special' character is the 'space' and I get the same JSON error as before. I have attached two screen shots:
Right, this was a bit of an oversight since we didn't expect Unix paths to contain spaces(we didn't have a Mac build at the time). If you place the wallet.dat in a path with no spaces, you should be able to use File->Import Wallet properly. That will let you scan all of the change addresses in your wallet without manually entering them. You won't need to use walletpassphrase either. Hope that helps.
Yes, I copied the wallet.dat to another directory and did the import bit and I got one transactions:
Status: 507478 confirmations
Date: 13/06/2015 07:40
From: unknown
To: xLteUZZQa4RLvEv54mfQUYM8CxA3rNdi2T (own address, label: importwallet)
Credit: 4.60545574 CLAM
Net amount: +4.60545574 CLAM
Transaction ID: da947cc0f2ce70f5d40bed208bf49a7f889e5e60fd915e65e98c4620d5124501-000
Thank you
Awesome! I'll make a bug report on this. Cheers!