Re: Save error in DW

Tony Steward wrote:
> When I edit ena existing page I get the following error
>
> <error>
> Warning: Cannot modify header information - headers already sent by (output started at
/hsphere/local/home/steward/locks.stewardclan.net/lockswiki/lib/plugins/incl_form/syntax.php:153)
in /hsphere/local/home/steward/locks.stewardclan.net/lockswiki/inc/actions.php on line 296
> </error>
>   
Sometimes a php file will have extra linefeeds or spaces after the final 
?>   This results in the line-feeds being sent out as part of your page, 
in advance of the actual headers which the server needs to send.  
Looking at the incl_form wiki page, I see that you have to cut and past 
the code from the page.  Make sure that there are no line feeds after 
the final ?> of syntax.php and action.php.  Or you can omit the final ?> 
altogether.  

_____________________
Myron Turner
http://www.room535.org
http://www.bstatzero.org
http://www.mturner.org/XML_PullParser/

--

-- 
DokuWiki mailing list - more info at
http://wiki.splitbrain.org/wiki:mailinglist

Re: Save error in DW

On Jun 30, 2007, at 15:52, Tony Steward wrote:

> When I edit ena existing page I get the following error
>
> <error>
> Warning: Cannot modify header information - headers already sent by  
> (output started at /hsphere/local/home/steward/ 
> locks.stewardclan.net/lockswiki/lib/plugins/incl_form/syntax.php: 
> 153) in /hsphere/local/home/steward/locks.stewardclan.net/lockswiki/ 
> inc/actions.php on line 296
> </error>
>
> If I then select back on the browser and usually refresh as well I  
> am back to the editing page.
> Now i click save again and DW saya that a newer version of the page  
> I am working on exists so I click save anyway and all is well.
>
> I cant expect users of my site to do this.
>

If you take a moment to read that error, you will see that the issue  
originates in the "incl_form" plugin that you have installed. I  
suggest you contact the author of that plugin.

What this error means is that the "incl_form" plugin started  
outputting html too early -- before Dokuwiki expected expected  
anything to be sent to the browser. Even if it outputs a blank space  
before the PHP opening tag it will still cause this error.

darcs changes 2007-07-01

Good Morning!

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

---------------------------------------------------------------------
Sun Jul  1 01:00:01 CEST 2007  Andreas Gohr <andi[at]splitbrain.org>
  tagged develsnap 2007-07-01

Sat Jun 30 13:01:32 CEST 2007  Andreas Gohr <andi[at]splitbrain.org>
  * Slovak language updates
---------------------------------------------------------------------

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

Re: patch to configure location of acl.auth.php

Guy Brand wrote:
> On 29 June at 22:34, Grant Gardner wrote
>   
>>  I raised this as a feature request previously to allow the location of 
>>  acl.auth.php the be outside dokuwiki's conf area.
>>     
>
>   Why having only the acl file outside conf/ and not the whole conf/
>   outside the dokuwiki root? I think this has already been done (in
>   the Debian packaging world?).
>   
Thanks Guy, I had not considered this option and after a quick look 
around I think I understand how to do it (define DOKU_CONF externally or 
change init.php).

That said, I was considering that the acl information is directly 
associated with the pages,namespaces and users of the wiki data that 
change daily rather than config of the dokuwiki engine which changes 
only occasionally, and particularly with a new release. If I was using 
plain auth I'd probably want to give  auth.users.php the same treatment.

In my case your suggestion would work. Upgrading to a new release would 
be a bit more complex but I suppose that's what package maintainers are 
for...

Cheers,
    Grant.

--

-- 

Re: Save error in DW

That great thank you.
There were additional blank lines at the end of the syntax.php for
incl_forms causing the error.

-----Original Message-----
From: dokuwiki-bounce <at> freelists.org [mailto:dokuwiki-bounce <at> freelists.org]
On Behalf Of Ben Coburn
Sent: Sunday, 1 July 2007 10:10 AM
To: dokuwiki <at> freelists.org
Subject: [dokuwiki] Re: Save error in DW

On Jun 30, 2007, at 15:52, Tony Steward wrote:

> When I edit ena existing page I get the following error
>
> <error>
> Warning: Cannot modify header information - headers already sent by  
> (output started at /hsphere/local/home/steward/ 
> locks.stewardclan.net/lockswiki/lib/plugins/incl_form/syntax.php: 
> 153) in /hsphere/local/home/steward/locks.stewardclan.net/lockswiki/ 
> inc/actions.php on line 296
> </error>
>
> If I then select back on the browser and usually refresh as well I  
> am back to the editing page.
> Now i click save again and DW saya that a newer version of the page  
> I am working on exists so I click save anyway and all is well.
>
> I cant expect users of my site to do this.
>

