[TYPO3-mvc] Feature: automatic target page determination

Franz Koch typo3.RemoveForMessage at elements-net.de
Thu Aug 5 11:10:30 CEST 2010


Hey,

>>>> you also have to consider multi-domain setups, so the query should also
>>>> be restricted to the rootpage (if defined).
>>>
>>> I guess this would be possible, but then it would add a complexity that
>>> isn't really needed. The "auto" setup is for a simple scenario. The
>>> multi-domain setup could still require setting the pids manually. But I
>>> am ok if Bastian wants to enhance the auto-setup to handle even more
>>> scenarios. :)
>>
>> well, for editors (those are the guys the auto setup is meant for,
>> right?) their website (in a multidomain setup) still could be a simple
>> website and might not look different then other websites they maintain,
>> but then would wonder why it's working on one website and not the other.
>
> An editor is not the one that set up plugins and configures extensions,
> right? The admin that set up the multi-domain site is the one that knows
> that his site is more "complex" and requires setting the pids.

An editor is not setting up the plugin - but he might be allowed to 
place plugins on the website. I currently have a situation, where a 
commune is allowing urban districts to build their website with the 
TYPO3 installation of the commune itself. So this is a) a multidomain 
setup and b) the districts can build up their website as they like 
(content wise) and thus I can't preconfigure all plugins as I f.e. don't 
know their future website structure and thus can't preconfigure viewPids 
etc.

So in those cases, the editors decide how the plugins are used, and for 
those scenarios the magic also has to work then. I agree that those are 
special scenarios, but they are possible and thus should also be 
supported (and it's not that hard to accomplish though)


> A simple "admin" would be a newby to the scene, installing TYPO3,
> installing some extension and adding the plugins to some pages. It
> works! He is far from making a multi-domain page tree. :)

sure, but there are situations where the site structure is up to the 
editors and even a 1337 admin can't preconfigure everything (see example 
above).

-- 
kind regards,
Franz Koch


More information about the TYPO3-project-typo3v4mvc mailing list