The temporary file isn't there for CURL! type error

HI

I am getting The temporary file isn't there for CURL! type error while logging with joomla account.And i have joomla 3.2 integrated with moodle 2.5 by joomdle R0.93 .
please suggest some solution.



Regards
Sumit

J3.2 has introduced a number of problems with many extensions including Joomdle, Kunena, etc. Therefore, I would first download Joomdle R0.94. I do not know that this will fix your problem with it will certainly prevent the other identified problems with J3.2 shared in this forum.

For your CURL error, some of the obvious: Do you have CURL installed and configured? Do you have appropriate permissions settings on your server? Have you tried configuring Joomdle file_get_contents instead?

You should enable debugging to get more details of the error.

Hi Chris

Can you just tell me the file permissions structure of server to resolve this error.

This message is shown when the file cannot be found in the joomla temp folder, maybe you have bad permissions there.

Also, you can use SSO with redirection. Most sites have no problem with it.

Hello all - I'm new to the Joomdle community, so still finding my feet a little.

My install of Moodle, Joomla and Joomdle as all gone swimmingly, except for this error:
The temporary file isn't there for CURL!
that I get every time a user logs in to Joomla.
I'm using Joomla 2.5 (for compatibility with Virtumart 2) and Moodle 2.5, with the Joomdle 0.94.
I'm on a shared host and the system check is Green apart from the 2 HTTP accesses. It requires the internal IP for the web services to work.
I have a duplicate, test version, set up on my local systems and it all works fine.
I checked the file permissions on the 'tmp' folder in Joomla and the web (Apache) user has full access.
If I try to debug the problem in Joomla, the whole site just breaks before I get to login . Issues with Virtumart.

Can you please let me have more information on how cURL should be working, so I can trace the error?

I'm a little bit stuck now .

Try disabling redirect-less SSO.

Thanks Antonio,

I've tried several combinations of that - Joomla only, Moodle only, Joomla & Moodle. I've also tried moving Moodle to a sub-directory of Joomla. It appears to be some condition on the shared platform, I just can't work out how I should trace the issue.

> I've tried several combinations of that - Joomla only, Moodle only, Joomla & Moodle

Not sure what you are talkign about. I was talking about the redirect-less SSO option.

Only the check box settings in the configuration in Joomdle on Joomla and the equivalent in Moodle > Auth > Joomdle. Should I be looking somewhere else?

Embarrassingly, I've just tried it again - Turning off 'Use redirectless SSO' & 'Use redirectless logout' and this appears to work - I'll come back if it breaks again.