[TYPO3-core] RFC: #9439: New Element Wizard has no option for hiding Elements via pageTS

Steffen Kamper info at sk-typo3.de
Tue Oct 21 17:16:47 CEST 2008


Hi Ernesto,

thx for sharing your ideas.

indeed you're right, best would be to pass the information with the 
create-link for both situations.

The new element wizard is very basic one, Dmitry told me that the core 
one was originally copied from TemplaVoilà :-)

I tried to use the core one for TV as well as it sucks to develop same 
module in different versions, best negative example is the element 
browser, which exists in core, rte (3times) and in DAM.
There is a different link-generation in TV one, but this can be solved easy.

I'm not quite sure about how to configure in classic (TV is easy using 
the DS), so atm i think about
positive:
XXX.col_pos.allowedCType = a,b,c
negative
XXX.col_pos.denyCType = d,e
also a general one without col_pos ...

Maybe i should think about some more and come with a complete solution 
for classic first with an enhanced wizard that can be used from TV as well.

vg Steffen

Ernesto Baschny [cron IT] schrieb:
> Hi Steffen,
> 
> this is an interesting patch. The intension is good, but this is somehow
> incomplete, as you figured out yourself.
> 
> Templavoila comes with a rather "old" copy of the wizard
> (mod1/db_new_content_el.php), which should be made "obsoleted", as soon
> as templavoila can use functions from TYPO3 core and not copy and modify
> them. The API for the Wizard should be:
> 
> For templavoila and also the page module with multiple-columns, the
> "context" to decide which elements to display doesn't have only to do
> with the page the user is in, but also where the user clicked to create
> a new content element (in templavoila the "xml-path", in regular TYPO3
> the "column"). We need to be able to pass this kind of "context"
> information to the wizard, so that it can call extensions that will
> handle the context information (to hide or add elements to the wizard).
> 
> So for example Templavoila could generate a link:
> 
> db_new_content_el.php?id=10&tx_templavoila[parentRecord]=tt_content:62:sDEF:lDEF:field_content:vDEF:1
> 
> whereas the page module will create a link like:
> 
> db_new_content_el.php?id=10&tx_cms[colPos]=0&tx_cms[uid_pid]=-601&...
> 
> The wizard itself would then call some hook, where the pertaining
> extensions will be allowed to manipulate the complete list of elements
> presented by the wizard.
> 
> The web_page module might use the hook, deciding which elements to hide
>  from pageTS configuration. Templavoila might decide it through some
> XML-setting in the parents DS.
> 
> In your patch, the web_page part is being handled, but this is currently
> not context sensitive, thus I would at least handle the colPos context
> that is already available. Although the wizard can also be called
> without that context information, where it presents the column chooser
> after the content element selection. Maybe this is an HCI issue. :)
> 
> Cheers,
> Ernesto
> 
> 
> Steffen Kamper wrote: on 27.09.2008 16:37:
> 
>> Type: Bugfix
>>
>> Bugtracker references:
>> http://bugs.typo3.org/view.php?id=9439
>>
>> Branches: trunk
>>
>> Problem:
>>
>> This seems a forgotten implementation, i did this with attached patch.
>> Its for the new Content Element Wizard.
>>
>> Use following setting:
>> mod.xMOD_db_new_content_el.hideItems = x,y,z
>>
>>
>> Additional Information:
>>
>> Following wizards are implemented by default:
>>
>> common, common_regularText, common_textImage, common_imagesOnly,
>> common_bulletList, common_table, special, special_filelinks,
>> special_multimedia, special_sitemap, special_plainHTML, forms,
>> forms_mail, forms_search, forms_login, plugins, plugins_general
>>
>> Dmitry: if this goes in i will make a patch for TV as well.
>>
>> vg Steffen
>>


More information about the TYPO3-team-core mailing list