Jo Hasenau
- Login: cybercraft
- Email: info@cybercraft.de
- Registered on: 2008-02-14
- Last sign in: 2024-11-14
Issues
| open | closed | Total | |
|---|---|---|---|
| Assigned issues | 7 | 39 | 46 |
| Reported issues | 9 | 115 | 124 |
Projects
| Project | Roles | Registered on |
|---|---|---|
| TYPO3 Core | Contributor | 2015-07-17 |
Activity
2024-09-05
-
11:07 TYPO3 Core Bug #89787: Copying element with IRRE element from one language to another
- Denis Mir wrote in #note-8:
> Error is still present in 12LTS. Even the `l10n_source` is not set at all.
That's c...
2024-04-01
-
- Based on the current translation mechanism, this behaviour is correct independently from the mode you've got for your...
2024-03-01
-
- The actual validation problem is, that the field is hidden AND got an autocomplete value - it does not matter if that...
2024-02-17
-
- For the connected mode adding a single line to content fetcher should be enough:...
-
- We recently picked up this issues again after discussing it in the Translation Handling Initiative. The problem seems...
2024-02-07
-
- Andreas Kiessling wrote in #note-13:
> > l18n_parent = id AND l10n_source = other-id -> The element is in connected ... -
- Markus Klein wrote in #note-19:
> > l18n_parent = id AND l10n_source = 0 -> shouldn't happen / db inconsistency.
> ...
2023-12-01
-
- Actually this should be the expected behaviour of the connected mode, since in connected mode the default language el...
2023-09-24
-
-
- This bug can still be reproduced at least in CMS 11.x but not just within a workspace - moving an element to another ...
Also available in: Atom