Hello,

The transactions that you see in the “Wallets” -> “Transactions” screen are stored in the wp_wallets_txs table. The export functionality dumps the data into CSV files, but replaces user ids with user emails. This helps when you migrate your data to another installation with different database IDs. As long as users use the same email in your new system, they should be fine even if they have different user ids. If you don’t care about migrating the data to another server, then you might as well use mysqldump or phpmyadmin to export this table. The wp_wallets_txs.account and wp_wallets_txs.other_account columns are WordPress user ids (you can join them with the wp_users.ID key).

From your description, I am not sure what the problem is. To be clear, you used the “Export” link from the coin adapter pages and you got a CSV file, which was working fine before, but now the new CSV export does not contain any new transactions? Also what do you mean by “registration is not displayed in the usual way”? What exactly is missing from the exported data?

Please describe the problem in more detail so I can help.

with regards

Hello,

Oops I think I know why this happens, and it’s a mistake on my part.

The code that does the export is this: https://github.com/dashed-slug/wallets/blob/4.4.8/includes/adapters-list.php#L29-L78

A file handle is opened here: https://github.com/dashed-slug/wallets/blob/4.4.8/includes/adapters-list.php#L38

And the data is written out to the file handle here: https://github.com/dashed-slug/wallets/blob/4.4.8/includes/adapters-list.php#L76

But I never called fclose().

My apologies for this, I feel like this is such a rookie mistake! I will of course fix it on the next release.

In the meantime, you can go to wp-content/plugins/wallets/adapters-list.php and add it between lines 77 and 78:

		fputcsv( $fh, $row, ',' );
	}
	fclose( $fh ); // this line was missing!
}

This must be it. The fix will go into the upcoming wallets release. Please let me know if you can’t edit the file or if you continue to face this issue for any reason.

with regards