Project

General

Profile

Actions

Bug #81386

closed

Preview language setting not always set

Added by Rainer Becker over 7 years ago. Updated almost 5 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Backend User Interface
Target version:
-
Start date:
2017-05-31
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
8
PHP Version:
7.0
Tags:
Complexity:
Is Regression:
Sprint Focus:
On Location Sprint

Description

The language getvar ist not always added to preview urls. Since the BE default language uid can differ from the DE default language this should consistently be added to all links leading from BE to FE preview

  • Context menu page tree => view:
    param not added (should be set according to default language => L=0)
  • Page module, display mode columns, view button in doc header:
    param not added (should be set according to selected language)
  • Page module, display mode languages, view button in doc header:
    param added correctly for default language and translations
  • View module:
    param not added in preview iFrame (should be set according to default language => L=0)
  • Edit content in default language, button save & preview:
    param not added (should be set according to default language => L=0)
  • Edit content translation, button save & preview:
    param added correctly

Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Bug #56351: view page in another language than default language from Backend is incorrectClosed2014-02-26

Actions
Related to TYPO3 Core - Bug #87794: View Page button creates link without langauge parameterClosed2019-02-26

Actions
Actions #1

Updated by Susanne Moog almost 7 years ago

  • Category set to Backend User Interface
Actions #2

Updated by Mona Muzaffar over 5 years ago

  • Related to Bug #56351: view page in another language than default language from Backend is incorrect added
Actions #3

Updated by Riccardo De Contardi over 5 years ago

I have not fully understood, reading the description, why the L=0 param should be added to the previews in default language; could some use case or example be added?

Anyway, I'll write here what I found testing the latest 10.0.0-dev master:

Context menu page tree => view:
Always shows the default language pages; the issue could be solved with/after #46017 IMO

Page module, display mode columns, view button in doc header:
Still troublesome; only the default lnaguage is shown, regardless of the language selected with the language dropdown

Page module, display mode languages, view button in doc header:
Still troublesome; only the default lanuage is shown, regardless of the language selected with the language dropdown; Instead, the preview button under the pagetitle in each language column works correctly.
By the way: in display mode: languages the dropdown in docheader that allows to choose language could be omitted. Or not?

View module:
Seems to work correctly; both the preview inside the iframe and the button lead to the correct language variant.

Edit content in default language, button save & preview:
On 10.0.0-dev only "view" button is used; it seems to work correctly; the page with default language is shown

Edit content translation, button save & preview:
On 10.0.0-dev only "view" button is used; it seems to work correctly; the page with selected language is shown

Actions #4

Updated by Riccardo De Contardi over 5 years ago

  • Related to Bug #87794: View Page button creates link without langauge parameter added
Actions #5

Updated by Rainer Becker over 5 years ago

I my case the default language in backend was EN (sys_language_uid=0), but the frontend would show another language (sys_language_uid>0) when no L-param was added.
To make sure the preview link leads to the language currently selected in BE, I think the L-Param should always be included.

Actions #6

Updated by Susanne Moog almost 5 years ago

  • Sprint Focus set to On Location Sprint
Actions #7

Updated by Susanne Moog almost 5 years ago

  • Status changed from New to Closed

As version 8 is in priority bugfixing mode only and in v9 and v10 with site configuration the problem does not exist anymore I'm closing the issue now.

Actions

Also available in: Atom PDF