We are moving to Git Issues for bug tracking in future releases. During transition, content will be in both tools. If you'd like to file a new bug, please create an issue.

Bug 3909

Summary: Upgrade or replicate phpMyVisites plugin to Piwik
Product: OJS Reporter: James MacGregor <jmacgreg>
Component: Plug-insAssignee: James MacGregor <jmacgreg>
Status: RESOLVED FIXED    
Severity: minor CC: a.marchitelli, kritikes.spoudes, pkp-support
Priority: P1    
Version: 2.3.x   
Hardware: PC   
OS: Mac OS X 10.0   
Version Reported In: Also Affects:

Description James MacGregor 2008-12-01 12:15:45 PST
phpMyVisites has been renamed to Piwik (http://piwik.org). The javascript they use has changed slightly, and so if any of our users move from phpMyVisites to Piwik, the plugin's pageTag.tpl javascript will no longer work. 

We will have to allow for those users who will not move to Piwik (at least for the time being). My suggestion would be to copy this plugin and replicate it as a "Piwik" plugin, rather than upgrade/overhaul the phpMyVisites plugin. The other option would be to extend the plugin to work with both via a toggle or somesuch. 

If the former is the better way to go, and since Piwik appears to be currently listed as 'alpha', perhaps the best place for the new plugin would be the plugin gallery. If so, I can take this on.
Comment 1 Alec Smecher 2008-12-01 12:19:56 PST
I would suggest duplicating the plugin (we've been through three renames now with OpenX, and the name mismatch does cause confusion). However, I'd suggest waiting until we're nearer to the next release, as this is a quick task and that way we won't have to maintain both copies.
Comment 2 Michael Felczak 2008-12-02 08:58:57 PST
Piwik is still under heavy development and some users may wish to stay using the latest stable release of phpmyvisites (or never switch). I would suggest a new and separate plugin for this altogether so that users can chose b/w GA, phpmv, or piwik.

I don't think that piwik is a replacement for phpmv in a release sense, so much as the lead developer of phpmv has moved over to the piwik project and development has generally stopped with the latest stable phpmv (2.3) which is still widely used and available.
Comment 3 James MacGregor 2008-12-03 17:56:34 PST
Since it sounds like replicating the plugin sounds like the way to go, and so should be possible for me to do, I don't mind taking this on. I'll post what I come up with to the plugin gallery first (and append a link here when it's up); when we approach a new release date, we can decide whether to include in the code base or not. 
Comment 4 Alec Smecher 2008-12-03 23:57:58 PST
Juan, if Piwik's still under heavy development, it's probably worth waiting until it's stabilized a little more; otherwise we'll probably have to play catch-up later on.
Comment 5 James MacGregor 2008-12-04 09:51:53 PST
Alec, I'll tell Juan that. :) In the meantime, I do think it'll be fine for me to go ahead with this -- from looking at the phpMyVisites plugin, and the Piwik website, the plugin will only need to insert the javascript into all page footers (which Michael's plugin already does). The Piwik package itself is/will be undergoing heavy development, but that shouldn't change the javascript much, nor the  information retrieval method of choice (embedded javascript) at all. 

In any case, I won't be rushing this out -- but it'll probably be a worthy learning project for me. 
Comment 6 Alec Smecher 2008-12-04 10:01:25 PST
James, Juan, whatever -- you techies all look the same to me.
Comment 7 James MacGregor 2008-12-18 10:30:48 PST
Vlilloh beat me to it: 

Piwik Plugin in our plugin gallery: http://pkp.sfu.ca/support/forum/viewtopic.php?f=28&p=14998#p14998

I think it's safe to close this now -- if at a later date we decide to include the Piwik plugin in the core codebase, we can reopen. 
Comment 8 James MacGregor 2011-11-09 21:45:01 PST
Add Piwik plugin to OJS
https://github.com/pkp/ojs/commit/44d529ce20266181f936c762447a68fc73cbfb56
Comment 9 James MacGregor 2011-11-09 21:49:28 PST
Closing -- this includes new locale files, so not committing to stable. Thanks to Vicente, Luiz, and Andrea for contributions to this plugin!