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
Plugins define translations they need as a hook: Remove _js hack! #4151
Labels
Milestone
Comments
Beautiful change guys... |
sabl0r
pushed a commit
to sabl0r/piwik
that referenced
this issue
Sep 23, 2014
… and automatically generate translation JS for all plugins. Translation JS is now treated as an asset and is included in merged JS. Note: - Includes tweaks to capture.js: on webpage error stop capture program.
sabl0r
pushed a commit
to sabl0r/piwik
that referenced
this issue
Sep 23, 2014
… and add event so plugins can specify which strings should be available client-side.
sabl0r
pushed a commit
to sabl0r/piwik
that referenced
this issue
Sep 23, 2014
… when merged assets is disabled.
sabl0r
pushed a commit
to sabl0r/piwik
that referenced
this issue
Sep 23, 2014
sabl0r
pushed a commit
to sabl0r/piwik
that referenced
this issue
Sep 23, 2014
sabl0r
pushed a commit
to sabl0r/piwik
that referenced
this issue
Sep 23, 2014
sabl0r
pushed a commit
to sabl0r/piwik
that referenced
this issue
Sep 23, 2014
sabl0r
pushed a commit
to sabl0r/piwik
that referenced
this issue
Sep 23, 2014
sabl0r
pushed a commit
to sabl0r/piwik
that referenced
this issue
Sep 23, 2014
sabl0r
pushed a commit
to sabl0r/piwik
that referenced
this issue
Sep 23, 2014
sabl0r
pushed a commit
to sabl0r/piwik
that referenced
this issue
Sep 23, 2014
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Use an event that plugins can use to determine which translations should be available in JavaScript and load them all automatically.
The text was updated successfully, but these errors were encountered: