Printable View
You need to enable the PHP CURL Extension. You either need to edit your php.ini and remove the semicolon from the line reading ';extension=php_curl.dll', or, according to this post, there should be a WAMP menu option for enabling/disabling extensions.Quote:
Originally Posted by Venom
Looks like you don't have the CURL module enabled. Make sure to double check both php.ini files as described in the guide, and you should be able to see the CURL module active for both (won't have a ; in front of it)Quote:
Originally Posted by Venom
Thanks for the reply's @Cuprum and @Kathroman. I followed the guide on the first page last night, I'll check the php.ini when i get home later (RL work sucks, lol)
edit:likely this was it, I vaguely remember last night something "funny" happening i tried to enable the curl
Edit2: You guys rocks!! the apache ini file didnt have the ; removed. thanks again
Back again with another question/problem. Can anybody tell me whats going on here?
It will continue to repeat those lines for a while ( i didn't watch it to tell how long)Code:C:\wamp\www\ctgs>C:\wamp\bin\php\php5.3.8\php.exe C:\wamp\www\ctgs\inc\fetch_dat
a.php
Curl error #23: Error while processing content unencoding: invalid code lengths
setCurl error #23: Error while processing content unencoding: invalid code lengt
hs setCurl error #23: Error while processing content unencoding: invalid code le
ngths setCurl error #23: Error while processing content unencoding: invalid code
lengths setCurl error #23: Error while processing content unencoding: invalid d
istance too far backCurl error #23: Error while processing content unencoding: i
nvalid code lengths setCurl error #23: Error while processing content unencoding
: invalid code lengths setCurl error #23: Error while processing content unencod
ing: invalid code lengths setCurl error #23: Error while processing content unen
coding: invalid code lengths setCurl error #23: Error while processing content u
nencoding: invalid code lengths setCurl error #23: Error while processing conten
t unencoding: invalid distance too far backCurl error #23: Error while processin
g content unencoding: incorrect data checkCurl error #23: Error while processing
content unencoding: incorrect data checkCurl error #23: Error while processing
content unencoding: incorrect data checkCurl error #23: Error while processing c
ontent unencoding: invalid code lengths setCurl error #23: Error while processin
g content unencoding: incorrect data checkCurl error #23: Error while processing
content unencoding: incorrect data checkCurl error #23: Error while processing
content unencoding: invalid code lengths setCurl error #23: Error while processi
ng content unencoding: invalid distance too far backCurl error #23: Error while
processing content unencoding: invalid distance too far back
I have the bat file set to run every 15min via windows 7 taskmanager, if it matters. The odd thing is it does not happen all the time, until that is this afternoon.
Edit: After posting this i decided to try just a fresh install (clicked the install.php rather than the notifications.php) and it seemed to get the AH data fine. still it would be nice to know how to fix the problem rather than work around it :D
I believe @Sinshroud had a similar issue awhile back. I don't remember if we ever had it resolved, but I'm 99% certain the error is caused on Blizzard's end and there isn't anything that can be done about it.Quote:
Originally Posted by Venom
One of my unconfirmed suspicions was that the error was being returned because of too many API lookups. If the issue persists, let me know, but I feel like you shouldn't have any issues with it once you're running under normal circumstances.
thanks again @Kathroman
Edit: Nevermind. Fixed it! I thought I had tried everything I could think of, but then I thought of something else. :) It *seems* to me that the issue is the first time I did the set up I put in port 25, not realizing that gmail only allowed STMP over SSL which is port 465. My fault for glossing over that section. Apparently, whatever you put in that first time is stuck there forever. For whatever reason, you can't change that port (maybe I could have I knew how to hell to use the mySQL console, but I don't) with the settings.php. So, I just went to my MySQL directory and deleted the CTGS subdirectory and then re-ran the installation and this time put in the correct port # the first time. Also the file path in the .bat file needed to be updated from PHP5.3.8 to PHP5.3.9, but that was trivial. Problem solved and my test notification went off without a hitch. By the way, thanks a ton for making this. :)
@Faxmonkey - that's a good reminder that the install process needs to be fixed. WAMP server has obviously been updated with a newer version of PHP, so for any future, fresh installs, you are likely to run into similar issues. Until I get around to updating this, remember to make the appropriate changes as described above.
Quote:
Originally Posted by Kathroman
Code:
C:\wamp\www\ctgs>ctgs.bat
C:\wamp\www\ctgs>C:\wamp\bin\php\php5.3.10\php.exe C:\wamp\www\ctgs\inc\fetch_da
ta.php
PHP Fatal error: Call to undefined function curl_init() in C:\wamp\www\ctgs\inc
\functions.php on line 47
PHP Stack trace:
PHP 1. {main}() C:\wamp\www\ctgs\inc\fetch_data.php:0
PHP 2. ParseAndStore() C:\wamp\www\ctgs\inc\fetch_data.php:39
PHP 3. _fetchData() C:\wamp\www\ctgs\inc\functions.php:98
Fatal error: Call to undefined function curl_init() in C:\wamp\www\ctgs\inc\func
tions.php on line 47
Call Stack:
0.0010 736936 1. {main}() C:\wamp\www\ctgs\inc\fetch_data.php:0
0.8078 822968 2. ParseAndStore() C:\wamp\www\ctgs\inc\fetch_data.php:3
9
0.8078 823216 3. _fetchData() C:\wamp\www\ctgs\inc\functions.php:98
C:\wamp\www\ctgs>
Getting the same problem as Venom but with curl enabled =\
EDIT: Going to the wamp task bar > PHP > PHP.ini, is not the same as browsing "C:\wamp\bin\php\(Version here)\php.ini"
so if you have problems edit everything like that.
EDIT 2: Got it working I set up for it to message me if maelstrom crystals are below 1000g... which they are and it doesn't email me =\
I received the confirmation email that it worked but that's all
That's correct - there are 2 different php.ini files. The second one is specifically used by the CLI and the batch file in the CTGS.Quote:
Originally Posted by j311yf1sh
RE: the notifications - First thing I would say is wait an hour. :p From debugging other people's issues in the past, I've noticed that CURL() doesn't really return any meaningful errors when Blizzard locks you out of the API for overuse, so it may go away with time. If not, can you confirm the email settings from phpmyadmin? If you need help with how to do that, send me a PM or come and find me in IRC.