Bug #56445
closed
TCA enablecolumns property ignored for fe_users and pages (at least)
0%
Description
I wrote a hook for $GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['GLOBAL']['extTablesInclusion-PostProcessing'][] to remove starttime and endtime fields from the where clause (i don't use it in my project) from pages and fe_users tables.
My hook works and i can see that the TCA is affected from the backend configuration module but nothing changes for the queries.
In fact enablecolumns is hard-coded and TCA is ignored for those two tables (at least). This can be checked on line 133 of the file FrontendUserAuthentication.php
Updated by Markus Klein over 10 years ago
Why do you need to remove them?
Just do not set them. You're not forced to use the fields.
Or do I get your intention wrong?
Updated by Grégory Duchesnes over 10 years ago
Hi and thanks for your answer (again). I need to unset for two good reasons :
- Typo3 API should respect what's written in the docs, therefore this is a bug.
- The use of those fields in a query fills the MySQL query cache with useless queries such as :
SELECT * FROM fe_users WHERE username='0.xxx@live.fr' AND pid IN (1) AND fe_users.disable=0 AND fe_users.deleted=0 AND (fe_users.starttime<=1393595211) AND (fe_users.endtime=0 OR fe_users.endtime>1393595211)
Call me "basic" but i don't like useless things
Updated by Helmut Hummel almost 10 years ago
- Status changed from New to Needs Feedback
Can you describe what exactly you removed from TCA?
Did you actually remove the TCA['fe_users']['ctrl']['enablecolumns'] section?
I agree that fe_users enablecolumns from TCA should be transferred to the FrontenduserAuthentication once the TCA is available.
However are you sure that enablecolumns for pages are still used even if not available in TCA? Can you also point to some code where this is the case?
Updated by Alexander Opitz over 9 years ago
- Status changed from Needs Feedback to Closed
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.