phpwiki-talk

Re: [Phpwiki-talk] 1.3.10 - config.ini location

[Matthew P. <mp...@he...>]

On Fri, May 14, 2004 at 03:53:45PM +1200, Jim Cheetham wrote:
> I don't feel very confortable about allowing that file to be returned by
> the web server, so I moved mine outside the DocumentRoot for my site,
> and amended the wiki index.php :-
> 
> #IniConfig(dirname(__FILE__)."/config/config.ini");
> IniConfig("/var/www/docs/<site>/wiki-config.ini");

I'd recommend placing it in /etc/phpwiki, along with the apache config
snippet and any other relevant files.  That's a nice default, BTW. 
Alternatively, you could .htaccess the config directory out of reach of web
browsers.

- Matt


-- 
"Alas, slideware often reduces the analytical quality of presentations. In
particular, the popular PowerPoint templates (ready-made designs) usually
weaken verbal and spatial reasoning, and almost always corrupt statistical
analysis." -- http://www.edwardtufte.com/tufte/books_pp

Re: [Phpwiki-talk] 1.3.10 - imagecache.php problem

[Jim C. <ji...@iN...>]

On Fri, 2004-05-14 at 16:30, Jim Cheetham wrote:
> Having done that, plugin CacheTest will work.
> VisualWiki doesn't yet, but I'll get there!

Bah, silly boy ... default path for 'dot' was /usr/local/bin/dot, and my
installation (Debian) has it in /usr/bin/dot. False alarm :-)
-- 
-jim cheetham  ::  ji...@iN...  ::   m+64 21 177 8606
iNode :: effective computing in an interconnected world

[Phpwiki-talk] 1.3.10 - imagecache.php problem

[Jim C. <ji...@iN...>]

In ~wiki/lib/imagecache.php, you need to change line 28:
#include "lib/config.php";
include_once "lib/config.php";

or else you get an error about redeclaration of check_php_version

Having done that, plugin CacheTest will work.
VisualWiki doesn't yet, but I'll get there!
-- 
-jim cheetham  ::  ji...@iN...  ::   m+64 21 177 8606
iNode :: effective computing in an interconnected world

[Phpwiki-talk] 1.3.10 - config.ini location

[Jim C. <ji...@iN...>]

By default, the 1.3.10 config.ini is placed within the public webspace
for the wiki.

This means that it can be retrieved by anyone asking for
http://<wikiname>/config/config.ini

I don't feel very confortable about allowing that file to be returned by
the web server, so I moved mine outside the DocumentRoot for my site,
and amended the wiki index.php :-

#IniConfig(dirname(__FILE__)."/config/config.ini");
IniConfig("/var/www/docs/<site>/wiki-config.ini");

Now, I expect that as PHP has to read this file, Apache can access it
too, but because it's not within the DocumentRoot (in my case
/var/www/docs/<site>/www) it is protected well-enough.

The most sensitive piece of data in there would be the dsn password,
which should have been locked down to the webhost only anyway, but that
won't protect against users who share a common machine with others.
-- 
-jim cheetham  ::  ji...@iN...  ::   m+64 21 177 8606
iNode :: effective computing in an interconnected world

[Phpwiki-talk] CVS oopses, version guessing and vhost strangeness

[bishop <bi...@pl...>]

Reini, everyone,

I have a small cron job that syncs and rolls an RPM package from CVS. 
It started whining with noises like this, sometime this week:

> --------
> cvs update: failed to create lock directory for `/cvsroot/phpwiki/phpwiki/themes/Crao' (/cvsroot/phpwiki/phpwiki/themes/Crao/#cvs.lock): Permission denied
> cvs update: failed to obtain dir lock in repository `/cvsroot/phpwiki/phpwiki/themes/Crao'
> cvs [update aborted]: read lock failed - giving up

Was there a dir created there that is, for some reason, unreadable for 
anon cvsers?

Also, I'm picking up and setting the version in the SPEC for the RPM 
from this line of configurator.php:

> define ('PHPWIKI_VERSION', '1.3.8pre');

Since 1.3.10 is out I'm thinking I'm triggering on the wrong bit of the 
wrong file.  Help me out while I've got 30 seconds of spare time this 
week and tell me where I should be awking?

