From: Reini U. <ru...@x-...> - 2004-12-18 23:13:33
|
I've made available a patch against 1.2.5 for a needed phpwiki-1.2.6 release, which will fix the flatfile database setup. Without this patch, flatfile is not functional for FindPage and Backlinks. I've also added the MostPopular feature on flatfile. Just for convenience. http://sourceforge.net/tracker/index.php?func=detail&aid=1087720&group_id=6121&atid=306121 which fixes this bug: http://sourceforge.net/tracker/index.php?func=detail&aid=1079662&group_id=6121&atid=106121 If noone objects I will package a new 1.2.6 release within two days. Thanks a lot to some user named Raj! -- Reini Urban http://phpwiki.org/ |
From: Reini U. <ru...@x-...> - 2004-12-19 00:27:43
|
phpwiki-1.2.6 is a bugfix for the flatfile database backend only. Other backends are not affected. Fixed TitleSearch and Backlinks for flatfile. (Thanks to some user Raj) Enable MostPopular (hitcount storage) for flatfile. Note, that 1.2.x is not in active development, and probably insecure, but is 10x faster, 10x smaller and has 10x less features than the current 1.3.x development branch. A new 1.3.11 release will arrive soon. I found one more minor issue with serial dumps containing the string "Mime-Version: 1.0 (Produced by PhpWiki 1.1.x)" which was fixed to carry the current version number. Download: http://sourceforge.net/project/showfiles.php?group_id=6121&package_id=14187 in some hours at your nearest mirror. ChangeLog: 2004-12-19 01:02 rurban Release 1.2.6 * lib/db_filesystem: fix GetAllWikiPagenames() which broke TitleSearch and Backlinks on flatfile. Thanks to Raj sf bug #1079662. * lib/db_filesystem: add MostPopular functionality for flatfile. * admin/zip.php: bump version number Reini Urban schrieb: > I've made available a patch against 1.2.5 for a needed phpwiki-1.2.6 > release, which will fix the flatfile database setup. > Without this patch, flatfile is not functional for FindPage and Backlinks. > I've also added the MostPopular feature on flatfile. Just for convenience. > > http://sourceforge.net/tracker/index.php?func=detail&aid=1087720&group_id=6121&atid=306121 > > which fixes this bug: > http://sourceforge.net/tracker/index.php?func=detail&aid=1079662&group_id=6121&atid=106121 > > If noone objects I will package a new 1.2.6 release within two days. > Thanks a lot to some user named Raj! -- Reini Urban http://phpwiki.org/ |
From: Joel S. <jo...@OA...> - 2004-12-19 02:20:53
|
Reini Urban wrote: > Note, that 1.2.x is not in active development, and probably insecure, > but is 10x faster, 10x smaller and has 10x less features than the > current 1.3.x development branch. A new 1.3.11 release will arrive soon. I hate to ask this but will 1.3.11 address some of the weirdnesses with the authentication? That has been the only gripe I have really had with the rtems wiki (http://www.rtems.com/phpwiki). Someone mentioned some issues with internationalization. If you are interested in a description, I can get him to write them up. I think it starts with his name having a non-ASCI character in it. I am not complaining. Thanks for phpwiki. -- 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-12-19 12:47:29
|
Joel Sherrill <jo...@OA...> schrieb: > Reini Urban wrote: >> Note, that 1.2.x is not in active development, and probably insecure, >> but is 10x faster, 10x smaller and has 10x less features than the >> current 1.3.x development branch. A new 1.3.11 release will arrive soon. > > I hate to ask this but will 1.3.11 address some of the weirdnesses > with the authentication? That has been the only gripe I have > really had with the rtems wiki (http://www.rtems.com/phpwiki). Which problems? I know about httpauth not being working (got better, just the admin_user is ignored), PersonalPages problems (not being able to reproduce). Most problems so far are related to PASSWORD_LENGTH_MINIMUM = 0 (allowing empty passwords), or non-persistent sessions. (which has nothing to do with auth) I print now a warning for all methods if PASSWORD_LENGTH_MINIMUM is violated. Or using slow USER_AUTH_POLICY = old and having IMAP or other issues then (as in previous vesions also). > Someone mentioned some issues with internationalization. If you > are interested in a description, I can get him to write them up. > I think it starts with his name having a non-ASCI character in it. I remember. That's another issue I introduced lately and have to fix. The docs state that all i18n username wordchars are valid, and current code disallows them. For security concerns with certain methods. I'll re-enable them for some auth methods: class specific isValidName() Bogo and PersonalPage are safe. -- Reini Urban |