Speaking of this "bug", I noticed that multiple extensions had similar issues when part of the page gets into parser cache before the data parsed for saved page does.

I tried to write quick-fix in the form of "Save and Refresh" extension and I couldn't make it work ("ArticleSaveComplete" hook simply didn't fire). Any idea how to make it happen?

It's a simple work-around for such problems until they are fixed in the core of the application - much better solution then disabling cache completely like many people do.

Will appreciate any help.

Thank you,

        Sergey


On Dec 18, 2007 2:22 AM, Markus Krötzsch <mak@aifb.uni-karlsruhe.de > wrote:
The issue with this is that all values move through the DB, i.e. when you
change a value it will be stored, but the result of the above query will not
have changed on the page yet. Another click on "refresh" (tab) or similar
action is needed to propagate the data to the query.

--
Sergey Chernyshev
http://www.sergeychernyshev.com/