Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

core:archive output is sometimes too verbose eg. "0 visits in last last260 weeks," #8612

Closed
mattab opened this issue Aug 20, 2015 · 3 comments
Closed

core:archive output is sometimes too verbose eg. "0 visits in last last260 weeks," #8612

mattab opened this issue Aug 20, 2015 · 3 comments
Labels
c: Usability For issues that let users achieve a defined goal more effectively or efficiently. wontfix If you can reproduce this issue, please reopen the issue or create a new one describing it.
Milestone
2.15.0

Comments

@mattab
Copy link
Member

mattab commented Aug 20, 2015 •
edited

Our goal is to make Piwik the easiest possible to use and manage. This includes our console commands which should output messages that make sense to everyone.

Recently we've made several improvements to the core:archive command messages in #7723 #7536 #8214 and in this issue we'll make the output a little better.

Currently it looks like this:

INFO CoreConsole[2014-12-15 23:18:29] [9369d] Archived website id = 14, period = week, 0 visits in last last260 weeks, 0 visits this week, Time elapsed: 15.551s
INFO CoreConsole[2014-12-15 23:18:35] [9369d] Archived website id = 14, period = month, 0 visits in last last52 months,

I suggest we simply remove the part visits in last last260 weeks, / 0 visits in last last52 months, as it is not useful, and is confusing to some users.
@mattab mattab added the c: Usability For issues that let users achieve a defined goal more effectively or efficiently. label Aug 20, 2015
@mattab mattab added this to the 2.15.0 milestone Aug 20, 2015
@tsteur
Copy link
Member

tsteur commented Aug 21, 2015

What is the confusing part here or why is it confusing?

@mattab
Copy link
Member Author

mattab commented Aug 21, 2015

Thanks for asking. I remembered this PR was opened: Fixed double last last messages in core:archive #7807 which would solve the problem of double last last.

Besides this small issue, i'm not actually sure what is confusing. I'm asking for more details, will update here next week.

@mattab
Copy link
Member Author

mattab commented Aug 21, 2015

it's not confusing. especially that the core:archive was already improved in 2.13.0 (but this user was using earlier version with less verbose core:archive output). Nothing to do

@mattab mattab closed this as completed Aug 21, 2015
@mattab mattab added the wontfix If you can reproduce this issue, please reopen the issue or create a new one describing it. label Aug 21, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
c: Usability For issues that let users achieve a defined goal more effectively or efficiently. wontfix If you can reproduce this issue, please reopen the issue or create a new one describing it.
Projects
None yet
Milestone
2.15.0
Development

No branches or pull requests
2 participants
@tsteur @mattab