TYPO3 Core

what about

$TYPO3_CONF_VARS['EXTCONF']['cms']['db_layout']['addTables']['tx_irfaq_q']⁰ = array(
'fList' => 'q,a,q_from,expert',
'icon' => TRUE
);

...taken as an example from irfaq

reuse the TCA: The palettes already exist.
---------------
'overview' => Array (
'Standard' => '2',
'Extended' => '3'
),
'palettes' => Array (
'1' => Array('showitem' => 'starttime, endtime, fe_group'),
'2' => Array('showitem' => 'price2, special_preparation, directcost, tax, offer, highlight'),
'3' => Array('showitem' => 'subtitle, www, itemnumber, inStock'),
'4' => Array('showitem' => 'size, unit, unit_factor, gradings, bulkily, weight'),
'5' => Array('showitem' => 'accessory2'),
'6' => Array('showitem' => ''),
)
----------

If I see this correctly, the method mentioned by Ingo already exists :-)
Sebastian

http://typo3.org/documentation/document-library/doc_core_api/Support_for_custom_t/

But you cannot set the function menu with this.

case 'tt_products':
$h_func = t3lib_BEfunc::getFuncMenu($this->id,'SET[tt_products]',$this->MOD_SETTINGS['tt_products'],$this->MOD_MENU['tt_products'],'db_layout.php','');
break;

But you cannot set the function menu with this.

if (!isset($dblist->externalTables[$table])) {
...
case 'tt_products':
$h_func =
t3lib_BEfunc::getFuncMenu($this->id,'SET[tt_products]',
$this->MOD_SETTINGS['tt_products'],$this->MOD_MENU['tt_products'],'db_layout.php','');
break;

function menuConfig() {
// MENU-ITEMS:
$this->MOD_MENU = array(
...
'tt_products' => array (
0 => $LANG->getLL('m_default'),
'ext' => $LANG->getLL('m_tt_products_ext')
),

cannot be configured from outside.

Hi,
yes, you are right with this. It would be really cool if you wrote a patch making this possible :-)
Sebastian

I have sent the patch already to the CORE list in December 2005.
So lets wait until someone will find the time to look on it.

The Web->Page module does not work correctly with TYPO3 4.0beta3. See attached image.

Hi Franz,

The Web->Page module does not work correctly with TYPO3 4.0beta3.
See attached image.

You being a core dev, I would say that you should look at this issue and propose a fix for it.

- michael

Hi!
What's the status of this? It would be a nice usability enhancement, especially when looking for 4.5.

+1
It would be nice to have the option to put records on page view

roger

@Roger Bunyan,

I think we are moving in circles here. There is already an API to put records on page module. See the first comment of this bug report. The link to the documentation about is changed to:

http://typo3.org/documentation/document-library/core-documentation/doc_core_api/current/view/3/8/#id2860649

What seems to be missing is an API to have different "views" of those records, like tt_news and other "hardcoded" extensions are able to do.

This has been discussed in the core list, but I don't think anything has been integrated, as this thread was a bit of a mess. Maybe we could get Franz Holzinger to recreate a patch to the current trunk of SVN and provide a RFC so it can be discussed in core again.

For me this patch makes really sense. The patch is already available, easy to test, increases the usability for important extensions. So why not intergrate it in V4.1?

Someone just has to make an organized summary and current patch (for current 4.0 trunk) about it and we can discuss it in the core list. I would suggest Franz as he was originally interested in it.

With "organized summary" I mean some clear text which all core developers can understand without having to install extensions or do much research. This is usually the easiest and fastes way to get it into the core.

I would really go for this patch in the next typo3 version. better listings on the page module would be very smooth thing - especially since the typo3 vers.5 with the more flexible ajax interface will still take some time ;-)

I have resent this patch again to the Core list that it comes into TYPO3 4.2.
Please have a look at it and tell me if something is still unclear. If you want an additional feature then I generally agree but want to deliver that in a separate patch.

Regards,

Franz

I have uploaded a new extension patch1822 into TER. So you can test and use it without applying the patch.

I just found this patch in static_info_table. Cool patch! What's about this into core?

Any progress?

Is this still valid?!

I think it is irrevant...
It's possible by using $TYPO3_CONF_VARS['EXTCONF']['cms']['db_layout']['addTables']...

reopened by request of franz H.

Franz, could you have a look at what Olly said in may 2009 and provide a new patch if needed? it would be so nice to get rid of this "patch" in TER and not having it anymore as an option in static_info_tables... :-)

I renewed the patch and wrote a demo extension using fe_users as example.

committed to trunk rev 6874