Torben Nehmer wrote: > Basically, it doesn't look like it works. On a first casual test, most > pages show up corrupted in another way it looks like the tag expansion > this time results in empty tags. This brings me (in Asgard) to the > point where I don't see the load of <[...]> in the output, but nothing > in place of it (the tables don't get built).
Are there entries in the cache table? > What is really strange is the following behavoir: To be sure, I tried > this: I cleaned up the page cache, clicked reload, and the output was > excellent, everything was fine. I clicked reload again, and I got the > currupted output again. The interesting thing is, that only the very > first request after the pagecache cleanup (with an simple rm -f *) > delivers a correct response. Even if a new page is requested, the > result is corrupt. Looks like the cache table is not being filled correctly. What you should have is: mysql> describe cache; +-----------+---------+------+-----+---------+-------+ | Field | Type | Null | Key | Default | Extra | +-----------+---------+------+-----+---------+-------+ | id | int(11) | | PRI | 0 | | | type | int(11) | | PRI | 0 | | | page | int(11) | | | 0 | | | sitegroup | int(11) | | | 0 | | +-----------+---------+------+-----+---------+-------+ 4 rows in set (0.00 sec) If not, drop the cache table and run database-upgrade. > 3. do a mv 37.php 37.backup in page-cache (which (theoretically) > empties the page cache) > 4. klick reload (Result corrupt!) > 5. Diff the new 37.php with the 37.backup file, no differences found. Somehow Midgard thinks that it doesn't need to walk the styles and reloads from the cache. If that cache is empty, what you describe sounds accurate. Look at the cache format, if it's the same we'll take it from there. Somehere during 1.4 development I changed the cache format, and they're not compatible. Emile --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