Thanks ever so much.  When I get back into the swing of things (or out 
of them, depending on the viewpoint), I'd like to re-examine the idea of 
one installed phpwiki and complete configuration for many vhost sites 
through some 10-line file in the http vhost root, like the attempt at 
the URL below.  Anyone doing this completely successfully, AND doing the 
USE_PATH_INFO hack to avoid the wiki.php?chapter bit?

http://cvs.platypus.bc.ca/cgi-bin/viewcvs.cgi/bishop/sites/wiki.mythtv.org/wiki?rev=1.20&content-type=text/vnd.viewcvs-markup
(that site was only a test)

Sorry I'm so out of touch.  It's that work thing.

  - bish

-- 
	WAP is the sound a clunky Internet-enabled cellphone makes
	when you throw it at a brick wall in frustration.
				 -- 'Frozen North'
	http://www.kuro5hin.org/story/2003/11/14/173126/56

[Phpwiki-talk] =?windows-1251?B?0eTl6+DpIO/g8+fzLi4uICAgLy/v8O7h6PDg//H8IOzl5uTzIOfl6+Xt?= =?windows-1251?B?++zoIOL78e7q6Ozo?=

[Ignite S. H. <dpa...@ma...>]

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4=2e0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3dContent-Type content=3d"text/html; charset=3dwindows-1=
251">
<META content=3d"MSHTML 6=2e00=2e2737=2e800" name=3dGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3d#ffffff>
<DIV><FONT face=3dArial size=3d1><IMG alt=3d"" hspace=3d0=20
src=3d"cid:feral=2ejpg" align=3dbaseline=20
border=3d0></FONT></DIV>
<DIV><FONT face=3dArial size=3d1></FONT>&nbsp;</DIV>
<DIV><FONT face=3dArial=20
size=3d1>=ea=ee=f2=ee=f0=fb=f5  =eb=e5=f2=ee=ec  =ed=e5 =e1=fb=e2=e0=e5=f2=
  =ea=e0=ef=eb=e8  =e2=ee=e4=fb;  =e2 =fd=f2=ee  </FONT></DIV></BODY></HT=
ML>

[Phpwiki-talk] =?windows-1251?B?0ejx8uXs+yDu8u7v6+Xt6P8sIOrg7eDr6Ofg9ujoLCDi7uTu8e3g4ebl?= =?windows-1251?B?7ej/ICAgICAgICDw4PHy7u/r5e3t++wg7ODx6+7sLCDq4Oog7+Xw5e/l?= =?windows-1251?B?6+7qLiDP7vHz5PMg5O7r5u3uIA==?=

[Armory O. A. <jo...@as...>]

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4=2e0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3dContent-Type content=3d"text/html; charset=3dwindows-1=
251">
<META content=3d"MSHTML 6=2e00=2e2737=2e800" name=3dGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3d#ffffff>
<DIV><FONT face=3dArial size=3d1><IMG alt=3d"" hspace=3d0=20
src=3d"cid:whippet=2ejpg" align=3dbaseline=20
border=3d0></FONT></DIV>
<DIV><FONT face=3dArial size=3d1></FONT>&nbsp;</DIV>
<DIV><FONT face=3dArial=20
size=3d1>=ea=f0=f3=ef=ed=ee=e9 =e4=e2=ee=f0=ee=e2=ee=e9  =f3=f2=ea=e8; =ef=
=e5=f0=fc=ff  =e8=ec=e5=eb=e0  =f1=e2=e5=f2=eb=ee-</FONT></DIV></BODY></H=
TML>

Re: [Phpwiki-talk] 1.3.10 released

[Rob F. <rfu...@dr...>]

Rob Fulwell wrote:
> http://prdownloads.sourceforge.net/phpwiki/phpwiki-1.3.10.tar.gz
> This file is only 12K?  Previous releases have been 4-7MB...
> Perhaps that file is only patches?

My mistake, please ignore me.

Rob.

Re: [Phpwiki-talk] 1.3.10 released

[Rob F. <rfu...@dr...>]

Reini Urban wrote:
> Just get the released tar.gz, though Carsten has just entered some 
> missing MacOSX buttons into CVS.

http://prdownloads.sourceforge.net/phpwiki/phpwiki-1.3.10.tar.gz

This file is only 12K?  Previous releases have been 4-7MB...

Perhaps that file is only patches?

Rob.

Re: [Phpwiki-talk] 1.3.10 released

[Reini U. <ru...@x-...>]

