Markus Klein
- Login: liayn
- Email: markus.klein@typo3.org
- Registered on: 2010-01-18
- Last sign in: 2024-10-16
Issues
open | closed | Total | |
---|---|---|---|
Assigned issues | 1 | 580 | 581 |
Reported issues | 16 | 640 | 656 |
Projects
Project | Roles | Registered on |
---|---|---|
TYPO3 Core | Contributor | 2013-05-05 |
Activity
2024-12-05
- 16:46 TYPO3 Core Feature #90323: Make it possible to turn off sys_log logging entirely?
- I'm not sure if I remember correctly, but I think I saw some implementation, presented some-when in 2024, where the b...
- 13:32 TYPO3 Core Bug #34383: Incorrect redirect with multiple user groups
- Benni Mack wrote in #note-16:
> Markus Klein wrote in #note-15:
> > Generally: The groups are rather "static data"....
2024-11-27
- 20:04 TYPO3 Core Bug #105713: Site sets setup.typoscript not loaded on Windows 10
- Wanna push your change to the review system?
- 16:21 TYPO3 Core Bug #105135 (Accepted): TypoScript object path "tt_content..20" does not exist
2024-11-22
- 12:20 TYPO3 Core Bug #105194 (Resolved): Lots of log entries for invalid http requests
- Applied in changeset commit:4148f82e9e800f725746f43774f57592e802a1fa.
- 10:00 TYPO3 Core Bug #105194 (Resolved): Lots of log entries for invalid http requests
- Applied in changeset commit:d21846771aa9c8286b5de2e17c4b76637142a2fa.
- 12:20 TYPO3 Core Bug #103129 (Resolved): Modified "Host" header with invalid port leads to exception when creating the ServerRequestFactory->fromGlobals
- Applied in changeset commit:4148f82e9e800f725746f43774f57592e802a1fa.
- 10:00 TYPO3 Core Bug #103129 (Resolved): Modified "Host" header with invalid port leads to exception when creating the ServerRequestFactory->fromGlobals
- Applied in changeset commit:d21846771aa9c8286b5de2e17c4b76637142a2fa.
- 12:18 TYPO3 Core Revision 4148f82e: [BUGFIX] Return HTTP 400 if request is invalid
- The request may be an unparsable URL or might
have other defects.
Specifically, the URI class may throw an
exception... - 10:02 TYPO3 Core Revision c0036819: [BUGFIX] Return HTTP 400 if request is invalid
- The request may be an unparsable URL or might
have other defects.
Specifically, the URI class may throw an
exception...
Also available in: Atom