I recently installed Serverbuddy on a test wordpress site to vet my basic site builds, and I kept getting "PHP Curl support" indicating as disabled/Fail. This is on a fairly stock RHEL5 system, and I was able to verify that the standard curl packages are installed and in active use by other packages/plugins.
Last night I tracked the issue back to the check done by Serverbuddy -- apparently it is looking to phpinfo() output for most of these checks (interestingly, using curl to acquire said output...), and is failing to match the cURL information in the output.
The problem apparently lies with Serverbuddy's rule for curl (definitions/general.txt & definitions/information.txt), which targets the text "cURL support", while the phpinfo() output shows a line for "CURL support". Changing the rule in each file from "cURL" to "CURL" allows the plugin to properly identify the system's 'PHP Curl support' status.
Note: a quick google search returned several references to cURL availability checks in other php apps/utils failing due to similar case-sensitivity issues. The common suggestion for resolution was to employ case-insensitive comparisons.
Case-sensitivity breaking Serverbuddy's cURL check...
No replies to this topic