Jump to content
Luis

Release: ProcessPiwikAnalytics

Recommended Posts

Hey Friends of Webanalytics,

I've finished the main work on porting Wanzes GA into a PiwikAnalytics Module.
Just uploaded it to the modules directory. 

It does pretty much the same like GAModule

So take a look at the module post: http://processwire.com/talk/topic/1609-processgoogleanalytics/

You could download the module in the directory or directly from my site: http://misterui.de/site/assets/files/1087/piwikanalytics.zip

Cheerio

  • Like 11

Share this post


Link to post
Share on other sites

yay! this is awesome.

couple of issues:

1.) comming soon (spelling is coming)

2.) is there any way to disable the module from showing any site IDs besides the one you enter? RIght now it shows all of the piwik sites, but i would only want to show the specified site, such as '6' (and not 1 • 2 • 3 • 4 • 5 • etc..)
 

Share this post


Link to post
Share on other sites

Thank you Macrura73,

updated to 1.0.1

fixes:

-typo

-eliminated some warnings

added:

- option in modules configuration to enable multi site tracking (only with multisite tracking enabled the ID list will appear)

git:

- pushed to git :D

https://github.com/Luis85/ProcessPiwikAnalytics

Share this post


Link to post
Share on other sites

Hey Luis - thanks looking awesome!

-marc

Share this post


Link to post
Share on other sites

Thanks for the module. 

I've got a problem with the data fetched from Piwik.

http://d.pr/i/vTlo

My visitors don't stay on the site for 3 days. The value should be (looking on the piwik panel) around 2 minutes. Maybe this bug is caused by the following lines in the .module file:

            case 'avg_time_on_site':
              $visitTime = $this->piwik->getSumVisitsLengthPretty();
              $value = $visitTime['value'];

Share this post


Link to post
Share on other sites

Please Philip,

I know your sites, can't imagine that they don't want to stay this long on your sites ;)

You are right, gonna try to fix this issue today after work. 

  • Like 1

Share this post


Link to post
Share on other sites

pushed a new version. Problem should be fixed

  • Like 1

Share this post


Link to post
Share on other sites

Hi Luis -

wondering if the PW piwik view could take into account child pages, when there are character delimiters in the page title; for example we have a slash in 3 page titles, and in the piwik, it shows those all as children of the text before the slash; in the PW piwik it only shoes the parent, but doesn't open up to show the children...

-marc

Share this post


Link to post
Share on other sites

Hey Marc,

could you please provide a screenshot comparing this behavior on both, piwik dash and PWpiwik.

Thank you in advance 

Share this post


Link to post
Share on other sites

Hi Luis,

thanks - here are the screenshots:

post-136-0-35468400-1370278787_thumb.png

post-136-0-46665400-1370278794_thumb.png

Share this post


Link to post
Share on other sites

Thank you Fenton. :)

@Marc: I´m really sorry for my late response, looks to me like I have to rework the output in the foreach loop to let it look like the Piwik way. 

Maybe you could take a look into the Git Repo, I hardly could find time.

Share this post


Link to post
Share on other sites

Hi Luis,

just realized that under "Demographics", entries for countries & cities are "unknown", although in my piwik dashboard different countries are displayed correctly ...any ideas?

thanks a lot, cheers, j

Share this post


Link to post
Share on other sites

Hi Luis !,

Great work !

This is a great tool, but I want to give access to some users, without give a superuser access.

Are this possible ?

Thanks in advanced.

Share this post


Link to post
Share on other sites

