Feeds:
RSS
Atom
RDF

How to fill RealURL cache

15. July 2008 by Dmitry Dulepov
Submitting your vote...
Rating: 4.5 of 5. 2 vote(s).
Click the rating bar to rate this item.

From time to time I see this question: how to fill RealURL cache with page addresses?

The answer is pretty simple. Make a new "hide in menu" page. Insert Sitemap there. Logout from Backend. Enter that new page address in the browser bar.

Notice that logging out is essential. RealURL will not cache anything if you are logged in to Backend.

This procedure will fill cache with page addresses. But it will not create cached entries for stuff like tt_news. So this tip is good if you have mostly pages.

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

5 Comments

  1. on Wednesday, 16-07-08 02:02 Nathan
    I have used this extension and it will fill the cache (even of just a branch) without logout of backend:

    fb_realurl_tweak
  2. on Wednesday, 16-07-08 10:26 Jonas
    Nice tip. Easy but powerfull.

    By the way. We use a realurl patch extension (just for us) which does nothing else than telling realurl that your not logged in even if your logged in.

    The reason is that if you open a page logged in into the backend and it gets cached, the realurls won't be cached. Now if you go on this page without logging in, the links won't work because they are not newly generated.

    This patch works great, and solves a lot of problems.
  3. on Wednesday, 16-07-08 17:37 Dmitry Dulepov
    Caching while IN BE is disabled because you can have hidden pages or pages with time simulation. RealURL cannot handle it, so it can create wrong page links. The whole issue is very complex, so the safest thing was to disable caching for logged in users at all.
  4. on Monday, 21-07-08 10:04 Jonas
    I know that, we discussed it on the dev days in 07 (or 06).

    The point is that it's a worse problem to have links which are not working, cause page is cached and realurl not, than to have some realurls in the cache somewhere which belong to hidden / disabled pages. In the end even if you have the realurl cached link you can not open the page, cause it's hidden/disabled. Is there some crash in this case?
  5. on Monday, 21-07-08 12:59 Dmitry Dulepov
    There is more. Suppose you have a page whose URl should look like /page1/page2/page3. Page3 is hidden, you are working on it and you can see it when logged in to BE. The problem is: sometimes you can get /page1/page2 cached as path to Page3. Next, when you unhide the page, all links to this page will lead to its parent.

    It is not clear to me when it happens. I had this problem for months on two servers (many sites on each server) but I could not catch it in development environment. The only way to stop it, was disabling caching when logged in to BE.

    I think having this problem is much much worse than disabled cache.

Leave a Reply