From: Joel S. <jo...@OA...> - 2004-10-22 06:04:12
|
Hi, We are trying to use PhpWiki 1.3.10 for the RTEMS Wiki (http://www.rtems.org/phpwiki) and are having a number of problems. Our content is growing quickly and I want to resolve the issues. Any help/advice we can get would be most appreciated. Some are certainly ignorance on my part, while I am not sure of the others. We are using MySQL as the database for content and that works fine. First, we do not seem to be able to get any password setup to work. If someone sets it in their preferences, and doesn't edit their personal page, they get locked out. At one point I had the Administrator password working but now I am so confused, it doesn't even work. I added an .htpasswd on a dummy page to force a login as the admin account and think that matches the settings in config.php. Here is another random issue from a user > >>I think I broke my wiki account. I set my preferences for sidebar display >>and now whenever I try to login I get : >>Fatal error: Call to a member function on a non-object in >>/home/rtems/phpwiki/themes/Sidebar/themeinfo.php on line 37 >>I don't seem to be able to change my preferences. >> I also have seen a random entry from an arbitrary IP address so I think some spammers have figure out how to automatically add Wiki entries. ;( I have seen this on PhpBB sites so it didn't surprise me. -- Joel Sherrill, Ph.D. Director of Research & Development jo...@OA... On-Line Applications Research Ask me about RTEMS: a free RTOS Huntsville AL 35805 Support Available (256) 722-9985 |
From: ReymanX <re...@gm...> - 2004-10-22 06:27:17
|
> First, we do not seem to be able to get any password > setup to work. If someone sets it in their preferences, > and doesn't edit their personal page, they get locked out. I have the same problem before, then I upgrade to phpwiki-1.3.11pre from CVS. I use to use suse 9.1 with apache 2.0, but it's not working. Then I use debian with apache 1.3.x, it's work now. -- Arie Reynaldi Zanahar reymanx at gmail.com http://www.reynaldi.com |
From: Joel S. <jo...@OA...> - 2004-10-22 14:15:45
|
ReymanX wrote: >>First, we do not seem to be able to get any password >>setup to work. If someone sets it in their preferences, >>and doesn't edit their personal page, they get locked out. > > > I have the same problem before, then I upgrade to phpwiki-1.3.11pre > from CVS. I use to use suse 9.1 with apache 2.0, but it's not working. > Then I use debian with apache 1.3.x, it's work now. As I mentioned in another email, we are using Fedora Core 1 which includes Apache 2.0. This is not the only thing hosted on this machine so switching versions or distributions is not something we would undertake lightly. I just reported that we are having all sorts of weird problems with preferences. :( -- Joel Sherrill, Ph.D. Director of Research & Development jo...@OA... On-Line Applications Research Ask me about RTEMS: a free RTOS Huntsville AL 35805 Support Available (256) 722-9985 |
From: Reini U. <ru...@x-...> - 2004-10-22 16:36:07
|
Joel Sherrill <jo...@OA...> schrieb: > ReymanX wrote: >>> First, we do not seem to be able to get any password >>> setup to work. If someone sets it in their preferences, >>> and doesn't edit their personal page, they get locked out. >> >> I have the same problem before, then I upgrade to phpwiki-1.3.11pre >> from CVS. I use to use suse 9.1 with apache 2.0, but it's not working. >> Then I use debian with apache 1.3.x, it's work now. > > As I mentioned in another email, we are using Fedora Core 1 > which includes Apache 2.0. This is not the only thing hosted > on this machine so switching versions or distributions is > not something we would undertake lightly. > > I just reported that we are having all sorts of weird problems > with preferences. :( yes, we know that > 1.3.8 doesn't work whth fedora core yet. strange apache2 issue. I got it working somehow previously but It was a major hack described somewhere. or use an older release. I'll look into these apache2 issues soon. first let me finish my testsuite for the more important errors. BTW: I had to switch http://phpwiki.sf.net/phpwiki back to the old mysql version. with gdbm and this php I got no sessions working. and the db is sometimes in a stale lock state. -- Reini Urban http://xarch.tu-graz.ac.at/home/rurban/ |
From: Reini U. <ru...@x-...> - 2004-10-23 13:18:46
|
Reini Urban schrieb: > Joel Sherrill <jo...@OA...> schrieb: >> ReymanX wrote: >> >>>> First, we do not seem to be able to get any password >>>> setup to work. If someone sets it in their preferences, >>>> and doesn't edit their personal page, they get locked out. >>> >>> >>> I have the same problem before, then I upgrade to phpwiki-1.3.11pre >>> from CVS. I use to use suse 9.1 with apache 2.0, but it's not working. >>> Then I use debian with apache 1.3.x, it's work now. >> >> >> As I mentioned in another email, we are using Fedora Core 1 >> which includes Apache 2.0. This is not the only thing hosted >> on this machine so switching versions or distributions is >> not something we would undertake lightly. >> >> I just reported that we are having all sorts of weird problems >> with preferences. :( > > > yes, > we know that > 1.3.8 doesn't work whth fedora core yet. > strange apache2 issue. > > I got it working somehow previously but It was a major hack described > somewhere. > or use an older release. > > I'll look into these apache2 issues soon. first let me finish my > testsuite for the more important errors. Well, this problem raised its importance from low-scale to highest, since this is the new configuration we'll have to deal with at the news sf.net web servers. The new sf.net will have fedora (oh my god! from debian to fedora), Apache 2 and php-4.3.8. Still with the pcre problems, but 4.3.8 has more effective memory handling than 4.1.x. It needs 2MB less. > BTW: I had to switch http://phpwiki.sf.net/phpwiki back to the old mysql > version. with gdbm and this php I got no sessions working. and the db is > sometimes in a stale lock state. The gdbm locking problems seems to be serious, since gdbm is vastly preferred over anything else. (See http://phpwiki.org/PhpMemoryExhausted/Testresults) At least php-4.3.x with gdbm will now support file-level locking, so our own software locks are not be that critical anymore. (stale locks after errors) Those session problems are typical if USECACHE is off. Then ob buffering is ineffective, and the session cookies are not handled properly, since some part already printed some character. -- Reini Urban http://phpwiki.org/ |