Katja Lampela
>> I think the easiest way would be to restrict the
if you define
$TYPO3_CONF_VARS['BE']['defaultPageTSconfig'] in some localconf file
you can set for every page any page default TS config
That makes however definition vulnerable - easy to make syntax error.
I put into tm_contentacc
woops - sorry my thunderbird crashed and everything is messed up...
(says the great TYPO3 ;D
- katja
TYPO3 kirjoitti:
> I think the easiest way would be to restrict the root page's access and
> activate include subpages (or sthing like that)
> - Katja
>
>
> dave typo kirjoitti:
>> is there a way
I think the easiest way would be to restrict the root page's access and
activate include subpages (or sthing like that)
- Katja
dave typo kirjoitti:
> is there a way to set all of a site's pages require a specific
> front-end (not backend access) user login without individually setting
> this asp
dave typo wrote:
> is there a way to set all of a site's pages require a specific
> front-end (not backend access) user login without individually setting
> this aspect on each page?
>
> ie: is there a recursive setting for front end access??
You can set default values for any field (including th
dave typo kirjoitti:
> is there a way to set all of a site's pages require a specific
> front-end (not backend access) user login without individually setting
> this aspect on each page?
>
> ie: is there a recursive setting for front end access??
Yes - in page properties starting from root page o
is there a way to set all of a site's pages require a specific
front-end (not backend access) user login without individually setting
this aspect on each page?
ie: is there a recursive setting for front end access??
thanks
-dave
___
TYPO3-english mail
