Hi, On Fri, 2003-09-05 at 10:45, pp wrote: > > You then also need to alter the cache table in your midgard database: > > > > alter table cache add column style int(11) not null default 0; > > alter table cache drop primary key; > > alter table cache add primary key (page,type,style,id); > > > > Let me know if this solves your problem. > > I do not think if this really solves problem.
Very possible, hence the let me know if... > And I am almost sure that this fixing "--with-cache-fix" doesn't fix that at all > because it is designed to fix page caching when page has more than one style. > Frankly I have never seen any page which has more than one style.... Think of a page that has it's style set to inherited and is root-page to more than one host. It is possible. Anyway, I've been in a situation where updates to a page would be visible directly, but a change of style would only show after deleting all records in the cache table. This was with cache feature turned off! Using the --with-cache-fix option partly solved this issue. > I do use (quite seldom at all) midgard with all new features compiled in > for about two months , and had to turn off cache feature to get midgard work > properly... :( So we need to adress that. In a different situation I hacked mgd_cache_is_current to always return false. As a result, all cached pages are regenerated on every request, defeating the purpose of page caching almost completely. Almost, because you do get the error-messages that point to a line-number in a file that can be located in a proper way. I've been too pressed to further investigate the problem, and I gather that so have you (and others, anyone?). Solving this issue is however very important, imho. wkr, -- Envida http://www.envida.net/ Armand A. Verstappen Graadt van Roggenweg 328 [EMAIL PROTECTED] 3531 AH Utrecht tel: +31 (0)30 298 2255 Postbus 19127 fax: +31 (0)30 298 2111 3501 DC Utrecht
signature.asc
Description: This is a digitally signed message part