John Cole schrieb:
> Reini,
>   I'm having trouble getting the 1.3.10 or later version from cvs.  I get
> the following error:
> 
> cvs checkout: Updating phpwiki/themes/Crao
> cvs checkout: failed to create lock directory for
> `/cvsroot/phpwiki/phpwiki/them
> es/Crao' (/cvsroot/phpwiki/phpwiki/themes/Crao/#cvs.lock): Permission denied
> cvs checkout: failed to obtain dir lock in repository
> `/cvsroot/phpwiki/phpwiki/
> themes/Crao'
> cvs [checkout aborted]: read lock failed - giving up

Oops.
This will need some time, because this has to be fixed by the sf.net 
admins. Normally two days.

Just get the released tar.gz, though Carsten has just entered some 
missing MacOSX buttons into CVS.
-- 
Reini Urban
http://phpwiki.sf.net/

[Phpwiki-talk] 1.3.10 released

[Reini U. <ru...@x-...>]

1.3.10 is released.
See http://phpwiki.sourceforge.net/demo/en/ReleaseNotes
and http://phpwiki.sourceforge.net/demo/ChangeLog

The main phpwiki site was also updated from 1.3.7 to the current 1.3.10 
release, keeping the MacOSX theme.
   http://phpwiki.sourceforge.net/phpwiki/
So it's easier to document the current features with actually working 
examples.

Some bugs haven't been fixed and some planned features haven't been 
added yet. See http://phpwiki.sourceforge.net/phpwiki/DevelopmentBranch 
for the RoadMap.
But since 1.3.9 had a permission problem with anon edit I thought it was 
appropriate to release the current stable and tested version. Only very 
few did the 1.3.9-p1 patch on public sites.

from UPGRADING:

UPGRADING from 1.3.9

At first you have to manually create a config/config.ini based on
config-dist.ini and your previous index.php. We don't have a script yet,
to do that automatically.

mysql:
   ALTER TABLE page CHANGE id id INT NOT NULL AUTO_INCREMENT;
NOTE: ?action=upgrade does this also, if your mysql user has the
       ALTER permissions.

UPGRADING from 1.3.7

mysql + postgres:
   ALTER TABLE session ADD sess_ip CHAR(15) NOT NULL;
   CREATE INDEX sess_date ON session (sess_date);

postgres:
   New pref and session tables have been added for more
   efficiency.

user and themes:

WikiUser and signin.tmpl changed from $user->getId() to
$user->getAuthenticatedId()
Authenticated reflects the level (confirmed by password),
Signed just the username (possibly by cookie only)

pgsrc:

To upgrade not-existing pages add "?action=upgrade" to
your HomePage url and press "Enter", which will
add all fresh pages from pgsrc to your pageset.
If you deleted some pages on purpose, you'll have to removed
them again with PhpWikiAdminisstration/Remove then.

-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

[Phpwiki-talk] =?utf-8?B?6K2m5ZGK77ya6YKu5Lu25ZCr5pyJ55eF5q+S77yB?=

[<ad...@sm...>]

MjAwNC0wNS0xMyAwMzo0NDowN+WPkemAgee7mWd1b21pbkBteC5jZWkuZ292LmNuO+eahOmCruS7
tuS4reeahOmZhOS7tlttZXNzYWdlLnNjcl3lkKvmnInnl4Xmr5JbbWVzc2FnZS5zY3I6VzMyL05l
dHNreS1QXeOAggoK5Y+R5L+h5Lq677yacGhwd2lraS10YWxrQGxpc3RzLnNvdXJjZWZvcmdlLm5l
dArpgq7ku7bkuLvpopjvvJpNYWlsIERlbGl2ZXJ5IChmYWlsdXJlIGd1b21pbkBteC5jZWkuZ292
LmNuKQrpmYTku7YgW21lc3NhZ2Uuc2NyXeWQq+acieeXheavklttZXNzYWdlLnNjcjpXMzIvTmV0
c2t5LVBdCuWuieWFqOmCruS7tue9keWFs+WvueeXheavkuaJgOWBmueahOaTjeS9nOaYr++8mmtl
ZXAK6L+H5ruk5Zmo6Kem5ZCN56ew77yaQW50aS12aXJ1cwrlronlhajpgq7ku7bnvZHlhbPlr7np
gq7ku7bmiYDlgZrnmoTmk43kvZzmmK/vvJpOb3RpZmljYXRpb247UXVhcmFudGluZSA=

Re: [Phpwiki-talk] very nice new theme but...

[Reini U. <ru...@x-...>]

