TYPO3 Mailingliste: nicht fragen - lesen!

Hello,

is there a way to restrict the allowed element types that can be used
within a CE field of an FCE?

E.g.:
I have an FCE with a CE field that can hold elements like "text",
"text-with-image", "image-only", ... or even other FCEs.
What I want is to limit the content elements that the user can select
from to a subset of all existing content elements, because in my
scenario only certain content elements make sense within that FCE.

Cheers, and thanks for your help,
Jörg.
_______________________________________________
TYPO3-project-templavoila mailing list
TYPO3-project-templavoila (AT) lists...netfielders.de
http://lists.netfielders.de/cgi-bin/...ct-templavoila

Hi!

Joerg Wagner wrote:
> is there a way to restrict the allowed element types that can be used
> within a CE field of an FCE?
>
> E.g.:
> I have an FCE with a CE field that can hold elements like "text",
> "text-with-image", "image-only", ... or even other FCEs.
> What I want is to limit the content elements that the user can select
> from to a subset of all existing content elements, because in my
> scenario only certain content elements make sense within that FCE.

No such way in TV

--
Dmitry Dulepov
http://typo3bloke.net/
_______________________________________________
TYPO3-project-templavoila mailing list
TYPO3-project-templavoila (AT) lists...netfielders.de
http://lists.netfielders.de/cgi-bin/...ct-templavoila

Hi Dmitry,

THX for your reply!
It's a pitty that there is no way to do that. In my context the
users/editors keep putting elements into the FCE's content field that do
not make any sense there - especially they tend to nest FCEs into each
other which just does not work in the DIV structure of the resulting
document.
It would have been great if I could have restricted the set of elements
that is presented to the user to fill a content element field in an FCE.

Well, maybe some day...
Do you think this qualifies for a feature request?

Cheers, Jörg.




Dmitry Dulepov [typo3] schrieb:
> Hi!
>
> Joerg Wagner wrote:
>> is there a way to restrict the allowed element types that can be used
>> within a CE field of an FCE?
>>
>> E.g.:
>> I have an FCE with a CE field that can hold elements like "text",
>> "text-with-image", "image-only", ... or even other FCEs.
>> What I want is to limit the content elements that the user can select
>> from to a subset of all existing content elements, because in my
>> scenario only certain content elements make sense within that FCE.
>
> No such way in TV
>
_______________________________________________
TYPO3-project-templavoila mailing list
TYPO3-project-templavoila (AT) lists...netfielders.de
http://lists.netfielders.de/cgi-bin/...ct-templavoila

Hi!

Joerg Wagner wrote:
> Well, maybe some day...
> Do you think this qualifies for a feature request?

Not really... You can disable page content types for users but globally in the system. TemplaVoila uses system "new content element" wizard.

--
Dmitry Dulepov
http://typo3bloke.net/
_______________________________________________
TYPO3-project-templavoila mailing list
TYPO3-project-templavoila (AT) lists...netfielders.de
http://lists.netfielders.de/cgi-bin/...ct-templavoila

On Wed, 25 Jun 2008 17:07:17 +0200, Joerg Wagner
<news.netfielders.de (AT) digilog (DOT) de> wrote:

> Hi Dmitry,
>
> THX for your reply!
> It's a pitty that there is no way to do that. In my context the
> users/editors keep putting elements into the FCE's content field that do
> not make any sense there - especially they tend to nest FCEs into each
> other which just does not work in the DIV structure of the resulting
> document.
> It would have been great if I could have restricted the set of elements
> that is presented to the user to fill a content element field in an FCE.
>
> Well, maybe some day...
> Do you think this qualifies for a feature request?
>
> Cheers, Jörg.

Hi Jörg,
you could apply some "red" warning color or so to the frontend view.
via CSS rules so your editors at least seeing that they doing "wrong".
not a perfect solution. but al little help for your editors.

like css rule like that sould do the trick this:
div.fce1 div.fce2 {border:10px solid #f00;}

greets chris

--
Christian Wolff // Berlin
http://www.connye.com

Latest Projects:
http://www.flycall.de | http://www.atr24.de | http://www.titanic.de
_______________________________________________
TYPO3-project-templavoila mailing list
TYPO3-project-templavoila (AT) lists...netfielders.de
http://lists.netfielders.de/cgi-bin/...ct-templavoila

Chris, this is a GREAT idea!
Will go that way. Thanks.

Cheers, Jörg.



Christian Wolff schrieb:
> On Wed, 25 Jun 2008 17:07:17 +0200, Joerg Wagner
> <news.netfielders.de (AT) digilog (DOT) de> wrote:
>
>> Hi Dmitry,
>>
>> THX for your reply!
>> It's a pitty that there is no way to do that. In my context the
>> users/editors keep putting elements into the FCE's content field that
>> do not make any sense there - especially they tend to nest FCEs into
>> each other which just does not work in the DIV structure of the
>> resulting document.
>> It would have been great if I could have restricted the set of
>> elements that is presented to the user to fill a content element field
>> in an FCE.
>>
>> Well, maybe some day...
>> Do you think this qualifies for a feature request?
>>
>> Cheers, Jörg.
>
> Hi Jörg,
> you could apply some "red" warning color or so to the frontend view.
> via CSS rules so your editors at least seeing that they doing "wrong".
> not a perfect solution. but al little help for your editors.
>
> like css rule like that sould do the trick this:
> div.fce1 div.fce2 {border:10px solid #f00;}
>
> greets chris
>
_______________________________________________
TYPO3-project-templavoila mailing list
TYPO3-project-templavoila (AT) lists...netfielders.de
http://lists.netfielders.de/cgi-bin/...ct-templavoila

Hi Dmitry,

> Not really... You can disable page content types for users but globally
> in the system. TemplaVoila uses system "new content element" wizard.

I think you got me wrong.
Generally disabling page content types is not what would help me. The
main problem is that an FCE is stacked within itself as a content
element. I cannot disable that FCE because using it as a content element
is a necessity, but NESTING it is an error.

Cheers,
Jörg.


Dmitry Dulepov [typo3] schrieb:
> Hi!
>
> Joerg Wagner wrote:
>> Well, maybe some day...
>> Do you think this qualifies for a feature request?
>
> Not really... You can disable page content types for users but globally
> in the system. TemplaVoila uses system "new content element" wizard.
>
_______________________________________________
TYPO3-project-templavoila mailing list
TYPO3-project-templavoila (AT) lists...netfielders.de
http://lists.netfielders.de/cgi-bin/...ct-templavoila

Seems there is a solution to control the nesting of TV FCEs showing up
on the horizon. "TemplaVoilÃ* Firewall" - a very handy title:
http://castor.t3o.punkt.de/files/tem...irewall_HD.mov

Looks like a great concept, solving in one elegant strike quite a bunch
of client usability problems associated with FCEs and CEs in general.

Cheers, Jörg.


Joerg Wagner schrieb:
> Hello,
>
> is there a way to restrict the allowed element types that can be used
> within a CE field of an FCE?
>
> E.g.:
> I have an FCE with a CE field that can hold elements like "text",
> "text-with-image", "image-only", ... or even other FCEs.
> What I want is to limit the content elements that the user can select
> from to a subset of all existing content elements, because in my
> scenario only certain content elements make sense within that FCE.
>
> Cheers, and thanks for your help,
> Jörg.
_______________________________________________
TYPO3-project-templavoila mailing list
TYPO3-project-templavoila (AT) lists...netfielders.de
http://lists.netfielders.de/cgi-bin/...ct-templavoila