TYPO3 Mailingliste: nicht fragen - lesen!

Hey guys,

I've started to use TV just recently, so I'm not sure about a lot of
stuff. One thing that bothers me is that I've usually got about 3 or
more TO with different content layout and when I want to change/add
element that's common for all TO (such as footer, language selector), I
need to go through all TO mappings and assign the new element manually.
This gets really anoying with more than 3 TO. Is there a way how to add
new element to DS easily without having to open all TO?

Another thing is, that I start with one template, set all neccessary
mapping. Then, I create another template and because I'm lazy, I copy
the first template, so I don't have to set all common mapping again. The
problem is, elements from first template, that are not present in the
second template, give me warning, because they have their mapping set,
but the element doesn't exist in the second template. And there's no way
how to delete just some mappings and not all of them.

So, how do you handle more templates? Do you click stuff for every
template again and again?

--
Jan Bednarik
www.bednarik.org - web about Typo3 in czech
_______________________________________________
TYPO3-project-templavoila mailing list
TYPO3-project-templavoila (AT) lists...netfielders.de
http://lists.netfielders.de/cgi-bin/...ct-templavoila

Hi!

Jan Bednarik wrote:
> I've started to use TV just recently, so I'm not sure about a lot of
> stuff. One thing that bothers me is that I've usually got about 3 or
> more TO with different content layout and when I want to change/add
> element that's common for all TO (such as footer, language selector), I
> need to go through all TO mappings and assign the new element manually.
> This gets really anoying with more than 3 TO. Is there a way how to add
> new element to DS easily without having to open all TO?

Two ways:
- use "Modify DS/TO" button
- edit DS XML manually

Adding a field to DS makes it available for evey TO associated with this DS

> Another thing is, that I start with one template, set all neccessary
> mapping. Then, I create another template and because I'm lazy, I copy
> the first template, so I don't have to set all common mapping again. The
> problem is, elements from first template, that are not present in the
> second template, give me warning, because they have their mapping set,
> but the element doesn't exist in the second template. And there's no way
> how to delete just some mappings and not all of them.

This question deserves to be in FAQ. Click "Ch.mode" and set mode to empty string.

--
Dmitry Dulepov
TYPO3 Core team
My TYPO3 book: http://www.packtpub.com/typo3-extens...velopment/book
In the blog: http://typo3bloke.net/pages/book-rev...garr-reynolds/
_______________________________________________
TYPO3-project-templavoila mailing list
TYPO3-project-templavoila (AT) lists...netfielders.de
http://lists.netfielders.de/cgi-bin/...ct-templavoila

> Two ways:
> - use "Modify DS/TO" button
> - edit DS XML manually
>
> Adding a field to DS makes it available for evey TO associated with this DS

That's OK. But now, with a new field, you have to go through all TO and
assign the new field. With more templates, this is really annoying.

I was thinking about creating a template the traditional way and using
TV just for the content part. This way I could add and remove template
elements easily without having to remap TO. But I'm not sure this can work.

--
Jan Bednarik
www.bednarik.org - web about Typo3 in czech
_______________________________________________
TYPO3-project-templavoila mailing list
TYPO3-project-templavoila (AT) lists...netfielders.de
http://lists.netfielders.de/cgi-bin/...ct-templavoila

Do you really need this many templates?
If - for example - your task is to have very similar templates, that
(again e.g.) only differ in the number of available columns, then you
should consider another approach:
Use just one page template, and then add FCEs that can be used as
content elements and that create different column layouts inside the
main template. If you are familiar with YAML have a look at how it uses
subtemplates to integrate into the main framework. The main YAML
framework would be your overall template, the subtemplates would be
realized as FCEs that create different floating column layouts. There is
even an extension (did not test it yet) that implements YAML with TV in
exactly this way. See http://yaml.t3net.de/Download.19.0.html?&L=1
(right now in German only).

Cheers,
Jörg.


Jan Bednarik schrieb:
>> Two ways:
>> - use "Modify DS/TO" button
>> - edit DS XML manually
>>
>> Adding a field to DS makes it available for evey TO associated with
>> this DS
>
> That's OK. But now, with a new field, you have to go through all TO and
> assign the new field. With more templates, this is really annoying.
>
> I was thinking about creating a template the traditional way and using
> TV just for the content part. This way I could add and remove template
> elements easily without having to remap TO. But I'm not sure this can work.
>
_______________________________________________
TYPO3-project-templavoila mailing list
TYPO3-project-templavoila (AT) lists...netfielders.de
http://lists.netfielders.de/cgi-bin/...ct-templavoila

Hi!

Jan Bednarik wrote:
> That's OK. But now, with a new field, you have to go through all TO and
> assign the new field. With more templates, this is really annoying.

There is no other way.

> I was thinking about creating a template the traditional way and using
> TV just for the content part. This way I could add and remove template
> elements easily without having to remap TO. But I'm not sure this can work.

No. You have to map fields with TV.

--
Dmitry Dulepov
TYPO3 Core team
My TYPO3 book: http://www.packtpub.com/typo3-extens...velopment/book
In the blog: http://typo3bloke.net/pages/book-rev...garr-reynolds/
_______________________________________________
TYPO3-project-templavoila mailing list
TYPO3-project-templavoila (AT) lists...netfielders.de
http://lists.netfielders.de/cgi-bin/...ct-templavoila

> Do you really need this many templates?

Well, sometimes I do.

> Use just one page template, and then add FCEs that can be used as
> content elements and that create different column layouts inside the
> main template. If you are familiar with YAML have a look at how it uses

Meaning, the whole page would contain just one element - FCE and all
elements (text, tables, forms) would be inside this FCE? This would be a
bit messy.

--
Jan Bednarik
www.bednarik.org - web about Typo3 in czech
_______________________________________________
TYPO3-project-templavoila mailing list
TYPO3-project-templavoila (AT) lists...netfielders.de
http://lists.netfielders.de/cgi-bin/...ct-templavoila

>> I was thinking about creating a template the traditional way and using
>> TV just for the content part. This way I could add and remove template
>> elements easily without having to remap TO. But I'm not sure this can
>> work.
>
> No. You have to map fields with TV.

You don't understand me, maybe. What I want to try is

page.10 = TEMPLATE
page.10.subparts.HEADER < lib.header

page.10.subparts.CONTENT < templa_voila

so, only content would be generated by TV. Is this possible? I'd have to
make sure that header parts and <body> element are not generated by TV.

--
Jan Bednarik
www.bednarik.org - web about Typo3 in czech
_______________________________________________
TYPO3-project-templavoila mailing list
TYPO3-project-templavoila (AT) lists...netfielders.de
http://lists.netfielders.de/cgi-bin/...ct-templavoila

Hi!

Jan Bednarik wrote:
> You don't understand me, maybe. What I want to try is
>
> page.10 = TEMPLATE
> page.10.subparts.HEADER < lib.header
>
> page.10.subparts.CONTENT < templa_voila
>
> so, only content would be generated by TV. Is this possible? I'd have to
> make sure that header parts and <body> element are not generated by TV.

Even if possible, it is not supported (and will not be).

--
Dmitry Dulepov
TYPO3 Core team
My TYPO3 book: http://www.packtpub.com/typo3-extens...velopment/book
In the blog: http://typo3bloke.net/pages/book-rev...garr-reynolds/
_______________________________________________
TYPO3-project-templavoila mailing list
TYPO3-project-templavoila (AT) lists...netfielders.de
http://lists.netfielders.de/cgi-bin/...ct-templavoila