Norberto Meijome schrieb:
> FWIW, I've asked one of our graphic designers to take a look @ it - 
> can't promise any time frame, but hopefully he can "fix" it up.
> 
 >> Reini:
>> Someone deeply familiar with this kind of IE CSS position:absolute 
>> problem should look at this. I searched the lists, but found nothing 
>> really appropriate. Maybe it must be rewritten or worked around with 
>> the dynamic isBrowserIE() function.
>>
>> I had to change width to 30% instead of auto for IE, but the icon 
>> alignment is still broken.

I fixes the IE problems with the button alignment by using a class 
instead of an ID for IE. It looks now the same as Gecko, but the only 
remaining problem is that is not fixed, it is absolute. That means, if 
you scroll the actionbar stays at the same position, with gecko it's 
always at the bottom.

The pagelists are also not okay yet.

http://phpwiki.sourceforge.net/demo/crao/

-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Re: [Phpwiki-talk] IE CSS

[Whit B. <wh...@tr...>]

More info on problems with position:absolute in different browsers:

http://www.positioniseverything.net/abs_relbugs.html 

- there's a hack for IE/Win suggested at the end of the page

and 

http://www.positioniseverything.net/posbugs.html

- there are problems with older Opera &c. too.

Whit

Re: [Phpwiki-talk] IE CSS

[Whit B. <wh...@tr...>]

Looking more closely at Edwards' fix, it does concern itself with MS's "box
model", and from discussion elsewhere it looks like the position:absolute
problem is an MS box model failing, so this _might_ really help here (for IE
>= 5.5). 

On Wed, May 12, 2004 at 12:05:15PM -0400, Whit Blauvelt wrote:
> It doesn't address this particular problem, but Dean Edwards has fixed some
> of the IE CSS issues using DHTML through an initial CSS stylesheet. See
> http://dean.edwards.name/IE7/intro/. Could there be a way to extend his
> approach to this current problem?

[Phpwiki-talk] IE CSS

[Whit B. <wh...@tr...>]

It doesn't address this particular problem, but Dean Edwards has fixed some
of the IE CSS issues using DHTML through an initial CSS stylesheet. See
http://dean.edwards.name/IE7/intro/. Could there be a way to extend his
approach to this current problem?

Whit

Re: [Phpwiki-talk] very nice new theme but...

[Norberto M. <nu...@me...>]

definitely very nice theme :-)

FWIW, I've asked one of our graphic designers to take a look @ it - 
can't promise any time frame, but hopefully he can "fix" it up.

Cheers,
Beto

Reini Urban wrote:

> Rob Fulwell schrieb:
>
>> I really like the new Crao theme:
>> http://phpwiki.sourceforge.net/demo/crao
>>
>> Too bad that slick docked buttonbar totally breaks on Internet 
>> Explorer (I took quick look with version 6).  I know this is due to 
>> IE not implementing (CSS?) properly but it still means I can't really 
>> use this theme on my site.
>>
>> Anyway, I would like to congratulate whoever is responsible for a 
>> slick, clean new interface to the Wiki and I hope there may be more 
>> to come in this vein.
>
>
> Someone deeply familiar with this kind of IE CSS position:absolute 
> problem should look at this. I searched the lists, but found nothing 
> really appropriate. Maybe it must be rewritten or worked around with 
> the dynamic isBrowserIE() function.
>
> I had to change width to 30% instead of auto for IE, but the icon 
> alignment is still broken.
>
> That's why I put it onto http://phpwiki.sourceforge.net/demo/crao but 
> cannot commit into CVS.


-- 
Norberto Meijome | numard at meijome dot net
"Everything is interesting if you go into it deeply enough." - Richard Feynman

Re: [Phpwiki-talk] User authentication patch

[Reini U. <ru...@x-...>]

Dan Frankowski schrieb:
> I was having a problem. I have a Phpwiki 1.3.9+ site. It has a .htaccess 
> file with a single username/password pair. The intent is that once you 
> enter that site-wide user/pw, each editor then logs in with their own 
> WikiWord to have the right tracking in the change logs. Only for some 
> reason you had to log on for each page, hence over and over again. I 
> found out why: the Apache-authenticated user was being taken before the 
> login provided by the user in the Phpwiki "Sign in as:" window. This was 
> wrong for me, I attach a patch below.
> 
> My index.php auth settings are:
>        $USER_AUTH_ORDER =
>            array(
>                  "PersonalPage",
>                  "Db",
>                  ) ;

