I would like to PM you but it doesn't seem to be possible, so I will just state it here:
Just checking if a admin wordpress account on a test environment would help you out enough (as opposed to a FTP-account) to do some testing to try and resolve the "cURL failed" issue with the last plugin?
Some details I can already give:
PHP version: 5.3
WP version: latest
Server environment: Linux
shared hosting provider: www.web-oke.nl
if a wordpress account is not enough I might be able to provide an FTP account as well, but again, this is a bit of a last resort method to me.
That said, I have commented out the "'ehough_shortstop_impl_transports_CurlTransport',"
line in the right place and this does indeed resolve the problem, however, according to some details I found in the FAQ of my hosting provider, cURL methods should be working just fine
Thanks for looking into it and priority is at the moment, as stated before, rather low because it all works fine with either the previous version of the plugin or the commented out line in the new version.
I'm sorry that you're still experiencing trouble with cURL. We try our very best to make sure that TubePress works on all server configurations, but obviously we aren't 100% bug free. I would still very much like to solve this issue once and for all.
We don't mean to blow off reports about this bug. To be a bit frank, it has been low priority because 1) thousands of sites are using cURL with TubePress without any trouble and 2) it's been impossible so far to reproduce reliably. I know that doesn't make it any better for you, but hopefully this adds some context to the situation.
So, how do we fix the bug? Best case would be shell and/or FTP access to your site. That would allow me to run some tests to find out exactly what's failing. Is it the network? PHP's configuration or version? The hosting provider? If you feel that you could provide this, please feel free to contact me privately over at the TubePress Community site. My username there is "eric".
Thanks for your understanding and I look forward to nailing down this issue once and for all!