Feeds:
RSS
Atom

There is one simple thing that you may forget in your RealURL configuration and it will screw up your sites.

If (1) you use have than one site in the page tree and (2) you have pages with the same path in both sites (like, /news/), you need to pay attention to one small detail: do not forget to configure all domains. For example, if you configured non-"www" domain but forgot to configure "www" domain, realurl will not be able to find correct page ID from URI when user visits "www" domain. User will either get "Page not found" or page from wrong domain (technically - page from the first domain in the tree, if page with such path exists). This is unavoidable limitation of RealURL.

If this error happens, you may see entries in RealURL error log for non-existing pages and RealURL 1.1.4 and newer will complain in admin panel about missing rootpage_id.

 

However, if you write your configuration correctly, you do not need to worry about it all. So always check your configuration carefully.

Like it? Then bookmark it! digg.comdel.icio.usgoogle.comMyLink.deYahooMyWebTechnoratiFurllive.comnetscapeTagThatWebnews

2 Comments

  1. on Wednesday, 24-01-07 05:00 Chris Paige
    I define all relevant domains in sys_domain already. Why do I have to define them again in realurl config?

    I'm sure there is a smart reason... but I wish realurl could look it up for me... or generate config code based on sys_domain... :)
  2. on Wednesday, 21-02-07 11:54 filter
    I ran in much harder problems when working with more then 1 language and realurl. It's urgent to use another browser (not tab) where your are not logged in backend to preview pages in a 2nd language. If you are logged in a browser and try to preview translated pages in another browser-tab you'll get unattended 404 errors. So it happens here using Firefox 1.5.0.9 on Dapper-Drake against a Typo3 4.0.5 with Real-Url 1.1.4 logged in backend as admin user. Took me hours to find out this very issue.

    polarizers 2 cent

Leave a Reply