From: David E. W. <da...@we...> - 2003-03-27 20:59:11
|
Steve, Thanks for getting back to me. Jeff and others - our company has vigorously adopted PHPWiki in part due to my strong recommendations and prior experience working with this wiki. We've encountered a number of issues with PHPWiki, however, the most serious by far being corruption of large documents. When we take a large wiki node, edit it, preview it, and save it, whole paragraphs are duplicated in the result. This is not operator error - it's happened several times, even from cut-and-pasting from a text editor window! I'm unclear as to what is causing this corruption, but it has rendered the wiki all but unuseable for large documents. There are other somewhat less serious issues, too -- when a wiki node has a large table in it (>200 rows) it simply freezes up the machine. PHP times out after 30 seconds and cancels the page load. "Document History" does not appear to work correctly for documents that have been edited a large number of times. (It does not show the most recent changes made.) Also, our listing of RecentChanges seems to have stopped about seven days ago. While these are all issues I'd like to see resolved, without the first -- namely fixing the corruption issue, we're going to have to switch to a different wiki. Have any of you guys seen this? Is this a misconfiguration? Is it a bug with an easy fix? We're using MySQL 3.23.49 as the backing store, PHP 4.3.1 with MySQL, Apache 2.0.43, and PEAR v1.50. This is using PHPWiki 1.3.4. One patch that you might want to know about (tiny) is in lib/config.php, where in order to support Apache2, this line: if (php_sapi_name() == 'apache') got changed to this line: if (php_sapi_name() == 'apache' || php_sapi_name() == 'apache2filter') Could it be something about our Apache2 interactions that's messing things up? Please help! :) Cheerio, Dave Weekly Developer, There.com ----- Original Message ----- From: "Steve Wainstead" <sw...@pa...> To: "David E. Weekly" <da...@we...> Cc: <php...@li...> Sent: Thursday, March 27, 2003 11:51 AM Subject: Re: Serious PHP Wiki Issue > > Good heavens! Did you post to phpwiki-talk? I haven't done any development > on PhpWiki in over a year, just doing the releases. Jeff Dairiki is the > principle architect over the last two years; I'm sure they can pinpoint > the problems very quickly! > > ~swain > > > On Thu, 27 Mar 2003, David E. Weekly wrote: > > > Steve, > > > > I need your help; our company is about to give up on PHP Wiki, declaring it > > "too broken to use"! It has been badly corrupting large files, freezing when > > tables get too large, etc. Please call me at (deleted by swain) as soon > as you > > can. I'd love to see PHP Wiki widely implemented, but I've seen these bugs > > and they're bad. > > > > Yours, > > David > > > > > > > > > > > > > > --- > http://www.panix.com/~swain/ > "Without music to decorate it, time is just a bunch of boring > production deadlines or dates by which bills must be paid." > -- Frank Zappa > |