@mgazdzik opened this issue on September 26th 2014

Currently Piwik allows to track not only Websites, but also mobile apps, etc. In future it would be great to have possiblity to remove 'Website' word from i.e. generated files for scheduled reports, beacuse processed reports don't always concern website. Possibly there could be new field in Website definition, where we can pick from dictionary or enter own value, so single idsite has type "mobile application" and this string is being inserted in reporting. That way single Piwik can track multiple type of entities and report titles would be meaningful.

@tsteur commented on September 26th 2014

I think this is covered by #4734

We talked about this a few times and were thinking about similar approach. Probably it is not only done by renaming "Website" (but would be good first step) but also depending on the type rename some reports, disable and activate some reports that make sense for a specific type etc. For instance you would not have "Pages" in a mobile app but maybe "Screens" etc. Some reports don't make sense for mobile apps but maybe some other new reports.

Shall we leave this one open or is it covered by the other ticket? It is scheduled for short term by the way

@mgazdzik commented on September 26th 2014

In that case maybe this ticket may remain open and marked with easy pick just for sake of 'meningful names' in reports ? #4734 scope is a bit bigger and involves this ticket, but maybe this could be done by community earlier and provide starting point ?

@tsteur commented on September 26th 2014

sure

@mattab commented on September 26th 2014

I definitely like this first step of removing "Websites" in the reports and hopefully we also find some other places where Websites is used but could be removed instead (a bit of Zen too - #4987).

@mattab commented on October 7th 2014

@mgazdzik Website is still used in several places (see list here) but if you find it in scheduled report or other place that it can be easily removed, let me know!

@mgazdzik commented on October 7th 2014

@mattab - great, thanks a lot for this fix :)

This issue was closed on October 7th 2014
Powered by GitHub Issue Mirror