Hi!

I tried the Fastest Cache hack in a site that really needed it ang got impressive results.

Then I found the bad news.

The site is uses xLanguage. xLanguage stores user language in a cookie, it doesn't modify the URL and the cache doesn't read it, so the cache doesn't know in what language is the page being requested.

So you're brwsing the site in spanish, then you go to a page that was cached in english,

OK, fixed.

Strategy number 2 worked like breeze.

I can't prepare a longer explanation now, as I'm doing a short trip, but anyone interested in GiJoe's Cache hack adapted for xLanguage, just send me a Private Message to Nachenko in xoops.org

GiJoe. mi modifications are just a bunch of lines of code, and my stuff is fully compatible with sites that don't have xLanguage installed. If you're interested, PM me in Xoops.org for details.

hi nachenko.

Quote:
No thank you

Because FCH can work fine with EMLH natively.

And I cannot have any interesting ML systems switching $xoopsConfig['language'] like xLanguage.

Such systems make the caching system of XOOPS non-sense.


EMLH is the only MultiLanguation can use caching system seamlessly.

Oh.

So no cache in xLanguage.

That explains a lot of things.

Thanks for the tip. You're right, EMLH is more simple, it just lacks a control panel, that's all.