Fieldtype, Module

Archived
Forum
(read-only)

CE Tweet

ExpressionEngine 2

Back to this add-on's main page
View Other Add-ons From Causing Effect

     

CE Tweet Exception Occurred: 0

Support (Resolved)

sm9
sm9

Hi Aaron,

I’ve got a similar issue to what was reported in this thread: http://devot-ee.com/add-ons/support/ce-tweet/viewthread/9610

CE Tweet is working fine locally (MAMP) and on our staging server (a cPanel server), but after putting a website live (a Plesk server), the CE Tweet tags won’t output anything.

I’m seeing this in the Output and Debugging:

***  CE Tweet debugThe cache file "/var/www/vhosts/mywebsite.co.uk/LIVE/www/docroot/my_system/expressionengine/cache/ce_tweet/p_d2bd6aae4c07a4a9e56b2fdfe66a5436" does not exist.
***  
CE Tweet debugAn exception occurred0 “

The EE Cache folder has 777 permissions and the Assets add-on is caching things in the folder okay. CE Tweet is creating a CE Tweet folder within the EE Cache folder, but it isn’t creating any files within it.

The staging server is using PHP 5.3.27 whilst the live server is using PHP 5.3.3. Both have Curl listed in the phpinfo (staging server: http://cl.ly/image/1f21053U0s1A, live server: http://cl.ly/image/2n1k2h1y3o3o). We’re using EE 2.5.5 and CE Tweet 1.3.8.

Do you have any idea what could be going wrong here? Or what other server settings I need to ask the web host to check?

Thanks,

Stephen

sm9
# 1
sm9

Hi Aaron,

I’ve just been looking at the PHP info further, and noticed that at the top of the page in the Configure Command box, it includes the text: ‘—without-curl’ (screenshot: http://cl.ly/image/1m0C0e053d1a). It says this, even though further down, it says that Curl is enabled (screenshot: http://cl.ly/image/2n1k2h1y3o3o).

Do you think this could be the cause of the issue?

Thanks,

Stephen

Causing Effect - Aaron Waldon
# 2
Developer
Causing Effect - Aaron Waldon

Hi Stephen!

An error code of 0 generally means that no error code is set up for that cURL error. I have run into this a couple of times before on some edge cases.

Can you please run that code in a test template, and uncomment the following lines in ‘third_party/ce_tweet/libraries/EpiCurl’ (around line 162-169)?

You’ll want to change the lines from this:

/*
//added by Aaron Waldon to get the curl error message on 3/7/2013
if ( $data === false )
{
   //exit( 'Curl error: ' . curl_error( $done[ 'handle' ] ) );
   throw new Exception( 'Curl error: ' . curl_error( $done[ 'handle' ] ) );
}
*/ 

to this:

//added by Aaron Waldon to get the curl error message on 3/7/2013
if ( $data === false )
{
   
//exit( 'Curl error: ' . curl_error( $done[ 'handle' ] ) );
   
throw new Exception'Curl error: ' curl_error$done[ 'handle' ) );

When you refresh the page, you should see an error. Can you please let me know what it is?

Just last week someone uncommented the above code and got an error that said: “Curl error: Problem with the SSL CA cert (path? access rights?)”. It turned out that it was some esoteric error that people on Stack Overflow had posted about, and the solution was to simply restart Apache. The error you get may be different though…

Please let me know what you find out. :)

sm9
# 3
sm9

Hi Aaron,

We found that Curl was working fine for calling http:// sites, but not working when trying to call https:// sites. So we got the web host to restart the server and the issue resolved itself after it had restarted, like you mentioned some people had posted about on Stack Overflow! :-)

Thanks,

Stephen

Causing Effect - Aaron Waldon
# 4
Developer
Causing Effect - Aaron Waldon

That’s very interesting. I wonder why that occasionally happens. It seems to be an Apache mystery at this point.

sm9
# 5
sm9

Yes, no idea. If I had control of the web hosting, I’d have turned it off and on a lot quicker too. :-)