[TYPO3-commerce] problems with template system

[Rik Willems]

Hi Robert,

Your welcome.
Too be honest I'm not sure how it should work with unsetting. The code 
still dictates what happens. The typoscript only configures.

Most people work hard and don't have much time. But sharing helps 
everybody. I'm still looking to translate the German manual to English 
as the German one is much more extensive. Hopefully that helps.

Concerning your last question: I don't have a clue.

Greets,
Rik

Bob Wild schreef:
> Hi, Rik,
> 
> I owe you a big thank you for your time and help!
> 
> As for 1) I don't quite understand why the behaviour does not grasp, 
> because the TS setup of commerce itself is configured that way. All I do 
> is overwrite (override? I still don't know the difference...) that 
> particular part of TS. There I thought deleting the title should result 
> in not showing anything for the title, as much as a title.warp = 
> <h2>|</h2> sets the text to H2.
> I have the weird feeling that this seems to be buggy... but I am too 
> less a programmer...
> 
> As for the problem that only a handful know what's going on in commerce, 
> I do understand and see the problem. On the other hand would this be the 
> place to get things clear and then maybe put some tutorials somewhere- 
> Latter is definately my intension and the reason simply is to have sth 
> which reminds me once I've forgotten things. If there is advantage for 
> others - great!
> 
> A question - maybe you have experience (I will only find time next week 
> to test it): is fe_attr_commerce still applicable for commerce 0.11.15?
> 
> Again a big thank you!
> Regards,
> Robert
> 
>> Hi Bob,
>>
>> 1)
>> Basically typoscript is a big configurator. It thus instructs the 
>> extension on how to behave. If you remove/delete parts of the 
>> typoscript it doesn't mean the extension does do anything. It will 
>> miss that part of the config and use default. Or in case it does need 
>> a config give weird output (like the image).
>> The extension also looks for the subparts, in this case <!-- 
>> ###CATEGORY_ITEM### -->. If it can't find it an error will be given. 
>> To remove the category text in single view you must remove the 
>> individual markers but keep the subpart. Then all be fine.
>>
>> 2)
>> It probaly has something to do with multilanguage. If you don't use 
>> that it seems normal that it doesn't produce output. You can look in 
>> the source how that marker gets filled.
>>
>> 3)
>> By the looks of it you can not do this here. To be sure you must look 
>> in the source. If you are willing to contribute this please make a 
>> patch so it can be added.
>>
>> 4)
>> I think it's a fragment of something. Below it says: allArticles. If 
>> you set this to 1 all articles of the chosen product will be shown. 
>> Set it to 0 and only one is shown.
>> In the last case you can add select boxes so customers can choose the 
>> right article. See the recent discussion 'Missing attribute drop-dowm 
>> menu' on how to do that.
>>
>>
>> Hopefully this answer most of your questions.
>> One of the reason that you might not be answered the fact that 
>> commerce is quite complex. There is only a handful of people how 
>> really know everything.
>>
>> Greets, Rik
>>
>>
>> Bob Wild schreef:
>>> Hi list,
>>>
>>> I posted this problem already some weeks ago, but I didn't get any 
>>> help, so - stubborn as I can be - I try it again.
>>>
>>> In particularly the situation is one with the HTML 
>>> category_products.tmpl and the TS that is supposed to (de)activate 
>>> certain markers or submakrs resp.
>>>
>>> This is the sequence of how the various Markers are called (at least 
>>> to my understanding):
>>>
>>> 1. ###CATEGORY_VIEW_DISPLAY### ,   this one calls the
>>> 2. ###CATEGORY_SUB_LIST### ,   which itself calls the
>>> 3. ###CATEGORY_LIST###
>>>
>>> and then - depending on the TS-config with templateMarkers, either 
>>> one, two or more
>>>
>>> 4. ###CATEGORY_ITEMS_LISTVIEW_[0|1|2|...]###
>>>
>>> are called.
>>>
>>>
>>>
>>>
>>> My questions are:
>>>
>>> ******************************************************************
>>>
>>> 1. As soon as one gets to the point where products are shown (<!-- 
>>> ###PRODUCT_VIEW_DETAIL### begin--> in the HTML template), there will 
>>> also be a field that shows the respective category to which those 
>>> products belong (<!-- ###CATEGORY_ITEM### begin -->).
>>> The corresponding TS looks like this:
>>>
>>> plugin.tx_commerce_pi1 {
>>>     singleView {
>>>         products.categories {
>>>             title ...
>>>             subtitle ...
>>>             description ...
>>>             image ...
>>>             teaserimages ...
>>>         }
>>>     }
>>> }
>>>
>>> My adaptation:
>>>
>>> plugin.tx_commerce_pi1 {
>>>     singleView {
>>>         products.categories >
>>>     }
>>> }
>>>
>>> Nevertheless the category is shown, meaning my TS does not work. 
>>> (Even if I delete the several objects seperately, like 
>>> "plugin.tx_commerce_pi1.singleView.product.categories.title > " no 
>>> changes happen, except for image, which results in the fact that the 
>>> image is not shown, but its name).
>>>
>>> Very strange in this context is, too, that when I delete that 
>>> respective submarker from my HTML template I get errors and the site 
>>> is not displayed.
>>> (Section "PRODUCT SINGLEVIEW" -> submarker "<!-- ###CATEGORY_ITEM### 
>>> -->")
>>>
>>> What am I misunderstanding here?
>>>
>>>
>>> ***********************************************************************
>>>
>>> 2. Which content or what meaningful line is the marker 
>>> ###LANG_HEADER_ACTION### supposed to display? The respective tag in 
>>> the language.xml is just empty.
>>>
>>>
>>>
>>> ***********************************************************************
>>>
>>> 3. TemplateMarkers enable the use of different div-containers for the 
>>> Product display (odd - even):
>>>
>>> LIST PRODUCT ITEM  ->  EVEN  ->  ###CATEGORY_ITEMS_LISTVIEW_2###
>>> LIST PRODUCT ITEM  ->  ODD   ->  ###CATEGORY_ITEMS_LISTVIEW_3###
>>>
>>> In the TS is says:
>>>
>>> plugin.tx_commerce_pi1 {
>>>   ...
>>>   // templateMarker.categoryProductList.0
>>>   // Number of Iterations in the Product List Number
>>>   templateMarker.categoryProductListTopIterations =  1
>>>   templateMarker.categoryProductListIterations =  2
>>>       // Change the templateMarker for product List to an iteration 
>>> System
>>>   // Now unlimeted Marker can be defined, same for topProducts
>>>   // Array with Template Marker from 0 to x as key
>>>       templateMarker.categoryProductListTop.0 = 
>>> CATEGORY_ITEMS_LISTVIEW_1     templateMarker.categoryProductList.0 = 
>>> CATEGORY_ITEMS_LISTVIEW_2
>>>   templateMarker.categoryProductList.1 = CATEGORY_ITEMS_LISTVIEW_3    
>>> ...
>>>
>>>   // Template marker for different views
>>>   templateMarker {
>>>    ...
>>>    productAttributesSelectorDropdown = SELECTOR_ATTRIBUTES_DROPDOWN
>>>    productAttributesSelectorRadiobutton = 
>>> SELECTOR_ATTRIBUTES_RADIOBUTTON
>>>    // make a selector Element or show all Artikels
>>>   }
>>> }
>>>
>>> Is there any way that I can use the same principle for displaying 
>>> subcategories in ###CATEGORY-LIST###?
>>>
>>> (Why? - Having severeal subcategories, I would like to display 2 
>>> categories next to each other. The different length of the texts 
>>> results in different lengths of the columns, which results in 
>>> overlapping of subcategories. The idea is to set a clear-div after 
>>> every second subcategory - but this seems not to be possible now. Or 
>>> do I have a wrong understanding of the system?)
>>>
>>>
>>> *********************************************************************
>>>
>>> 4. In the plugin.tx_commerce_pi1.templateMarkter section (see under 
>>> 3) there is a line saying:
>>>
>>> // make a selector Element or show all Artikels
>>>
>>> Can anybody explain, what that means? And maybe give an example?
>>>
>>>
>>>
>>> Any help is greatly appreciated!
>>>
>>> Regards, Robert