Feature #34823

Remove language "default" from Alternative Page Language Records

Added by Roland Behme over 9 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Backend User Interface
Target version:
-
Start date:
2012-03-14
Due date:
% Done:

0%

Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

Just had the case that a customer created Alternative Page Language Records with language "default". Since this does not make sense at all and I really don't know how TYPO3 deals with such records (and probably do not want to know at all), the creation of such records should be impossible from the Backend.
I think best would be to remove the option "default" from the language dropdown in Alternative Page Language Records.


Files

new_page_translation.png (8.51 KB) new_page_translation.png TemplaVoilà (left) and standard page module (right) : new page translation Jigal van Hemert, 2012-03-16 21:24

Related issues

Related to TYPO3 Core - Bug #48673: Changed language overlay behaviour in TYPO3 6.*Closed2013-05-30

Actions
#1

Updated by Jigal van Hemert over 9 years ago

  • Status changed from New to Needs Feedback

Your customer used the List module to create an Alternative Page Language record. This is just not the right tool for the job.
The page module has logic to detect which translations are already present and will only offer the missing languages.
The list module is simply an interface to manipulate all kinds of records; the list module has no knowledge about the purpose of these records.

#2

Updated by Roland Behme over 9 years ago

Hmmm, you're right. The standard TYPO3 page module does not have the option to edit the language field of an Alternative Page Language record. The site was made using TemplaVoila, so I think this issue is related to the TemplaVoila page module. I will open another ticket in the TV bugtracker, so this one can be closed. Thanks!

#3

Updated by Markus Klein over 9 years ago

Jigal van Hemert: Besides that the list module has no knowledge about the purpose, but I question the purpose of "Default" for an Alternative Page Language in general.

#4

Updated by Jigal van Hemert over 9 years ago

Both Page modules of TemplaVoilà and TYPO3 have the possibility to create translations of pages. Behind the scenes this is done by creating an Alternative Page Language record.
The Page modules show which translations (Alternative Page Language records) are already present on the page and which website languages (the Website Language records in the root of the installation) do not have an Alternative Page Language record on the page.
See attached image.

I still think that your customer used the List module to create extra Alternative Page Language records. This is a possible method, but the List module doesn't have the knowledge about the function of those records. So it happily create multiple records of a certain language.

Before filing a bug report with TemplaVoilà it may be a good idea to ask your customer how they created those records and maybe teach them how to create translations with the Page module.

#5

Updated by Jigal van Hemert over 9 years ago

@Markus : it seems that an option for 'default' is not needed, but I'm not 100% sure that there won't be problems if it was removed from the TCA.

#6

Updated by Roland Behme over 9 years ago

He created the page translations through the page module, but then edited the translated page properties, fiddled around with the language setting and set the record to "default" language. So technically it's possible for an editor to create records that make no sense (either with list module or TV page module), so I agree with Markus: maybe it should be considered to remove the "default" option from TCA if possible.
Of course then you can still create multiple Page Language records for the same language using the list module, but that is probably not a likely case since most editors don't know about these records or have them hidden through user page TSCONFIG settings anyway.

#7

Updated by Oliver Hader over 9 years ago

  • Tracker changed from Bug to Feature
#8

Updated by Oliver Hader over 9 years ago

  • Status changed from Needs Feedback to Accepted

Alright, I've moved it to the feature tracker... looks like a topic for "simplify TYPO3"...

#9

Updated by Stefan Neufeind over 7 years ago

From reading I agree that having "default" in the dropdown for an alternative language-record doesn't make sense and we might want to consider removing that option.

#10

Updated by Gerrit Code Review almost 7 years ago

  • Status changed from Accepted to Under Review

Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/35695

#11

Updated by Gerrit Code Review almost 7 years ago

Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/35695

#12

Updated by Gerrit Code Review almost 7 years ago

Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/35695

#13

Updated by Gerrit Code Review almost 7 years ago

Patch set 4 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/35695

#14

Updated by Gerrit Code Review almost 7 years ago

Patch set 5 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/35695

#15

Updated by Gerrit Code Review almost 7 years ago

Patch set 6 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/35695

#16

Updated by Wouter Wolters almost 7 years ago

  • Status changed from Under Review to Resolved
#17

Updated by Benni Mack about 3 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF