headers
Andreas Gohr | 1 Aug 04:00
Favicon
Gravatar

darcs changes 2007-08-01


Good Morning!

This are the darcs changes for DokuWiki committed
yesterday. Please test them and report bugs.

---------------------------------------------------------------------
Wed Aug  1 01:00:01 CEST 2007  Andreas Gohr <andi[at]splitbrain.org>
  tagged develsnap 2007-08-01
---------------------------------------------------------------------

Single patches can be downloaded from
http://dev.splitbrain.org/darcs/index.cgi/dokuwiki/?c=patches

Bye,
your darcs changelog mailer

--

-- 
DokuWiki mailing list - more info at
http://wiki.splitbrain.org/wiki:mailinglist
Permalink | Reply | 0 comments |
headers
Jason Keltz | 1 Aug 21:51
Picon

dokuwiki questions - authentication and external url

Two questions..

I have written a custom authentication module for DokuWiki for our 
custom user back-end.  I would like to install a separate forum package 
(phpbb/phorum I guess) and link to that site from the DokuWiki install.

Two questions:

1) Now that I have done the work of authenticating our users to 
DokuWiki, is there any way that I can share that authentication 
information with the forum system without having the user re-login?

2) I see a few plugins for DokuWiki re: external urls, but I don't think 
I see anything that just opens up the link in a new web browser window. 
  Does that functionality exist in DokuWiki or in a separate plugin?  It 
would sure be nice if I could use syntax built into DokuWiki to do it.. 
I can imagine say, prepending a ^ to a URL to make it open up in a new 
window.

3) Although this definately isn't a topic for this list, anyone have any 
recommendation for a simple forum package? Discussion dokuwiki plugin 
isn't really enough for our purposes, but I don't really need anything 
overly complicated either.  Many of our users are just using 
google/yahoo groups.  You should probably just reply directly to me with 
the answer to this question because I don't want to make anyone on the 
list unhappy with un-Dokuwiki-related questions.

Thanks everyone..

Jason.
(Continue reading)

Permalink | Reply | 2 comments |
headers
Jason Keltz | 2 Aug 05:16
Picon

useheading question

Hi everyone,

I use the "useheading" configuation option which allows a link to be 
represented by the first H1 on the page.  I am putting a bunch of DokuWiki 
sites together and am propagating each fresh site with a bunch of 
pre-loaded namespace directories and wiki pages in the data dir, but 
without preloading any of the other directories with data.  I use the 
hierarchical breadcrumbs.  I find that each time I copy the pages to a new 
site, the first time that I visit each page, the breadcrumb bar shows the 
name of the link, as if the useheading option is off.  If I reload, the 
proper name shows up in the breadcrumb bar, and if I visit the site again, 
it seems okay.  What other information do I need to keep to ensure that 
the breadcrumbs use the H1 the first time around?

Jason.
--

-- 
DokuWiki mailing list - more info at
http://wiki.splitbrain.org/wiki:mailinglist
Permalink | Reply | 17 comments |
headers
Chuck Soper | 2 Aug 09:13

making DokuWiki secure on a shared web host

Hello,

I'm about to install DokuWiki on a shared web host. I need prevent 
internet users in general and other users at my web host from viewing 
or modifying any part of the wiki. I'm using the wiki create 
collaborative product spec. I'm looking forward to having this 
on-linie soon.

I have a SSL certificate and plan to force https at login. I have 
reviewed the following pages:
  http://wiki.splitbrain.org/wiki:acl
  http://wiki.splitbrain.org/wiki:auth:backends
  http://wiki.splitbrain.org/wiki:install:permissions
  http://wiki.splitbrain.org/wiki:security
  http://wiki.splitbrain.org/wiki:discussion:security

Is the "wiki:security" page up to date?
What is the best way to ensure that my docuwiki is secure and protected?
Unfortunately, I'm not a PHP developer. Will I need a PHP developer 
to set up dokuwiki to be secure?

Is this email list the best place to ask questions or is the forum 
at forum.dokuwiki.org a better place?

Thanks,
Chuck
--

-- 
DokuWiki mailing list - more info at
http://wiki.splitbrain.org/wiki:mailinglist
(Continue reading)

Permalink | Reply | 7 comments |
headers
Andreas Gohr | 2 Aug 09:30
Favicon
Gravatar

Re: making DokuWiki secure on a shared web host

Chuck Soper writes:

> Is the "wiki:security" page up to date?

Yes, however keep in mind that most things there are recommended precautions 
but not strictly neccessary.

> What is the best way to ensure that my docuwiki is secure and protected?

Set up an restrictive ACL and make sure file permissions are set to a bare 
minimal needed value. The latter might be difficult for you to do on a 
shared host, depending on how the Webserver/PHP was setup. See 
http://wiki.splitbrain.org/wiki:install:permissions for details.

> Unfortunately, I'm not a PHP developer. Will I need a PHP developer 
> to set up dokuwiki to be secure?

No! Of course not.

> Is this email list the best place to ask questions or is the forum 
> at forum.dokuwiki.org a better place?

Both is fine.

Andi

--

-- 
DokuWiki mailing list - more info at
http://wiki.splitbrain.org/wiki:mailinglist
(Continue reading)

Permalink | Reply | 6 comments |
headers
Gabriel Birke | 2 Aug 09:42
Favicon

Re: dokuwiki questions - authentication and external url

Hello, 

> 1) Now that I have done the work of authenticating our users to 
> DokuWiki, is there any way that I can share that authentication 
> information with the forum system without having the user re-login?

