… 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:
<!– 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.
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.
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.
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!
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.
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.
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 😉
@braekling: Yes, the mapped domain issue still exists (in 0.9.5).
How can one configure 0.9.5 individually on a per-blog basis, as you pointed out:
2. You can add the plugin to your WordPress multisite, activate it on each blog and configure it individually.
I’ve tried to figure out how, but unlike any other plugin, WP-Piwik is missing in the “Plugins” section of the individual blogs.
From the install notes:
Just add WP-Piwik to your /wp-content/plugins folder and enable the Plugins page for individual site administrators.
What does “enable the Plugins page for individual site administrators” mean?
See WordPress network documentation:
Site Specific Plugins: WordPress Plugins to be activated or deactivated by an individual site admin are stored in the plugins directory. You need to enable the Plugins page for individual site administrators from the Network Admin’s Settings -> Network Settings menu. Specific site administrators can then toggle optional plugin activation.
Okay that seems different than the usual approach then. Normally I enable a plugin “network wide” which then allows admins site-specific configuration of the plugins functionality.
I just re-read marsevs recent post and realised that we’re talking about the same thing:
The way WP-Piwik currently uses the “network activate” feature is different from how any other plugin uses that feature.
The mu-plugins dir would _definitely_ be the correct place to store the centrally managed variant.
If WP-Piwik would follow that concept like other plugins do, the need to grant all site-admins plugin management rights would be avoided.
@braekling would it be an option for you to go the mu-plugins path with WP-Piwik?
- The topic ‘[Plugin: WP-Piwik] The new style WPMU variant disrespects mapped domains’ is closed to new replies.