Bug #18625
Warning for permanently enabled Install Tool won't be seen if user has chosen a module to open on start-up
| Status: | Closed | Start date: | 2008-04-16 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - | |||
| TYPO3 Version: | 4.2 | Complexity: | medium | |
| PHP Version: | 5.2 | |||
| Votes: | 0 |
Description
If there is a warning (Install-Tool is active, standard-password is still in use, admin has standard-username and password) this won't be recognized, because of the chosen module opening immediatelly.
To enhance security, the chosen module should only be shown, if there is no warning displayed. Otherwise the modules-module should be shown.
(issue imported from #M8134)
Related issues
| related to Core - Feature #24009: System health status self monitoring | Resolved | 2010-11-10 | ||
| related to Core - Feature #24011: Overwrite the "start in module" setting of admin users wh... | Accepted | 2010-11-10 | ||
| related to Core - Bug #21092: Add checks from t3lib_BEfunc::displayWarningMessages() to... | Closed | 2009-09-18 | ||
| related to Core - Bug #20970: Add a reports module | Closed | 2009-09-01 | ||
| related to Core - Bug #22659: Warn when KEEP_FILE is set | Closed | 2010-05-16 |
History
Updated by Lars Houmark about 5 years ago
I second that!
+1
Updated by Chris topher over 4 years ago
Also see the thread under:
http://lists.typo3.org/pipermail/typo3-team-hci/2009-January/002618.html
Updated by Ingo Renner over 3 years ago
I agree, the system must be able to force admins to check the system status if something is wrong
Updated by Xavier Perseguers almost 2 years ago
- Target version changed from 4.6.0-beta1 to 4.6.0-beta2
Updated by Thorsten Kahler almost 2 years ago
- Status changed from New to Accepted
- Complexity set to medium
Possible solutions:
- forced flash messages - is this possible?
- send a "health status" along with the repsonse of the Ajax login check if BE user is an admin
Other ideas?
Updated by Ingo Renner almost 2 years ago
... force redirect the user to the status report would be another idea
Updated by Xavier Perseguers over 1 year ago
- Target version changed from 4.6.0-beta2 to 4.6.0-beta3
Updated by Oliver Hader over 1 year ago
- Target version changed from 4.6.0-beta3 to 4.6.0-RC1
Updated by Xavier Perseguers over 1 year ago
- Target version changed from 4.6.0-RC1 to 4.6.0
Updated by Chris topher over 1 year ago
- Target version changed from 4.6.0 to 4.6.1
Updated by Chris topher over 1 year ago
- Target version changed from 4.6.1 to 4.6.2
Updated by Xavier Perseguers over 1 year ago
- Target version deleted (
4.6.2)
Updated by Gerrit Code Review 9 months ago
- Status changed from Accepted to Under Review
Patch set 1 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/14022
Updated by Chris topher 9 months ago
- Status changed from Under Review to Closed
http://review.typo3.org/14022 is not related to this issue (18625), but to Mantis(!) 18625.