Very strange.  I can’t even speculate on an explanation for that.

If you want to track it down, I’d suggest a fresh EE install on the same server, and installing only this extensions to see if it still happens.

D-Rock - 17 November 2009 07:36 AM

Just tried this on another website on a completely different web server (running php 5.1.6) and it worked great, first time.

Glad it worked out on another server. I wonder if maybe the first server was lacking cURL and had fopen disabled?  One of the two are required to authorize.

Hi there,

I’ve finally got this extension working on that particular server!   Although both fopen and Curl were listed as being enabled in the phpinfo, I noticed in the Apache settings that CurlSSL and Curlwrappers weren’t enabled. Enabling these seems to have done the trick.

Thanks for the great extension and look forward to the EE2 accessory when you get a chance to look at this!

Having a funky problem w/ this extension: When I try to save the settings, I get the good ol’ white screen of death.

fopen and cURL are enabled. Any ideas?

FWIW, I have the same problem with Seeries - when I try to save any settings, I get a white screen. Haven’t been able to sort that out either.

thx!

When I try to save the settings, I get the good ol’ white screen of death.

Two things come to mind: are you running PHP 5+? Have you uploaded the ‘analytics_panel’ folder to your /system/lib/ directory?

D-Rock - 07 February 2010 01:49 PM

Two things come to mind: are you running PHP 5+? Have you uploaded the ‘analytics_panel’ folder to your /system/lib/ directory?

Aye to both.  Running 5.1.6, and the folder is uploaded.

Dylan - hmm, not sure what could be causing that then.  Perhaps an extension conflict.  If you’re able to disable all other extensions, you could give that a try.

In other news, I just updated the extension to version 1.1.5, which adds hourly caching of “today’s” stats (ported from the necessary work on the forthcoming 2.0 accessory), along with a few other small fixes..

For interested folks, I just released the EE2 accessory version of Analytics Panel, called CP Analytics. Check out the forum thread or find it on GitHub.

Would there be any reason why 1 server running PHP 5.2.4 can’t authenticate whereas if I use all the same settings on a server running PHP 5.2.9 there are no problems.

allow_url_fopen is on/on
cURL support enabled
on both servers. Used the same google username/pass for both servers.

GA Plugin 1.1.5
EE 1.6.8 on both - although the working one is build 20090723, the non-working one is build 20100121
Error message is: Couldn’t authenticate with the credentials provided.

There are different extensions in each site, but I’m not getting any white screen issues or php error messages. Just the authentication problem. I’ve reuploaded all the files a couple times. Even changed my GA account password.

Works like a charm on one, but not the other. Anything else I can look for?

Marc – that’s an odd one.  I can’t think of anything that might be causing this.  I’ve got version 1.1.5 running just fine on all recent 1.6.8 builds.

If you’re comfortable digging around i some code, the GAPI class that’s included with the extension (in the /lib/ folder) has some commented-out exception throws in it.  You could uncomment these and see if you could track f=down where exactly the authentication is failing. (Look in the authenticateUser() and httpRequest() functions.)

Ah disregard. I had my host reboot my server last night and this morning I can now authenticate. Weird.

Thanks for the fast reply and the awesome addon!