Bug #49181
closed
Columns mode doesn’t respect language
Added by Rainer Becker over 11 years ago.
Updated over 8 years ago.
Description
If you are editing in columns mode and switch to a non-default language, both icons on top of edit area View Webpage and Page Properties lead to the default preview/page properties.
Since the icons are below the language selection this is not reasonable.
- Target version set to 7.4 (Backend)
- Is Regression set to No
still present in both 6.2.14 and 7.4-dev (latest master)
- Target version changed from 7.4 (Backend) to 7.5
- Target version changed from 7.5 to 7 LTS
- Status changed from New to Needs Feedback
- Assignee set to Mathias Schreiber
Hi Rainer,
would you remove the preview link in general when another language has been set?
Hi Mathias,
no, I would just change the action of the preview button to give a preview of the currently selected language (like when you click preview when editing a localized content element).
But where do we link to?
You can set a language based off almost anything, ranging from GET params to domains or to time of day :)
I will give this some thought, because this is a really tricky thing.
Shouldn’t it reflect the language I am currently editing (language drop down)?
I know, but what is the URL we call in the frontend?
defaultLanguageUrl&L=3
won't work
When I edit a content element in language [1] on page [2] and click preview I will see /index.php?id=2&L=1; why is that not possible when in column editing mode?
Because maybe you did not use the parameter L
to switch the language.
Maybe you use a domain to switch the language.
Or you use a parameter called lang
or something else.
So simply attaching L=2
to the URL is not sufficient.
Does this somehow get across? :)
Now I got your point :)
When editing translated content you rely on the L param as well; however these cases should be treated the same.
What is the state of this issue?
- Status changed from Needs Feedback to Closed
- 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.
Also available in: Atom
PDF