Re: [Phpwiki-talk] PHPwiki newbie questions/suggestions

[Carsten K. <car...@ya...>]

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).