Piwik 0.6-rc1 is available for download as a public release. Please try it out on your test server and let us know, in this thread, if you have any issue. If not, this will be released as Piwik 0.6 stable at the end of April.
Known bugs
the Visits per server time report doesn’t show dates in the website specified timezones, but in UTC
the tooltip in the Goal report page doesn’t display conversion counts
How to beta test Piwik?
The easiest way is to install a new Piwik, on a fresh DB, and add the code to your website (next to your existing Piwik JS tracking code).
If you want to test your existing Piwik install upgraded to 0.6-rc1, we recommend the following method:
copy your current Piwik database in a test database that you will use with 0.6-rc1
download Piwik 0.6-rc1 and unzip in your server in test_piwik/ - do NOT overwrite your current production Piwik.
copy your config/config.ini.php from your running stable Piwik 0.5.5 (or other) and copy it in your test_piwik/config/
VERY IMPORTANT: modify test_piwik/config/config.ini.php and replace your stable DB name with your copy test DB. This ensures that the upgrade is only executed in the test DB.
go to your website/test_piwik/ and run the upgrade. This might take a long time as there are large DB schema upgrades.
get the JS code from the test_piwik install and copy paste it in your website footer, just after your original Piwik JS tracking code. Visits will be tracked in both Piwik at the same time.
Report bugs
Please write bugs that you may find in this forum thread. We will read it often and ensure we follow up and fix issues. Thank you for your help!
As further clarification to beta testers, the instructions above would be to set-up a second Piwik installation, and run it in parallel to an existing installation.
And if you don’t already have Piwik installed, you can still try out the release candidate. All feedback is welcome.
0.6RC1 works fine for me! Congrats for this good work!
Settings -> Websites -> Global Website Settings -> Global list of Excluded IPs:
My IP is already shown (“Your current IP address is 217.235.222.xx”). Why not making it an option to insert the respective IP automatically? Tomorrow I’ll have another IP for sure…
BTW: Excluding my IP works perfectly! Waiting for this feature for sooo long!
Settings -> Users -> Add a new user -> New users access: Admin -> Logout
Login with new user account for the first time: Settings page is shown with “User settings”, “Users” and “Websites” tabs.
Clicking on “Websites” forces Superuser login.
Why doesn’t an admin user have access to websites settings? And if not, why show him the tab?
Cron job works now! I’m just trying it with few tens of visits, but it makes his job.
But I don’t understand : why configure “Reports for today will be processed at most every…” so that we have already created a crontab?
When changing time zone and currency of an existing website or adding another website you have to press the little green check mark on the outer right of the respective row. style_emoticons/<#EMO_DIR#>/blink.gif
Just clicking [Enter] doesn’t work because this only sends the POST-command of the pages [save]-button. And this one only seems to be responsible for global websites settings (lower part of the settings page). style_emoticons/<#EMO_DIR#>/angry.gif
It’s not very intuitive, but it works the intricate way.
Maybe you can make it a whole page save button sometime?
First of all nice work on Piwik, I really hope this project grows and gains momentum and support. I will give myself a month to familiarise myself with the operations and then find a way where I can contribute back a little.
Now on to my first question, I read an exception to Timezones in your post above. Now I’m a little confused in how this is working, I have a server in Melbourne Australia which is +10hrs EST zone. The server time matches here, however when I put “Melbourne” in the city when installing it now is showing the current hour as the 15th hour when it should be the 1st hour.
Any help with this is appreciated, i’m not sure if by your opening post you meant this is an outstanding bug or something else.
