> I am sorry for my tardiness with respect to giving you more > information. Things have been hectic here and my time at the office has > been limited.
No apologies, please - if the pace of my work on this project has been any yardstick, we're lucky we get anything done at all. :) > With newsletters turned off, flexwiki has remained stable. My > suggestion would be to include something in the read.me suggesting that > if you have runaway cpu turn off newsletters and come and post to the > mailing list. In this way any user that hits the issue (which may well > be related to the sheer size of my wiki, or incorrect configuration for > all I know at this stage) immediately has some way of counteracting it. > > I would say that it would be useful for some upgrade steps to be > included in the archive as I had to hunt round a bit to work out how to > upgrade from 1.8 I'll throw together a readme that mentions both the CPU/newsletter potential issue and upgrade steps. My plan is that later this week I'll make a new build that includes the readme and the current bits, and I'll push it out as FlexWiki 2.0 RTW. So if you don't want me to do that, speak up now. :) ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Flexwiki-users mailing list Flexwiki-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flexwiki-users
