The undefined curl function in console (WampServer)
Stupid stupid me. On Windows/WampServer, I’ve always had this problem when working with PHP code that can run in the console and using cURL methods..
Fatal error: Call to undefined function curl_init() in D:\Shiki\github\yii-clockwerk\test-app\CurlHelper.php on line 90
It (cURL) works in the browser but not when in console. I didn’t think that it was this simple to fix. The PHP CLI uses a different config file (php.ini) compared to the one used by WampServer/Apache. You can see the location of the config file being used by typing:
Result:
Loaded Configuration File: C:\wamp\bin\php\php5.3.0\php.ini
Scan for additional .ini files in: (none)
Additional .ini files parsed: (none)
You can then fix the curl problem by enabling it in the php.ini file being used. Make sure this is not commented out:

Filipe Correia 6:16 am on July 16, 2010 Permalink
Hi! Thanks for writting this post. It was the only reference I’ve found to this issue…
I’m finding the same problem myself (using dropbox too), but I’m not being able to solve it the same way you did.
Here’s what I’m seeing:
error: * Ignoring funny ref 'refs/remotes/origin/master (fcorreia's conflicted copy 2010-07-14)' locally
Already up-to-date.
$ git branch "merge" "master (fcorreia's conflicted copy 2010-07-14)"
fatal: Not a valid object name: 'master (fcorreia's conflicted copy 2010-07-14)'.
$ git branch
* master
Any thoughts that might help?
Thanks!
Shiki 3:55 pm on July 16, 2010 Permalink
From my experience, you could no longer merge with that branch. It seems to be a corrupted branch file because it was overwritten by somebody else who pushed to the dropbox repo.
Deleting the branch didn’t work for you? Are you deleting it from the dropbox repo? When I get errors like this, I just delete that conflicted branch and fetch-merge-push again. I never lost any of my commits due to the conflict. They just didn’t get pushed properly because of dropbox’ syncing conflicts.
Filipe Correia 5:49 pm on July 16, 2010 Permalink
I’m not being able to delete it. In fact, it’s not showing up when I list the branches (only “master” shows up). It seems there isn’t actually a branch named “master (fcorreia’s conflicted copy 2010-07-14)”.
Filipe Correia 6:10 pm on July 16, 2010 Permalink
Ok, I think i’m on to something. I’ve just checked my repo files (on dropbox) and found these two files on the path “/refs/heads”:
master (fcorreia's conflicted copy 2010-07-14)
It seems that this “master” file as conflicted, so dropbox automatically copied it to another filename. I wonder if I can just delete this file from the repo without leaving other garbage behind, and without losing commits.
Shiki 10:36 am on July 17, 2010 Permalink
Yes that’s right. You should use the repo on Dropbox. I’ve deleted conflicted branches like that with no problem. All I had to do was fetch-merge-push again to put my local changes to the Dropbox repo. Use
to delete it if you can’t delete it with “branch -d” (small d).
Also, notice that your Git repo actually still works with that conflicted copy in there. It just annoys you with the warning message when you fetch.
Filipe Correia 8:19 pm on July 19, 2010 Permalink
Ok, got it. Turns out I was trying to delete the branch locally (although it obviously only existed on the server). Thanks!