[TYPO3-english] Realurl: Moving of pages

[Dmitry Dulepov]

Hi!

Steffen Gebert wrote:
> I guided a bigger client through the update to TYPO3 4.5. Additionally
> few other things were introduced, e.g. Caching Framework activation + a
> hand full of performance-related patches (one of them is a back-ported
> rootline cache from 6.0).
>
> They're now experiencing a nasty behaviour, which did not happen with 4.4:
>
> * Page A is created and shown in frontend
> * Page A is renamed to page B
> * A new page called A is created
> * Links to that page lead to the old page A (now B) instead of the new
> one, because the realurl caches are not up to date.

That's right :) Here is why.

When you rename page A to page B, RealURL will know and will update all 
cached records for page B with path /A to have expiration time. When the 
user comes to /A, it will redirect it to /B with 302 HTTP code. This is 
made to be Google-friendly (no rude 404s but polite 302s to the new 
location). It worked like this for years.

Now you create a new page A and expect it to be available at /A. But 
RealURL has a cache record for path /A, which points to B. Just creating a 
new A does not add /A to the cache. Thus, when you navigate to /A RealURL 
looks to the cache, finds a record with /A->/B there and redirects.

What can you do? Go to page B in Web>Info and remove all entries that say 
/A for it. That's all.

-- 
Dmitry Dulepov

Simplicity will save the world.