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.

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

Better naming for "Continue to Piwik" #12336

Closed
wants to merge 2 commits into from
Closed

Better naming for "Continue to Piwik" #12336

wants to merge 2 commits into from

Conversation

zbrag
Copy link

@zbrag zbrag commented Dec 6, 2017

Better naming for "Continue to Piwik" in Database upgrade screen (#9108) as suggested by @mattab

zbrag and others added 2 commits December 6, 2017 13:32
Better naming for "Continue to Piwik" in Database upgrade screen (#9108)
Copy link
Member

@sgiehl sgiehl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Our test result images are stored on Git LFS. Your changes would change that for the updated images.

@@ -106,7 +106,7 @@
"ComputedMetricCountWithValueDocumentation": "The number of entries that have a value set for %s",
"ConfigFileIsNotWritable": "The Piwik configuration file %1$s is not writable, some of your changes might not be saved. %2$s Please change permissions of the config file to make it writable.",
"Continue": "Continue",
"ContinueToPiwik": "Continue to Piwik",
"ContinueToPiwik": "Upgrade and continue to Piwik",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This translation text is also used in Installation. Imho it wouldn't make sense to show "upgrade and continue" there. Maybe we would need to introduce a new translation text.

@zbrag
Copy link
Author

zbrag commented Dec 10, 2017

I was not aware of the lfs option, I will make the suggested changes, thank you

@mattab mattab added this to the 3.4.0 milestone Jan 10, 2018
@zbrag zbrag closed this Mar 10, 2018
@zbrag zbrag deleted the patch-1 branch March 10, 2018 12:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants