Project

General

Profile

Actions

Bug #69649

closed

Info Module - Localisation Overview is broken

Added by Daniel Goerz over 8 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
-
Target version:
Start date:
2015-09-10
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
7
PHP Version:
Tags:
Complexity:
Is Regression:
Yes
Sprint Focus:

Description

It is not possible to create new Alternative Page Languages in the info module.
Additinally there are some other flaws as well:

Steps to reproduce

  1. Create at least one system language
  2. select a not yet localized page
  3. go to info module
  4. Choose Localization overview in the dropdown
  5. Choose a specific language or ALL in the language dropdown
Now the following bugs occure:
  1. If you hover over the pencil behind the default label it states "Edit all page properties" but if you click it only a subset of properties are editable.
  2. The plus icon behind the other language(s) states on hover: "Create new translation headers" when in fact a new page_language_overlay record is created.
  3. If you dont check the checkbox and click on the plus sign you end up on an empty page with the abort and save icons on top having no functionality.
  4. If you check the checkbox and click the plus icon you are on a page that states "Create new Alternative Page Language on page ..." but you cant save the record.

Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #69651: Not possible to create Alternative Page LanguagesClosed2015-09-10

Actions
Actions #1

Updated by Daniel Goerz over 8 years ago

  • Parent task set to #69617
  • Is Regression changed from No to Yes

The main bug (Nr.4 in the list from the description) is a formEngine regression.

Additionally it is not possible to create new page translations in list module either.

Actions #2

Updated by Daniel Goerz over 8 years ago

Daniel Goerz wrote:

  1. If you check the checkbox and click the plus icon you are on a page that states "Create new Alternative Page Language on page ..." but you cant save the record.

In fact a bunch of JavaScript errors occure.

Actions #3

Updated by Christian Kuhn over 8 years ago

The main issue in FormEngine is fixed with the related issue. is the rest of the issue still FormEngine related and a regression of the main patch?

Actions #4

Updated by Christian Kuhn over 8 years ago

  • Parent task deleted (#69617)
Actions #5

Updated by Daniel Goerz over 8 years ago

  • Status changed from New to Resolved

I'll create a new ticket for the minor bugs. This one is resolved for now.

Actions #6

Updated by Riccardo De Contardi over 6 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF