Title: rmwb's Replies | WordPress.org --- # rmwb [ ](https://wordpress.org/support/users/rmwb/) * [Profile](https://wordpress.org/support/users/rmwb/) * [Topics Started](https://wordpress.org/support/users/rmwb/topics/) * [Replies Created](https://wordpress.org/support/users/rmwb/replies/) * [Reviews Written](https://wordpress.org/support/users/rmwb/reviews/) * [Topics Replied To](https://wordpress.org/support/users/rmwb/replied-to/) * [Engagements](https://wordpress.org/support/users/rmwb/engagements/) * [Favorites](https://wordpress.org/support/users/rmwb/favorites/) Search replies: ## Forum Replies Created Viewing 6 replies - 1 through 6 (of 6 total) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Bitcoin Payments for WooCommerce] SyntaxError: Unexpected token < in JSON at position 0](https://wordpress.org/support/topic/syntaxerror-unexpected-token-in-json-at-position-0-4/) * [rmwb](https://wordpress.org/support/users/rmwb/) * (@rmwb) * [9 years, 4 months ago](https://wordpress.org/support/topic/syntaxerror-unexpected-token-in-json-at-position-0-4/#post-8873347) * I’ve also been seeing this error after every 18-20 successful transactions… a temporary fix seems to be to create a new Electrum wallet and update the MPK, but a permanent solution would be great… can provide error_log details if required * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Bitcoin Payments for WooCommerce] Unable to fix malformed JSON](https://wordpress.org/support/topic/unable-to-fix-malformed-json/) * [rmwb](https://wordpress.org/support/users/rmwb/) * (@rmwb) * [9 years, 9 months ago](https://wordpress.org/support/topic/unable-to-fix-malformed-json/#post-8261225) * Try this link to further diagnose the problem: [https://mikejolley.com/2015/11/12/debugging-unexpected-token-in-woocommerce-2-4/](https://mikejolley.com/2015/11/12/debugging-unexpected-token-in-woocommerce-2-4/) I eventually found this error: * > ERROR: cannot generate bitcoin address for the order: ‘Failed to find/generate > bitcoin address. Problem: Generated ’20’ addresses and none were found to be > unused. Possibly old merchant’s wallet (with many used addresses) is used for > new installation. If that is the case – ‘starting_index_for_new_btc_addresses’ > needs to be proper set to high value’ * and I seem to have fixed it by generating a new electrum wallet… * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Google Analytics Dashboard] Google's new oauth?](https://wordpress.org/support/topic/googles-new-oauth/) * [rmwb](https://wordpress.org/support/users/rmwb/) * (@rmwb) * [11 years, 2 months ago](https://wordpress.org/support/topic/googles-new-oauth/#post-6123545) * I’ve got the same problem… has this plugin been orphaned or is someone still developing it? * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Bitcoin Payments for WooCommerce] Exchange Rate?](https://wordpress.org/support/topic/exchange-rate-1/) * Thread Starter [rmwb](https://wordpress.org/support/users/rmwb/) * (@rmwb) * [12 years, 5 months ago](https://wordpress.org/support/topic/exchange-rate-1/#post-4617682) * I dug through some code & I think I figured out that you are actually using the Blockchain ticker price [https://blockchain.info/ticker](https://blockchain.info/ticker) and not the Mt.Gox API (as it can be quite slow)… * Should this be updated in the documentation? They may have been the same in the past, but they show very different prices these days. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WooCommerce] update 2.0.20](https://wordpress.org/support/topic/update-2020/) * [rmwb](https://wordpress.org/support/users/rmwb/) * (@rmwb) * [12 years, 8 months ago](https://wordpress.org/support/topic/update-2020/#post-4342449) * 2.0.20 broke one of my sites too… If you need to rollback, older versions can be found here [https://github.com/woothemes/woocommerce/releases](https://github.com/woothemes/woocommerce/releases) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [New Google Sitemaps Plugin v. 3.0b8](https://wordpress.org/support/topic/new-google-sitemaps-plugin-v-30b8/) * [rmwb](https://wordpress.org/support/users/rmwb/) * (@rmwb) * [18 years, 10 months ago](https://wordpress.org/support/topic/new-google-sitemaps-plugin-v-30b8/#post-599707) * `Plugin could not be activated because it triggered a fatal error.` * on WP 2.2.2 Viewing 6 replies - 1 through 6 (of 6 total)