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.<br><br>I tried to write quick-fix in the
form of &quot;Save and Refresh&quot; extension and I couldn&#39;t make it work
(&quot;ArticleSaveComplete&quot; hook simply didn&#39;t fire). Any idea how to make
it happen?
<br><br>It&#39;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.<br><br>Will appreciate any help.<br><br>
Thank you,<br><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Sergey<div><br><div class="Ih2E3d"><br><div class="gmail_quote">On Dec 18, 2007 2:22 AM, Markus Krötzsch &lt;<a href="mailto:mak@aifb.uni-karlsruhe.de" target="_blank">mak@aifb.uni-karlsruhe.de</a>
&gt; wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The issue with this is that all values move through the DB, i.e. when you<br>change a value it will be stored, but the result of the above query will not<br>have changed on the page yet. Another click on &quot;refresh&quot; (tab) or similar
<br>action is needed to propagate the data to the query.<br></blockquote></div><br></div></div><font color="#888888">-- <br>Sergey Chernyshev<br><a href="http://www.sergeychernyshev.com/" target="_blank">http://www.sergeychernyshev.com/
</a>
</font>