Feature #39326

Add BackendUser.allowedLanguages

Added by Oliver Klee 10 months ago. Updated about 1 month ago.

Status:Rejected Start date:2012-07-27
Priority:Should have Due date:
Assignee:- % Done:

0%

Category:Extbase: Domain
Target version:Extbase 6.1
Has patch:No Tags:
Votes: 0

Related issues

blocked by Extbase MVC Framework - Feature #39145: Add a BackEndUser model Resolved 2012-07-20

History

Updated by Markus Günther 10 months ago

  • Status changed from New to Accepted
  • Target version set to Extbase 6.0

Updated by Markus Günther 9 months ago

We will not create a language model at the moment... we sadly don't have enough time for it. We need the property so the first change will be only a string of language ids from the db.

Updated by Gerrit Code Review 9 months ago

  • Status changed from Accepted to Under Review

Patch set 1 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/13933

Updated by Ingo Pfennigstorf 8 months ago

  • Target version changed from Extbase 6.0 to Extbase 6.1

Updated by Gerrit Code Review 5 months ago

Patch set 2 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/13933

Updated by Gerrit Code Review 5 months ago

Patch set 3 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/13933

Updated by Gerrit Code Review 3 months ago

Patch set 4 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/13933

Updated by Wouter Wolters about 1 month ago

  • Status changed from Under Review to Rejected

Christian Kuhn Feb 9 19:51

Patch Set 4: I would prefer that you didn't submit this

I do not think it is useful to add a property that just gives some string of id's. If we implement this, the result should be a (lazy) objectStorage that returns language objects. Furthermore, there is currently no use case for us to implement this. So, all we achive if we now add this property this way would be a b/w compat problem that we get if it is changed to some objectstorage later on.

Also available in: Atom PDF