Secondly, as I said in my post, even if you want to force certain feature, it should be done behind the scenes, without leaving user guessing. Same reason why, according to good interface design, it shouldn’t matter to software how user enters, say, phone number: as #######, ###-####, or ### ## ## — software should recognize and strip unnecessary charachters, and then output it in one particular and consistent format regardless of user input.

Thirdly, I don’t think enforcing a protocol is such a good idea. User might have Piwik installed at the http:// website, but access it from, as you’ve said, https:// website or whatnot.

I will document it more clearly and perhaps even accommodate for the http:// being there (force protocol to be http://).

Maybe explicitly put http:// right in front of the hostname form field, or let user choose protocol of installation (dropdown or tick box).

The bug, as you call it, is actually by design. The form is called ‘hostname’, not ‘protocol + hostname’.

The design is: use the same protocol as the page the tracking code is on. So https:// pages are directing to the https:// Piwik installation. This is done to avoid mixed secure and non-secure content on the same page.

I understand the confusion, I will document it more clearly and perhaps even accomodate for the http:// being there (force protocol to be http://).

Regards, Jules (the plug-in author).

I’m able to run other two probably because I’ve upgraded the memory some time ago (good way to spend $25) up to 512 MB. And I’m going to switch entirely to Ubuntu after more testing, because of streamlined and familiar interface and network browsing.

And the gfaphics seems slow somhow like when moving windows and stuff. Do you know why?