I was thinking about having per user tracking display, but it seems it is not possible to save the per user piwik settings. When I save one, it immediately becomes that for all the others. So always the last Piwik authentication string is the one that is set for everybody.

Comments

xlyz’s picture

I'll look into it. Stay tuned.

dagomar’s picture

Will do xlyz! Thank you!

xlyz’s picture

Status: Active » Needs review

I was not able to replicate your issue, but nonetheless there were some flaws when per user auth was used that I fixed. Please check the latest dev release to see if your issue is still there.

xlyz’s picture

Status: Needs review » Active
dagomar’s picture

Hi xlyz,

The problem persists. I found that when I try to set it for another user, it doesn't save and always has the value for user 1. If you need any more information, I'd be happy to oblige.

Thanks, Dagomar

xlyz’s picture

try with this check list:

- dev version included latest commit when you updated (usually it takes a few hours)?
- any module installed that impacts user profile?
- piwik server configuration?

dagomar’s picture

Hi again!

This time I tried with a blanc minimal install, same problem persists. I have to say that I am on D7.10, do u think that matters?

- fresh install
- in piwik created a site and a user (view rights)
- in drupal piwik added tracking
- in drupal created a testuser
- added the auth string from the piwik user to the testuser > save
- checked and find it back at anonymous

This was done with the latest dev. Probably later today I'll try again with updated drupal install. Is there anything else I could check for you?

xlyz’s picture

I have 7.10 as well.

The only other thing I can think of is to check that your piwik user has proper view permissions set.

In case pick your minimal install, change admin password to "pass", dump the db and attach it here. If I have time I'll look into in.

But be patient as I'm going to have a very busy week.

xlyz’s picture

Status: Active » Closed (cannot reproduce)

not able to replicate it.

feel free to re-open it if needed but please put me in condition to replicate it (see #8)

zeyfah’s picture

Hello,

I have the same issue.

- In the module configuration - reports, the "Piwik authentication string" is left empty so each user can set his/her own authentication string in his/her Drupal account as said in its description .
- Any Piwik authentication string saved on 'user 1' account is set to all other accounts.

I have changed the pass like said and nothing changed.

xlyz’s picture

I'll look into it (again)

what version are you using? beta2? dev?

xlyz’s picture

Status: Closed (cannot reproduce) » Active
zeyfah’s picture

Thanks for the quick reply! I'm using The beta2 release.

Any strings that 'user 1' save on his account are set to all other accounts regardless their roles/permission in both Drupal and Piwik accounts. This only happens if I leave the Authentification string empty in the report setting of the module.

I went through the code. Does it have to do anything with the token auth for global users in the .module file?

xlyz’s picture

Status: Active » Needs review

Fixed (at least I hope so).

What was happening is that if you edited an user profile logged in as administrator, user profile form would show the value of the auth of the administrator, not that of the user. Now should work as expected.

Please update to latest dev, test it and let me know.

zeyfah’s picture

Hi xlyz,

Sorry for the late reply. I've been using the new dev for a few weeks. The issue is solved and it is now working as expected! Thanks.

Found a bug that it doesn't fetch the report when I tried to change the URL for the report page and when I alter how it behaves for different users in different roles in both Drupal and the Piwik server. Apparently it just happened occasionally.

I'm still trying to reproduce it. I'll let you know soon.

Thanks for the useful module.

xlyz’s picture

Status: Needs review » Fixed

in case please file a new issue.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.