Very odd. Since none of those extensions are mission critical from the front-end, can you try disabling them and see if it is indeed a conflict?
Nothing related to the Analytics Panel extension should be loading anywhere but on the extension settings screen until some settings are input, so I can’t see how it could be clashing with anything else. Did you try deleting and uploading a fresh copy?
I hate the be the problem child here but when I enabled the extension and entered my Google information I get the following error:
Warning: Analytics_panel::require_once(/www/eh10465/public_html/ohs/lib/analytics_panel/gapi.class.php) [function.Analytics-panel-require-once]: failed to open stream: No such file or directory in /www/eh10465/public_html/ohs/extensions/ext.analytics_panel.php on line 93
?
I hate the be the problem child here but when I enabled the extension and entered my Google information I get the following error:
It would appear you didn’t upload the /analytics_panel/ folder to the /lib/ folder.
Is there any way in future versions to set which member groups are able to view this via the extension settings?
Great idea - will put it on the list.
Just tried this on another website on a completely different web server (running php 5.1.6) and it worked great, first time.
I’ll have to do some more testing to try and narrow down whether my previous issues are down to a clash with another addon or the php version number.
Great extension though, just what the CP home page needed.
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.
@D-Rock
Have you ever thought about releasing this extension as a module or as a extension/module combo? The extension would be a quick view of the analytics whereas the module would allow you to dig deeper. Plus, with the module the admin could set which member groups could view it.
The only reason I was really thinking about it being a module instead of an extension was for this situation:
Imagine I only want the superadmin (me) to be able to view the analytics. I normally offer analytics as a service (includes actually analyzing the analytics, not just slapping them up there), so I always incorporate analytics into my sites, but I don’t tell the clients. This way I can still collect info on the performance of the site while I try to upsell them.
So say one day I need to sign in to the website to make a quick admin setting update while the client is with me. Well the first thing that they would see would be the analytics extension on my CP home page. If it was a module, it would be buried in behind the modules tab and not viewable when you first sign in.
I’m not sure how many other people use it this way, but I thought I would let you know how I could use it so you have some insight on how people want to use your extension.
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.