[TYPO3-dev] edit and use all tables in backend forms with TCA

Franz Holzinger franz at fholzinger.com
Wed Mar 8 23:06:36 CET 2006


Hello Ernesto,

> Franz Holzinger schrieb am 08.03.2006 19:55:
> 
>>doesn't anyone have a opinion to the topic how to make all possible
>>tables configurable in the backend?
>>
>>I will soon have to do more coding for this and would like to have your
>>suggestions into which direction this should go.
>>
>>Maybe a global page id should be used under which the mm tables can be
>>edited. So the TYPO3 functions needs some adaptions to work with mm
>>tables that do not have a pid and no uid field.
>>  
> 
> Just as an idea:
> 
> How would it be if we could edit these "extra fields" that you want to
> store in the MM-relation directly in the
> browse_links.php wizard?
Yes this is the best solution to make a new popup window with the
backend of the MM table. I have done this already this way.
However on the backend of the MM table there is needed another select
box. This is because you do not want to close and reopend this window
when you change the uid_local data.

> Currently there I can just select the desired
> records ("Select Record"). But if instructed by TCA we could have other
> fields (integer, strings, etc) there that are attached together with the
> chosen record and which get added to the select field and later stored
> in the MM-table together with the IDs.
The additional fields of the MM table have to be entered somehow. (See
above). First the user selects the entry of the foreign table and then
he edits the attributes for this MM relation.


This is the issue for MM tables.

However my question has been bigger.
I would like to find a solution where a normal table, e.g.

field1
field2
...
fieldn

can be displayed in the backend. There should be written a TCA (or
automatically generated from the 'CREATE TABLE').
So every possible table should have a backend TCE. No need for pid or
uid any more.


- Franz







More information about the TYPO3-dev mailing list