Why don't you use "File", with AUTH_USER_FILE = /your/.htaccess
apache auth is always before phpwiki auth.

> Perhaps my index.php authentication settings should be different, but it 
> still seems to me the Phpwiki login should trump the .htaccess login .. 
> hmm, maybe not always? Could I fake my way in with a trumped-up cookie?

You could fake the userid with the cookie, but not the authentication 
setting, the _level. So you are signed, but not authenticated.

Otherwise, if you prefer to always have the server auth prompt, your 
patch is okay.

> diff -b -u -r1.3 main.php
> --- main.php    14 Apr 2004 21:57:25 -0000      1.3
> +++ main.php    11 May 2004 18:01:21 -0000
> @@ -568,12 +568,15 @@
>     }
> 
>     function _deduceUsername() {
> +        // User login on the Wiki page.
> +        //
> +        // DSF: Overrides browser pop-up window, to allow the whole 
> site to
> +        // be behind browser authentication with one username/pw, then
> +        // each page editor to have their own login.
> +        //
> +
>         if (!empty($this->args['auth']) and 
> !empty($this->args['auth']['userid']))
>             return $this->args['auth']['userid'];
> -        if (!empty($_SERVER['PHP_AUTH_USER']))
> -            return $_SERVER['PHP_AUTH_USER'];
> -        if (!empty($_ENV['REMOTE_USER']))
> -            return $_ENV['REMOTE_USER'];
> 
>         if ($user = $this->getSessionVar('wiki_user')) {
>             $this->_user = $user;
> @@ -586,6 +589,14 @@
>                 return $userid;
>             }
>         }
> +
> +        // User login through a browser pop-up window
> +        if (!empty($_ENV['REMOTE_USER']))
> +            return $_ENV['REMOTE_USER'];
> +
> +        if (!empty($_SERVER['PHP_AUTH_USER']))
> +            return $_SERVER['PHP_AUTH_USER'];
> +
>         return false;
>     }
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Re: [Phpwiki-talk] very nice new theme but...

[Reini U. <ru...@x-...>]

Rob Fulwell schrieb:

> I really like the new Crao theme:
> http://phpwiki.sourceforge.net/demo/crao
> 
> Too bad that slick docked buttonbar totally breaks on Internet Explorer 
> (I took quick look with version 6).  I know this is due to IE not 
> implementing (CSS?) properly but it still means I can't really use this 
> theme on my site.
> 
> Anyway, I would like to congratulate whoever is responsible for a slick, 
> clean new interface to the Wiki and I hope there may be more to come in 
> this vein.

Someone deeply familiar with this kind of IE CSS position:absolute 
problem should look at this. I searched the lists, but found nothing 
really appropriate. Maybe it must be rewritten or worked around with the 
dynamic isBrowserIE() function.

I had to change width to 30% instead of auto for IE, but the icon 
alignment is still broken.

That's why I put it onto http://phpwiki.sourceforge.net/demo/crao but 
cannot commit into CVS.
-- 
Reini Urban
http://phpwiki.sf.net/

Re: [Phpwiki-talk] very nice new theme but...

[Arnaud F. <ar...@cr...>]

Le mar 11/05/2004 =E0 20:06, Rob Fulwell a =E9crit :
> I really like the new Crao theme:
> http://phpwiki.sourceforge.net/demo/crao
>=20
> Too bad that slick docked buttonbar totally breaks on Internet Explorer=20
> (I took quick look with version 6).  I know this is due to IE not=20
> implementing (CSS?) properly but it still means I can't really use this=20
> theme on my site.

I know ... We are working to ... hmmm ... tune the css in order to make
this theme usable with the Internet Exploiter web crasher ..=20
But as we don't have any version of this gadget, it's hard to test ...
So if you have some bug report and screenshots, you can send them to me
(ar...@cr...) or to Laurent (la...@cr...).

> Anyway, I would like to congratulate whoever is responsible for a slick,=20
> clean new interface to the Wiki and I hope there may be more to come in=20
> this vein.

We'll see with Reini to include the http://igenerator.net/ and/or the
http://autrans.net/ theme to PhpWiki.

And as I'm working on some stuff to easily manage a wiki farm, I'm also
working on some easy ways to customize a wiki theme.
--=20
Arnaud Fontaine
ar...@cr...
ICQ: 82629567

