Feature #19053
closedselect function which considers language, enableFields and workspace
0%
Description
There should be a function which considers language and workspace while selecting records from a table:
->getRecords('table', $where);
There are just few extensions which do language handling the right way and nearly none which are able to preview workspace.
We realy tried very hard to comprehend and integrate workspace preview (with versionOL), but it just not works like it should and nobuddy can realy answer how it has to be done.
It would make things that much easier if one could call a function with table name and where clause which returns the records considering language and workspace (and all the other cool TYPO3 things).
(issue imported from #M8889)
Updated by Bernd Wilke over 16 years ago
perhaps it would be enough to enhance enablefields(), as this function is used everywhere.
The first iteration could be other ...fields()-functions like:
languagefields() and workspacefields()
but maybe it couldn't be separated and it had to be integrated into one single function.
Updated by Christian Weiske over 13 years ago
- Target version deleted (
0)
I'd used the issue vote button if there was one, but now I have to post this "me too" comment.
Updated by Mathias Schreiber almost 10 years ago
- Description updated (diff)
- Category deleted (
Communication) - Target version set to 7.2 (Frontend)
Updated by Benni Mack over 9 years ago
- Target version changed from 7.2 (Frontend) to 7.4 (Backend)
Updated by Susanne Moog over 9 years ago
- Target version changed from 7.4 (Backend) to 7.5
Updated by Benni Mack about 9 years ago
- Status changed from New to Needs Feedback
- Assignee set to Benni Mack
- Target version deleted (
7.5)
Does this problem still exist? @Christian - I guess the PageRepository and BackendUtility methods do the job quite right?
Updated by Alexander Opitz almost 9 years ago
- Status changed from Needs Feedback to Closed
- Assignee deleted (
Benni Mack)
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.