Bug #64986
closed
tt_content colPos is filled wrong every time open an existing element
0%
Description
Every time I open an existing tt_content element, the colPos is reseted to "left".
This is very annoying, that you had to change the colPos every time you edit a content element.
This bug occurs in the newest 4.5.39 version. Possibly in older versions, too. I have not tested that.
Files
Updated by Mathias Schreiber almost 10 years ago
- Status changed from New to Needs Feedback
- Assignee set to Mathias Schreiber
Hi Christian,
we can rule out any TSConfig settings being set in the tree?
Because I can't reproduce this here.
Updated by Christian Finkemeier almost 10 years ago
- File TSConfig.pdf TSConfig.pdf added
Hi Mathias,
I have no personal TSConfig setting applied. I have attached my TSConfig tree.
Updated by Mathias Schreiber almost 10 years ago
Thanks.
No extensions like GridElements installed or something else that could fiddle around with the Forms?
Hooks, userFuncs etc.?
See #62118 for example
Updated by Christian Finkemeier almost 10 years ago
Nothing, no extensions installed so far. But I think I have disabled some default activated core modules. This is my extension-list:css_styled_content, context_help, extra_page_cm_options, impexp, tstemplate, tstemplate_ceditor, tstemplate_info, tstemplate_objbrowser, tstemplate_analyzer, lowlevel, install, beuser, setup, info_pagetsconfig, rtehtmlarea, t3skin, t3editor, info, perm, filelist, rsaauth, saltedpasswords
When I look into the html source code, the selected colPos (e.g. right: 2) is not selected by default. The input hidden field is set to "0".
Updated by Jigal van Hemert almost 10 years ago
- Status changed from Needs Feedback to New
That's a really minimalistic list of extensions :-) Nothing essential seems to be missing. Also no page TSconfig that overrides this field seems to be present.
At the moment I don't have a clean 4.5 installation (without extra extensions that influence the Page module) available to test on. There haven't been any changes lately that can affect this, so it's kind of mystery what happens in your installation.
Updated by Benni Mack over 9 years ago
- Status changed from New to Needs Feedback
can you give us more information? Can you ping me on slack (see https://forger.typo3.org/slack) so we can find out the problems directly. thx.
Updated by Alexander Opitz about 9 years ago
- Assignee deleted (
Mathias Schreiber)
No feedback within the last 90 days => closing this issue.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.
Updated by Alexander Opitz about 9 years ago
- Status changed from Needs Feedback to Closed