Debug parsetime equals 0
If not logged in in the backend, the parsetime
is shown as 0 in the HTML source code.
HTML Source: <!-- Parsetime: 0 ms-->
(issue imported from #M12277)
#3 Updated by Thomas Deinhamer almost 10 years ago
I think it would be okay to only enable the timetracker,
if you're logged in to the backend and have admin-rights.
But then this should be clearly stated in the source somehow,
or nothing should get displayed at all.
Generally this throws up the idea of a debug-mode which
gets enabled by setting a GET variable, when logged in to
the backend; maybe a secret phrase. (Just an idea.)
#4 Updated by Christian Kuhn almost 10 years ago
The parsetime is only added as a comment after the </html> if $TYPO3_CONF_VARS['FE']['debug'] = '1'; is set. So we don't need another special GET var or something.
I propose to reanimate getMilliseconds() somehow to make this work again without BE login.
#5 Updated by Christian Kuhn almost 10 years ago
Attached a simple patch which ads implementation of getMilliseconds() to timetracknull, but this solution is not very nice.
If getMilliseconds() in t3lib_timetrack is made static it would have these disadvantages:
- Breaks backwards compatibility
- another class need to be loaded in FE
Maybe it would be better to add a new static class for time handling and calculation and deprecate those methods in the timetrack classes. t3lib_div has some more related methods: convertmicrotime(), milliseconds()
#8 Updated by Andy Weber over 8 years ago
Here's a good reason:
When you are logged into the TYPO3 backend, you'll getting much higher parsing times rendering a frontend site, compared to the same site, when you are not logged in. (no admin-panel, etc. active...)
I tried that with different benchmark tools.
Is there are reason why? Can someone reproduce that?