Re: useslash and full path in links

Done:
http://bugs.splitbrain.org/index.php?do=details&task_id=1176

many thanks for the help

Oliver

Andreas Gohr wrote:
> That's correct. The slash should work as namespace separator when
> useslash is enabled. Please submit a bug report about the intial
> problem.
>
> Andi
>
>   

-- 
Oliver Schulze L.   | http://tinymailto.com/oliver  
Asuncion - Paraguay | http://www.solojuegos.mobi    

--

-- 
DokuWiki mailing list - more info at
http://wiki.splitbrain.org/wiki:mailinglist

Best practices of multiple documentation releases

Folks, we're using dokuwiki for managing all documentation of our
software project. It's getting pretty large and we need to have
multiple versions of this documentation - each version for one major
release.

We have the following schema of large releases: 2007.1, 2007.2, 2007.3
and so on. Once we make a release we copy the "trunk" directory of
documentation into new directory called after the release. Once copied
we apply simple perl one liner which fixes all links for all pages in
this directory.

Well it works but honestly I'm not sure how good this solution is.

The biggest issue is searching, some stuff is duplicated from release
to release and when someone finds duplicated entries there's no easy
way to say to which release this stuff actually belongs to without
proceeding the link.

Another issue is quite a dirty way of fixing links for each release
after copying it (some CLI script in bin directory, say, "dw.php"
could be very helpful, e.g:

$php dw.php move foo:bar zoo:foo
$php dw.php copy foo:bar zoo:foo

)

Hence the question, what do you think about it? Any tips, suggestions?
Maybe it makes sense to have a separate dokuwiki installation per
release? Thanks!

Re: Best practices of multiple documentation releases

breadcrumbs "crashes" dokuwiki?

Greetings.

Just installed dokuwiki 2007-06-26 in HPUX11i+Apache 2.0.52+PHP 4.3.8
but I can't use it. After installation, the doku.php start page is
rendered only until the breadcrumbs and it stops at "Trace:" (no
footer tool/buttonbar and images).

Pressing "Create this page" only changes this button to "Show  page".
The breadcrumbs remain as before and no footer.

This is a public wiki (ACL disabled) and chmod -R 777 for dokuwiki
folder; I'm running httpd with the user owning the dokuwiki files.

The results of "?do=check" are (if I enable ACL, "?do=check" doesn't work) :

<do=check>
DokuWiki version: Release 2007-06-26
Consider upgrading PHP to 4.3.10 or higher for security reasons (your
version: 4.3.8)
Datadir is writable
Attic is writable
Mediadir is writable
Cachedir is writable
Lockdir is writable
conf/users.auth.php is not writable
mb_string extension not available - PHP only replacements will be used
Debugging support is enabled. If you don't need it you should set
$conf['allowdebug'] = 0
You are currently not logged in
Your current permission for this page is 8
The current page is not writable by the webserver
The current page is writable by you
</do=check>

I've previously installed this same dokuwiki version in CentOS in 5
minutes and it's fully working
(http://xserver.kicks-ass.org/dokuwiki/doku.php) ... this is driving
me mad!:D How can I debug this PHP code and find out where this is
going wrong?

I've also manually added a couple of "start.txt" but can't see them in
dokuwiki. My current pages filestructure :

.
./wiki
./wiki/dokuwiki.txt
./wiki/syntax.txt
./playground
./playground/playground.txt
./start.txt
./lagois
./lagois/start.txt

Any tips on how can I proceed? Meanwhile, I'll be trying to install
dokuwiki on Windows!;)
Regards,
-- 
Luís Góis
--

-- 
DokuWiki mailing list - more info at
http://wiki.splitbrain.org/wiki:mailinglist

Re: breadcrumbs "crashes" dokuwiki?

Luís Gois wrote:
> Greetings.
>
> Just installed dokuwiki 2007-06-26 in HPUX11i+Apache 2.0.52+PHP 4.3.8
> but I can't use it. After installation, the doku.php start page is
> rendered only until the breadcrumbs and it stops at "Trace:" (no
> footer tool/buttonbar and images).
You might start by putting the following in local.php:
$conf['breadcrumbs'] = 0;
This will turn off breadcrumbs and let you see if it is in fact the 
breadcrumbs that are causing the problem.

-- 

_____________________
Myron Turner
http://www.room535.org
http://www.bstatzero.org
http://www.mturner.org/XML_PullParser/

--

-- 
DokuWiki mailing list - more info at
http://wiki.splitbrain.org/wiki:mailinglist