[TYPO3-dev] Switching to realUrl on an webpage existing for 4 year

["Christian Müller (Kitsunet)"]

On 21.11.2010 16:21, Steffen Ritter wrote:
> Am 21.11.2010 16:13, schrieb Steffen Gebert:
>> Have you thought of this way?
> Hi Steffen,
> yes I did, but what about MountPoints and Extensions?

What is the problem about that?

RewriteCond %{DOCUMENT_ROOT}%{REQUEST_FILENAME} !-f
RewriteCond %{DOCUMENT_ROOT}%{REQUEST_FILENAME} !-d
RewriteCond %{DOCUMENT_ROOT}%{REQUEST_FILENAME} !-l
RewriteRule ^/.+\.(.+)\.[0-9]\.html /index.php?id=$1 [R=301,L,QSA,NE]

Should work like a charm (taken from CoolURI manual). I used it in 
similar situations and had no problems.


> About the Duplicate Content we do not have to care... Most parts of the
> website is not known to Google anyways.
> It's in a very bad condition (missing title tags, no meta tags at any
> place, crappy html code, hardcoded index.php?id= links).
>
> The first rule is: the old hardcoded internal links have to work.
> Anything else could have been thought later of...
>
> Would be cool If I would have sth like this:
> If realUrl error, call classes of simulateStatic, decodeUrl, generate
> new realurl Link, save to RealUrl rewriteTable and redirect 301 to this
> page.

I guess you could do that with a custom RealURL advanced class and 
consider simulateStatic within. I have one project with my own realurl 
page path encoder/decoder and it can do magic things ;-)

Regards,
Christian