Thanks, also another issue with debugging, the __triggerError() method doesn't provide very much info if cURL barfs. It just prints the error code and not the error message, which isn't very helpful. I've fixed it by changing this line:
You can e-mail it to my sourceforge address if you want ;)
I see what you mean, though. I'll add that in, and check it in to the svn repository, but there probably won't be another official release for a while.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Trying out the new 0.7.0, I'm seeing debug statements all over my site.
Line 892 seems to be the culprit:
if (debugResponse) echo("<p>".str_ireplace("&","<br>",$strtosign)."<p>");debugResponse gets evaluated as a string, so the if will always be true, resulting in debug code all over the place.
Thanks. I'll update the repository and post the fixed version as 0.7.1.
Thanks, also another issue with debugging, the __triggerError() method doesn't provide very much info if cURL barfs. It just prints the error code and not the error message, which isn't very helpful. I've fixed it by changing this line:
To this:
Well that didn't work very well. The line should be:
*sigh*
trigger_error(sprintf("SimpleDB::%s(): %s %s", $functionname, $error, $error), E_USER_WARNING);
Sorry for the spam, it's barfing on the 'code' key of the $error array
You can e-mail it to my sourceforge address if you want ;)
I see what you mean, though. I'll add that in, and check it in to the svn repository, but there probably won't be another official release for a while.