Menu
▾
▴
phpwiki-talk
|
From: <art...@vo...> - 2002-11-11 13:16:02
|
Hi,
I now have a working PHPwiki. I've read all the released docs, but I still have
some questions/suggestions/problems.
I use PHPwiki for my personal use. The Web server is Apache and my site is
protected by HTTP auth (and SSL). I use the latest PHPwiki from cvs, as it's a
long time since the latest release.
1) Questions
- I'd like PHPwiki to automatically sign me in with my HTTP auth login.
I tried setting ALLOW_HTTP_AUTH_LOGIN to true but it didn't work.
Maybe it's because my login name is not a WikiWord ?
- Does the WikiFormPlugin exist ? It would be great to include forms to search
Google, etc. in wiki pages.
- Where can I enable/disable LinkIcons ?
- Where can I find a good doc about themes ? I'd like to create my own theme
but I can't find any doc, I have to look at the other themes.
2) Suggestions
Please excuse me if some features are already implemented, I didn't find them.
- Login names should not have to be WikiWords. A WikiWord could be associated
with a login name when creating a homepage. That is:
- get the login from the Web server and use it for authoring
(eg: page modified by <login> from <hostname>)
- in the UserPreferences page, let the user create/remove his homepage and
supply/modify a WikiWord identifying that page
- UserPreferences should be saved in the database or in a flat file,
so that the user could keep its preferences when using different computers
- There should be a "Rename" and a "Remove" button with the "Edit" button
for each page. An index.php option could tell PHPwiki to
- ask the user to confirm and perform the operation (for private wikis)
- send a mail to the administrator for confirmation (for public wikis)
- History and Diffs could be merged and improved. What about this:
- use a unique History button (no more Diffs button)
- in the History page, show all revisions
- let the user select two revisions and then see the diffs
- put a "Revert" button after each revision to immediately revert to it
(without having to see it, edit it and save it)
- A SiteMap plugin would be helpful for large wikis.
- It would be great to be able to organize some pages in a hierarchical manner
(=E0 la Yahoo) and then move them in the hierarchy and create links between
directories. All the pages should not have to be placed in the hierarchy.
- With the current PHPwiki, there's no topic separation: if you want to have
one wiki per topic, you need to install one PHPwiki for each topic.
Being able to manage multiple wikis (topics) with one PHPwiki installation
would be great.
- I like to start with an empty wiki. PHPwiki should have an "empty wiki" admin
button, or if topics are implemented, they should start empty (with a form
asking for the first WikiWord).
3) Problems
- My index.php contains "define('ENABLE_REVERSE_DNS', true);" but I only get IP
addresses even if a reverse DNS exists.
- I had to comment "ob_start('ob_gzhandler');" in lib/Request.php to make
PHPwiki work with Galeon (see previous post).
------------------------------------------
Faites un voeu et puis Voila ! www.voila.fr
|
|
From: Carsten K. <car...@ya...> - 2002-11-11 15:07:10
|
Hi,
(I see you are running Galeon, you can ignore my previous message.) I=20
have a feeling Galeon will have to be updated or some setting changed=20
in it to overcome the gzip problem. Maybe PhpWiki can be modified check=20=
for Galeon then not enable compression?
I can answer some of your questions, I'll leave the rest for others to=20=
respond:
- A new plugin called "ExternalSearch" is available to create forms for=20=
redirecting to external web sites.
- There is really no documentation for themes yet aside from the=20
comments inside the themeinfo.php file, so the following might help:
LinkIcons are set in themeinfo.php. Just comment them out to disable=20
linkicons:
/*
* Link icons.
*/
//$Theme->setLinkIcon('http');
etc.
To create your own theme, duplicate the folder which most closely=20
resembles the layout you want to modify.
- For example, copy the "Portland" directory to "Arthur" then modify=20=
the themeinfo.php file and other files inside.
- Set your theme in index.php: if (!defined('THEME')) define('THEME',=20=
'Arthur');
- When PhpWiki does not find a file in your theme it then looks for it=20=
in "default", but don't change any files in the default theme. Copy=20
"login.tmpl" (or whatever) from "default" into your theme then make=20
your changes there.
Use this method to override the default theme rather than editing=20
"default" directly. If you change your mind you can easily delete a=20
file from your theme and everything will still work without any need to=20=
reinstall.
Regarding some of your other suggestions:
The History screen now does allow you to select two revisions for=20
comparison, you can remove the Diff link/button from the theme template=20=
if you're happy using only a History link.
Multiple Wikis are possible but I can't remember how to do it, I think=20=
the instructions are written somewhere in <http://phpwiki.sf.net>.=20
Basically it involves duplicating only index.php but not the whole=20
phpwiki.
An empty wiki can be started by renaming or moving the pgsrc directory=20=
(and locale pgsrc directory if not using english), but you must create=20=
HomePage before moving the directories back. An easier way to do this=20
might be nice to have for those experienced Wiki admins who don't want=20=
all the PhpWiki documentation inside their personal wiki.
Carsten
On Monday, November 11, 2002, at 08:15 AM, arthur.chereau wrote:
> Hi,
>
> I now have a working PHPwiki. I've read all the released docs, but I=20=
> still have
> some questions/suggestions/problems.
>
> I use PHPwiki for my personal use. The Web server is Apache and my=20
> site is
> protected by HTTP auth (and SSL). I use the latest PHPwiki from cvs,=20=
> as it's a
> long time since the latest release.
>
>
> 1) Questions
>
> - I'd like PHPwiki to automatically sign me in with my HTTP auth =
login.
> I tried setting ALLOW_HTTP_AUTH_LOGIN to true but it didn't work.
> Maybe it's because my login name is not a WikiWord ?
>
> - Does the WikiFormPlugin exist ? It would be great to include forms=20=
> to search
> Google, etc. in wiki pages.
>
> - Where can I enable/disable LinkIcons ?
>
> - Where can I find a good doc about themes ? I'd like to create my own=20=
> theme
> but I can't find any doc, I have to look at the other themes.
>
>
> 2) Suggestions
>
> Please excuse me if some features are already implemented, I didn't=20
> find them.
>
> - Login names should not have to be WikiWords. A WikiWord could be=20
> associated
> with a login name when creating a homepage. That is:
> - get the login from the Web server and use it for authoring
> (eg: page modified by <login> from <hostname>)
> - in the UserPreferences page, let the user create/remove his=20
> homepage and
> supply/modify a WikiWord identifying that page
>
> - UserPreferences should be saved in the database or in a flat file,
> so that the user could keep its preferences when using different=20
> computers
>
> - There should be a "Rename" and a "Remove" button with the "Edit"=20
> button
> for each page. An index.php option could tell PHPwiki to
> - ask the user to confirm and perform the operation (for private=20
> wikis)
> - send a mail to the administrator for confirmation (for public=20
> wikis)
>
> - History and Diffs could be merged and improved. What about this:
> - use a unique History button (no more Diffs button)
> - in the History page, show all revisions
> - let the user select two revisions and then see the diffs
> - put a "Revert" button after each revision to immediately revert to=20=
> it
> (without having to see it, edit it and save it)
>
> - A SiteMap plugin would be helpful for large wikis.
>
> - It would be great to be able to organize some pages in a=20
> hierarchical manner
> (=E0 la Yahoo) and then move them in the hierarchy and create links=20=
> between
> directories. All the pages should not have to be placed in the=20
> hierarchy.
>
> - With the current PHPwiki, there's no topic separation: if you want=20=
> to have
> one wiki per topic, you need to install one PHPwiki for each topic.
> Being able to manage multiple wikis (topics) with one PHPwiki=20
> installation
> would be great.
>
> - I like to start with an empty wiki. PHPwiki should have an "empty=20
> wiki" admin
> button, or if topics are implemented, they should start empty (with=20=
> a form
> asking for the first WikiWord).
>
>
> 3) Problems
>
> - My index.php contains "define('ENABLE_REVERSE_DNS', true);" but I=20
> only get IP
> addresses even if a reverse DNS exists.
>
> - I had to comment "ob_start('ob_gzhandler');" in lib/Request.php to=20=
> make
> PHPwiki work with Galeon (see previous post).
|
|
From: Jeff D. <da...@da...> - 2002-11-11 17:41:24
|
Thanks for all the suggestions!
> - Where can I find a good doc about themes ? I'd like to create my own
> theme
> but I can't find any doc, I have to look at the other themes.
There is none. If someone want to write some that would be great.
Otherwise the only hint is "Use the source, Luke!", and ask here
if you get stuck.
> - Login names should not have to be WikiWords.=20
Yes. That requirement is/should be just for bogo-logins,
I think.
The user authentication code is currently under development
(by Reini Urban). I think it's currently somewhat broken
--- but I haven't played with it much, so I could be wrong.
> - UserPreferences should be saved in the database or in a flat file,
> so that the user could keep its preferences when using different
> computers
Yes, that's the plan. See above.
> - There should be a "Rename" and a "Remove" button with the "Edit"
> button
> for each page.
"Rename" functionality is tricky (have to rename all the links in
all pages). "Remove" functionality is there, but the remove button
only shows up if you have permission to use it (currently that means
it only shows up if you're logged in as the admin user.)
> - ask the user to confirm and perform the operation (for private
> wikis)
Note that if you delete all text from a page (via the edit form), it acts
(for the most part) as if the page were deleted. (Links to the page wil=
l
have the question mark.)
I've always planned (though it's not implemented yet) to have a mechanism
whereby empty/deleted pages which have been empty for N days get
automatically
fully deleted.
(More traditional wiki methods of handling messages to the admin is
a RequestForPageDeletion page or some such, or a DeleteMe tag on the
page.)
> - History and Diffs could be merged and improved. What about this:
> - use a unique History button (no more Diffs button)
> - in the History page, show all revisions
> - let the user select two revisions and then see the diffs
We have this, right?
> - put a "Revert" button after each revision to immediately revert to
> it
> (without having to see it, edit it and save it)
I think that would make it too easy for vandals (or edit wars).
("Revert"ion shouldn't, I think, be a very frequent operation.)
> - It would be great to be able to organize some pages in a hierarchical
> manner
> (=E0 la Yahoo) and then move them in the hierarchy and create links
> between directories. All the pages should not have to be placed in th=
e
> hierarchy.
The wiki solution to this is to use Category tags.
Personally, before adding mechanisms to make this more explicit
I'd rather add mechanisms to enable "book-style" hierarchies
of pages (parent/ordered-sibling relationships)
("Up", "Next", "Prev").
It's not clear to me how to do either of these cleanly.
> - With the current PHPwiki, there's no topic separation: if you want to
> have
> one wiki per topic, you need to install one PHPwiki for each topic.
> Being able to manage multiple wikis (topics) with one PHPwiki
> installation would be great.
You only have to replicate the config file (currently index.php), and
the page database. You can, of course, share the rest of the PhpWiki
source between multiple distinct wikis (on the same server).
There's information on this on the FrequentlyAskedQuestions
and PrettyWiki pages of the PhpWiki wiki.
> - I like to start with an empty wiki. PHPwiki should have an "empty
> wiki" admin
> button, or if topics are implemented, they should start empty (with a
> form asking for the first WikiWord).
You can, of course, adjust the definition of WIKI_PGSRC (or delete all
but the HomePage from the pgsrc directory) before firing up PhpWiki the
first time...
> - My index.php contains "define('ENABLE_REVERSE_DNS', true);" but I onl=
y
> get IP
> addresses even if a reverse DNS exists.=20
Currently the ENABLE_REVERSE_DNS only affects the output in the=20
PhpWiki generated access_log (which is only generated if ACCESS_LOG
is defined in the config file.)
|
|
From: Reini U. <ru...@x-...> - 2002-11-11 18:08:46
|
arthur.chereau schrieb:
> Hi,
>
> I now have a working PHPwiki. I've read all the released docs, but I still have
> some questions/suggestions/problems.
>
> I use PHPwiki for my personal use. The Web server is Apache and my site is
> protected by HTTP auth (and SSL). I use the latest PHPwiki from cvs, as it's a
> long time since the latest release.
>
> 1) Questions
>
> - I'd like PHPwiki to automatically sign me in with my HTTP auth login.
> I tried setting ALLOW_HTTP_AUTH_LOGIN to true but it didn't work.
> Maybe it's because my login name is not a WikiWord ?
try to unset ALLOW_BOGO_LOGIN also
theoretically it should work:
// HTTP Authentification
elseif (ALLOW_HTTP_AUTH_LOGIN and !empty($PHP_AUTH_USER)) {
// if he ignored the password field, because he is already
authentificated
// try the previously given password.
if (empty($passwd)) $passwd = $PHP_AUTH_PW;
}
maybe $PHP_AUTH_PW is not global. I'll check this.
> - Does the WikiFormPlugin exist ? It would be great to include forms to search
> Google, etc. in wiki pages.
yes. but WikiForm is only for internal administrative purposes.
We had some phpwiki: syntax before for these types of forms.
> - Where can I find a good doc about themes ? I'd like to create my own theme
> but I can't find any doc, I have to look at the other themes.
I started to fix the old themes docs.
See themes/default/templates/README.
The template API has completely changed with 1.3.3.
Templates may be nested. Usage sample: <?= Template('browse') ?>
See lib/Template.php for more, esp. the defined global php variables.
($request, $user, $page, $Theme and some action specific local vars.)
There's no ###<variable>### markup anymore, instead normal php
variables, constants and code can be used.
> 2) Suggestions
>
> Please excuse me if some features are already implemented, I didn't find them.
>
> - Login names should not have to be WikiWords. A WikiWord could be associated
> with a login name when creating a homepage. That is:
> - get the login from the Web server and use it for authoring
> (eg: page modified by <login> from <hostname>)
ALLOW_HTTP_AUTH_LOGIN or ExtAuth is for this.
unset ALLOW_BOGO_LOGIN and set ALLOW_USER_LOGIN.
> - in the UserPreferences page, let the user create/remove his homepage and
> supply/modify a WikiWord identifying that page
I will finish this if I get some air in my current work.
> - UserPreferences should be saved in the database or in a flat file,
> so that the user could keep its preferences when using different computers
UserPreferences are stored in his homepage (if exists), in a seperate
database (if defined), or in a cookie.
> - There should be a "Rename" and a "Remove" button with the "Edit" button
> for each page. An index.php option could tell PHPwiki to
> - ask the user to confirm and perform the operation (for private wikis)
> - send a mail to the administrator for confirmation (for public wikis)
Only the admin may do this. With PagePermissions (later this year) the
PageOwner or WikiAdmin may do this or may give others extended rights.
> - History and Diffs could be merged and improved. What about this:
> - use a unique History button (no more Diffs button)
> - in the History page, show all revisions
> - let the user select two revisions and then see the diffs
> - put a "Revert" button after each revision to immediately revert to it
> (without having to see it, edit it and save it)
good idea.
> - A SiteMap plugin would be helpful for large wikis.
Already in CVS. We just have to use bread-first search instead of the
current depth-first search and cut off the first page.
http://phpwiki.sourceforge.net/demo/en/SiteMap
> - It would be great to be able to organize some pages in a hierarchical manner
> (à la Yahoo) and then move them in the hierarchy and create links between
> directories. All the pages should not have to be placed in the hierarchy.
see http://phpwiki.sourceforge.net/phpwiki/SubPages
or http://phpwiki.sourceforge.net/phpwiki/PageGroup
> - With the current PHPwiki, there's no topic separation: if you want to have
> one wiki per topic, you need to install one PHPwiki for each topic.
> Being able to manage multiple wikis (topics) with one PHPwiki installation
> would be great.
see SubPages or http://phpwiki.sourceforge.net/phpwiki/WikiFarm
> - I like to start with an empty wiki. PHPwiki should have an "empty wiki" admin
> button, or if topics are implemented, they should start empty (with a form
> asking for the first WikiWord).
see http://phpwiki.sourceforge.net/demo/en/WikiAdminRemove
(when it is fixed)
> 3) Problems
>
> - My index.php contains "define('ENABLE_REVERSE_DNS', true);" but I only get IP
> addresses even if a reverse DNS exists.
strange. is there a nameserver in your /etc/resolv.conf?
> - I had to comment "ob_start('ob_gzhandler');" in lib/Request.php to make
> PHPwiki work with Galeon (see previous post).
thanks.
--
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/
|
|
From: Russ M. <rm...@no...> - 2002-11-11 20:42:46
|
> > - With the current PHPwiki, there's no topic separation: if you want to have > > one wiki per topic, you need to install one PHPwiki for each topic. > > Being able to manage multiple wikis (topics) with one PHPwiki installation > > would be great. > > see SubPages or http://phpwiki.sourceforge.net/phpwiki/WikiFarm Any idea how user permissions will work across multiple wikis? russ |
|
From: Reini U. <ru...@x-...> - 2002-11-12 16:06:31
|
Russ Miller schrieb: >>see SubPages or http://phpwiki.sourceforge.net/phpwiki/WikiFarm > > Any idea how user permissions will work across multiple wikis? A WikiFarm may share config variables, but not the page database. So you have to setup an external user/group database table to share the users and groups. But the page permissions are completely seperate. I don't think that SubPages should inherit some permissions unlike a unix fs. The "x" in the permission bit would be for administrative tasks like remove/rename/ and some other "ActionPlugins". (e.g. EmailNotify, WikiAdmin*). -- Reini Urban http://xarch.tu-graz.ac.at/home/rurban/ |
|
From: Russ M. <rm...@no...> - 2002-11-12 19:17:02
|
From: "Reini Urban" <ru...@x-...> > A WikiFarm may share config variables, but not the page database. > So you have to setup an external user/group database table to share the > users and groups. But the page permissions are completely seperate. Generally, I like all the thinking going on for permissions. In the WikiFarm instance, it might be nice if there were a convenient way to map different wikis to permission groups. Another thought I had for the WikiFarm -- it might be nice if different wikis could live separately, but in the same actual database. Commercial providers often only give you one db (in my case, one MySQL db) for a certain pricing point... maybe there could be a hack to give each separate wiki a prefix for table names? Does that seem reasonable? When I get around to my implementation (heh), I'd be happy to submit a patch to do so. russ |
|
From: Jeff D. <da...@da...> - 2002-11-12 19:29:09
|
On Tue, 12 Nov 2002 14:17:00 -0500 "Russ Miller" <rm...@no...> wrote: > maybe there could be a hack to give each separate > wiki a prefix for table names? Does that seem reasonable? PhpWiki can already do this (via $DBParams['prefix'] in the config file). The only minor catch is that you have to manually edit the table prefixes in the appropriate schemas/*.sql. |
|
From: Reini U. <ru...@x-...> - 2002-11-18 16:40:23
|
Russ Miller schrieb: > From: "Reini Urban" <ru...@x-...> > >>A WikiFarm may share config variables, but not the page database. >>So you have to setup an external user/group database table to share the >>users and groups. But the page permissions are completely seperate. > > > Generally, I like all the thinking going on for permissions. In the WikiFarm > instance, it might be nice if there were a convenient way to map different > wikis to permission groups. > > Another thought I had for the WikiFarm -- it might be nice if different > wikis could live separately, but in the same actual database. Commercial > providers often only give you one db (in my case, one MySQL db) for a > certain pricing point... maybe there could be a hack to give each separate > wiki a prefix for table names? Does that seem reasonable? When I get around > to my implementation (heh), I'd be happy to submit a patch to do so. ISP's generally charge for a single Mysql DB Namespace (like "username_%") and not for a single database. In that namespace you should have the CREATE permission. So you may create the databases "username_wiki1", "username_wiki2", ... Otherwise you will have to change the $DBParams['prefix']. -- Reini Urban http://xarch.tu-graz.ac.at/home/rurban/ |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X