If you add this line at the end of the array in public static function getModuleInfo() { 

'permission' => 'page-view' 

it will give your other users access. You could even give it a new custom permission, like: 

'permission' => 'analytics-view' 

then create that permission and assign it to the role of the users you want to allow access to. Of course these options are hacking the module core code and so hopefully Luis will reply soon with something along these lines. Hope that helps in the meantime.

  • Like 2

Share this post


Link to post
Share on other sites

thank you adrian for providing support. 

I can only apologise, I hardly find time to update or work on my published modules. However, they are on Git, so you easily could fork them or do a commit.

regards

EDIT: The module now needs permission 'analytics-view' 

  • Like 1

Share this post


Link to post
Share on other sites

This is not a question about the module specifically but if you're using Piwik perhaps you'll know something about the problems I ran into today.

I had no luck with Piwik for some reason. It seemed to install okay, I found the info I needed for this module's settings and put the Piwik generated tracking JS on my pages but after visiting a few pages nothing was getting added to the Piwik database so there was nothing to report.

That's when I stumbled upon an issue with Piwik and eAccelerator. In the Piwik admin there's a page for Diagnostics where it says "You are using the PHP accelerator & optimizer eAccelerator which is known to be not compatible with Piwik. We have disabled eAccelerator, which might affect the performance of Piwik. Read the related ticket for more information and how to fix this problem." Really?! In what context?

I'm using PHP5.4 and eAccelerator. The hosting company suggested eAccelerator over APC and eAccelerator's home page says it is compatible with 5.4 but as recently as 5 weeks ago Piwik is saying "eaccelerator is not supported anymore and Piwik is not compatible with it." Haven't found much in the web about this. Any clues?

Share this post


Link to post
Share on other sites

Hi Luis, great module! Thank you much!

I see a small display glitch using PW 2.5 and the standard admin theme. 

The tabs are half overlapping this text string:

Data from Site ID: 1

Also, instead of SideID, which is meaningless to my client, can this instead output the site name for that ID from the PIWIK panel?

Share this post


Link to post
Share on other sites

Hi,

great Modul, thanks!

I installed it on 2.5.3 and cannot set to multisite tracking, after saving it´s disabled again.

Share this post


Link to post
Share on other sites
The tabs are half overlapping this text string:

Data from Site ID: 1

@ceberlin, you can solve this very easy in source: /public_html/site/modules/ProcessPiwikAnalytics/ProcessPiwikAnalytics.css

add this code:

#content .container > form, #content .container > .ui-helper-clearfix > form {
    top: 30px !important;
}
  • Like 1

Share this post


Link to post
Share on other sites

Thank you Guenter55 - much appreciated.

I personally prefer not to alter pw-core or module code myself (which would be overwritten with any next update) but to report this here so it get fixed for everyone, eventually ...one day ...maybe ;-)

Share this post


Link to post
Share on other sites

