[TYPO3] RealURL / cache_pages

[Dmitry Dulepov [typo3]]

Hi!

Vincent Mans wrote:
> This has led to a few questions:
> 1) Is it a feature that the page cache gets updated for a domain that
> doesn't exist in the TYPO3 environment? Especially for larger
> organisations with extensive pagetrees this page cache mechanism may
> cause trouble. Or is there a trick that I don't know of (who knows
> what I know)?

There are several points:
1. By default cache is enabled for performance reasons.
2. Really "real" URLs are created only if you use "tx_realurl_advanced" in pagePath. Otherwise you (meaning anyone actually) will see "/13/"-like path. May be it is time to use tx_realurl_advanced by default. In any case the majority uses it.

> 2) It's definitely a feature that a config for RealURL is needed, but
> are there plans to make it work differently? The rootpage ids and
> domains are already available through the database. Point is, to pick

Unfortunately it is not that easy. For now you have to specify domains and rootpage_id values. Remember that you can have different configurations for different domains (languages, postVars, etc). rootpage_id can be found through domain record but that adds extra query. I am against even a single extra query (performance!!!). It does not take much time to specify rootpage_id manually :)

> one, the divided roles in an organisation - the configfile may cause
> extra system admin work for people who are often extremely busy. And
> if they are, they don't understand why it works this way. Taking it
> further: wouldn't it be easier if RealURL was manageable through
> TypoScript, Page properties or a dedicated record at rootpage level?

Unfortunately (again!) it cannot be managable through TypoScript. When user comes to http://www.example.com/path/to/page/, there is no TypoScript. There is no even root page.

> On one hand, the autoconfig is already a very usefull tool, certainly
> for the defaults, but it may need a system admin action (at least to
> delete the file). But if it comes to tailor work config, then it's
> different. E.g. CoolURI chooses an XML file, which is not what I mean.
> I'm looking for consistency in backend activities.

You can also generate autoconfig in PHP format, copy it and adjust manually. But it has to be done someway. There is no magic in the world...

I can only try to simplify admin's life by providing better defaults. This is the idea you gave me :D Thanks to you, I will do it :)

-- 
Dmitry Dulepov
E-mail: dmitry at typo3.org
Skype: callto:liels_bugs
TYPO3 technical: http://typo3bloke.net/