Profiling dashboard: Add translations (#6879)
This commit is contained in:
Jan Skovgaard
committed by
Sebastiaan Janssen
Sebastiaan Janssen
parent
0b16c48fc3
commit
c8ec7ce8ba
@@ -6,39 +6,51 @@
|
||||
|
||||
<umb-box ng-hide="vm.loading">
|
||||
<umb-box-content>
|
||||
<h3 class="bold">Performance profiling</h3>
|
||||
<h3 class="bold">
|
||||
<localize key="profiling_performanceProfiling">Performance profiling</localize>
|
||||
</h3>
|
||||
<div ng-show="vm.profilerEnabled">
|
||||
<div class="mb4">
|
||||
<p>
|
||||
Umbraco currently runs in debug mode. This means you can use the built-in performance profiler to assess the performance when rendering pages.
|
||||
</p>
|
||||
<p>
|
||||
If you want to activate the profiler for a specific page rendering, simply add <b>umbDebug=true</b> to the querystring when requesting the page.
|
||||
</p>
|
||||
<p>
|
||||
If you want the profiler to be activated by default for all page renderings, you can use the toggle below.
|
||||
It will set a cookie in your browser, which then activates the profiler automatically.
|
||||
In other words, the profiler will only be active by default in <i>your</i> browser - not everyone else's.
|
||||
</p>
|
||||
<localize key="profiling_performanceProfilingDescription">
|
||||
<p>
|
||||
Umbraco currently runs in debug mode. This means you can use the built-in performance profiler to assess the performance when rendering pages.
|
||||
</p>
|
||||
<p>
|
||||
If you want to activate the profiler for a specific page rendering, simply add <b>umbDebug=true</b> to the querystring when requesting the page.
|
||||
</p>
|
||||
<p>
|
||||
If you want the profiler to be activated by default for all page renderings, you can use the toggle below.
|
||||
It will set a cookie in your browser, which then activates the profiler automatically.
|
||||
In other words, the profiler will only be active by default in <i>your</i> browser - not everyone else's.
|
||||
</p>
|
||||
</localize>
|
||||
</div>
|
||||
<div class="mb4">
|
||||
<div class="flex items-center">
|
||||
<umb-toggle checked="vm.alwaysOn" id="profilerAlwaysOn" on-click="vm.toggle()"></umb-toggle>
|
||||
<label for="profilerAlwaysOn" class="mb0 ml2">Activate the profiler by default</label>
|
||||
<label for="profilerAlwaysOn" class="mb0 ml2">
|
||||
<localize key="profiling_activateByDefault">Activate the profiler by default</localize>
|
||||
</label>
|
||||
</div>
|
||||
</div>
|
||||
<h4>Friendly reminder</h4>
|
||||
<p>
|
||||
You should never let a production site run in debug mode. Debug mode is turned off by setting <b>debug="false"</b> on the <b><compilation /></b> element in web.config.
|
||||
</p>
|
||||
<h4>
|
||||
<localize key="profiling_reminder">Friendly reminder</localize>
|
||||
</h4>
|
||||
<localize key="profiling_reminderDescription">
|
||||
<p>
|
||||
You should never let a production site run in debug mode. Debug mode is turned off by setting <b>debug="false"</b> on the <b><compilation /></b> element in web.config.
|
||||
</p>
|
||||
</localize>
|
||||
</div>
|
||||
<div ng-hide="vm.profilerEnabled">
|
||||
<p>
|
||||
Umbraco currently does not run in debug mode, so you can't use the built-in profiler. This is how it should be for a production site.
|
||||
</p>
|
||||
<p>
|
||||
Debug mode is turned on by setting <b>debug="true"</b> on the <b><compilation /></b> element in web.config.
|
||||
</p>
|
||||
<localize key="profiling_profilerEnabledDescription">
|
||||
<p>
|
||||
Umbraco currently does not run in debug mode, so you can't use the built-in profiler. This is how it should be for a production site.
|
||||
</p>
|
||||
<p>
|
||||
Debug mode is turned on by setting <b>debug="true"</b> on the <b><compilation /></b> element in web.config.
|
||||
</p>
|
||||
</localize>
|
||||
</div>
|
||||
</umb-box-content>
|
||||
</umb-box>
|
||||
|
||||
@@ -2257,4 +2257,41 @@ To manage your website, simply open the Umbraco back office and start adding con
|
||||
<key alias="publishedCacheStatus">Published Cache Status</key>
|
||||
<key alias="caches">Caches</key>
|
||||
</area>
|
||||
<area alias="profiling">
|
||||
<key alias="performanceProfiling">Performance profiling</key>
|
||||
<key alias="performanceProfilingDescription">
|
||||
<![CDATA[
|
||||
<p>
|
||||
Umbraco currently runs in debug mode. This means you can use the built-in performance profiler to assess the performance when rendering pages.
|
||||
</p>
|
||||
<p>
|
||||
If you want to activate the profiler for a specific page rendering, simply add <b>umbDebug=true</b> to the querystring when requesting the page.
|
||||
</p>
|
||||
<p>
|
||||
If you want the profiler to be activated by default for all page renderings, you can use the toggle below.
|
||||
It will set a cookie in your browser, which then activates the profiler automatically.
|
||||
In other words, the profiler will only be active by default in <i>your</i> browser - not everyone else's.
|
||||
</p>
|
||||
]]>
|
||||
</key>
|
||||
<key alias="activateByDefault">Activate the profiler by default</key>
|
||||
<key alias="reminder">Friendly reminder</key>
|
||||
<key alias="reminderDescription">
|
||||
<![CDATA[
|
||||
<p>
|
||||
You should never let a production site run in debug mode. Debug mode is turned off by setting <b>debug="false"</b> on the <b><compilation /></b> element in web.config.
|
||||
</p>
|
||||
]]>
|
||||
</key>
|
||||
<key alias="profilerEnabledDescription">
|
||||
<![CDATA[
|
||||
<p>
|
||||
Umbraco currently does not run in debug mode, so you can't use the built-in profiler. This is how it should be for a production site.
|
||||
</p>
|
||||
<p>
|
||||
Debug mode is turned on by setting <b>debug="true"</b> on the <b><compilation /></b> element in web.config.
|
||||
</p>
|
||||
]]>
|
||||
</key>
|
||||
</area>
|
||||
</language>
|
||||
|
||||
@@ -2273,4 +2273,41 @@ To manage your website, simply open the Umbraco back office and start adding con
|
||||
<key alias="publishedCacheStatus">Published Cache Status</key>
|
||||
<key alias="caches">Caches</key>
|
||||
</area>
|
||||
<area alias="profiling">
|
||||
<key alias="performanceProfiling">Performance profiling</key>
|
||||
<key alias="performanceProfilingDescription">
|
||||
<![CDATA[
|
||||
<p>
|
||||
Umbraco currently runs in debug mode. This means you can use the built-in performance profiler to assess the performance when rendering pages.
|
||||
</p>
|
||||
<p>
|
||||
If you want to activate the profiler for a specific page rendering, simply add <b>umbDebug=true</b> to the querystring when requesting the page.
|
||||
</p>
|
||||
<p>
|
||||
If you want the profiler to be activated by default for all page renderings, you can use the toggle below.
|
||||
It will set a cookie in your browser, which then activates the profiler automatically.
|
||||
In other words, the profiler will only be active by default in <i>your</i> browser - not everyone else's.
|
||||
</p>
|
||||
]]>
|
||||
</key>
|
||||
<key alias="activateByDefault">Activate the profiler by default</key>
|
||||
<key alias="reminder">Friendly reminder</key>
|
||||
<key alias="reminderDescription">
|
||||
<![CDATA[
|
||||
<p>
|
||||
You should never let a production site run in debug mode. Debug mode is turned off by setting <b>debug="false"</b> on the <b><compilation /></b> element in web.config.
|
||||
</p>
|
||||
]]>
|
||||
</key>
|
||||
<key alias="profilerEnabledDescription">
|
||||
<![CDATA[
|
||||
<p>
|
||||
Umbraco currently does not run in debug mode, so you can't use the built-in profiler. This is how it should be for a production site.
|
||||
</p>
|
||||
<p>
|
||||
Debug mode is turned on by setting <b>debug="true"</b> on the <b><compilation /></b> element in web.config.
|
||||
</p>
|
||||
]]>
|
||||
</key>
|
||||
</area>
|
||||
</language>
|
||||
|
||||
Reference in New Issue
Block a user