Re: MasonHQ node caching, and other bugs

> > Are you still having this problem? If so, after editing and saving a
page,
> > check the node entry database to see if it has been updated. If not,
then
> > for some reason your query isn't being committed to the database. (Are
you
> > using a database with transactions?)
>
> I solved the problem by setting MaxrequestsPerChild to 1. But the site
> became very slow, so I would like to find other solution.
>
> I use mysql for storage. I'm fairly certain that data gets committed to db
> right after submitting web form.

You shouldn't have to set MaxRequestsPerChild to 1. Can you reproduce the
same bug on masonhq.com? If so, let me know the steps to do so. If not, then
it is something with your installation...

> Thanks. I have made several updates and it works fine. But it seems that
> the rules can over lap. I sometimes get Wiki words inside code tages. For
> example will [=/opt/SUNWabc] generate a wiki word.

Yeah, can't help you with that.

> > A better installation journal would be great. Actually this should
probably
> > be put on the wiki and linked from
http://masonhq.com/?SourceForThisSite, so
> > that it can be easily updated.
>
> Should I send my journal directly to you first?

Nope, just go ahead and post to the wiki!

Thanks
Jon



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click