blistovmhz

How does the plugin check for confirmations? I’m assuming it’s just a periodic poll? If so, how often does it poll and for how long? ie: will the poll survive a reboot?

Tried WebDesZ’s solution, which seems to have worked. Exchange rate was correct, transfer seems to have gone through, just waiting on confirmation.

What exactly did I just … do? and why’d it work, and should I be worried?

@gleb, yup, that worked. But why? Is MT.Gox refusing to service my request, while allowing others?

Oh, I did just notice while tcpdumping that the plugin does contact MT.Gox. I’ve no idea what all happens in that exchange. Are we expecting a certain port to be open for this plugin to work?

@gleb, Sorry, somehow didn’t send yesterday (oops). Sent again.

@gleb, I sent you admin access by email yesterday. Test server is just sitting waiting.

Well, it’s never worked for me, but the issue is as you described. Once the plugin is loaded, I can’t access woo-settings or checkout page. Both just hang and there’s nothing reported in Apache logs.

This is interesting though that it worked for you up until yesterday and now does not.
I’ve been trying to figure out what the API key actually does, and if it’s required. Have you entered anything into the API key field in plugin settings?

@webdesz, I’m assuming you’ve already tested deactivating the Bitcoin plugin from BitcoinWay and confirmed that doing so results in your woo-settings page loading correctly again yes?

I setup a new instance of WP on the same server and tried again. Installed WC and then Bitcoin plugin. Same issue exactly.

Installed WC on my desktop and tried with a new instance, and works fine. I dunno, gotta be something with Ubuntu 12.10 server I suppose. Would be nice to figure it out on my production server, but in the mean time I’m building a new instance with Ubuntu 12.04 LTS to see what happens there.

Paysius seems to work (loads anyhow) without issue.
Yes, connected to internets. Everything else seems totally normal at this point. No other plugin issues anywhere.
I may build a new VM and test it on a clean install, as I did have the earlier issues with WP in general.
I’ll dig into that tcpdump tonight to see what’s actually going on. The fact that Apache isn’t reporting anything in access log seems … odd, but I don’t know enough about … something… to know why the connection clearly comes back to the server but Apache doesn’t seem to notice.

Ha! Thanks! I no longer receive any errors regarding pre-defined constants, but the WooComm settings page and checkout still hang ??
No errors in debug.log, apache-error.log, and hell, nothing even in the apache-access.log. (Apache error logging set to debug).
I click Woo Settings or checkout and everything just hangs.
I did confirm via tcpdump that the request is making it to the server, but haven’t had time yet to parse through it. Seems odd though that the request never hits apache logging though. What would cause this?

I’ve also disabled all other plugins except woocommerce and bitcoin, to the same effect.

What causes the server to hang, without throwing any logging whatsoever?

Hosted locally, Ubuntu server 12.04, Apache-2.2.22, PHP-5.4.6, Mysql-14.4

As I said, I strongly suspect something was injected into the DB during the first installation attempt when my installation was broke.
Is there any way to enable debugging of the plugin so we can watch the failure/hang?
Sorry, totally newb to WP.

I enabled WP debug and got this:

Notice: Constant BWWC_VERSION already defined in /var/www/wordpress/wp-content/plugins/bitcoin-payments-for-woocommerce/bwwc-include-all.php on line 9
Notice: Constant BWWC_EDITION already defined in /var/www/wordpress/wp-content/plugins/bitcoin-payments-for-woocommerce/bwwc-include-all.php on line 12
Notice: Constant BWWC_SETTINGS_NAME already defined in /var/www/wordpress/wp-content/plugins/bitcoin-payments-for-woocommerce/bwwc-include-all.php on line 15
Notice: Constant BWWC_PLUGIN_NAME already defined in /var/www/wordpress/wp-content/plugins/bitcoin-payments-for-woocommerce/bwwc-include-all.php on line 16
Notice: Constant BWWC_I18N_DOMAIN already defined in /var/www/wordpress/wp-content/plugins/bitcoin-payments-for-woocommerce/bwwc-include-all.php on line 20
Notice: Constant BWWC_VERSION already defined in /var/www/wordpress/wp-content/plugins/bitcoin-payments-for-woocommerce/bwwc-include-all.php on line 9
Notice: Constant BWWC_EDITION already defined in /var/www/wordpress/wp-content/plugins/bitcoin-payments-for-woocommerce/bwwc-include-all.php on line 12
Notice: Constant BWWC_SETTINGS_NAME already defined in /var/www/wordpress/wp-content/plugins/bitcoin-payments-for-woocommerce/bwwc-include-all.php on line 15
Notice: Constant BWWC_PLUGIN_NAME already defined in /var/www/wordpress/wp-content/plugins/bitcoin-payments-for-woocommerce/bwwc-include-all.php on line 16
Notice: Constant BWWC_I18N_DOMAIN already defined in /var/www/wordpress/wp-content/plugins/bitcoin-payments-for-woocommerce/bwwc-include-all.php on line 20

If I comment out all the defines, … nothing hangs ?? but of course the plugin doesn’t do much. I can see it in payment gateways and enable it, but it doesn’t get enabled.

I’ve also tried uninstalling the plugin and manually removing “BWWC-Settings” from wp_options table, then reinstall. No difference.

Thanks Gesman. Unfortunately no. I’ve run into this before long ago after a WP update, but WP fixed the problem a few days later. More recently the same issue came up but WP folks are saying it’s not their issue and to discuss with plugin maintainers. The WooCommerce guys sent me a patch for one of their plugins which fixed the problem, but I suspect as very few people are having this issue, it’s gotta be something infrastructure side, that happens to be repairable on the plugin side as well. I suspect though, that fixing on the plugin side may not be the right answer.
*le sigh*.