[TYPO3-core] FYI24: #16337: [reports] System health status self monitoring

[Ingo Renner]

Hi there,

long time no see, but I'm doing great and the Mexican sun does work well 
for relaxation ;)

this is a SVN patch request.

Type: Feature

Branch: trunk only

BT reference: http://bugs.typo3.org/view.php?id=16337

Problem / Solution:
In an attempt to bring self-monitoring to TYPO3 this is the first step 
to achieve this.
When opening the status report the highest severity of all status checks 
is determined and stored in TYPO3's registry.

When an admin logs in the registry is checked and if a severity higher 
than OK is found the warning box is enabled reporting that issues have 
been found, linking to the status report for more details. System issues 
previously listed in the warning box, such as checking for joh316 as the 
install tool password, are removed as they're covered by the system 
report now.

By clicking the link the system report is shown and the highest severity 
is recorded again. Now the user has seen what issues have been found and 
will go to fix them. Once fixed, he comes back to confirm the fix with 
the status report, again recording the highest severity.

Once all issues are fixed the recorded highest severity is equal or 
below (OK) the threshold triggering the warning box, making it disappear.


Notes:
I will commit this to the reports module after a grace period of 24h. I 
just would like to see your opinion, especially since the warning box is 
a part outside of the reports module...

As you can see from the bugtracker issue, a couple more changes will be 
coming to make this feature complete.


all the best
Ingo

-- 
Ingo Renner
TYPO3 Core Developer, Release Manager TYPO3 4.2

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 16337.diff
Type: text/x-diff
Size: 7703 bytes
Desc: not available
URL: <http://lists.typo3.org/pipermail/typo3-team-core/attachments/20101110/85183049/attachment.diff>