[Phpwiki-talk] User authentication patch

[Dan F. <dfr...@cs...>]

I was having a problem. I have a Phpwiki 1.3.9+ site. It has a .htaccess 
file with a single username/password pair. The intent is that once you 
enter that site-wide user/pw, each editor then logs in with their own 
WikiWord to have the right tracking in the change logs. Only for some 
reason you had to log on for each page, hence over and over again. I 
found out why: the Apache-authenticated user was being taken before the 
login provided by the user in the Phpwiki "Sign in as:" window. This was 
wrong for me, I attach a patch below.

My index.php auth settings are:

        $USER_AUTH_ORDER =
            array(
                  "PersonalPage",
                  "Db",
                  ) ;

Perhaps my index.php authentication settings should be different, but it 
still seems to me the Phpwiki login should trump the .htaccess login .. 
hmm, maybe not always? Could I fake my way in with a trumped-up cookie?

Dan


diff -b -u -r1.3 main.php
--- main.php    14 Apr 2004 21:57:25 -0000      1.3
+++ main.php    11 May 2004 18:01:21 -0000
@@ -568,12 +568,15 @@
     }

     function _deduceUsername() {
+        // User login on the Wiki page.
+        //
+        // DSF: Overrides browser pop-up window, to allow the whole site to
+        // be behind browser authentication with one username/pw, then
+        // each page editor to have their own login.
+        //
+
         if (!empty($this->args['auth']) and 
!empty($this->args['auth']['userid']))
             return $this->args['auth']['userid'];
-        if (!empty($_SERVER['PHP_AUTH_USER']))
-            return $_SERVER['PHP_AUTH_USER'];
-        if (!empty($_ENV['REMOTE_USER']))
-            return $_ENV['REMOTE_USER'];

         if ($user = $this->getSessionVar('wiki_user')) {
             $this->_user = $user;
@@ -586,6 +589,14 @@
                 return $userid;
             }
         }
+
+        // User login through a browser pop-up window
+        if (!empty($_ENV['REMOTE_USER']))
+            return $_ENV['REMOTE_USER'];
+
+        if (!empty($_SERVER['PHP_AUTH_USER']))
+            return $_SERVER['PHP_AUTH_USER'];
+
         return false;
     }

[Phpwiki-talk] very nice new theme but...

[Rob F. <rfu...@dr...>]

I really like the new Crao theme:
http://phpwiki.sourceforge.net/demo/crao

Too bad that slick docked buttonbar totally breaks on Internet Explorer 
(I took quick look with version 6).  I know this is due to IE not 
implementing (CSS?) properly but it still means I can't really use this 
theme on my site.

Anyway, I would like to congratulate whoever is responsible for a slick, 
clean new interface to the Wiki and I hope there may be more to come in 
this vein.

Cheers,

Rob.

Re: [Phpwiki-talk] Re: Development on phpwiki

[Dan F. <dfr...@cs...>]

Reini Urban wrote:

> Dan Frankowski schrieb:
>
>> http://www.wikilens.org/index.php/RecommendersEverywhere
>> http://www.wikilens.org/index.php/WikiLens
>
>
> BTW: Do you have some kind of public or semi-public archive (ftp,cvs) 
> of the wikilens code?
>
> I saw at bimike.net that people already wrote a lot of new apps, and I 
> am very interested.


Cool! I set up a nightly script to make the latest publicly visible site 
available in a tarball at http://www.wikilens.org/wikilens-src.tgz.

> >> WikiLens and Presidents :: 2004-04-09 09:45:08
>
> And I want to see how the buddie feature developed in the meantime, to 
> make it eventually WikiUserNew independent. I.e. to provide some useful
> hooks in the core.


I agree it would be useful to think about the relationship between 
WikiUserNew and buddies (by the way, singular "buddy"). To integrate 
1.3.9 into our site, I ended up moving things around, and making a 
RatingsUser class that is pretty much independent. That is, it could be 
ripped out of WikiUserNew and put somewhere else, although that might 
cause a bunch of files to have to include that new place.

> Lately I added some kind of generic adodb/sql query function, mainly 
> for action=upgrade, but togther with your generic pageiterator this 
> might be something needed.


We don't have a very generic pageiterator yet. We are still working on 
integrating our newest preference apps with PageList. Right now, 
PreferenceApp (e.g., SodaApp, SoftwareProjectApp) is not based on PageList.

Dan

