Piwik authentication string ?
memger - March 11, 2009 - 20:11
| Project: | Piwik - Web analytics |
| Version: | 6.x-1.x-dev |
| Component: | User interface |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Description
The readme doesn't mention where to find the authentication string. There's no such setting in the piwik users management. Any hints on what to enter there?

#1
You can find this authentication string inside the piwik administration UI... (not the Drupal module). I hope this haven't changed in the latest piwik version, but it was there in past.
#2
I've attached a screen shot my piwik interface. I guess that's the location you a re referring to?
Any hints on where to find that string?
I can however add additional users and i can see their respective authentication strings, but which should I choose and how does the plugin know which user it should use to authenticate against piwik?
#3
I have installed the latest version today and checked out. You are one the right page. Create a user on the bottom and use the
token_authvalue in the drupal module.#4
Ups - No it think it's a different value... click in your piwik the "API" link... than you see the auth key... not sure if the other will work... I need to test myself
#5
It still doesn't seem to work (couldn't locate the piwik jscript in the page source), although I've now found the token string thanks to your help. Is there a way to check functionality or diagnose the plugin? Logging or something?
thx
#6
#7
#8
Look inside a node, it is there, but not in the filtered pages like "admin"
#9
I found the error: piwik just didn't work with my custom theme. As soon as I switched back to one of the default themes, everything worked.
Do you have any good guess what might cause this?
#10
My best guess so far is, that the fact that piwik js doesn't show up when my custom theme is enabled, has something to do with drupal_add_js not working correctly. Do I need to modify my theme anyway to deal with this? thx!
#11
I've finally tracked down the error. It was indeed my custom theme. Appending a
<?phpprint $closure
?>
cheers!
#12
Well, buggy theme... this is the fix
#13
Automatically closed -- issue fixed for 2 weeks with no activity.