It is possible, but will require some work on the forum software: If the
authentication and user administration is pluggable like it is for DokuWiki,
then it will be easy to write your own adapter. Otherwise you have to "hack
the core" of the forum software to
a) synchronize the user info for the forum users with your other user
database
b) set the "login"-Status in the session. For this you have to figure out
(for the forum software) the name of the session cookie and what the session
of a logged in user contains.

> 2) I see a few plugins for DokuWiki re: external urls, but I  don't think 
> I see anything that just opens up the link in a new web 
> browser window. 
>   Does that functionality exist in DokuWiki or in a separate plugin?  It 
> would sure be nice if I could use syntax built into DokuWiki to do it.. 
> I can imagine say, prepending a ^ to a URL to make it open up in a new
window.

If you want _all_ external URLs to open in a new window, just set the
external link target in you Wiki configuration page ("Link Configuration")
to "_blank".

Greetings,
(Continue reading)

Permalink | Reply | 1 comment |
headers
Chris Smith | 2 Aug 10:32
Picon

Re: useheading question

Jason Keltz wrote:
> Hi everyone,
>
> I use the "useheading" configuation option which allows a link to be 
> represented by the first H1 on the page.  I am putting a bunch of 
> DokuWiki sites together and am propagating each fresh site with a 
> bunch of pre-loaded namespace directories and wiki pages in the data 
> dir, but without preloading any of the other directories with data.  I 
> use the hierarchical breadcrumbs.  I find that each time I copy the 
> pages to a new site, the first time that I visit each page, the 
> breadcrumb bar shows the name of the link, as if the useheading option 
> is off.  If I reload, the proper name shows up in the breadcrumb bar, 
> and if I visit the site again, it seems okay.  What other information 
> do I need to keep to ensure that the breadcrumbs use the H1 the first 
> time around?
>
> Jason.

What version of DW are you using?

Older versions of DW will only have headings for pages that have been 
parsed and had their "instructions" cached. These are the ".i" files in 
the cache.

The most recent version picks up heading information from metadata.  It 
should be able to generate fresh metadata for any page without it and so 
display all the required headings.  Copying metadata along with the 
pages will reduce the load on your server.

Chris
(Continue reading)

Permalink | Reply | 9 comments |
headers
Luke Howson | 2 Aug 11:19

Re: making DokuWiki secure on a shared web host

Andreas Gohr wrote:
> Chuck Soper writes:
>
>> Is the "wiki:security" page up to date?
>
> Yes, however keep in mind that most things there are recommended
> precautions but not strictly neccessary.
>
>> What is the best way to ensure that my docuwiki is secure and protected?
>
> Set up an restrictive ACL and make sure file permissions are set to a
> bare minimal needed value. The latter might be difficult for you to do
> on a shared host, depending on how the Webserver/PHP was setup. See
> http://wiki.splitbrain.org/wiki:install:permissions for details.

Chuck wants his wiki protected from "other users at my web host from
viewing or modifying any part of the wiki". I don't have much experience
with secured shared web hosting, but on a plain vanilla linux, my
understanding is that you usually have php run in the process space of
apache (and hence shares the security context it is run with.) If you
just have a bunch of virtual hosts setup, they will all run under the
same context, so all PHP scripts can access precisely the same files.

I am ignorant of how shared web hosting works in practice, but what you
need to do is somehow tie different uids to different apache processes.
This *would* be done using the |perchild module, adding the AssignUserID
directive in the virtual host section, and the || ChildPerUserID in the
global section of the apache conf file. I say "would" because the
perchild mod does not work yet.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Andreas Gohr | 2 Aug 11:27
Favicon
Gravatar

Re: making DokuWiki secure on a shared web host

Luke Howson writes:

>>> What is the best way to ensure that my docuwiki is secure and protected?
>>
>> Set up an restrictive ACL and make sure file permissions are set to a
>> bare minimal needed value. The latter might be difficult for you to do
>> on a shared host, depending on how the Webserver/PHP was setup. See
>> http://wiki.splitbrain.org/wiki:install:permissions for details.
> 
> Chuck wants his wiki protected from "other users at my web host from
> viewing or modifying any part of the wiki". I don't have much experience
> with secured shared web hosting, but on a plain vanilla linux, my
> understanding is that you usually have php run in the process space of
> apache (and hence shares the security context it is run with.) If you
> just have a bunch of virtual hosts setup, they will all run under the
> same context, so all PHP scripts can access precisely the same files.

Which is described at the mentioned page. However there are several ways to 
have different uids for different vrtual hosts, like FastCGI or suPHP and 
many of the better hosters use one of those methods. Which is what I was 
refering to with "depending on how the Webserver/PHP was setup".

Andi
--

-- 
DokuWiki mailing list - more info at
http://wiki.splitbrain.org/wiki:mailinglist
Permalink | Reply | 0 comments |
headers
Simon Heimlicher | 2 Aug 17:15
Picon
Picon

Re: Core Features vs Plugins

Hi,

Wes wrote:
> Seriously. The extra languages should be plugins, not core features.
How about a "Language Manager" that works just like the plugin-manager?

DokuWiki could be delivered with just the English language pack, but the 
other language packs might be "pre-set" in the Language Manager such 
that the URL to fetch them is already stored and the installation just a 
matter of one click.

If a new language pack were created, the admin would then be able to 
download it by entering its URL, just like with a plugin.

Cheers,
Simon

-- 
Simon Heimlicher
Communication Systems Research Group, ETH Zurich
Web: http://www.csg.ethz.ch/people/simonh
Office: ETZ G 60.1, Gloriastrasse 35, 8092 Zurich
Phone: +41 44 632 7022  Fax: +41 44 632 1035
--

-- 
DokuWiki mailing list - more info at
http://wiki.splitbrain.org/wiki:mailinglist
Permalink | Reply | 1 comment |

Gmane