[Phpwiki-talk] Re: Development on phpwiki

[Reini U. <ru...@x-...>]

Dan Frankowski schrieb:
> http://www.wikilens.org/index.php/RecommendersEverywhere
> http://www.wikilens.org/index.php/WikiLens

BTW: Do you have some kind of public or semi-public archive (ftp,cvs) of 
the wikilens code?

I saw at bimike.net that people already wrote a lot of new apps, and I 
am very interested.

 >> WikiLens and Presidents :: 2004-04-09 09:45:08

And I want to see how the buddie feature developed in the meantime, to 
make it eventually WikiUserNew independent. I.e. to provide some useful
hooks in the core.
Lately I added some kind of generic adodb/sql query function, mainly for 
action=upgrade, but togther with your generic pageiterator this might be 
something needed.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

[Phpwiki-talk] Re: Development on phpwiki

[Reini U. <ru...@x-...>]

Dan Frankowski schrieb:
> I am going to devote more time to Phpwiki this summer. I may also get 
> two undergraduates working for 30 hours/week. I'd really like to push 
> forward recommenders everywhere and wikilens.org so it becomes very 
> cool. For me, recommenders everywhere only works if the features we're 
> excited about get into a widely available and well-known system. For a 
> refresher, see
> 
> http://www.wikilens.org/index.php/RecommendersEverywhere
> http://www.wikilens.org/index.php/WikiLens

I could add to this.

> Moreover, there are certain features we absolutely must have. These 
> include:
> 
> - Working and easy-to-use user/page permissions

my current top goal.

> - Sorting on the PageList widget 

sortby=rating? ok.

> - others will arise (e.g., things in PageList, making categories more 
>   "natively" supported in Phpwiki, etc.)

This is new to me. Can you describe this?
Do you mean dynamic categories? We had some kind of patch for this 
feature some years ago. page : category relation in the database.
Other wiki's tried that also.
We didn't like that. We thought that manual fixes (links at the bottom 
of each page) and backlinks are easier, just the engine should support 
the needed features people are proposing.

> I am happy to work on these things, but I hesitate because if you are 
> also working on them, my proposed changes may not be useful, hence that 
> is wasted work. On the other hand, if you don't believe in them (for the 
> sake of argument, making category pages special), they will never be 
> accepted.

I want to bring out a release today, so I will answer tommorrow.
There are still several known problems, and lot of tests to do.

> Thus, I would be interested in hearing more from you about how you think 
> of the Phpwiki development process. That is, what should I keep in mind 
> to make my work most likely to be accepted by the Phpwiki team? How can 
> I best help out the Phpwiki team, given my interests?
> 
> This sort of thing might include just plain knowing more about you or 
> other Phpwiki developers. Possible examples:
> 
> - How much time do you devote to it?

Currently full time. In the near future about 4 hrs a week. Not as less 
time as in the last two years for sure.

> - How long have you been around?

phpwiki development since my acadwiki, which started with 1.2 and then 
came jeffs 1.3.x tree.
for some early software development see my website.

> - What is the team style?
> - What development processes do you think work well?
> - Where could there be improvement?
> - How would you like to grow the Phpwiki development team so that it can 
>   make faster progress?
> 
> My boss said I should feel free to call long distance to talk about 
> these things, if you are willing. Give me a phone#, propose a time.

I'd rather prefer email or wiki discussion. I worked as teleworker for 
several US companies before and was never convinced in the usefulness of 
phone conversation.

> Some things I've noticed:
> - Phpwiki is downloaded often (~200 times a day).
> - You are the most active developer right now. Most other developers are 
> inactive, a couple (e.g., Joby) seem somewhat active.
> - You seem to be working on many things at once.
> - More documentation would be nice. The Phpwiki Phpwiki has a lot of 
> good stuff, and a lot of what might be old cruft.
> - People are asking for stability.
> - Phpwiki releases have some features which work well, and others which 
> are experimental or non-functional. The difference is not always obvious.
> - People are asking for features.
> - The email list phpwiki-talk is the best place to gather right now
> 
> I would be eager to help where I can. I am not entirely useful, though. 
> For example, unfortunately, I do not know the code or functionality as 
> well as you or other developers, so I cannot take over documentation.

At least you can start if you feel a urgent desire to so. We already 
discussed this. Others can fix wrong things then.

I have to stop now, because I have to prepare a radio show about the 
nature and importance of science, and several misleading paths in the past.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/