Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

piwik_log_visit remains empty when plugin Provider is active #4931

Closed
anonymous-matomo-user opened this issue Mar 31, 2014 · 1 comment
Closed
Labels
Bug For errors / faults / flaws / inconsistencies etc. duplicate For issues that already existed in our issue tracker and were reported previously. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical.

Comments

@anonymous-matomo-user
Copy link

Problem :
Piwik 2.1.0 installed yesterday.
WP-Piwik installed on my Wordpress site to be analyzed.

After lots of tests, table piwik_log_visit remains empty. Some other tables seems to fill (piwik_archive_*, piwik_log_action, ...)
Followed installation guide, double checked troubleshooting page : problem remains.

Awaited behavior :
the table fills after visits on the site, and the report shows it

Workaround :
This morning, I found this entry on Piwik forum :
http://forum.piwik.org/read.php?6,112757
The workaround is to disable the Provider plugin
It worked for me, when I disable the plugin, instantly I gathered a hit in the Piwik dashboard after refreshing the main page of my site.

I have no clue to investigate about the dysfunction of the plugin, but if I can help in any way to gather information on my installation, I'm ready to give a hand. Just explain me what to do :)

This bug is very annoying since it's simply breaks the whole purpose of Piwik just after installing it. Maybe the plugin should be disabled by default on fresh install before the bug is fixed ?

Many thanks for your concern !

Keywords: provider plugin piwik_log_visit empty

@mattab
Copy link
Member

mattab commented Mar 31, 2014

#4886#ticket

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug For errors / faults / flaws / inconsistencies etc. duplicate For issues that already existed in our issue tracker and were reported previously. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical.
Projects
None yet
Development

No branches or pull requests

2 participants