Is there any chance this gets updated to PW3 and the new PIWIK?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Gadgetto
      SnipWire - Snipcart integration for ProcessWire
      Snipcart is a powerful 3rd party, developer-first HTML/JavaScript shopping cart platform. SnipWire is the missing link between Snipcart and the content management framework ProcessWire.
      With SnipWire, you can quickly turn any ProcessWire site into a Snipcart online shop. The SnipWire plugin helps you to get your store up and running in no time. Detailed knowledge of the Snipcart system is not required.
      SnipWire is free and open source licensed under Mozilla Public License 2.0! A lot of work and effort has gone into development. It would be nice if you could donate an amount to support further development:

      Status update links (inside this thread) for SnipWire development
      2020-07-03 -- SnipWire 0.8.7 (beta) released! Fixes some small bugs and adds an indicator for TEST mode 2020-04-06 -- SnipWire 0.8.6 (beta) released! Adds support for Snipcart subscriptions and also fixes some problems 2020-03-21 -- SnipWire 0.8.5 (beta) released! Improves SnipWires webhooks interface and provides some other fixes and additions 2020-03-03 -- SnipWire 0.8.4 (beta) released! Improves compatibility for Windows based Systems. 2020-03-01 -- SnipWire 0.8.3 (beta) released! The installation and uninstallation process has been heavily revised. 2020-02-08 -- SnipWire 0.8.2 (beta) released! Added a feature to change the cart and catalogue currency by GET, POST or SESSION param 2020-02-03 -- SnipWire 0.8.1 (beta) released! All custom classes moved into their own namespaces. 2020-02-01 -- SnipWire is now available via ProcessWire's module directory! 2020-01-30 -- SnipWire 0.8.0 (beta) first public release! (module just submitted to the PW modules directory) 2020-01-28 -- added Custom Order Fields feature (first SnipWire release version is near!) 2020-01-21 -- Snipcart v3 - when will the new cart system be implemented? 2020-01-19 -- integrated taxes provider finished (+ very flexible shipping taxes handling) 2020-01-14 -- new date range picker, discount editor, order notifiactions, order statuses, and more ... 2019-11-15 -- orders filter, order details, download + resend invoices, refunds 2019-10-18 -- list filters, REST API improvements, new docs platform, and more ... 2019-08-08 -- dashboard interface, currency selector, managing Orders, Customers and Products, Added a WireTabs, refinded caching behavior 2019-06-15 -- taxes provider, shop templates update, multiCURL implementation, and more ... 2019-06-02 -- FieldtypeSnipWireTaxSelector 2019-05-25 -- SnipWire will be free and open source Plugin Key Features
      Fast and simple store setup Full integration of the Snipcart dashboard into the ProcessWire backend (no need to leave the ProcessWire admin area) Browse and manage orders, customers, discounts, abandoned carts, and more Multi currency support Custom order and cart fields Process refunds and send customer notifications from within the ProcessWire backend Process Abandoned Carts + sending messages to customers from within the ProcessWire backend Complete Snipcart webhooks integration (all events are hookable via ProcessWire hooks) Integrated taxes provider (which is more flexible then Snipcart own provider) Useful Links
      SnipWire in PW modules directory SnipWire Docs (please note that the documentation is a work in progress) SnipWire @GitHub (feature requests and suggestions for improvement are welcome - I also accept pull requests) Snipcart Website  

       
      ---- INITIAL POST FROM 2019-05-25 ----
       
    • By Sten
      Hello
      Till now I hacked something with the twig template but it works no more with new PW versions so I look forward to create a module. I am working on a site in multiple languages : French, English, Italian, German, Spanish, Portuguese, Hebrew, Russian. The new posts are entered in any language with a field for language. Till now, I got twig files to get the translations with constants defined for each part of the pages.
      So I'd like to create a module to include theses files added according to the url /fr/en/...
      Have you some observations to do before I begin about the direction to take ?
      Thank you
    • By ukyo
      Mystique Module for ProcessWire CMS/CMF
      Github repo : https://github.com/trk/Mystique
      Mystique module allow you to create dynamic fields and store dynamic fields data on database by using a config file.
      Requirements
      ProcessWire 3.0 or newer PHP 7.0 or newer FieldtypeMystique InputfieldMystique Installation
      Install the module from the modules directory:
      Via Composer:
      composer require trk/mystique Via git clone:
      cd your-processwire-project-folder/ cd site/modules/ git clone https://github.com/trk/Mystique.git Module in live reaction with your Mystique config file
      This mean if you remove a field from your config file, field will be removed from edit screen. As you see on youtube video.
      Using Mystique with your module or use different configs path, autoload need to be true for modules
      Default configs path is site/templates/configs/, and your config file name need to start with Mystique. and need to end with .php extension.
      Adding custom path not supporting anymore !
      // Add your custom path inside your module class`init` function, didn't tested outside public function init() { $path = __DIR__ . DIRECTORY_SEPARATOR . 'configs' . DIRECTORY_SEPARATOR; Mystique::add($path); } Mystique module will search site/modules/**/configs/Mystique.*.php and site/templates/Mystique.*.php paths for Mystique config files.
      All config files need to return a PHP ARRAY like examples.
      Usage almost same with ProcessWire Inputfield Api, only difference is set and showIf usage like on example.
      <?php namespace ProcessWire; /** * Resource : testing-mystique */ return [ 'title' => __('Testing Mystique'), 'fields' => [ 'text_field' => [ 'label' => __('You can use short named types'), 'description' => __('In file showIf working like example'), 'notes' => __('Also you can use $input->set() method'), 'type' => 'text', 'showIf' => [ 'another_text' => "=''" ], 'set' => [ 'showCount' => InputfieldText::showCountChars, 'maxlength' => 255 ], 'attr' => [ 'attr-foo' => 'bar', 'attr-bar' => 'foo' ] ], 'another_text' => [ 'label' => __('Another text field (default type is text)') ] ] ]; Example:
      site/templates/configs/Mystique.seo-fields.php <?php namespace ProcessWire; /** * Resource : seo-fields */ return [ 'title' => __('Seo fields'), 'fields' => [ 'window_title' => [ 'label' => __('Window title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'attr' => [ 'placeholder' => __('Enter a window title') ] ], 'navigation_title' => [ 'label' => __('Navigation title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'showIf' => [ 'window_title' => "!=''" ], 'attr' => [ 'placeholder' => __('Enter a navigation title') ] ], 'description' => [ 'label' => __('Description for search engines'), 'type' => Mystique::TEXTAREA, 'useLanguages' => true ], 'page_tpye' => [ 'label' => __('Type'), 'type' => Mystique::SELECT, 'options' => [ 'basic' => __('Basic page'), 'gallery' => __('Gallery'), 'blog' => __('Blog') ] ], 'show_on_nav' => [ 'label' => __('Display this page on navigation'), 'type' => Mystique::CHECKBOX ] ] ]; Searching data on Mystique field is limited. Because, Mystique saving data to database in json format. When you make search for Mystique field, operator not important. Operator will be changed with %= operator.
      Search example
      $navigationPages = pages()->find('my_mystique_field.show_on_nav=1'); $navigationPages = pages()->find('my_mystique_field.page_tpye=gallery');
    • By Robin S
      This is a module I made as an experiment a while ago and never got around to releasing publicly. At the time it was prompted by discussions around using Repeater fields for "page builder" purposes, where the depth feature could possibly be used for elements that would be nested inside other elements. I thought it would be useful to enforce some depth rules and translate the depth data into a multi-dimensional array structure.
      I'm not using this module anywhere myself but maybe it's useful to somebody.
      Repeater Depth Helper
      This module does two things relating to Repeater fields that have the "Item depth" option enabled:
      It enforces some depth rules for Repeater fields on save. Those rules are:
      The first item must have a depth of zero. Each item depth must not be more than one greater than previous item depth. It provides a RepeaterPageArray::getDepthStructure helper method that returns a nested depth structure for a Repeater field value.
      Helper method
      The module adds a RepeaterPageArray::getDepthStructure method that returns a multi-dimensional array where the key is the page ID and the value is an array of nested "child" items, or null if there are no nested children.
      Example

      The module doesn't make any assumptions about how you might want to use the depth structure array, but here is a way you might use it to output a nested unordered list.
      // Output a nested unordered list from a depth structure array function outputNestedList($depth_structure, $repeater_items) { $out = "<ul>"; foreach($depth_structure as $page_id => $nested_children) { $out .= "<li>" . $repeater_items->get("id=$page_id")->title; // Go recursive if there are nested children if(is_array($nested_children)) $out .= outputNestedList($nested_children, $repeater_items); $out .= "</li>"; } $out .= "</ul>"; return $out; } $repeater_items = $page->my_repeater; $depth_structure = $repeater_items->getDepthStructure(); echo outputNestedList($depth_structure, $repeater_items);
       
      https://github.com/Toutouwai/RepeaterDepthHelper
      https://modules.processwire.com/modules/repeater-depth-helper/
    • By MoritzLost
      Cacheable Placeholders
      This module allows you to have pieces of dynamic content inside cached output. This aims to solve the common problem of having a mostly cacheable site, but with pieces of dynamic output here and there.  Consider this simple example, where you want to output a custom greeting to the current user:
      <h1>Good morning, <?= ucfirst($user->name) ?></h1> This snippet means you can't use the template cache (at least for logged-in users), because each user has a different name. Even if 99% of your output is static, you can only cache the pieces that you know won't include this personal greeting. A more common example would be CSRF tokens for HTML forms - those need to be unique by definition, so you can't cache the form wholesale.
      This module solves this problem by introducing cacheable placeholders - small placeholder tokens that get replaced during every request. The replacement is done inside a Page::render hook so it runs during every request, even if the response is served from the template cache. So you can use something like this:
      <h1>Good morning, {{{greeting}}}</h1> Replacement tokens are defined with a callback function that produces the appropriate output and added to the module through a simple hook:
      // site/ready.php wire()->addHookAfter('CachePlaceholders::getTokens', function (HookEvent $e) { $tokens = $e->return; $tokens['greeting'] = [ 'callback' => function (array $tokenData) { return ucfirst(wire('user')->name); } ]; $e->return = $tokens; }); Tokens can also include parameters that are parsed and passed to the callback function. There are more fully annotated examples and step-by-step instructions in the README on Github!
      Features
      A simple and fast token parser that calls the appropriate callback and runs automatically. Tokens may include multiple named or positional parameters, as well as multi-value parameters. A manual mode that allows you to replace tokens in custom pieces of cached content (useful if you're using the $cache API). Some built-in tokens for common use-cases: CSRF-Tokens, replacing values from superglobals and producing random hexadecimal strings. The token format is completely customizable, all delimiters can be changed to avoid collisions with existing tag parsers or template languages. Links
      Github Repository & documentation Module directory If you are interested in learning more, the README is very extensive, with more usage examples, code samples and usage instructions!
×
×
  • Create New...