WordPress.org

1. megamule
   Member
   Posted 4 months ago #

   ... effectively rendering it useless for tracking.

   - even if one happens to encounter the solution on how to reconfigure a network install since 0.9.0 outlined here:

   http://wordpress.org/support/topic/plugin-wp-piwik-network-activate-doesnt-work-w-09?replies=10

   The result:
   <!-- WP-Piwik ERROR: Tracking code not availbale -->

   Even if the non-mapped domain is configured in Piwik, it will still fail with the above error in the source code.

   One should never declare a flawlessly working piece of software "EXPERIMENTAL" in the course of an update.

   That should've been done in it's own plugin and tagged EXPERIMENTAL from the very beginning.

   http://wordpress.org/extend/plugins/wp-piwik/

2. braekling
   Member
   Posted 4 months ago #

   I'm sorry, but WP-Piwik's network support was declared EXPERIMENTAL all the time. There never was a network enabled WP-Piwik (WPMU-Piwik/multisite) release declared as "not experimental" or even "flawlessly". In fact each WP-Piwik description tells you to "test it on your own (e.g. using a local copy of your WP multisite) before you use it in an user context" if you use network mode. Furthermore WP-Piwik itself tells you after each update to check your settings.

   If you are working with experimental software, you should be prepared to make sure its serviceability on your own regularly. But I'll be happy about each detailed error description to improve this plugin, of course.

   Did your check your settings? Is the shown JavaScript code at your WP-Piwik settings page your primary blog's code? The given information doesn't suffice to help you.

   You can find a test script to check Piwik's answers on WP-Piwik's requests: http://peepbo.de/source/piwik-test.php.txt Maybe this will help to get some answers.

3. megamule
   Member
   Posted 4 months ago #

   Sorry for being misleading. I had noticed that it was tagged 'experimental for multisite' for a longer period already.

   However, 'multisite support' breaks down to using the correct functions for e.g. accessing the database. If a developer does this, then the plugin _will_ simply work in a multisite environment. You had done that correctly.

   It's only about a good coding style. A multisite user who knows that will accept what you say about the state of the "normal" plugin as the state of your multisite support too --- there is basically no difference.

   Now with 0.9.0 you changed the whole approach and, in essence, _removed_ true multisite support, _replacing_ it with a central-managed configuration.

   Note that I like this new approach, as it fits _my_ use case well. Still, people who like to use different Piwik installations for tracking different blogs (of the same network) will loose that option in 0.9.0.

   That's why I consider it a change that's simply too big for just calling it an 'update'.
   As the whole approach changed it's rather a new plugin. Maybe it'd be good to offer the new way as an option instead.

   Sorry for being harsh & thanks for developing the plugin in the first place!

4. braekling
   Member
   Posted 4 months ago #

   Alright, I think I got it. :) There seems to be a misunderstanding. ;)

   Old WP-Piwik versions provided these ways to use them:

   1. Use it as a simple plugin just regarding to one blog - OR - use it as a network plugin: global activated but individual configured.

   2. Enable multisite mode by changing a boolean in the plugin's source code and use it as "network activated". Now WP-Piwik was running with a central-managed configuration, called WPMU-Piwik.

   These old structure based on old WordPress versions with earlier multisite handling ("WordPress MU"). Because changing the boolean each time the plugin was updated was annoying to everyone using "WPMU-Piwik", I decided to use the new options WordPress provides:

   1. You can enable your plugin as a simple plugin in a single blog. Nothing changed.

   2. You can add the plugin to your WordPress multisite, activate it on each blog and configure it individually. (Similar to use it as a network plugin without changing the boolean before... just the respective activation comesalong.)

   3. You can add the plugin to your WordPress mutlisite, activate it as a "network plugin" and use it with a central-managed configuration. (Like using it as a network plugin before with changing the boolean: "WPMU-Piwik".)

   Of course I realized I have to explain this much better - and I will do so to avoid misunderstandings.

   Please give me some more details about your mapped domain configuration because I like to replicate and fix this issue.

   Best regards,
   André

5. marsev
   Member
   Posted 4 months ago #

   Hi Braekling,

   I really like your "2 way approach": WP-Piwik and WPMU-Piwik. I'm fine with the central management because that is what I was looking for. The new version works perfect, no problems on my site.

   But taking the critics serious, perhaps it would be better to rethink the "network activate" thing. WP multisite comes with a folder "mu-plugins". Perhaps this would be the better place for activating WPMU-Piwik with central management. At least other plugins are doing it that way. Unfortunately you loose the possibility to auto-update plugins located there.

   Best redards

6. braekling
   Member
   Posted 3 months ago #

   Hi all.

   Does the mapped domain issue still exist in 0.9.0?

   @marsev: Hopefully the new description and the bugfix regarding the simple plugin usage will solve the misunderstanding about different configuration options. I want to support everybody's favorite method if possible ;-)

Reply

You must log in to post.